We can't read your family's messages.

That's not just a promise. It's how the system is built: messages are end-to-end encrypted, locked on one family phone and only unlocked on another. The one exception is yours to make: if you choose to share the messages you review, to help improve the screening, we can read the ones you share, with phone numbers and email addresses removed.

Encrypted before it leaves the phone.

Your child's messages, contacts, locations and browsing history, your alerts and your settings are encrypted with a key that only your family's phones hold. Our server passes the encrypted package along and can't open it.
Messages are checked for things that need a parent on your child's phone, not on our servers.
Places report arriving and leaving. We keep no trail of where your child has been.

What our server can see

Carrying sealed packages still means seeing some things about the delivery. We'd rather tell you exactly what than call the list empty.

A random channel number that identifies a pairing. Not a name, and not a phone number.
Which direction each package went, how big it was, and when it arrived.
The notification token needed to wake a phone up.
The internet address the phone connected from, the same as any website you visit.
The child's phone model, its Android version and security update level, the version of our app, and whether Android has offered it an update, so we can test that update before your child's phone installs it.
Which kind each of your records is (an acceptance, a certification, a sharing choice or a request to delete), but not what it says.
If we set up your child's phone for an order, the code it was set up with, which connects the pairing to that order and its email address.
Whether the phone's subscription is current, and until when.
Whether your child's phone is paired with more than one parent's phone: the server links each added parent's pairing to the first one, so it knows they belong to the same phone.
When each phone last contacted the server, and whether the service that wakes phones up has reported that our app is no longer on your child's phone.
Your child's age group: under 13, or 13 to 17. For a child under 13, also where confirming you're an adult stands (requested, emailed, confirmed or withdrawn), when, and Epic's reference number. If your order email was used for it, we keep only a masked version.
If someone at your child's phone asks for a code, to release the phone or to confirm a new main parent: that it was asked for and when, a masked form of the address we emailed it to, and a scrambled copy of the code so it can check the one typed on the phone. It is deleted a day later.
With website filtering on, your child’s phone asks our name server whether each site is allowed, so that server sees every domain the phone looks up. It sees them against a filter identity that we deliberately don’t link to your pairing anywhere in our data, so the filtering side of the system doesn’t know which family it belongs to. A name server has to see the names it is asked about, and we’d rather say so than claim otherwise. Those lookups are kept for at most 24 hours, and usually deleted within minutes.

What reaches us on purpose

A problem report you write and send, and a crash report your app sends after a crash. Both name your pairing so a fault can be found, and neither contains your child's messages, contacts, phone numbers or location.
A record of each thing you agree to or tell us: accepting the terms, certifying you are the child's parent or guardian, the age band you gave for your child, your sharing choice, agreeing to confirm you're an adult for a child under 13 (or withdrawing it), and any request to delete your data.
Only if you choose to share: your judgements on the messages you review, and if you pick that option, the text of the messages you judged, with phone numbers and email addresses removed.

Other companies that help run the app

Google delivers the notification that wakes a phone, which never carries message text, and runs Android's location services. When your app shows where your child is and they aren't at one of your places, it asks Google to turn that position into a street address, which sends Google the exact position.
Mapbox draws the map in your app. The map areas your app asks for can show Mapbox which area is being looked at.
For a child under 13, Kids Web Services, part of Epic Games, checks that you're an adult, with its payment processor Stripe. It receives your email address and whatever you confirm with. We never see your card or your number.
When someone at your child's phone asks for a code, to release the phone or to confirm a new main parent, we email it to the address on your account through Brevo, the email service we use. Brevo receives that address and the email.

What stays with your family

Message content

No readable message content, no contact names and no phone numbers reach our sync server.

Your keys

The keys that unlock your family's messages never leave the phones that made them.

Your child's trust

Nothing is hidden. Your child's phone says it's supervised.

This website keeps an ordinary visitor log: the internet address each visit came from, the page asked for, and the time. Nothing on this site tracks you across other sites. If you ask us to tell you when Paired Parent is available, we keep the email address you give us so that we can, and whether you offered to help test it before launch. The photographs are illustrations, not photographs of real families.

The full privacy policy and terms of use are published at pairedparent.com. Questions: privacy@pairedparent.com

Paired Parent is for a parent or legal guardian supervising a phone they provide to their own child. Every feature described here is enforced by the software on the child's phone; where a feature has limits, the page says so.

This site keeps a visitor log: the internet address the visit came from, the page asked for, and the time. Nothing on this site tracks you across other sites. What else we keep, and why, is on the Privacy page. The photographs on this site are illustrations, not photographs of real families.

Paired Parent™ is a trademark of Paired Parent LLC. Android is a trademark of Google LLC. App, site and company names appear only to show what Paired Parent works with, and belong to their owners; no endorsement is implied. © 2026 Paired Parent LLC.