Privacy
What we hold, and what we refuse to
A product that supervises a child accumulates the most sensitive data a family has. The design position is to collect the least that makes it work, and to make the boundary something you can check rather than something we assert.
What is collected
Your account
Your email address, a hashed password, which devices belong to your household, and your settings. This is the part a normal service holds.
From the tablet
Which apps are installed and which were opened, what was blocked, and whether the device is reachable and healthy. Enough to show you a list you can act on.
What is not collected
- Message content, from any app.
- Photos, files, or anything from the camera or microphone.
- Location tracking.
- Keystrokes, screen recordings, or screenshots of what a child is doing.
We are not building the product that reads a teenager's conversations and mails them to a parent. That product exists; this is a different one.
The wall between your child and our marketing
This is the part we are most willing to be held to.
Marketing consent is separate, off by default, and split into three independent choices you can change at any time from your dashboard. Nothing is on because you did not notice a pre-ticked box.
Behind that, there is a filter every outbound marketing event has to pass. It works on the payload, not the label: an event carrying a device identifier or any marker of child telemetry is refused before consent is even consulted, no matter what type it claims to be. A bug that mislabels a child event as a marketing one therefore does not leak it — it gets dropped.
Why it is built that way. Consent checks fail the moment something is labelled wrong, and labels are written by people. Checking the contents instead means the boundary holds even when we make a mistake.
Technical detail attached to a bug report
When you send us a report, there is a tick box for attaching technical details. It is opt-in, it is redacted before it leaves your machine, it is capped in size, and nothing is transmitted until you press the button. Untick it and you send only your words.
The child's app also reports its own crashes so we can fix them. A crash report says what failed inside the app; it does not carry what the child was doing.
Your data
- Delete your account and the household goes with it — devices, profiles, policies, activity.
- Ask us what we hold about you and we will tell you.
- Withdraw any marketing consent at any time, from the dashboard, without contacting anyone.
Private testing. FrameBright is not yet a launched service, and this page describes how the system is built rather than a finalised legal notice. A full privacy policy ships with the paid launch. If you are testing with us and want something in writing before then, ask and you will get a straight answer.