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-30. 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 your child's information, except the records listed under "What survives deletion" in Section 13 of the Privacy Policy (for example, an item a specific legal obligation or a legal hold requires us to keep, kept only until that ends, and a $1 verification claim whose charge was kept but never recorded, kept until our employees resolve it).
1. Personal information we collect about children and teens — and what we do not
| We collect | Only when | Who can read it |
|---|---|---|
| Precise location, accuracy, battery level and whether the phone is charging, the phone type (iPhone or Android), and a short status your child can choose to show (for example "At school"; optional, off until your child picks one) | 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 key that can read it (the one related item we hold is an encrypted backup of the circle owner's signing key, locked by the owner's 12-word recovery phrase, which only the circle owner holds; it gives no access to location). |
| Basic device status — whether the phone is online, the times of check-ins (including when it goes offline), the device platform, and whether it reports a simulated location | While your child's phone is connected, after your consent | Kinfara and our hosting provider (Supabase). It is encrypted in transit and at rest, but not end-to-end encrypted, so our servers can read it (Privacy Policy §5B(d)); it never contains a location or a name. |
| Safety events the app creates — SOS, check-ins, and arrive / leave 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. |
| Network (IP) address of your child's phone | Each time the phone talks to our server, after your consent | Kinfara and our hosting provider (Supabase), in its request logs; and TomTom, only if "show a real map" is chosen on that phone (see Section 5) |
| Device identifier for notifications | When the app runs on your child's phone after your consent and notifications are allowed | Kinfara and the service providers listed in Section 5, only to deliver safety alerts to your child's phone |
| Sign-in session — the network address and the browser type recorded for that sign-in | When your child's phone signs in, after your consent | Kinfara and our hosting provider (Supabase), only to keep the phone signed in so it keeps sharing and can receive alerts |
| Google Play's install ID (Android only) — a random code Google gives the app on your child's phone, which does not survive a reset of the phone | When the app reads your child's age range from Google Play, after your consent | Kinfara and the service providers listed in Section 5. We keep only a hashed version of it (a keyed hash — made with a secret key held on our server, from which the ID cannot be read back) with your child's phone record, only so that, if you withdraw your approval of Kinfara in Google Family Link, we can match Google's notice to your child's phone and stop its sharing. Google does not allow any other use, and we never use it to track your child, never sell it and never share it except as Section 5 describes. |
| Apple's app transaction ID (iPhone only) — a code Apple gives this app for the Apple account on your child's iPhone | When the app reads your child's age range from Apple, after your consent | Kinfara and the service providers listed in Section 5. We keep only a hashed version of it (a keyed hash — made with a secret key held on our server, from which the ID cannot be read back) with your child's phone record, only so that, if you withdraw your consent through Apple, we can match Apple's notice to your child's phone and stop its sharing. We never use it to track your child, never sell it and never share it except as Section 5 describes. |
| Consent records — your age range, your child's age range, 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 held by our hosting provider (Supabase). 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 range — no name, no location, and no link to your child, a device or a network address; it carries a hashed version of 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.
Profile and location information of Children and Teens using the Services may be shared with other members of any circle they join. Kinfara does not enable your child to make personal information publicly available. You are responsible for monitoring your Child or Teen's account and location-sharing activity through our Services and for blocking or permitting location-sharing features.
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. Once your account is verified, adding another child under 13 does not need another $1. 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, a refund of that $1 or such a fraud warning withdraws your consent for every child under 13 it verified, and those children are removed and their information deleted. No full card number or security code reaches Kinfara — we keep the payment record described in Section 9 of the Privacy Policy (payment and customer references, the amount, card brand and last four digits, your account id, email address, network address and device details, and which terms you accepted) as proof of consent. 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 successful card charge alone does not establish the payer's age, identity or relationship to the child. As part of our consent process, 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's profile, the name and the request details you typed are deleted automatically. If a $1 verification was attempted, its separate attempt record can retain the account reference, child reference and Stripe payment reference for 30 days after its last update, even after the consent request is removed. A claim whose charge was kept but never recorded is kept until our employees resolve it; 30 days after its last update, its child reference is removed. These attempt records follow the A $1 verification attempt row in Section 3. Other retained records are 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), kept only as long as necessary to resolve disputes, establish legal defenses and comply with applicable laws, then deleted, and a record on your account that the request was removed (your account id and when), kept only as long as necessary to resolve disputes, establish legal defenses and comply with applicable laws, then deleted. |
| 13 to 17 | Your teen joins with their own account and turns on their own location sharing; where the app store asks for a parent's approval, the parent approves in the app store. | 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, Our policy towards children & teens.)
When your child turns 13. The under-13 protections and the parent's consent stay in place after the 13th birthday; nothing changes automatically.
3. Data retention
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 no longer, with the two exceptions Privacy Policy §9 names (an item a specific legal obligation or a legal hold requires us to keep, kept only until that ends; and an unrecorded $1 verification claim until our employees resolve it); 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 (every 15 minutes we delete location data more than 24 hours old); the single newest location of each phone is kept at most 30 days | Deleted automatically. The location history 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 |
| Arrive / leave alerts for saved locations (whether it was an arrival or a departure, and the place's name, are encrypted) | 7 days | Deleted automatically |
| Check-in / "I'm OK" messages (who checked in and when — no location) | 30 days; a check-in nobody acknowledged up to 90 days | Deleted |
| Basic device status (online or offline, latest check-in time, device platform, simulated-location flag) | Only the current value, replaced as new readings arrive, while your child's phone is part of the circle | Deleted when that phone or your child is removed, or with your account (within 30 days) |
| Sharing and consent records (when location sharing was turned on or off, and the steps of your consent) | While your child is in the circle | Deleted when your child, or the account, is deleted (within 30 days), except the proof-of-consent record below |
| Alert-delivery receipts (reference, your account id, time, status — no child data) | 7 days | Deleted |
| Network (IP) address in our hosting provider's request logs | 7 days | Deleted automatically by our hosting provider |
| Device identifier for notifications | While the app is installed and registered on your child's phone | Removed |
| Sign-in session (network address and browser type) | While your child's phone stays signed in | Deleted when the phone signs out, after 30 days without use, or with your account |
| 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 range, with no name, no location and no link to your child, a device or a network address, and a hashed version of 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 only as long as necessary to resolve disputes, establish legal defenses and comply with applicable laws | — |
| Payment record of the $1 check (payment and customer references, the amount, card brand and last four digits, your account id, email address, network address and device details, and which terms you accepted — never your full card) | Kept only as long as necessary to resolve disputes, establish legal defenses and comply with applicable laws | Deleted. If you delete your account, your email address, network address and device details are removed from it straight away. |
| A $1 verification attempt (which account and which child it was for, and Stripe's payment reference) | 30 days after its last update (for example, when it was recorded or refunded), even if the child's request was removed sooner, with two exceptions: the record of a completed $1 is kept while the child it was for is still in the circle, to resolve disputes (a later dispute or refund of the charge withdraws the consent); and a claim whose $1 was kept but never recorded is kept until our employees resolve it (they are alerted every day) - once its child has been removed and 30 days have passed since its last update, it no longer says which child it was for, and only the account and Stripe's payment reference stay | Deleted |
| A hashed version of Google Play's install ID (Android only) | While your child's phone is part of the circle | Deleted when that phone is removed or your account is deleted |
| A hashed version of Apple's app transaction ID (iPhone only) | While your child's phone is part of the circle | Deleted when that phone is removed or your account is deleted |
| 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's profile, the name you typed and the request details are deleted. If a $1 verification was attempted, its separate attempt record can retain the account reference, child reference and Stripe payment reference for 30 days after its last update, even after the consent request is removed. A claim whose charge was kept but never recorded is kept until our employees resolve it; 30 days after its last update, its child reference is removed. These attempt records follow the A $1 verification attempt row above. Other retained records are 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 — kept only as long as necessary to resolve disputes, establish legal defenses and comply with applicable laws, then deleted, and a record on your account that the request was removed (your account id and when), kept only as long as necessary to resolve disputes, establish legal defenses and comply with applicable laws, then deleted |
4. Managing your child's account or information
- Review, delete or withdraw consent. In the Kinfara app, at once: open Your child's data on your child's card to see, download or copy what our servers hold for your child; see your child's recent locations in their History; and save what is on your phone and what our servers hold about your account with Settings → Account & Subscriptions → Download my data. Parents may review the child's personal information, revoke consent, request deletion, and request a copy of the child's data. We will honor requests within a reasonable timeframe and will delete data as required by law. For questions, to review or delete a child's information, or to revoke consent, contact privacy@kinfara.com. We act only on a request from the verified parent on the account — made in the app, or emailed from the account's email address — and we may ask you to confirm a code we send to that email. We never ask for a government ID.
- Delete one child: open the child → "Remove from circle". Collection stops and what we hold for that child is erased, except the records listed under "What survives deletion" in Section 13 of the Privacy Policy.
- Delete everything: Settings → Account & Subscriptions → Delete my account. Completes on our servers within 30 days.
- Withdraw consent: deleting the child withdraws it; for under-13, a chargeback or a refund of the $1 verification, or a fraud warning about it from your card issuer, also withdraws it for every child under 13 that $1 verified. We then stop collecting and delete. For a child under 13: on Android, withdrawing your approval of Kinfara for your child's phone in Google Family Link also withdraws it, and on iPhone so does withdrawing your consent for your child's iPhone through Apple. Once Google or Apple tells us, we stop accepting anything from your child's phone: it can no longer share its location or send an SOS to your circle. You can then remove your child (see "Delete one child" above) to erase what we hold for them, except the records listed under "What survives deletion" in Section 13 of the Privacy Policy.
- Stop further sharing with a member: remove that member from the circle to cut off their access through the circle. Removing them does not erase information already delivered to their phone, including previously received location records.
- Verifying it's you: before we show or export a child's data, we confirm the request comes from the verified parent on the account — for example, the request must come from the account email, or be made from inside your signed-in app. (Everyone in your circle can view your child's location after your consent; only the verified parent can ask us to review, export, or delete the child's data; a circle admin (the creator or a co-admin) can also remove the child from the circle, which erases what we hold for that child, except the records our Privacy Policy lists under "What survives deletion" in Section 13.)
- No one sees your child until you consent — then your circle does. Before you complete consent, no one — not even the circle's creator or a co-admin — can see that your child is in the circle, or anything about your child. After you consent, everyone in the circle sees your child like any member; you control this by who is in the circle.
- We will not condition your child's use of the service on giving more information than the safety feature needs.
5. Information disclosures about children and teens
Except in the three narrow cases below, personal data from your child will be shared by Kinfara only to provide our products and services; it will not be shared with third parties for their marketing purposes. 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. Apart from the three narrow exceptions below, 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, apart from the limited own uses our Privacy Policy §15 describes (Stripe: fraud prevention, security and improving its services; TomTom: de-identified map-request data; Google: Firebase push service data; Cloudflare: its bot check). Apple delivers alerts to iPhones under Apple's own developer terms; Apple publishes no separate data-processing agreement for this. None of them may use it to profile a child, contact a child or advertise to anyone. So there is no separate third-party disclosure for you to consent to. Apart from the three narrow exceptions below, we do not disclose a child's information to advertisers, data brokers or any other outside company. There are three narrow exceptions: for legal reasons — where valid law or legal process requires it, or in good faith where we reasonably believe it is necessary to prevent death or serious physical harm; to our lawyers and accountants or auditors, under a duty of confidentiality and only as much as they need to advise us; and in a business transfer (a merger or acquisition), with notice to you; we will seek to require the new owner to keep the promises on this page, or give you notice and a choice as the law requires. (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.) Apart from those exceptions, the companies that handle the data for us 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 identifiers for notifications, consent records, Google Play's install ID (Android only) or Apple's app transaction ID (iPhone only), received only to be hashed on arrival with a secret key held on our server (only the keyed hash is kept; the ID itself is never stored) and the type and time of each safety event, and the network (IP) address of each phone's requests in its request logs (7 days) |
| 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 (it names the person only as "Someone in your circle" or "your child"), the device identifier for notifications |
| 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 |
| Zoho Mail (our business mailboxes) | The emails you send us (your address and what you write), for example a request about your child |
| 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 a circle member is viewing — which shows your child's approximate area when that member looks at your child — and that phone's IP address, only if that member chose a real map (this happens on that member's own phone, and any circle member who chose a real map sends these requests, not only a parent); a position-only mode sends nothing |
No advertising or analytics company receives anything.
6. What your child sees on their own phone
- An ongoing notification: "Kinfara Circle — sharing your location. Your circle can see where you are." Android shows it while sharing is on; your phone's own settings may let you dismiss or silence it.
- Their own "Share my location" switch — off until they turn it on — and the "Who can see me" screen, which shows who can see them while sharing is on (and, on Android, the ongoing notification while sharing is on).
- Settings → "Leave this circle" — your child can leave at any time; you are told they did, and keep their name (encrypted, readable only on your phone) and last known location as your own record.
- Kinfara Circle is a consensual family-safety circle — there is no hidden mode, and it is never used to monitor an adult.
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-30 · Privacy Policy · Terms of Use · Consumer Health Data Notice · Children’s Privacy