Children's Privacy Notice — Kinfara

Kinfara Labs LLC · 300 Delaware Ave, Ste 210 #250, Wilmington, DE 19801, USA · +1 305 399 6377 · privacy@kinfara.com · children's requests: privacy@kinfara.com Effective: 2026-10-11. This page is a plain summary for parents. The full Privacy Policy governs.

The Children's Online Privacy Protection Act and its rule (together, "COPPA") require us to tell parents and legal guardians ("parents") how we collect, use, and disclose personal information from children under 13. This page is our COPPA online notice (16 CFR §312.4(d)) and a plain summary for parents; the direct notice for consent is the email we send when you add a child (Section 2). Our full Privacy Policy — at kinfara.com/privacy — governs and describes our complete information practices. Kinfara does not knowingly collect personal information from children under 13 without first obtaining verifiable parental consent; verifiable parental consent is obtained before any collection of personal information from a child under 13. Our service is US-only.

If a child's information reaches us without consent. If we learn that we have inadvertently collected personal information from a child under 13 without the verifiable parental consent the law requires, we will take appropriate steps to delete it. If you are a parent or guardian and discover that your child is using Kinfara without your consent, please alert us immediately at privacy@kinfara.com and we will remove the child and delete the information.

1. What we collect from your child's phone — and what we do not

We collect Only when Who can read it
Precise location, accuracy, battery level and basic device status Your consent is confirmed and your child has turned on their own "Share my location" switch (it is off until they do) Your family's phones only. It is encrypted on your child's phone before it is sent. Kinfara stores encrypted data it cannot read and holds no usable key (only an encrypted backup you alone can unlock with your 12-word recovery phrase).
Safety events the app creates — SOS, check-ins, and place alerts When an event happens The members of your circle, including you. Kinfara's server also stores the event's type and time with an internal, non-identifying reference - so it can deliver the alert and keep it as described in Section 3 - never your child's name.
Consent records — your age band, your child's age band, when and how you consented, the last four digits and brand of the card used for the $1 check When you add a child Kinfara, in an access-restricted record. If the child is later removed or your account is deleted, the surviving proof of consent keeps your email address, the consent details (method, version, time) and your child's age band — no name, no location, and no link to your child, a device or a network address; it carries a scrambled code made from your account ID, used only to delete it on schedule.

We take special care to collect only as much information as is reasonably necessary for your child to use the safety service, and no more. We do not read your child's messages, calls, photos, browsing or app use; we do not record audio; we do not create a voiceprint or any other biometric identifier; we show no advertising; we sell nothing.

2. How you give consent

Your child's age How consent works What happens if you do not complete it
Under 13 Verifiable parental consent is obtained before any collection of personal information from a child under 13, using a COPPA-recognized method — a payment-card transaction. You receive a direct-notice email. It links to a verification page where Stripe charges $1 to your payment card. The $1 is kept, not refunded — except in the cases our Terms of Use list under "When we give it back" (Section 8): a verification we could not complete, a duplicate charge, a fraud warning from your card issuer, or where the law requires a refund; a chargeback or such a fraud warning withdraws your consent. No full card number or security code reaches Kinfara — we receive only a payment reference, the card's last four digits and its brand. Nothing is collected from your child or your child's phone before this step. The name you typed when you added the child and the request details are kept only for the consent request; if you do not confirm, they are deleted 24 hours after you added the child. A card charge alone only confirms an adult with a card in their name — so you also confirm in the app that you are this child's parent or legal guardian and have the right to set up Kinfara on their phone (the checkbox when you add the child). The link works for 24 hours. If you do not confirm within 24 hours, the child you added is removed, and the child, the name and the request details you typed are deleted automatically; what is kept is the request's consent-log entries with every link to the child, the account, a device and a network address removed (each keeps only what happened, the age group, the consent-text version and the day), deleted once 7 years old, and a record on your account that the request was removed (your account id and when), deleted once it is 7 years old and the account no longer exists.
13 to 17 Your teen joins by entering the circle's invite code on their own phone and turns on their own location sharing. A parent adds them (with the $1 verification) only where the app store's age signal or your state's law requires a parent to approve. No collection until the required consent is given.
Who can see your child After your consent, everyone in your circle can see your child, the same as any other member. You control this by who is in the circle — add or remove anyone, or use a separate circle. Your child's phone always shows who can see them. Before your consent is complete, no one can see your child.

(See Privacy Policy §7, Children's privacy.)

3. How long we keep each item

We keep a child's personal information only as long as is reasonably necessary to provide the safety service your family turned on and to meet our legal obligations, and never indefinitely; each item's purpose and deletion window are set out below (and in full, with the business reason we keep each one, in Privacy Policy §9).

Item Kept for Then
Location (encrypted) Up to about 25 hours on our server (a purge runs every 15 minutes, deleting positions more than 24 hours old); the single newest position of each phone is kept at most 30 days Deleted automatically. The trail you see lives on your own phone (plan window; on-device cap 30 days / 5,000 points), erased on sign-out.
Encrypted record around a fired alert Kept up to 90 days Deleted automatically. Nothing is kept unless an alert fires.
Safety alerts 30 days; an alert nobody acknowledged up to 90 days Deleted
Alert-delivery receipts (reference, your account id, time, status — no child data) 7 days Deleted
Account and family profile Until you delete the account, then within 30 days Deleted, except the proof-of-consent fact below
Proof that you consented Link to your child erased on deletion; a minimal record — your email, the consent method, version and date, and your child's age band, with no name, no location and no link to your child, a device or a network address, and a scrambled code made from your account ID so that we can delete it on schedule (used only to check whether your account still exists) — kept only to prove consent, and deleted once it is 7 years old and your account no longer exists —
Service event counts (recorded with the account id once you are signed in — an event before sign-in carries no account id; never a location, a name or a message; no child data) Within 14 days Only daily totals remain
Unfinished under-13 consent 24 hours Child removed; the child, the name you typed and the request details are deleted; what is kept is the request's consent-log entries with every link to the child, the account, a device and a network address removed — each keeps only what happened, the age group, the consent-text version and the day — deleted once 7 years old, and a record on your account that the request was removed (your account id and when), deleted once it is 7 years old and the account no longer exists

4. Your rights — review, delete, revoke

5. Who else touches the data (our processors)

We do not sell a child's personal information, we do not share it for advertising, and we show no ads in a child's account. We disclose it only to the service providers listed below — each needed to run the safety service and allowed to use it only to do that work for us — so there is no separate third-party disclosure for you to consent to. We do not disclose a child's information to advertisers, data brokers or any other outside company. (Letting the members of your circle see your child is covered by your parental consent — see Section 2 — it is sharing within your family circle, which you control by circle membership, not disclosure to any outside company.) The only companies that ever touch the data are the service providers below, each limited to what it needs to run the service:

Processor What reaches them
Supabase (hosting, EU/Frankfurt) Encrypted location it cannot read, the names you typed, stored encrypted so Supabase and we cannot read them, account email, family membership, device tokens, consent records
Cloudflare (website host & edge network) Website requests; for a waitlist sign-up, the connection details Privacy Policy §3A describes; for the Turnstile bot check (§3B), your IP address, browser user-agent and TLS fingerprint, the page it runs on, and the Turnstile token; for the email-domain lookup (§3A), only the domain of a waitlist email address — never a child's name or location
Google — Firebase Cloud Messaging (Android phones in your family) The alert being delivered (codename or "your child"), the push token
Apple — APNs (iPhones in your family) The same
Resend (email) Your (the parent's) email and the transactional email text — never a child's name or location
Stripe ($1 verification) Your card, entered on Stripe's own page, and your email address. We also give Stripe internal reference numbers for your account and for the child being verified (no names) so that the charge is matched to the right request.
TomTom (map tiles, shown in the app) The map area you are viewing and your phone's IP — only if you chose "show a real map"; a position-only mode sends nothing

No advertising or analytics company receives anything.

6. What your child sees on their own phone

Questions: privacy@kinfara.com. Complaints: your state Attorney General; in California, the California Privacy Protection Agency.


Kinfara Labs LLC · 300 Delaware Ave, Ste 210 #250, Wilmington, DE 19801, USA · privacy@kinfara.com · Effective: 2026-10-11 · Privacy Policy · Terms of Use · Consumer Health Data Notice · Children’s Privacy