Skip to content
KinShield

Privacy policy

Last updated: 12 November 2026.

In short. KinShield keeps what it needs to work: your name, your email, the circles you are in and a record of the checks you make. It never listens to your calls, never tracks where you are, never reads your contacts and never shows you adverts. We do not sell your data. You can delete everything from Settings at any time.

Who we are

KinShield is provided by Cre8Tive Synergy, the trading name of a sole trader in the United Kingdom, who decides how your personal data is used (the "controller").

Questions about your data, or to use any of your rights: privacy@kinshield.app.

What KinShield is

KinShield is a second channel for a phone call. Families pair their phones, usually in person, then ask for the code on the screen. With Pro, a circle owner can also add someone far away, checked through two phone calls and a day’s wait. Organisations that actually use KinShield can show a branded card on a customer’s phone.

KinShield is not a deepfake detector, not a call recorder, not a bank, and not a payment rail. It does not listen to your calls. It does not scan audio for clones. A green tick means a real check ran — never a guess, a timer, or an error treated as success.

This policy covers KinShield (circles, pairing, words, safe word, Learn, optional organisation cards), the website kinshield.app, and the console that staff of an organisation using KinShield sign in to.

What we collect, and why

  • Your account. Your name, email address and sign-in identifiers from Clerk, our sign-in provider, and a profile photo if you add one (Clerk stores it). We use them to run your account and so your family can recognise you. Legal basis: providing the service you signed up for (contract).
  • Your circles. Circle names, the names people are shown by, and any challenge questions a circle sets. A safe word and challenge answers are stored only as salted hashes, never as the words themselves. Legal basis: contract.
  • Pairing. Each phone’s public key and a fingerprint of each pair secret. The pair secrets that make the words stay on the two phones; the server never has them. Legal basis: contract.
  • History of checks. Who checked whom, which method (words, a check sent to their phone, safe word, challenge question), whether it passed, and when. Never call audio or a recording. Legal basis: contract.
  • Notification tokens. If you allow notifications, a push token so someone in your circle can ask your phone to check. On iPhone, Live Activity tokens so a check can show in the Dynamic Island and on the Lock Screen. Legal basis: contract. You can refuse the permission, or turn off Live Activities in iPhone Settings.
  • Your phone. Each phone makes its own random key, which no backup can move to another phone. The app sends it to us, and we keep only a one-way hash of it. With the hash we keep when we first and last saw the phone, whether it is on hold or kept off, how it was confirmed, and, where we know it, whether it is an iPhone or Android. We use it to tell a phone that was restored or newly signed in from one that simply updated, so the people in your circle can be told. The key is random: it contains nothing about you. The key stays on your phone when you sign out or delete your account. Our record of it is deleted with your account. Legal basis: our legitimate interest in keeping your account and your circle safe.
  • Joining from far away (Pro). If a circle owner invites someone far away, we keep the invite: the owner’s own name for that person (only the owner sees it), who opened the link, and when each step happened. The link’s secret is kept only as a one-way hash. To check the two phone calls, the two phones exchange public keys and random values through us, and each sends a fingerprint of the secret they worked out. The secret itself, and the numbers you read to each other, never reach us. If the person joining has paired in person with other people, those people get a notification naming who is joining and who invited them, so they can stop it if something is wrong. It never names the circle. Legal basis: contract.
  • Joining the beta on Android. Until Google Play opens KinShield’s test to everyone, it lets in only members of KinShield’s Google Group, so joining on Android means joining that group with your Google account. Google runs the group; as its owner, we can see each member’s email address. We use it to let you into the test, and you can leave the group at any time. Legal basis: contract.
  • Subscription status. If you buy KinShield Pro, Apple or Google takes the payment. We store whether Pro is active, which plan and its dates, never your card details. Legal basis: contract.
  • Crash reports (optional). On builds where it is switched on, a crash report goes to Sentry with email addresses, phone numbers, tokens and secrets removed first. No session replay and no screenshots. Legal basis: our legitimate interest in keeping the app working.
  • Backup (optional). If you turn it on, your phone’s pairing key, the secret shared with each person you paired with, and your circle’s safe word are saved to your own iCloud Keychain (iPhone) or Google account backup (Android), so a new phone signed in to the same account can restore them. Apple and Google encrypt them end to end. KinShield’s servers never receive them. Turning backup off, or deleting your account, deletes the backup.
  • Organisations. Staff of an organisation using KinShield type their brand details, case references and agent names. An organisation can only send a card to a customer who has already linked them from the Providers screen, and webhook messages to the organisation never include customer profile ids or emails.

What we do not collect

  • Call audio, microphone recordings or voicemail.
  • Your location, precise or approximate.
  • Your contacts. The app asks for no contacts permission.
  • Your phone number.
  • Advertising identifiers. There are no adverts, analytics or tracking in the app or on the website.
  • Card numbers or bank details. Sending money inside the app is switched off.

Permissions

  • Camera — to scan a family member’s pairing code, or to take a profile photo if you choose.
  • Local network and Bluetooth (iPhone) — to find a family member’s phone in the same room when you pair. Your first name and a one-time pairing code (no secret) go directly between the two phones; none of it is sent to us.
  • Notifications — optional, so a family member can ask you to check.
  • Photos — optional profile photo. The system picker hands KinShield only the photo you choose.

None of these listen to a phone call.

Who can see what

People in your circle, whether you paired in person or they joined from far away, can see what that circle needs: names, the current words with you, the history of checks in that circle, and your profile photo if you set one.

While someone joins from far away, the owner who invited them sees the name they signed up with and how new their account is, and they see the owner’s name. Nobody is told who stopped a join.

A linked organisation sees the outcome of its own check (approved, declined, expired) and the case reference it already had. It does not receive a directory of KinShield families.

Demo names such as Northbank or Orbit Mobile are fictional. They are not partners and they do not receive your data.

We do not sell personal data, use it for advertising, or give lists of families to anyone.

Service providers

These companies process data for us, under contracts that limit them to providing their service:

  • Clerk — sign-in and profile photos (United States).
  • Supabase — our database and server functions (Ireland, in the EU).
  • Expo — delivers notifications (United States), through Apple Push Notification service on iPhone and Google Firebase Cloud Messaging on Android.
  • Apple and Google — the app stores, Pro subscriptions, iPhone Live Activities, and the optional backup.
  • Sentry — crash reports, only on builds where it is switched on.
  • Cloudflare — hosts kinshield.app.
  • logo.dev — supplies an organisation’s logo when one is shown in the app; it receives your device’s IP address and nothing else.

Data outside the UK

Our database is in Ireland, which UK law recognises as giving adequate protection. Where a provider above handles data in the United States, it does so under the UK International Data Transfer Addendum to the European Commission’s standard contractual clauses in its data processing terms, or under the UK–US data bridge where the provider is certified.

How long we keep it

  • Your account, circles and pairings: until you delete your account, or until you leave a circle.
  • The record of each phone you use: until you delete your account.
  • A notice that a phone was put on hold, and who was told: 30 days after the hold ends.
  • History of checks: 12 months.
  • Expired codes, pairing sessions and invites, including invites to join from far away: 30 days after they end.
  • Notification tokens: removed when you sign out, or after 90 days unused.
  • Records of store subscription events: 24 months.

A daily job deletes data when these periods end.

When you delete your account (Settings → Delete Account), we delete your data straight away: your profile, sign-in, the circles you own and everything in them, your memberships and pairings, your notification tokens and the record of your phones. The pairing secrets on that phone are removed too; the phone’s own random key stays, and holds nothing about you. Checks you made are deleted with your account; a check someone else made of you stays in their circle’s history, without your account attached. See Delete your account.

Your rights

Under UK data protection law you can ask to see the data we hold about you, correct it, delete it, restrict or object to how we use it, and receive a copy to take elsewhere. Delete Account in Settings deletes everything at once; for anything else, email privacy@kinshield.app from the address you sign in with. We reply within one month.

If you are unhappy with how we handle your data, you can complain to the Information Commissioner’s Office: ico.org.uk or 0303 123 1113. We would like the chance to put it right first.

Cookies and storage on your device

kinshield.app runs no analytics or tracking scripts, and sets one cookie of its own: if you enter an invite code on our beta sign-up page, a cookie on your device remembers that for 30 days, so you are not asked for the code again. It holds no information about you and is not used to track you; it is strictly necessary to show you that page, so it needs no consent. Cloudflare, which hosts the site, may set a strictly necessary security cookie to block automated attacks.

The app keeps on your phone only what it needs to work: your sign-in session, your pairing secrets and the phone’s own random key, a copy of your circle so the app opens with poor signal (all in the phone’s secure storage), and your settings. This is strictly necessary for the service, so it needs no consent.

Automated decisions

KinShield makes no automated decisions about you that have legal or similarly significant effects, and does no profiling.

Children and young people

KinShield is for people aged 13 and over. If you are under 18, we suggest using it with a parent or guardian. If we learn that an account belongs to someone under 13, we delete it.

KinShield is designed with the UK Children’s Code in mind: private by default, no location, no public profiles, nothing shared outside the circle, and no prompts nudging you to share more.

If you are in the United States

  • We do not sell your personal information or share it for cross-context behavioural advertising.
  • kinshield.app does not track you across websites, so it treats every visit the same whether or not your browser sends a Do Not Track signal.
  • Wherever you live, you can ask to access, correct or delete your information at privacy@kinshield.app, and we will act on it.
  • KinShield is not for children under 13.

Changes

When this policy changes, we update the date at the top. If a change affects what we collect or how we use it, we will tell you before it takes effect, in the app or in the notes for the update that brings it.