How we protect
How TinyBeacon protects family privacy
How we protect your family's data. Here is what happens on a device using Tiny Beacon, and what your family chooses to share.
What each build can share
The short version: choose the signal that helps your family make a good next decision. Every data-collecting scope starts off except emergency help, and your child can see what is shared. TinyBeacon is specific about platform boundaries. Here is the useful signal, the place it works, and the choice that enables it. Location and safe zones — location plus named-place arrival and leave alerts — every build. Emergency help — a tap-or-type safe word or SOS signal — every build. Device wellbeing — a coarse battery band, charging state, connection bucket, and server-recorded last-seen time — every build when enabled with parent or legal guardian consent. App time — app/package names, categories, time used, screen opens, and daily totals — Android only when a parent or legal guardian consents and Android Usage Access is on; iOS does not collect cross-app app-use details. Screen check-in — a supported concerning-content heads-up — supervised Android; screenshot path is partial. Web-safety rules — a chosen rule by domain or category — supervised builds. Messages and calls — a supported safety review signal — supervised-plus Android only. Screen-time limits and bedtime — device-supported limits — fully wired on iOS; best-effort on Android.
A supervised edition is a separately installed Android build with additional features. Families are told what each feature does before they choose it.
Supported screen check-in
A supported signal is not a promise about every screen, message, or conversation. TinyBeacon shows the scope before a family chooses it.
Your family chooses the scope
Every data-collecting scope starts off except emergency help. A parent or legal guardian chooses what to enable, and your child can see what is shared. The parent or legal guardian can withdraw a safeguard when your family's needs change. Data is kept within a rolling 7–180-day window, with a 30-day default. Retention trims older data; it does not expire consent. Consent ends only when a parent or legal guardian explicitly withdraws it. Check the current in-app setting and privacy policy for the exact scope before enabling a supervised feature. Screenshot evidence kept for a parent is end-to-end encrypted — only your family's devices hold the key. Each frame is checked by our safety service first, and frames that are not a concern are never stored. Location and other safety data are encrypted in transit and at rest. We say what the protection covers, and we do not turn that statement into a promise of access beyond the chosen scope.
A supported screen check-in
Choose a safeguard
Aisha’s family chooses a screen-content check-in on supervised Android. The scope is off until a parent or legal guardian gives consent.
Scope starts off
A useful heads-up
A supported concern can become a short, plain-language heads-up. It is a signal for a conversation, not a complete view of every screen or message.
Supported supervised Android
Talk it through together
Aisha and her parent can see the same shared explanation, then talk. Her parent can adjust the safeguard or turn it off.
Shared explanation
This path is limited to supported supervised Android builds. The family sees the scope and gives separate consent before it starts.