Previous version. This is the Kinfara Privacy Policy last updated 2026-10-28, in effect until 2026-10-29. The current Privacy Policy is at kinfara.com/privacy.

Privacy Policy — Kinfara Circle

Kinfara Labs LLC ("we," "us").

Effective date: 2026-10-28 · Last updated: 2026-10-28

This policy covers the Kinfara Circle family-safety app — one app that every member of a family circle uses to share their own location and see the others, with SOS and place alerts. There is no separate "parent" or "child" app.


1. Our privacy commitments (at a glance)

We built this app so the data that could be abused doesn't exist to abuse. These are binding commitments, not slogans — short summaries of the sections below, where each is set out in full:

  1. We do not sell your personal information, and we do not share it for advertising or with data brokers. We do not "share" it for cross-context behavioral advertising, and we do not disclose location or any data to data brokers, ad networks, or analytics-monetization partners — and never have. We use a small set of service providers (hosting, payments, push, maps, email) only to run the service, on our instructions, except the limited own uses of Cloudflare (its bot check and public DNS resolver), Stripe (fraud prevention, security, improving its services, and payment details you save with Link), TomTom (de-identified map-request data) and Google (Firebase push service data) described in §15; Apple and Google also handle App Store and Google Play payments as the stores, under their own privacy policies, and Google receives the reports its program requires for a kinfara.com subscription started from the Android app (§15).
  2. Your location is visible only to the members of the circles you join. Anyone who joins with a circle invite code joins at once, with no approval step in the circle (a teen whose app store requires a parent's approval cannot join until the store reports that approval), and can see you as soon as the circle creator's phone has passed them the circle's keys (for a child under 13, that key delivery happens only after verifiable parental consent is complete); we tell you, in the app and by email, when someone new can see your location. Give a circle invite code only to the person you mean to invite: whoever enters it joins at once. You can stop sharing or leave a circle at any time, and a circle admin — the person who created the circle, or a co-admin — can remove a member from the circle (removing a co-admin also needs the creator, or a co-admin the creator has allowed to manage co-admins; the creator cannot be removed). (One exception — drawing a map: if you choose to see a real map, your phone fetches map tiles from our map provider, TomTom, which reveals the approximate area to TomTom; you can choose a position-only view instead, and then nothing is sent to any map provider. The screen where you save a location such as Home or School is part of this: if you set it up with a real map, the map our provider draws around that place shows that place's area to TomTom; if you chose position-only, that screen draws no map and nothing is sent — see §15.)
  3. We use precise location solely to provide the safety service you requested — never for any secondary or commercial purpose. (We bind ourselves to the FTC "sensitive location data" standard: a direct relationship with you, your affirmative opt-in, and use only for the requested service.)
  4. No third-party advertising SDKs and no behavioral-analytics trackers are in the app.
  5. We encrypt data in transit and at rest, use end-to-end encryption for your location and the names you give members, and minimize what we hold.
  6. We apply a sensitive-location safeguard: Kinfara does not intentionally build, infer, sell, or disclose a record of visits to sensitive places (health facilities, places of worship, etc.). The one exception is under your control: when you choose to draw a real map, your phone asks the map provider for the tiles around a member's location, which reveals that approximate area to the provider (see Section 15 — you can choose the position-only view instead, and then no map provider is contacted).

2. Who we are

The controller is Kinfara Labs LLC, 300 Delaware Ave, Ste 210 #250, Wilmington, DE 19801, USA. Telephone: +1 305 399 6377 (a line for you to reach us; we do not call or text you, except a settlement-conference video call the parties agree to in a dispute — see §10). Email: privacy@kinfara.com. Our privacy contact details are in §17.


3. Information we collect

Category Examples Source
Account information name/label, contact information (your email address), the name (and, from Google, the profile-photo link) your Google or Apple sign-in sends, circle membership, pairing codes, and your age group (under 13 / 13–15 / 16–17 / 18+), worked out on your phone from the date of birth you enter and, where your app store provides one, its age signal (the younger wins) — we never receive your birthday you (when you sign up with your email address), or your Google or Apple account if you sign in with it
Precise location live location, accuracy, recent location history (per §9), battery, mock-GPS flag each member's device, with consent
Saved locations (like Home or School) not collected — the saved locations you create stay on your own phone (and, on an iPhone, in your own iCloud or computer backup of it, if you turned one on), where they are checked, and are never sent to us (see §9) kept on your phone
Safety-event data SOS triggers, check-ins, and timestamps your device, when an event occurs
Device & diagnostic device type/OS, app version, internal device identifiers, the network (IP) address and the browser type (of the app or browser your device connects with) (kept in the security logs, sign-in sessions, request logs and payment records listed in §9), and service event counts (recorded with your account id once you are signed in — an event before sign-in carries no account id; no crash data is collected and no crash-reporting tool is in the app) automatically
Device identifiers for notifications an identifier issued by your phone's push service (Google's Firebase Cloud Messaging, or Apple's push service) that lets us deliver a safety alert to your phone. It identifies the app instance on your device; linked to your account and device record, it can identify the account or device it belongs to, and it is used only to send you the alerts you asked for. Every member's app registers a device identifier for notifications so each member can receive circle alerts. your device's operating system, when you allow notifications
Age signal (from your app store) on Android, if Google Play offers it where you live, Google Play tells the app on your phone an age range (under 13 / 13–15 / 16–17 / 18+) and whether a parent still has to approve. On iPhone (iOS 26.2 or later), only where Apple says the law where you live requires it, Apple shows its own screen and, if you choose to share, tells the app your age range in the same way; if you decline, the date of birth you enter decides. The app keeps, as your age group, only the younger of that range and the date of birth you enter — never the store's age answer itself. We use it only to apply the correct age-based protections and parental-consent rules required by law (e.g. Texas, Utah, Alabama, California). We do not receive your date of birth, and a store answer never widens a protection. On Android, Google Play's answer also carries an install ID — a random code Google gives the app on that phone, which does not survive a reset of the phone. We keep only a hashed version of it with your phone's record — a keyed hash, made with a secret key held on our server, from which the ID cannot be read back — and only so that, if a parent withdraws their approval of Kinfara in Google Play, we can match Google's notice (hashed the same way) to your phone and stop its sharing, as the law requires; Google does not allow it to be used for anything else, and we never use it to track you, never sell it and never share it except as Section 15 describes. It is deleted when that phone is removed from your account or your account is deleted. On iPhone, Apple's answer comes with Apple's app transaction ID — a code Apple gives this app for the Apple account on your phone. We keep only a hashed version of it in the same way and only so that, if a parent withdraws consent through Apple, we can match Apple's notice (hashed the same way) to your phone and stop its sharing; we never use it to track you, never sell it and never share it except as Section 15 describes. For a child under 13, after either withdrawal notice is matched, we stop accepting anything from that phone: it can no longer share its location or send an SOS to the circle. Google Play on Android; Apple on iPhone, only where Apple offers it
Children's data a minor's location and profile, collected only with a parent's or legal guardian's consent (for a child under 13, verifiable parental consent) parent/guardian (see §7)
Payment & billing 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); for an App Store or Google Play purchase, the purchase and your account id; for a kinfara.com subscription started from the Android app, Google's one-time code for that link Stripe, at checkout for the $1 verification or a web subscription; Apple or Google when you subscribe in their store; Google Play, through the Android app, when the app sends you to kinfara.com to subscribe; your account id, email address, network address and device details come from your account and our server at that checkout

We do not read your messages, social media, photos, web history, or microphone. Kinfara Circle uses the location sensors only, and only to provide the family location and safety features you turn on.

Inviting someone. An invite is a code you pass on yourself. We do not ask for or receive any details about the person you invite when you create or pass on the invite; they give us their own details only when they sign up. (Adding a child under 13 is different — see §7.)

How you sign in. You create and access your Kinfara account with your email address and a password, or with Sign in with Google or Sign in with Apple. With email and a password, our sign-in provider stores your password only in hashed form — never readable. When you use Google or Apple, we receive from the identity provider only what you authorize on its consent screen — your name, your email address (or Apple's private relay address if you choose to hide it), a stable account identifier that lets us create or locate your Kinfara account, and, from Google, if available, a link to your profile photo (we do not show or use it). That name and photo link are kept with your sign-in account, readable to us (not end-to-end encrypted), and are deleted with your account. We do not receive access to your Gmail, Google Drive, Contacts, iCloud, photos, or any other Google or Apple service. How Google or Apple handles your data during sign-in is governed by their own privacy policies.


3A. If you join our website waitlist

Before the app is something you install, you can ask to be told when it launches by giving us your email on our website (kinfara.com). This is separate from the app and from any family account.

What we collect when you join: the email address (and first name, if you give one) you type; and, worked out automatically from your connection when you submit the form, your approximate location (country, region or city, and time zone), your internet provider or network and its network number (ASN), whether that network looks like a VPN or data center, your IP address, the browser type (the browser/device string, or user-agent, your browser sends), the page that referred you, and a basic deliverability check on your email address (our website server looks up only your email's domain — the part after the @, never the full address — in Cloudflare's public DNS resolver, 1.1.1.1, to see whether it can receive mail). We use this only to run the waitlist, to gauge interest, to guard against fake or abusive sign-ups, and to email you about the launch.

Who processes it: the form is served and the connection details are added by Cloudflare (our website host and edge network); the entry is stored by Supabase (our database host, in the EU); and the confirmation and launch emails are sent by Resend (our email provider) — if you reply to one, your reply reaches our business mailbox (hosted by Zoho). Each acts only on our instructions, except Cloudflare's limited own use of the bot-check details (§3B) and of the domain lookup in its public DNS resolver — see §15.

How long we keep it: the whole entry is deleted automatically within 12 months — the email address (and first name, if you gave one) you typed, and every connection detail stored on it (your approximate location, internet provider or network and its network number (ASN), the VPN/data-center flag, your IP address, the browser type (the browser/device string, or user-agent, your browser sent), the page that referred you, and the deliverability check). You can unsubscribe from the emails with the one-click unsubscribe link in each waitlist email, or by writing to privacy@kinfara.com, and we then remove your entry - or ask us at privacy@kinfara.com to remove it at any time.


3B. Cookies and Do Not Track (our website)

We keep our website deliberately light. We do not use advertising cookies, and we do not use third-party analytics or tracking cookies. We use only the small amount of browser storage a site needs to work — for example, to keep you signed in on your account pages. We do not track you across other websites or services. If you block this storage in your browser, our website cannot keep you signed in.

Bot and abuse protection. On our waitlist sign-up forms, and when you create an account, sign in or reset your password on our website or in the Kinfara app (the app runs the check invisibly through our page kinfara.com/turnstile.html), we use Cloudflare Turnstile, a bot check that helps us tell real people from automated abuse. It is a security measure — not analytics or advertising. It loads a small script from challenges.cloudflare.com, which receives your IP address, your browser's user-agent and TLS fingerprint (technical details of how your browser connects), and which of our pages the check runs on. The check gives a one-time token that is sent with that request and checked with Cloudflare by our sign-in service; we do not keep it. Cloudflare uses them to run the check for us and, under its own Turnstile privacy terms, also to improve its bot detection. We do not use it to track you across other sites or to build a profile of you. Cloudflare is listed in §15.

Because we do not track you across sites, a browser "Do Not Track" (DNT) signal or a Global Privacy Control (GPC) signal does not change what we collect — we already do not sell, share, or track. Where an opt-out of sale or sharing applies, we honor GPC.


4. Why we may process your data


5. How we use your information

Kinfara uses your information to power the safety service you asked for, to communicate with you about your account and alerts, to provide customer support, for security and fraud prevention, to comply with law, and to send optional offers about our own subscriptions. Specifically, we use it solely to: show consented circle members' locations; deliver place arrival/leave, low-battery and offline alerts; raise SOS alerts to the members of your circles; operate, secure, and support the Services; comply with law; and send those optional subscription offers, which you can unsubscribe from as Section 12 explains. We do not use your information for third-party advertising or profiling, we do not sell it, and we do not use it to train artificial-intelligence or large-language models. We do not run artificial-intelligence or machine-learning models over your end-to-end-encrypted content (your location and the names you give members) — our servers cannot read it.

A limit on arrive / leave alerts for saved locations. Because your location is encrypted and our server cannot read it, the saved locations you define (home/school/work) are checked on a member's device — not on our server. A practical consequence, stated plainly: these place-based alerts are produced while the Kinfara Circle app is running on the relevant phone (in the foreground, or active in the background) — not by an always-on server that watches your circle's location for you, because by design it cannot. If the app is fully closed or the operating system has suspended it, a place-based alert may be delayed until it runs again. The SOS button sends its alert as soon as it is pressed and the phone has a connection.


5A. No microphone, no audio

Kinfara requests no microphone permission and processes no audio of any kind. No recording, transcript, voice template, voiceprint, or other biometric identifier is created, retained, or sent.


5B. Location encryption, our access limits, and security

(a) End-to-end encryption and access limits. Kinfara uses end-to-end encryption to secure your live location. Your location is encrypted on your device before it is transmitted and can be decrypted only by the devices of the members of your circle (anyone who joins with a circle invite code; the app tells you when someone new can see your location). No one outside your circle can access your end-to-end encrypted data — not even Kinfara — and we believe this data remains secure even in the case of a data breach in the cloud; however, we cannot guarantee its absolute security. Kinfara never generates or holds a usable key that can decrypt your location. The one related item we hold is an encrypted backup copy of the circle owner's signing key (the key that lets the owner take the circle back and make new keys for it), locked by the owner's 12-word recovery phrase — we cannot open it without those 12 words, which only the circle owner holds, so it does not give us access to your location; see §9. Consequently, Kinfara cannot decrypt, view, or reconstruct your live location — we store only end-to-end encrypted data that cannot be read by Kinfara. Although we comply with valid legal process and may disclose responsive information in our possession or control — such as your account and profile data, the limited payment record we keep (payment and customer references, the amount, your card's brand and last four digits, your account id, email address, network address and device details, and which terms you accepted, never your full card; and, if you took a free trial on kinfara.com, a keyed one-way code made from the card or other payment method you used), device and connection metadata, device identifiers for notifications, and the end-to-end encrypted data of your location — we cannot decrypt the precise location we hold, because the usable decryption keys live only on your circle members' devices and never on our servers. We therefore cannot produce your precise location in readable form from our systems. (Connection metadata such as an IP address can suggest an approximate or inferred location, and a device in your circle may hold a readable copy.)

(b) No sale or advertising sharing. We do not sell your location data, and we do not share it with advertisers or data brokers. It is used solely to provide the sharing features you enable, to the circle you choose.

(c) Security disclaimer. We implement strong, industry-standard administrative, technical, and physical safeguards (including encryption in transit and at rest) designed to protect your information. However, no method of transmission over the Internet, and no method of electronic storage, is 100% secure. While we use commercially reasonable, modern cryptographic means to protect your data, we cannot and do not guarantee its absolute security, and we make no representation or warranty that the Services are invulnerable to unauthorized access. You share your location through the Services with people you know and trust, at your own risk.

(d) What we can see: connection metadata, not your content. End-to-end encryption protects your content — your locations and the real names you give members. To operate the service, our servers do process a small amount of metadata that is encrypted in transit and at rest, but is not end-to-end encrypted: whether a device is currently online, the timestamps of check-ins (including when a phone goes offline), the device platform, whether the phone reports a simulated location, and internal, non-identifying tags our servers use to route messages and label alert records. The real name you give a member is encrypted (stored in a way that cannot be read by Kinfara) or stays on your circle's phones; those internal tags are not your real name. The safety-alert records we store (for example "went offline") never carry the name you typed: their titles use the member's internal tag or a neutral phrase such as "your child" or "Someone in your circle." This metadata is what lets the app tell you a phone went offline. Your phone's battery level travels inside the same encrypted message as its location, so we cannot read it; the low-battery alert is worked out on your circle's phones. It does not contain your precise location or your real names (the network address a phone connects from can only indicate an approximate area). Its limits: over time, connection metadata such as check-in timestamps and online/offline status can indicate coarse patterns — for example, roughly when a device is usually active — even though it never contains anyone's precise location. That is why we minimize this metadata and use it only to operate the safety service — never for advertising, profiling, or sale. So "we cannot read your data" refers to your content (locations and real names); it does not mean we are blind to the fact that a device exists or is currently connected.


6. Information we disclose — and our "no sale" commitment

We share personal information only with:

Kinfara does not sell your personal data, including as "sale" is defined in Nevada and California. Kinfara also does not "share" your personal data as that term is defined in California (that is, we do not disclose it for cross-context behavioral advertising), and we do not disclose it to data brokers or advertising networks. We honor Global Privacy Control signals. We extend these no-sale and no-share commitments to any successor: if we are ever involved in a merger, acquisition, or sale of assets, the commitments in this policy continue to apply to your information, and we will seek to require any successor to honor them, subject to applicable law, or give you notice and a choice as the law requires.

How we relate to data-broker laws. We collect information directly from the people who use the app — with whom we have a direct, consensual relationship — and we do not sell or license it. On that basis we do not sell or license your information and do not believe we are a covered "data broker" under US state data-broker-registry laws (including California, Texas, Oregon, and Vermont, and other states that adopt data-broker registries), subject to applicable law.


7. Our policy towards children & teens

Kinfara Circle is for consensual family safety only (never covert or adult-on-adult monitoring). Our Services are only intended to be used by younger members with significant parental or guardian involvement, and approval where required by applicable law.


8. Sensitive-location safeguard

Precise geolocation is treated as sensitive (CPRA "sensitive personal information," and sensitive data under other US state privacy laws that classify precise location as such). We minimize its collection, use it only for the requested safety purpose, and we do not build, infer, retain for analytics, sell, or disclose records of visits to sensitive places (e.g., health facilities, places of worship, shelters).

Health information. Kinfara does not ask for, collect or infer health information, and we do not infer visits to health-care facilities: your location is end-to-end encrypted and stored in a way that cannot be read by Kinfara, and the only places in the app are the ones a member draws (for example "Home" or "School"), checked on that member's own phone. Washington, Nevada and Connecticut residents can read our separate Consumer Health Data Notice at kinfara.com/consumer-health.


9. Data retention

For each category below we publish why we collect it, why we keep it, and when it is deleted — as COPPA (16 CFR §312.10) requires. Children's information is not kept beyond the windows below, with two exceptions: an item a specific legal obligation or a legal hold requires us to keep, kept only until that ends (see the end of this section); and a $1 verification claim whose charge was kept but never recorded, kept until our employees resolve it (they are alerted every day), because it is the last trace of that money.

Data Why we collect it Why we keep it at all Deleted
Live location (encrypted) To show the circle the current location they asked to see The current location answers "where are they now?"; the recent ones are what an emergency is reconstructed from Ordinary location data up to 25 hours: every 15 minutes we delete all ordinary location data more than 24 hours old. The newest location of each phone is exempt from that deletion and is kept at most 30 days — and sooner when that member or phone is removed or the account is deleted. All location data is encrypted to your circle's key — we cannot read any of it.
Arrive / leave alerts for saved locations (encrypted) To deliver "arrived / left" alerts to your circle Each record holds the member and the time; whether it was an arrival or a departure, and the saved location's name, are encrypted to your circle's key and we cannot read them 7 days, then deleted automatically
Location history So members can see where a member has been today The location history you actually look at is built on your own phone — our servers are not asked for it On your phone: the displayed location history follows your plan's window (Silver 7 days / Gold 30 days), capped at 30 days / 5,000 points per member. Stored points are pruned every time the app opens or updates the location history, and erased on sign-out or account deletion; if the app does not run, older cached points can remain until it next prunes them. On our servers: a rolling buffer of encrypted ordinary location data, up to 25 hours (deleted every 15 minutes: all ordinary location data more than 24 hours old goes). The newest location of each phone is exempt from that deletion and is kept at most 30 days, sooner when that member or phone is removed or the account is deleted.

⚠️ Why we keep 24 hours rather than nothing. When an SOS alert fires, the answer a family needs is "where were they in the hours around it?" — and the phones may have been off, offline, or the app closed, so they recorded nothing. That 24-hour buffer is the only place the emergency record can be cut from. It is encrypted to your circle's key: we hold it, and we cannot open it.
Incident records (encrypted) — only when an SOS alert actually fires So the circle can still answer "where was the member when the alarm went off?" — including when a phone was off, offline or the app was closed, and therefore recorded nothing itself A phone only records while it is running, and can hold nothing if it was off, offline or the app was closed. An emergency is exactly when that gap is likely, and exactly when the answer matters most. Kept up to 90 days from when each location was recorded (all of it gone within 91 days of the alert), then deleted automatically. Covers roughly a day either side of the alert. We cannot read any of it — it is encrypted to your circle's key, which we do not hold. Only your circle's devices can open it.
SOS / safety alerts To deliver the emergency to the circle and let them confirm it was handled A member must be able to see and acknowledge an alert they may have missed 30 days, then deleted. An alert still unacknowledged is kept longer so an emergency nobody has seen is never silently discarded — but never beyond 90 days, after which it is deleted regardless.
Check-in / "I'm OK" messages To let a member tell everyone they are safe, and to show that reassurance A member must be able to see a check-in they may have missed 30 days, then deleted. A check-in nobody has acknowledged is kept longer so a message no one saw is never silently dropped — but never beyond 90 days, after which it is deleted regardless. A check-in carries only who checked in and when — no location.
Connection & presence metadata — a device being online or offline, "went offline"/"reconnected" notices, and check-in timestamps To tell the circle a phone went offline, so no one is left guessing in an emergency The circle needs to know a phone is reachable now, and a missed "went offline" notice must still be seen The current-state values (online/offline, latest timestamp) are overwritten as new readings arrive — no history is kept. The alerts these generate (for example "went offline") are kept with the other safety alerts: 30 days, an unacknowledged one up to 90 days, then deleted. This metadata never contains your precise location or your real names (see §5B).
Age signal (from your app store) To apply the correct age-based protections and parental-consent rules the law requires We do not keep the store's answer — only the age group we derive from it is retained, under Account information; on Android we also keep a hashed version of Google Play's install ID for the app on your phone, and on iPhone a hashed version of Apple's app transaction ID (keyed hashes — we never keep the IDs themselves), only to act on a parent's withdrawal of approval in Google Play or through Apple The store's raw answer is never stored as a separate record; the derived age group follows the Account information row; the hashed install ID or app transaction ID is deleted with your phone's record (when the phone is removed or the account is deleted)
Account information (name/label, contact information (your email address), the name (and, from Google, the profile-photo link) your Google or Apple sign-in sends, circle membership, pairing codes, age group) To create the circle, route alerts to the right people, and apply the age-based protections the law requires Needed for as long as the account exists Until you delete your account, then within 30 days — except a minimal proof-of-consent record (your email, the consent version, method and date, the child's age range, and a hashed version of your account ID) we must keep to demonstrate verifiable parental consent under COPPA, retained in an access-restricted record and used only for that purpose (see §7). An account nobody has used for 12 months (no sign-in, no app use, no location shared by a phone in a circle it created or helps manage, and none by the phone it joined a circle with) is deleted after two email warnings, 30 and 7 days before (never while it has an active plan, an unacknowledged SOS or a legal preservation request - see Section 13); a sign-in account whose holder never accepted our Terms is deleted 30 days after it was created (see Section 13).
Encrypted key backup (the circle owner's signing key, locked by the owner's 12-word recovery phrase; we cannot open it) To let the circle owner take the circle back on a new phone when the old phone is gone Kept while the circle owner's account exists; replaced when a new backup is saved Deleted with the owner's account, together with the circle's other keys
Consent and sharing records (when location sharing was turned on or off, and the steps of a child's parental consent) To honour each member's sharing choice and to show that a child's consent was asked for and given Needed while the member is in the circle Kept while the member is in the circle; deleted when that member, or the account, is deleted (within 30 days). A record that a child's parental consent was requested or given, with the link to the member removed, is kept as described in "Proof that you gave consent" below.
Service event counts (sign-up completed, member added, phone paired, and which kind of alert fired — recorded with your 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 crash data is collected and no crash-reporting tool is in the app) To know the app works and where families stop Short window to investigate a fault Within 14 days (in practice sooner), then deleted automatically, including events recorded before anyone signs in. Before deletion we keep only daily totals, which contain no install identifier, no account and nothing tied to a person or device. They are de-identified statistics, not personal information, and are kept as such.
Saved locations (like Home or School) So the app can send your "arrived / left" alerts Needed while a saved location is set We do not store your saved locations. They stay on your own phone (and, on an iPhone, in your own iCloud or computer backup of it, if you turned one on), where they are checked, until you delete them or your account, and are never sent to us (if you chose a real map, the map drawn while you set one up reveals that area to our map provider — see Section 15). Your location and your "arrived / left" alerts, which include the saved location's name, do pass through our servers, encrypted so we cannot read them
Device & diagnostic (device type/OS, app version, internal device identifiers; the network (IP) address and browser type are kept in the separate security-log, sign-in-session, request-log and payment rows of this table) To operate and secure the app Needed while the account is active Device type/OS, app version and internal device identifiers: deleted within 30 days of account deletion; the network address and browser type follow their own rows in this table
Device identifiers for notifications To deliver safety alerts to your phone Needed to reach your phone Kept while the app is installed and registered, then removed
Alert-delivery receipts (internal log) To confirm that an alert we promised to send was actually dispatched So we can stand behind our safety promise and answer accurately if anyone ever asks "did the alert go out?" 7 days, then deleted automatically. Each receipt holds only an internal alert reference, your account id, a timestamp, the delivery channel and the delivery status (including any error the push service returned) — no member name, no location, no message content.
Support cases our employees record in our support system (who asked and what about) To answer you and keep a record of what we did Needed to handle your request and any follow-up Deleted 364 days after the case was opened (e-mails you send us are kept in our business mailbox for as long as necessary to fulfill the purpose for which you sent them, to resolve disputes, establish legal defenses and comply with applicable laws; ask privacy@kinfara.com to delete them at any time; see Section 15)
A $1 verification attempt (which account and which child it was for, and Stripe's payment reference) To match the $1 charge to the right consent request and to handle a refund or dispute Needed while the verification is open Deleted 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
$1 verification record (a payment reference, card brand and last four digits — never your full card) To prove parental consent (the $1 verification) It is part of the proof of parental consent The link to that child is deleted when the child or your account is deleted. The minimal payment evidence of the $1 itself (reference, brand, last four — unlinked from the child) is retained as consent and tax/chargeback evidence only as long as necessary to resolve disputes, establish legal defenses and comply with applicable laws, exactly as the Payment record row below describes — it is the same $1 charge, not a second one.
Payment record (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; for an App Store or Google Play purchase, the purchase and your account id); for a kinfara.com subscription started from the Android app, Google's one-time code for that link and the payment reports we send Google To verify parental consent (the $1 charge), process any web subscription, report a web subscription started from the Android app to Google as its program requires, record App Store and Google Play purchases, and answer tax and chargeback questions Tax and chargeback law Kept only as long as necessary to resolve disputes, establish legal defenses and comply with applicable laws, then deleted. If you delete your account, your email address, network address and device details are removed from it straight away. Google's one-time code for a link is kept only until Google accepts the first report (a link no subscription follows is deleted after 3 days), and the record of what we reported to Google (our random reference, the payment reference, the amount and the time) is deleted 400 days after the last payment it covers.
Terms and privacy-policy acceptance record (account id, accepted versions, time) To show which terms governed the account Needed to evidence which version the account accepted Kept while the account exists; after that, kept only as long as necessary to resolve disputes, establish legal defenses and comply with applicable laws — and never less than the Terms promise (at least 3 years, or one year after your subscription ends, whichever is longer) — then deleted.
Free-trial card check (a keyed one-way code made from the card used for a free trial (or, for another payment method, its account identifier, such as the Link email address) — never the card number — with when it was first seen, a trial count and the first subscription reference — no account id, name or email) So each card gets one free trial To stop the same card from starting repeated free trials 12 months after it was first recorded, then deleted automatically (checked every hour). It is kept for that time even if your account is deleted, so a deleted and re-opened account cannot start a second free trial with the same card.
Account-recovery activity (security log) To protect your account when someone asks to recover it To look into a misuse 90 days, then deleted automatically; a pending phone-change request is deleted when it is completed or cancelled, or with your account
Account-activation log (security log: when the 6-digit activation code we emailed you was used, and the network address and browser type it was used from) To protect your account when it is activated To look into a misuse 90 days, then deleted automatically; deleted with your account if that is sooner
Sign-in sessions (for each device you are signed in on: the network address and the browser type recorded for that sign-in) To keep you signed in, so your phone keeps sharing and can receive alerts Needed while you stay signed in on that device and keep using it Kept while you stay signed in on that device; deleted when you sign out on it, after 30 days without use, or with your account
Our hosting provider's request logs (the network address and browser type of each request your app or browser makes to our servers) To run the service and protect it from attacks Short window to investigate a fault or an attack 7 days, then deleted automatically by our hosting provider (Supabase)
Phone-unlink log (if our employees ever have to disconnect a phone from a circle: which phone, an internal reference to the member, when, and the reason) To keep a record of every action our employees take on a circle To look into a misuse 90 days, then deleted automatically; the link to the phone and member is removed at once when that member or the account is deleted
Record of service emails sent (which notice, to which account, when) So we never send you the same notice twice Short window to prevent duplicates 120 days, then deleted automatically
Website waitlist entry (email, optional first name, and the sign-up connection details in §3A) To run the pre-launch waitlist and guard against fake or abusive sign-ups Short interest window Within 12 months, then deleted automatically; sooner on request (see §3A)
Record that a deletion was carried out (your account id, which deletion step, and when — no name, email or location) To show, if a regulator asks, that we deleted what we promised to delete We must be able to evidence compliance even after an account is gone Kept only as long as necessary to resolve disputes, establish legal defenses and comply with applicable laws, once the account no longer exists, then deleted automatically
Proof that you gave consent (your email address, which consent, which method, which policy version, and when, the child's age range, and a hashed version of your account ID that we use only to delete the record on schedule) To show, if a regulator asks, that we obtained a parent's permission before collecting anything from a child — as the law requires We must be able to evidence compliance even after an account is gone The parent's email address and the consent details are retained after account or child deletion solely to demonstrate verifiable parental consent, as described in Section 7. A consent request that was never completed has no consent details; what survives it is set out in the "A child you added but whose consent was never completed" row of Section 13. We keep the completed-consent record only as long as necessary to evidence that consent and to establish or defend legal claims, and then delete it — it is not kept indefinitely.

We do not keep a long-term server-side history of where anyone has been. The everyday location history is built and kept on the phones of your circle's members. Our servers hold only, in encrypted form we cannot read: the rolling buffer described in the table above (every 15 minutes we delete all ordinary location data more than 24 hours old, so no ordinary location data is kept longer than about 25 hours); the newest location of each phone, exempt from that deletion and kept at most 30 days so your circle can see where a member was last; the place arrival/departure records (7 days); and the incident records created when an SOS alert fires — for the periods stated in the table. Non-location records (safety alerts, check-ins, account and billing data) are kept as the table sets out. This is deliberate.

What that means for your right to see a member's information. Your everyday location history is on your own phone, so you already hold it: open the History view to see it at any time. If the circle owner changes or loses their phone, the circle's keys can be handed over from the old phone, or, if the old phone is gone, the owner can take the circle back with the 12-word recovery phrase plus a code we email to the account, and the app then makes new keys for the circle. We keep only an encrypted copy of the owner's signing key, which we cannot open without those 12 words, so we cannot recover it for you. Recovery with the 12 words gives the circle new keys; records encrypted before it can be opened only on a member's phone that still holds the earlier keys. If the old phone is gone and the 12 words are lost, the owner cannot take the circle back — and we can never open any of it. Keep the phrase somewhere safe. Everything we do hold, you can delete from the app (Settings → Delete my account), and you can review it, receive a copy of it, or delete it by writing to privacy@kinfara.com — except the few records listed under "What survives deletion" in Section 13, which we must keep for the reasons stated there.

We delete or anonymize data as soon as it is no longer needed for the purpose it was collected for. Where we de-identify or aggregate data, we maintain it in de-identified form, do not attempt to re-identify it, and contractually require anyone who receives it not to re-identify it (consistent with CCPA/CPRA de-identification requirements). Deletion is automated and monitored; if the automated deletion ever fails, we are alerted. These windows describe our live systems; routine encrypted backups are deleted on a rolling cycle shortly afterward, and we retain an item longer only where a specific legal obligation or a legal hold requires it — then we delete it.

How long we keep information, in general. Kinfara retains the information we receive as described in this Privacy Policy for as long as you use the Services or as otherwise necessary to fulfill the purpose(s) for which it was collected, to resolve disputes, establish legal defenses, conduct audits, pursue legitimate business interests, enforce our agreements, and to comply with applicable laws. The purposes for which we process information may dictate different retention periods for the same types of information. The table above shows, for each kind of information, how short those periods are. We do not keep information indefinitely, apart from the two exceptions at the start of this section (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); once it is no longer needed for these purposes we delete or anonymize it.


10. Security

We use administrative, technical, and physical safeguards to protect your personal data, taking into account the nature of the personal data and the processing, and the threats posed. These include encryption in transit (TLS) and at rest; end-to-end encryption for your location and the names you give members; access controls and least-privilege; and secure development practices. No security system is impenetrable, and no method of transmission over the Internet or electronic storage is 100% secure, so we cannot guarantee absolute security. We operate a breach-notification process: if we determine that a breach affecting your personal information has occurred, we will notify affected individuals and the appropriate authorities without unreasonable delay, and within the timeframe the applicable US state data-breach-notification law requires.

How we will — and will not — contact you. Kinfara contacts you only by push notification, in-app message, and email. We never send text messages (SMS) and never telephone you (this does not cover a settlement conference you and we agree to hold by video call in a dispute under our Terms of Use). We never ask you to send us your password, a full card number, a card security code, or a government ID in a message or call. If a message claiming to be from Kinfara asks you to send any of these, it is not from us. For account activation, recovery, or a rights request you initiate, we may ask you to confirm a one-time code sent to your account email. That verification code is different from a card security code; do not give it to someone who unexpectedly contacts you. Email you send to us is not encrypted in transit to our mailbox, so please do not include card numbers or other sensitive details in an email to us. You are responsible for maintaining the secrecy of your password and ensuring the email address associated with your account(s) is accurate. If you believe your account has been compromised, change your password immediately via the applicable app or website; if you use Sign in with Google or Sign in with Apple, change the password of that Google or Apple account.


11. Where your data lives, and international transfers

The core data our app holds — your encrypted location and your account — is stored in the European Union, with Supabase. That is true for every user, wherever you live. We chose EU hosting as part of our data-protection approach. A few service providers necessarily handle limited data elsewhere, including in the United States — payments (Stripe), email (Resend and Zoho), our website (Cloudflare) and push delivery (Apple and Google) — each only as §15 describes. This is where we store your data, not where the Services are offered: Kinfara is operated from, and intended for users in, the United States (see our Terms of Use). Storing data in the EU is a data-protection choice, not an offering of the Services outside the US.

Where data is processed or accessed from another country (for example by a service provider or our employees), we implement appropriate safeguards to ensure that your personal information is treated securely and in accordance with this Privacy Policy, such as appropriate contractual and security terms for that transfer.

11A. Law enforcement and governmental requests

We think you are entitled to the real answer here, not a comfortable one.

Kinfara Labs LLC is a United States company. Under US law — including the CLOUD Act — a US company can be ordered to produce data in its possession, custody, or control, even when that data is stored abroad. Storing your data in the EU does not, by itself, place it beyond the reach of a US legal order. Any company that tells you otherwise is overstating what hosting location achieves.

What actually protects your family is not geography — it is that we cannot read the most sensitive thing you trust us with: your location is end-to-end encrypted. We hold your location only in a way that cannot be read by Kinfara. The usable keys live on your circle's devices, not on our servers. If we were compelled to produce a member's location history (the precise locations shared in the app), we would produce encrypted data we cannot decrypt — and we could not decrypt it for anyone else either.

Because that data is stored in the European Union, authorities there can also ask for it under their own law. Your information may be accessible to law enforcement or other authorities pursuant to a lawful request. The commitments below apply to any such request we receive. Your precise location (the one shared in the app) stays encrypted data we cannot read; the records we can read — such as your account details (including your email address), sign-in sessions, security and request logs, and payment records (see Sections 9 and 15) — could be produced only under valid legal process, or in the emergency case described in commitment 1 below. The network (IP) addresses in those sign-in, security and request records can indicate an approximate area (see §5B).

Our commitments if we receive a demand:

  1. We will require valid legal process and refuse informal or voluntary requests — except that we may disclose limited information in good faith where we reasonably believe it is necessary to prevent death or serious physical harm.
  2. We will challenge orders that are overbroad or legally defective, disclose only the minimum the law, or the emergency in commitment 1, actually requires, and contest such orders rather than quietly comply.
  3. We will tell you when we receive a request for your data. We won’t give notice when legally prohibited under the terms of the request; where we are gagged, we will say so as soon as we lawfully can. And we might not give notice in the case of emergencies, such as threats to a child’s safety or threats to someone’s life, in which case we’ll provide notice if we learn that the emergency has passed.
  4. Where and when we are able to, we aim to publish aggregate information about the legal demands we receive and how we respond.

We also hold an encrypted backup of each circle owner's signing key, locked by the owner's 12-word recovery phrase; because we do not hold the phrase, we cannot open it without the phrase — so it does not give us access to your location (see §5B and §9), and a legal demand for it produces only data we cannot decrypt.


12. Your choices about your information

At Kinfara, we respect your ability to know, access, correct, transfer (obtain a portable copy of), restrict the processing of, and delete your personal data. Depending on where you live you may also have the right to opt out of sale, sharing, targeted advertising and profiling, limit the use of sensitive personal information, withdraw consent, and appeal a decision we make on your request. Your right to know includes the categories of personal information we collect, the categories of sources it comes from, the business or commercial purpose for collecting it, the categories of third parties (if any) to whom we disclose it, and the specific pieces we hold — for Kinfara, the sources are you, your phone (including the age signal your app store gives it), your Google or Apple sign-in, our website when you join the waitlist, and Stripe, Apple or Google when you pay, the purpose is the safety service, and the recipients are the members of the circles you join (the core function), the service providers listed in §15 (Supabase, Cloudflare, Apple for push and App Store purchases, Google for push and Google Play purchases and for the reports its program requires for a kinfara.com subscription started from the Android app, TomTom, Stripe and its Link checkout, Resend, and Zoho), the professional advisors described in §6, a successor in a business transfer (merger or acquisition) as described in §6, with notice, and — only where valid law requires, or in the emergency case described in §11A — the legal or emergency recipients described in §6. An alert you trigger is shown only to the members of your circle (it is delivered through the push services listed in §15); Kinfara never contacts emergency services. We give the same rights to everyone in the United States, regardless of state. We never discriminate or retaliate against you for exercising any of these rights, and you will not receive a lesser standard of service for doing so — we note only that some information is necessary to provide the service, so if you delete your account we can no longer provide it to you.

No automated decision-making. We do not make decisions about you that produce legal or similarly significant effects based solely on automated processing or profiling.

List of third parties (Minnesota and where provided by law). On request, we will give you a list of the specific categories of third parties — and, where your state's law requires (for example, Minnesota), the specific third parties — to whom we have disclosed your personal information. For Kinfara, the third parties to whom we disclose your information are the service providers in §15 and the professional advisors described in §6, and — only as §6 and §11A describe — recipients where valid law requires it or where it is needed to prevent death or serious physical harm, and a successor in a business transfer. Beyond that, your location is shared only with the circle members you choose (at your direction — the core function), including the members your alert reaches when you trigger or confirm it. To a legal recipient — and even in the emergency case described in §11A — we can only ever hand over your precise location (the one shared in the app) encrypted, because we cannot read it — the network (IP) addresses in the readable sign-in, security and request records can indicate an approximate area (see §5B); an emergency disclosure therefore covers only the readable account records §11A lists. We do not sell it or disclose it to anyone else, except to a successor in a business transfer as §6 describes, which receives it still encrypted.

We honor these rights for everyone in the United States, regardless of which state you live in and regardless of each state's own thresholds or effective dates, as a matter of policy.

How to make a request. Use the in-app controls (Settings → Account & Subscriptions: Download my data, which saves at once what is on your phone and what our servers hold about your account, and Delete my account; Leave this circle on a member's own phone; a circle admin (the creator or a co-admin) can open a member and choose Remove from circle), or email privacy@kinfara.com from the address on the account. If you email us, we will process your request and send a confirmation email. We may ask you to confirm a code sent to your email; we never ask for a government ID or a card number to verify a rights request. We will only use personal information provided in the request to verify the requestor's identity or authority to make it, and to handle the request; we delete it once the request is handled, except what Section 9 lets us keep to resolve disputes, establish or defend legal claims, or comply with applicable law (for example the e-mails you send us). Authorized agents may submit a request with your written permission, and we may still confirm directly with you.

Timing. We respond within 45 days, extendable once by 45 days where the law allows, and we tell you if we extend (a deletion we complete within 30 days — see §§7 and 13). We do not charge a fee to process or respond to your request unless it is excessive, repetitive, or manifestly unfounded; if we decline a request or would charge for it, we tell you why first.

Appeal. If we deny your request, you may appeal our decision by contacting us at privacy@kinfara.com. If you have concerns about the result of your appeal, you may contact the attorney general in the state where you reside.

"Do Not Sell or Share My Personal Information" / "Limit the Use of My Sensitive Personal Information." We do not sell or share your personal information and have not done so in the past 12 months, and we do not use sensitive personal information for any purpose you can limit. You may still submit either request at privacy@kinfara.com, and we treat a Global Privacy Control (GPC) signal as a valid opt-out; we will confirm in writing.

A teen's own rights. A teen aged 13 to 17 holds their own member account and may exercise these rights over their own account — they can ask to review, receive a copy of, or delete their own data, and they can leave a circle from their own phone. For a child under 13, the verified parent on the account exercises these rights (see §7). A circle admin (the creator or a co-admin) can also remove a teen from the circle.

Your communications choices. Kinfara communicates only by push notification, in-app message, and email — never by SMS or phone call. Any optional email (for example our launch email to the early-access list, or an offer about a subscription) carries a one-click unsubscribe link, and you can turn push notifications off in your device settings at any time — but then SOS and other safety alerts cannot reach you on that phone, so we recommend keeping them on. You cannot opt out of the messages that are the safety service — SOS and other safety alerts, and essential account, security, consent, and billing notices — because they are how the service protects you and keeps your account secure. (This does not cover a settlement conference you and we agree to hold by video call in a dispute under the Terms of Use, which is not a routine service communication.)


12A. California Notice at Collection

For California residents, this is our notice at or before the point of collection: the categories of personal information we collect, the purpose of each, whether each is sold or shared, and how long we keep it. We do not sell or share any of it. End-to-end encrypted, so we cannot read it: your precise location; the real names you give members are likewise stored in a way that cannot be read by Kinfara. Other categories (email, billing, metadata) are encrypted in transit and at rest but are not end-to-end encrypted.

Category Purpose Sold or shared? Retention
Account information (name/label, contact information (your email address), the name (and, from Google, the profile-photo link) your Google or Apple sign-in sends, circle membership, pairing codes, age group) — Category: Identifiers; Characteristics of protected classifications under California or federal law (age) Create the circle, route alerts, and apply the age-based protections the law requires No Until you delete your account, then within 30 days
Website waitlist (only if you join it on kinfara.com: email, optional first name, and connection details - approximate location and time zone, network and its ASN, VPN/data-center flag, IP address, user-agent, referring page, and a check whether your email's domain can receive mail (only the part after the @ is looked up)) — Category: Identifiers; Internet or other electronic network activity; Geolocation (approximate, not precise) Tell you when Kinfara is available and keep the list free of abuse No The whole entry within 12 months (Section 3A)
Bot check (when you create an account, sign in or reset your password on our website or in the app, or join the waitlist: your IP address, your browser's or the app's web view's user-agent and TLS fingerprint, the page the check runs on, and the one-time check token) — Category: Identifiers; Internet or other electronic network activity Keep accounts and the waitlist free of automated abuse No We do not keep the token; Cloudflare runs the check under its own Turnstile privacy terms (Section 3B)
Precise location — sensitive (end-to-end encrypted) — Category: Geolocation (sensitive) Show consented circle members your location and raise safety alerts No Ordinary location data up to 25 hours on our servers (every 15 minutes we delete all ordinary location data more than 24 hours old); the newest location of each phone is exempt from that deletion and kept at most 30 days so the circle can see where it was last; when an SOS alert fires, a separate encrypted incident record keeps location for 90 days; on members' phones the location history stays within your plan's window (Silver 7 days / Gold 30 days, capped at 30 days / 5,000 points per member)
Arrive / leave alerts for saved locations (end-to-end encrypted) — Category: Geolocation Deliver arrive / leave alerts to your circle No 7 days on our servers, then deleted automatically
Saved locations (like Home or School) — not collected: they stay on your own phone (and, on an iPhone, in your own iCloud or computer backup of it, if you turned one on) — No Never on our servers
Safety-event data (SOS) — Category: Geolocation; Identifiers Deliver and let you acknowledge alerts No 30 days (unacknowledged up to 90)
Device & diagnostic data (the network (IP) address and browser type follow their own rows in §9) — Category: Identifiers; Internet or other electronic network activity Operate and secure the app No Kept while your account is active; deleted within 30 days of account deletion (the network address and browser type: see their own rows in §9)
Service event counts (recorded with the account id once you are signed in; an event before sign-in carries no account id) — Category: Identifiers; Internet or other electronic network activity Measure that the app works No Within 14 days
Payment record (payment and customer references, the amount, card brand + last four, your account id, email address, network address and device details, and which terms you accepted; for an App Store or Google Play purchase, the purchase and your account id; for a kinfara.com subscription started from the Android app, Google's one-time code for that link and the payment reports we send Google — never your full card) — Category: Commercial information; Identifiers Verify parental consent (the $1 charge), process any web subscription, report a web subscription started from the Android app to Google as its program requires, and record App Store and Google Play purchases No Kept only as long as necessary to resolve disputes, establish legal defenses and comply with applicable laws, then deleted. If you delete your account, your email address, network address and device details are removed from it straight away.
Device identifiers for notifications — Category: Identifiers Deliver safety alerts to your phone No While the app is installed and registered
Age signal (from your app store, if allowed; on Android, a hashed version of Google Play's install ID; on iPhone, a hashed version of Apple's app transaction ID) — Category: Identifiers; Characteristics of protected classifications under California or federal law (age) Apply the correct age-based legal protections, and act on a parent's withdrawal of approval in Google Play or through Apple No The store's answer is not kept beyond applying the protection; the hashed install ID or app transaction ID is kept with your phone's record and deleted when the phone is removed or the account is deleted
Children's data — a child's precise location is sensitive (end-to-end encrypted), plus profile — Category: Identifiers; Geolocation (sensitive); Characteristics of protected classifications under California or federal law (age) The consented family-safety features for that child No Per the children's windows in §9; a minimal proof-of-consent record is kept as COPPA requires
Other records (support cases and the e-mails you send us, the account-recovery security log, the account-activation security log, sign-in sessions, our hosting provider's request logs, the terms-acceptance record, the free-trial card check, the record that a deletion was carried out, proof of consent, alert-delivery receipts, the record of service e-mails sent, the phone-unlink log, check-ins, connection and presence records (a phone going offline or reconnecting), the location-sharing on / off and consent-step records, the $1 verification attempt and the $1 verification record) — Category: Identifiers; Commercial information; Internet or other electronic network activity; Characteristics of protected classifications under California or federal law (age) Answer you, keep accounts secure, show what the law requires us to show, give each card one free trial, avoid sending a notice twice, tell the circle a phone went offline, honour each member's sharing choice, and match and prove a parent's $1 verification No As set out for each in Section 9

We do not sell or "share" (as the CCPA/CPRA define those terms) any category above, and have not in the past 12 months; disclosures to our vendors are limited to service providers/contractors bound to use the data only to provide their services to us, and to professional advisors (§6) under a duty of confidentiality, apart from the narrow own uses the law allows a service provider and that §15 lists (such as keeping its own service secure and preventing fraud), and payment details you choose to save with Link, which Stripe holds for you under its own privacy policy. We do not use sensitive personal information for any purpose you can limit, so no "Do Not Sell or Share" or "Limit the Use of Sensitive Personal Information" action is required — but you may still submit either request (see §12). Retention detail is in §9.


13. Deleting your information

You can leave at any time — whether or not you have accepted these Terms or this Privacy Policy, and for any reason, including that you no longer agree to them.

If you have not accepted yet: simply do not continue, and uninstall the app. Before you sign in, the bot check can process connection details as described in Section 3B, and request logs and service events can be recorded as described in Section 9; a service event before sign-in carries no account id. Joining our website waitlist is separate and is covered by §3A. Signing in comes before accepting, so if you signed in and stopped there, our servers hold the sign-in account you created, including your email address; if you never accept, we delete it automatically 30 days after it was created; to have it deleted sooner, write to privacy@kinfara.com from that address.

If you have set up or joined a circle: the single step that removes your data on our side — except the few records listed under "What survives deletion" below — is deleting your account (in the app: Settings → Delete my account; or from the web page kinfara.com/delete-account, as Apple and Google require). Deleting your account wipes the data we store for you — your circle membership, your linked device, and your encrypted location and safety-alert data — and removes your login itself. If you created a circle, deleting your account closes it: its other members lose access to it, and we send each of them a notice on their phone that the circle was closed. If you verified a child under 13, deleting your account removes that child from the circles where you gave the consent and deletes their data there, except the consent record described in this section.

Because your location is end-to-end encrypted with a key kept only on your circle's own devices — one we never hold in usable form — we can never read it, and deleting your account removes the encrypted location and safety data we hold for you; the only records that survive are the ones listed under "What survives deletion" below. Uninstalling the app then stops all collection and removes the app from your phone.

If a member dies. A family member or the person handling the member's estate can ask support@kinfara.com to close the account; we close it only after we receive official proof of death (such as a copy of the death certificate) and confirm the request, and then delete it as this section describes.

Deletion windows, stated plainly. These are the timeframes our automated deletion actually runs on:

What When it is gone
Anything we hold about a member, child, or an account, after you ask us to delete Within 30 days of your request, except the records listed under "What survives deletion" below
A child you added but whose consent was never completed 24 hours after the child was added, the child is removed automatically, and the child's profile, the name/label the parent typed and the request details are deleted (nothing was collected from the child or the child's phone in the meantime). 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 9. 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
Location data on our servers (end-to-end encrypted, stored in a way that cannot be read by Kinfara) Ordinary location data up to 25 hours: every 15 minutes we delete all ordinary location data more than 24 hours old. The newest location of each phone is exempt from that deletion and kept at most 30 days (sooner when that member or phone is removed or the account is deleted).
The encrypted incident record kept around a fired SOS alert Kept up to 90 days after each location it holds was recorded — all of it gone within 91 days of the alert; sooner if the member is removed from the circle or deletes the record themselves. Only if we receive a valid legal request to preserve records (for example a court order or a law-enforcement preservation letter) do we keep a sealed, still-encrypted copy of the affected records, until that request ends
Safety alerts themselves 30 days; an alert nobody acknowledged is kept up to 90 days, never longer
An account nobody has used for 12 months (no sign-in, no app use, no location shared by a phone in a circle it created or helps manage, and none by the phone it joined a circle with) Each warning email (30 days and 7 days before) states the exact deletion date, and the account is deleted on that date unless it is used first — never while it has an active plan, an unacknowledged SOS, or a legal preservation request
A sign-in account whose holder never accepted our Terms 30 days after it was created

What survives deletion: the parent's email address together with the consent details (which method, which policy version, and when) and the child's age range, kept only because the law requires us to be able to show that consent was obtained, and kept only as long as necessary to resolve disputes, establish legal defenses and comply with applicable laws, then deleted (this record holds no name and no location, and no link to the child, a device or a network address - only a hashed version of the account ID, used to check whether the account still exists); for a child whose consent was never completed, the records set out in the row "A child you added but whose consent was never completed" above; a record that the deletion was carried out (your account id and when), kept only as long as necessary to resolve disputes, establish legal defenses and comply with applicable laws, then deleted; the record of which Terms and Privacy Policy versions the account accepted (account id, versions, time), kept only as long as necessary to resolve disputes, establish legal defenses and comply with applicable laws, then deleted; the payment record described in Section 9, with your email address, network address and device details removed, kept only as long as necessary to resolve disputes, establish legal defenses and comply with applicable laws, then deleted; and, if a card or other payment method was used for a free trial, a keyed one-way code made from it (never the card number, no account id), deleted 12 months after it was first recorded; a $1 verification claim whose charge was kept but never recorded, kept until our employees resolve it as Section 9 describes; a support case you opened, deleted 364 days after it was opened, with the e-mails you sent us, kept as Section 9 describes; and anything a specific legal obligation or a legal hold requires us to keep, only until that ends. See the retention table in Section 9 for exactly what is deleted and when.


15. Service providers

We use a deliberately small set of processors, each listed in the table below and contractually bound to use data only on our instructions, except the limited own uses of Cloudflare (its bot check and public DNS resolver), Stripe (fraud prevention, security, improving its services, and payment details you save with Link), TomTom (de-identified map-request data) and Google (Firebase push service data) noted in the table; Apple and Google also handle App Store and Google Play payments as the stores, under their own privacy policies, and Google receives the reports its program requires for a kinfara.com subscription started from the Android app. No advertising SDKs and no behavioral-analytics trackers are used — the app contains no Google Analytics, Firebase Analytics, Amplitude, Mixpanel, Segment, AppsFlyer, Meta SDK, Sentry or Crashlytics. Our own analytics are first-party and carry no coordinates, names or emails.

Who What reaches them Why
Supabase — hosting Encrypted location (stored in a way they cannot read), the names you typed, stored encrypted so Supabase and we cannot read them, account email, the name (and, from Google, the profile-photo link) from a Google or Apple sign-in, circle membership, device identifiers for notifications, internal device identifiers, Google Play's install ID (Android only) or Apple's app transaction ID (iPhone only), received only to be hashed on arrival with the secret key we hold (only the keyed hash is stored), and the network addresses and browser types in sign-in sessions, security logs and request logs (§9) Runs the service. They store the encrypted data; they hold no key.
Cloudflare — website host & edge network Website requests; for a waitlist sign-up, the connection details described in §3A (approximate location, network/ASN, VPN flag, IP address, user-agent); for the bot check (§3B), your IP address, browser user-agent and TLS fingerprint, the page it runs on, and the Turnstile token; for the deliverability check (§3A), the domain of a waitlist email address Serves kinfara.com, runs the Turnstile bot check (§3B), answers the email-domain lookup (§3A) and adds the sign-up connection details. Cloudflare also acts for itself for the bot-check details (to improve its bot detection, under its Turnstile privacy terms) and for the domain lookup (its public DNS resolver keeps lookups up to 25 hours and uses them only in aggregate, under its resolver privacy commitments). The app uses Cloudflare only for this bot check, when you create an account, sign in or reset your password.
Apple APNs / Google FCM — push The alert that is being delivered, and the recipient device's push identity Delivers safety alerts directly to a member's phone. Google provides Firebase Cloud Messaging as our service provider and, under its Firebase terms, also uses Firebase service data to maintain and improve Firebase. Apple delivers alerts to iPhones under Apple's own developer terms; Apple publishes no separate data-processing agreement for this.
Apple — App Store purchases If you subscribe in the iPhone app: your purchase, and your Kinfara account ID (a random code, not your name or email) that we attach to it Apple takes the payment; we check the purchase with Apple to switch your plan on.
Google — Google Play purchases, and reports of kinfara.com subscriptions started from the Android app If you subscribe in the Android app: your purchase, and your Kinfara account ID (a random code, not your name or email) that we attach to it. If the Android app sends you to kinfara.com and you subscribe there: for each payment and refund, the amount, the time, the country (United States), Google's one-time code for that link, a random reference we create and, for a partial refund, the payment service's reference for that refund — never your name, email or Kinfara account ID Google takes the payment; we check the purchase with Google to switch your plan on, and Google tells us when it renews, is cancelled or is refunded. For a kinfara.com subscription started from the Android app, Google's program for such links requires us to report each payment and refund.
TomTom — map tiles See the note below Draws the map, in every map style.
Resend — email delivery Your email address and the text of the email being sent (welcome and sign-up codes; parental consent and the $1 verification; "someone new can see your location" notices; password-changed, device-takeover and recovery notices; subscription offers, confirmations and reminders) Sends the emails the service needs. Never a child's name or anyone's location.
Stripe — the $1 parental-consent charge, and subscriptions bought on kinfara.com Your card details, entered on Stripe's own checkout page (they never touch our code or our servers); for the $1 verification we also give Stripe your email address and internal reference numbers for your account and for the child being verified (no names); we receive payment and customer references, the amount, the card's last four digits and brand, and the time. When you start a free trial on kinfara.com we also read the card's (or other payment method's) identifier from Stripe and keep only a keyed one-way code made from it, never the card number, so each card gets one free trial (see "Free-trial card check" in Section 9). We keep that reference as our proof of consent only as long as necessary to evidence your consent and to establish or defend legal claims, and then delete it — it is not kept indefinitely Processes the $1 payment used for verifiable parental consent under COPPA. If you subscribe on our website, Stripe also processes that subscription: it renews automatically at the price shown until you cancel, and you can cancel any time by signing in at kinfara.com and opening Manage subscription or by e-mailing "Cancel my subscription" to support@kinfara.com from your account's address. A subscription bought on kinfara.com is sold through Link, Stripe's checkout: Link receives your payment details, collects any sales tax, sends your receipts and handles order support. Stripe also uses payment information for its own purposes, such as preventing fraud, enhancing security and improving its services, under its own privacy policy; payment details you choose to save with Link are held by Stripe under that policy.
Zoho Mail — our business mailboxes The emails you send us (your address and what you write), including any reply to our website waitlist emails (§3A) Lets us answer support and privacy requests and keep our own records.

The one you should read carefully — map tiles. To draw a map around a member, your phone asks a map provider for the square tiles covering that area. Those requests reveal approximately where that member is (to tile precision — roughly a neighbourhood block at close zoom), along with your phone's IP address. This happens on your device, not on our servers — we never send anyone's location to a map provider, and we could not, because we cannot read it. But the request still leaves the phone.

This applies whenever the map is on screen: the live map, the location-history map, and the screen where you save locations such as Home and School — that last one reveals those places specifically.

Provider used: TomTom, for every map style. The request identifies the app, not your account: no name, email, or account identifier is sent with it. TomTom processes these requests for us and, under its terms, may also use them in aggregated, de-identified form for analytics and to improve its products.

You choose whether this happens at all. The first time a map would be drawn — before the app requests a single map tile — it asks whether to draw a real map or show a location without one. Neither option is preselected. If you choose position-only, nothing is sent to any map provider: you still see exactly where a member is, how far away and in which direction, how accurate the fix is, and how recent it is, all worked out on your own phone. You can change your mind at any time in Settings → Show a real map.

The screen where you mark home and school follows the same choice: if you chose a real map, it draws one around the place you are setting up, which reveals that place to TomTom; if you chose position-only, it shows the place without a map.


15A. Links to other websites and services

The app and our website sometimes link to services run by others — for example Stripe's checkout page, Apple's App Store or Google Play, or a map provider's attribution page. Anything you provide to one of those services is handled under that service's own privacy policy, not this one, and we are not responsible for their practices. The named processors we rely on to run Kinfara are listed in Section 15.


16. Changes to this privacy policy

We will post updates with a new "Last updated" date. We offer access to archived versions for your review: the previous version (last updated 2026-10-24) is at kinfara.com/privacy-2026-10-24; for older versions, write to privacy@kinfara.com. Any information that is collected through your use of our Services is covered by the Privacy Policy in effect at the time such information is collected. We will not reduce your rights under this Privacy Policy without your explicit consent. For a material change, we tell you at least 30 days before it takes effect, in the app, and ask you to accept it in the app. We will not use information we already hold in a materially different way from what this policy said when we collected it unless you agree first. For a child under 13, we ask the parent for new consent before any material change in how we collect, use or share the child's information. If you are only on our website waitlist, we post the change here, and you can ask us to remove your waitlist entry at any time (privacy@kinfara.com).


17. Contact us if you have questions or concerns

Kinfara Labs LLC is a US company serving the United States only.


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