FamilyGuard is being built around a local-first model for protection and a minimal-data approach for cloud features. This notice explains what data we expect to collect, what stays in your home, and how community and AI-assisted features are intended to work.
FamilyGuard is intended to provide parental controls, network-level blocking, access-request workflows, and optional premium guidance for website approval decisions. The design goal is to keep sensitive household activity local wherever practical and to use cloud services only where they provide clear value, such as account management, subscriptions, and anonymised recommendation signals.
In plain English: our product direction is guidance, not surveillance. We want parents to understand what is happening on their network without forcing families to hand over more data than is necessary.
If you join the FamilyGuard waitlist on the website, we collect the email address you submit and use it to:
We do not intend to use waitlist email addresses for unrelated marketing campaigns. If that changes, this notice should be updated first and the signup flow should make that clear.
FamilyGuard is designed so core network protection takes place on the FamilyGuard device in the home. Subject to final implementation, the following categories are intended to stay local by default:
Visited sites, blocked requests, request history, and device-level activity logs are intended to remain on the FamilyGuard device unless a parent explicitly chooses a connected feature that requires cloud transmission.
DNS filtering, firewall enforcement, bedtime schedules, device grouping, and similar network controls are intended to operate locally so protection can continue even if connected services are unavailable.
This local-first approach matters because family internet activity can be sensitive. Our intention is that the FamilyGuard service should not need a complete remote copy of household browsing behaviour in order to be useful.
One of FamilyGuard's premium features is intended to show parents how similar parents responded to requests for specific websites or categories. To support that, FamilyGuard may collect anonymous or aggregated decision signals such as:
FamilyGuard is not intended to contribute named children, household identities, device nicknames, full browsing histories, or raw event timelines to the community recommendation dataset.
FamilyGuard may use AI-assisted systems to help explain what a website is, what it is commonly used for, and what parents may want to consider before approving access. Our intended use of AI is advisory, not autonomous.
That means:
Where possible, AI inputs should be limited to the site or request context needed to produce the explanation. FamilyGuard should avoid sending complete household browsing histories to AI systems where a smaller data scope is sufficient.
The FamilyGuard website and connected services may collect routine technical information such as IP address, browser type, device type, and server logs to keep the service secure, diagnose issues, and understand product performance at a high level.
If analytics or monitoring tools are added before launch, this notice should be updated to name them clearly and explain what they collect and why.
FamilyGuard may use third-party service providers to help operate the website, email delivery, hosting, payments, customer notifications, and other core functions. Those providers should only receive the data needed to perform their role for FamilyGuard.
Examples of processor categories may include:
FamilyGuard does not intend to sell personal data.
FamilyGuard should keep personal data only for as long as needed to provide the relevant service, meet legal obligations, resolve disputes, or maintain security. Exact retention periods should be confirmed before launch and then reflected here.
Waitlist records should be retained only while launch communications remain relevant, unless the user becomes an account holder or asks to remain on a product update list.
Activity data that remains local should follow the retention settings offered inside the product, or reasonable defaults where no setting is available.
FamilyGuard is a parental tool intended for adults who manage internet access for their household. It is not intended for direct signup by children. Where the service processes information relating to children's devices or activity, the product should be designed to minimise cloud collection and to keep detailed data local by default wherever practical.
Depending on where you live, you may have rights to access, correct, delete, or object to certain processing of your personal data. FamilyGuard may also publish a dedicated contact route for privacy requests and explain the process for handling them.
If you joined the waitlist and no longer want updates, you should be able to unsubscribe from future communications.
FamilyGuard may update this notice as the product evolves. If material changes are made, the updated version should be published with a new effective date and, where appropriate, brought to users' attention in a visible way.