Privacy policy
Last updated: 16 November 2026. Effective: 10 November 2026.
This policy explains what CheckIn collects, why we use it, who helps us provide the service, how long information is kept, and the choices you have. If anything is unclear, email contact@checkin-chicken.com.
1. Who we are
CheckIn ("we", "us", "our") operates the CheckIn dating service. We decide how the personal information described in this policy is used. Contact us at contact@checkin-chicken.com.
2. Information we collect
We collect information you provide, including your email address or the Apple or Google account you sign in with, your date of birth and age, name, gender, who you are looking for and your other dating preferences, photos, voice prompts (your spoken, typed or GIF answers, and any question you write yourself), which spoken answer is your Reveal pick and which, if any, you pin to your profile card, the song you add to your profile (one you choose from Apple Music, or a song name and artist you type in), interests, any pronouns and languages you add, whether your star sign is shown and the sign if you choose it yourself, a phone number or Instagram details if you choose to add them, and support messages. Every member also has a "Met in person?" code, a random code we create for you that you can show as a QR code. While your code is showing on your "Met in person?" page, the app tells us so every 30 seconds, and we note the time your code stops working. If you added a bio or a voice intro, which we stopped showing on 9 October 2026, we still hold it with your account, but it is no longer shown to anyone. When you allow it, the app reads your phone's location while the app is open and refreshes it at most every five minutes. The app asks your phone for a low-accuracy reading, but we treat the coordinates as precise location data and keep them private. When you finish signing up, we also save the name of the area you were in, your London borough, your council area elsewhere in the UK, or your country if you're outside the UK, not the spot itself. When you scan someone's code in the app, your phone's camera looks for the code. The camera picture stays on your phone, and only the code it reads is sent to us. Nothing from the camera is recorded or stored. If you scanned someone's code with your phone's camera before you had CheckIn and chose to get the app and match, we save a match for that code against a random number that only your phone keeps: CheckIn's App Clip keeps it in your phone's keychain, or our web page keeps it in your browser. Once you have signed up, CheckIn sends it to us so we can match you with the person whose code it was, and then forgets it. Nothing is copied to your clipboard, and the app never reads your clipboard. We also collect activity such as likes (including which voice prompt a like was on), passes, Super Likes, rewinds, Reveals, Spotlights (including the area you were in when you switched one on), matches and held likes, "Met in person?" activity (when you open your code, your scans, including a match made by a scan, a scan that could not make a match and why, and when you get a new code), "Met in person?" matches saved for someone who did not have CheckIn yet (whose code it was, when, which account used it, and whether it became a match), Check-Ins (including times you book for a CheckIn later), chat messages (including typed messages, GIFs, songs you send from Apple Music, voice notes and reactions), a goodbye message if you choose to leave one when you unmatch someone, contact-sharing choices, blocks, reports, safety checks, moderation and verification status, whether you have paused your profile, when, and the reason you chose, referrals (including one-way codes of the phones you use CheckIn on, so your own code can't be used on them), purchases, credits, weekly allowances and entitlements, notification choices and device registrations, the weekly jokes we gave you and when you closed one, and the free Spotlights we gave you. Our service and providers also receive technical information. This includes account and session identifiers, IP address (including when someone opens a "Met in person?" code's App Clip or web page, described in section 5), device and app information (including your phone's time zone, which features your version of the app supports, when you last used the app and which days you used it, and which sign-up pages you opened), call connection metadata, timestamps, our own analytics, audit records, error or security events, and crash and error reports (described in section 9).
3. How we use your information
We use this information to create and secure your account; build and show profiles; provide likes, matches, held likes, Reveals, Spotlights, "Met in person?" matches, chat, Check-Ins and calls; leave out of held likes, for now, people who have not used the app for 14 days; show people who have used the app recently earlier in Discover more often, so likes tend to reach people who will see them; verify identity and age; deliver notifications, holding some until the morning in your own time zone (one reminder about "Met in person?", 48 hours after you join, and one request for an App Store review, at least five days after you join and an hour after a match, are set by the app on your phone, not sent by us), and a weekly joke on Wednesday evenings unless you turn it off; process and restore purchases and track weekly allowances; operate referrals and stop the same person or phone claiming a reward twice; make sure the free welcome Spotlights are given once per person; give you a free Spotlight on your birthday, using your date of birth, and one when you have gone two weeks without a like (at most once every 90 days); provide support; investigate reports; prevent fraud and abuse, including limiting how many codes one member can scan in a short time, and stopping a banned member joining again on the same phone; enforce our rules; understand and improve how the service performs, including finding and fixing crashes and errors, and counting how many members come back to the app and how far people get through signing up; count how many members joined in each area, twice a week, as totals per area, to see where CheckIn is growing and where to advertise (only CheckIn's team sees these totals, never as individual members or locations); and comply with law. Some decisions are made automatically, without a person looking first. When someone reports you, we decide what happens from the reports and our records alone; we never listen to voice notes or transcribe anything. A report of threats, harassment, unwanted sexual content or nudity closes your account straight away if it passes our reliability checks (for example, that the person reporting you had actually been in touch with you, has passed the ID check, finished signing up at least 3 days before and has a good record); otherwise your account is hidden for up to 72 hours and closed if someone else reports you for one of those things. Reports from several different people who had been in touch with you, or who have passed the ID check, lead to a warning, then a 7-day pause, then a 30-day pause, then closure. A report from someone who finished signing up less than 3 days before is kept but does nothing by itself. A report that you might be under 18 hides your account until you pass an ID check; your matches are kept. When you finish signing up, an automated tool estimates the age of the face in your profile photos, starting with your main photo and moving on until one shows a face clearly. If the estimate suggests you could be under 21, your profile is hidden until you pass the ID check in section 6. Each photo you add is also checked automatically before it's saved, and one that looks like it shows nudity or sexual content is refused and not stored. If none of your photos shows your face clearly, we ask you to add one that does, and check again when you do. If the ID check in section 6 shows you are under 18, or the date of birth on your ID does not match the one you gave us, the check is refused, and an under-18 account is suspended. You can appeal a pause, or a closure in its first 30 days, once in the app: we decide the appeal automatically by checking the reports behind the decision again. You can ask a person to review any automatic decision by emailing contact@checkin-chicken.com.
4. Legal bases (UK & EU GDPR)
Depending on the processing, we rely on performing our contract with you, our legitimate interests in operating and protecting CheckIn, your consent where we ask for it (such as camera, location and notification permissions, which you can turn off in your phone's settings), your explicit consent for the quick selfie described in section 6, which compares your face and which you give by choosing to take it, and compliance with legal obligations. Where information such as identity evidence may reveal sensitive data, the verification provider handles it under the permissions and legal bases presented in its flow. You can withdraw consent, but that does not affect earlier lawful use. Counting members by area relies on our legitimate interests in growing CheckIn; it uses only totals and never singles anyone out.
5. Profiles, discovery and other users
Other members can see the profile information the app presents to them: your name, age, gender, photos, voice prompts (each question with your spoken, typed or GIF answer), the song you add (its name, artist and cover, and a 30-second preview from Apple Music they can play in the app; a song you typed in shows its name and artist only), interests, any pronouns and languages you add, your star sign if you switch it on (worked out from your date of birth, or the one you choose; your date of birth itself is never shown), who you are looking for, the name of your area, how far away you are in whole miles, and your verification badge. Pronouns, languages and your star sign are optional, and we never use them to decide who you see or who sees you. If you pin a spoken answer to your profile card, its question is shown on your card in Discover and the answer can be played from there. Distances are worked out from roughly 1 km squares, and your exact coordinates are never shown to anyone. Matches can also see whether you were active in the app today (a yes or no, never a time) and anything you share through matching, Check-Ins and chat. Your phone number and Instagram handle are only shown to a match you choose to share them with. Your photos are only sent to members who are signed in and allowed to see you, never to someone you have blocked or who has blocked you, and each link to a photo stops working within about 12 hours. Discover and new likes only happen between people whose age range and distance settings include each other (apart from "Met in person?", below). Once someone has liked you, they stay on your Likes page wherever either of you is, and liking them back makes a match even if one of you has since moved or changed your age range. When you like someone, they can see that someone likes them, blurred, can play your Reveal pick before seeing who it is, and may use a Reveal to see who. Your Reveal pick is one of your spoken voice prompts: your first, unless you choose another. The question it answers is not shown with it. If you like one of their voice prompts, they can see which one. If someone likes you back while you already have five matches, it does not become a match yet: we hold it, and only you are told, as a number, until you free up a slot and choose to match. To them it looks like a like that has not been returned, and they are not told you have five matches. While you have five matches, you do not appear on anyone's Likes page. If you pause your profile (at the bottom of Profile), you don't appear in Discover or on anyone's Likes page, your "Met in person?" code doesn't work, and nobody new can match with you. When you pause, you choose why. If you are taking a break, your matches stay as they are. If you are taking things further with one match, you choose which one: that match stays and your other matches end, and the likes and passes between you and them are deleted, so you could meet and match again in future. Everything else is kept until you resume. "Met in person?" is for people who have met face to face. Anyone who scans your code in the app matches with you straight away, without either of you liking the other first, and whatever either of you has set in "Looking for" or passed on before. This works only while you both have a free match slot. If either of you has five matches, both of you are told whose match slots are full. If you were matched before and one of you unmatched, you can't match again this way, unless the match ended because one of you paused to take things further with someone else. Your code only works while it is showing on your "Met in person?" page, with the app open, so a photo of it can't be used later. Someone who scans it at any other time is told only that the code isn't active, nothing about you, and you are not told. Getting a new code in the app stops the old one working straight away. Blocking someone stops them matching with you this way. If someone scans your code with their phone's own camera instead of the app, it opens CheckIn's App Clip (a small part of CheckIn that opens without installing the app) or, if the App Clip can't open, a page on our website. Neither shows your name or anything else about you; they offer to get the app and match, and the page also offers to open CheckIn. If they choose to get the app while your code is showing, we save the match for 48 hours against a random number that only their phone keeps. Once they have signed up, CheckIn on their phone sends us that number, and you match under the same rules as a scan in the app; you are both told as for any new match. Only the person whose phone saved the match can be matched with you this way, and nobody else who joins is shown to you or asked about. Do not put information in your profile or messages that you do not want the intended users to see.
6. Identity verification
Stripe Identity runs the identity-verification flow and receives the document images, selfie and information you submit to it. CheckIn does not receive or store the raw identity document or selfie. CheckIn stores the Stripe verification-session identifier, its status, the verification time and, if a check fails, the reason. To check your age, CheckIn reads the name and date of birth that Stripe verified from your ID. We compare that date of birth with the one you gave us. If they differ, or the ID shows you are under 18, the check is refused. If your profile has no date of birth, the one from your ID is saved to it. Once your birthday has been checked against your ID, changing it means verifying again. We do not keep the name from your ID. We do store a one-way keyed code (a hash) made from the name and date of birth on the ID. It cannot be turned back into your name or birthday. We use it only to stop one person running several accounts, returning after a ban, signing up before they are 18, or claiming a referral reward twice. Stripe applies its own retention and privacy terms to information it holds. When you delete your account, we ask Stripe to erase the information from your ID checks (Stripe can take a few days to finish), unless we keep the safety record described in section 12. Quick selfie: before your first video CheckIn, unless you have verified your ID or been in a CheckIn call before, we ask for a quick selfie instead: two photos from your front camera, one looking at the camera and one with your head turned a little. Amazon Rekognition checks that each shows one clear face, that both are the same face, that it looks 21 or over, and that it matches one of your first three profile photos. Comparing faces in this way uses biometric data, so we only do it when you choose to take the selfie; you can use the ID check instead. We do not keep the photos: they are sent to Amazon for the check and then dropped by us. Amazon does not keep them or use them to improve its own services. We keep whether it passed, when, and how many times you tried that day. If it doesn't pass, you can verify your ID with Stripe instead.
7. Calls and communications
CheckIn does not record or store the audio or video content of calls. Where possible, calls connect directly between the two phones, so each phone can see the other's network (IP) address. When a direct connection is not possible, the encrypted audio and video are relayed through Cloudflare's servers, with Cloudflare acting as our processor. Access to the relay uses short-lived credentials that expire, and they are only issued to members aged 18 or over who have passed identity verification and have a CheckIn ringing or accepted. Cloudflare handles the network addresses, credentials and connection metadata needed to carry the live encrypted stream, but CheckIn does not ask it to record call content. CheckIn processes call and signalling information needed to connect and end a call, such as participant account identifiers, Check-In identifiers, timing and connection state. We also keep a record that a call between two members connected, and when, to check reports (see section 11). Chat messages are stored to deliver conversation features. Voice-note audio is scheduled for deletion after three days, and the words of a typed message are deleted three days after it is sent; a message record may remain to show that it expired. If you leave someone a goodbye message when you unmatch them, only they see it and they can’t reply. We keep it until they read it, or for 30 days if they don’t, and then delete it. If someone reports you from a chat, we keep the words of any typed message you sent them with the report as evidence, even after it disappears from the chat. If you delete a message for both of you, it disappears from the chat for both of you straight away. For a voice note, GIF, one-off text, or phone number or Instagram card, we keep a hidden copy for 30 days, which nobody can see in the app; it is used only if one of you reports the other. Deleting never keeps anything longer than not deleting would: a deleted text's words still go three days after it was sent, and a deleted voice note is never played again and its audio is deleted when its three days are up. Your data export includes the deleted messages of yours that we still keep; the other person's export shows only that a message was deleted, not what it said. A reaction (an emoji you put on something a match sent you) stays with that message, and goes when the message does. If you change or take off a reaction, we keep a hidden record of the earlier one for 30 days, which nobody can see in the app; it is used only if one of you reports the other. If someone reports you from a chat, we keep your reactions on their messages with the report as evidence. When you search for an emoji to react with, what you type stays on your phone and is never sent to us. Your voice prompts (spoken answers of up to a minute, or typed answers of up to 150 characters) stay on your profile until you replace or delete them, or delete your account.
8. Payments
Apple or Google processes in-app purchases, and RevenueCat helps CheckIn validate and restore purchases and manage entitlements. RevenueCat receives your CheckIn account identifier and your email address, so we can help with purchase questions, and tells us when a purchase is made, renewed, cancelled or moved to another account. CheckIn no longer sells anything through Stripe. If you bought a subscription on the web through Stripe before then, we have switched off its renewal. Stripe still holds those billing records, and CheckIn keeps a copy of them, such as invoices, payments, billing details and your card's brand and last four digits. CheckIn receives the purchase, product, entitlement, transaction and limited customer information needed to provide paid features and support billing. We never receive full payment-card numbers.
9. Service providers and disclosures
We use service providers to run CheckIn: Clerk for sign-in, with Apple or Google when you choose to sign in with them; Stripe Identity for identity verification, and Stripe for the records of past web purchases in section 8; RevenueCat and the applicable app store for in-app purchases; Amazon Web Services (Amazon Rekognition, in London, United Kingdom) to estimate the age of the face in a new member's profile photos, to check new profile photos for nudity, and for the quick selfie before a first video CheckIn (section 6), photos which Amazon does not keep or use to improve its own services; Google Maps to turn coordinates into the name of your area and to draw the map preview, with OpenStreetMap's Nominatim service used instead when Google is unavailable; Cloudflare as the call-relay processor; Sentry to receive crash and error reports from the app and our servers, which it stores in the European Union: the error and where in the app or server it happened, the app version, your phone's model and system version, what the app was doing just before (such as which screen was open and which of our web addresses it used, without what was sent), and your CheckIn account identifier, but never your photos, voice, messages or location; Expo and Apple or Google for push delivery; Railway for hosting: the application, its PostgreSQL database and private file storage, in the European Union (Amsterdam, the Netherlands); Google Workspace (Gmail) for our support mailbox, which receives the messages you send through Contact us and our moderation notices, including a record of each automatic ban, pause and appeal with the reports behind it; GIPHY for GIF search and for the GIFs you choose as answers to your voice prompts, which other members' phones load from GIPHY's servers; Apple Music for the songs you can add to your profile or send in a chat: our servers send Apple what you type into the song search and which song you chose, and phones fetch song covers and 30-second previews straight from Apple, so Apple receives the network (IP) address of the phone that plays or shows them; and Meta for optional Instagram connection features. These providers receive the information needed for their role and apply their own terms where they act independently. We may also disclose information to professional advisers, authorities when lawfully required, or a buyer as part of a business reorganisation. We do not sell personal information or share it for third-party behavioural advertising.
10. Storage and security
CheckIn stores application records in PostgreSQL. These include profiles and precise coordinates, relationships, messages, support, safety, billing metadata, credits, referrals, analytics and audit history. Profile photos, imported Instagram photos, generated blurred thumbnails, spoken voice prompts, voice-note audio and any voice intro you recorded are kept separately in private cloud object storage. Messages you send through Contact us are also delivered to our support mailbox. Your "Met in person?" code is stored in PostgreSQL with your account, together with the time it stops working while it is showing on your phone. A saved "Met in person?" match is stored in PostgreSQL with a one-way code (a hash) of the random number the App Clip or page made for it and, once it is used, the account that used it. Some account tokens and preferences, such as which guides you have already seen, when your "Met in person?" reminder is due, a "Met in person?" match saved before you had CheckIn (until it has been used), and when to ask you for an App Store review, are stored on your device, and providers store information in their own systems. We use access controls and other technical and organisational safeguards appropriate to the service, but no storage or transmission method can be guaranteed completely secure.
11. Retention
We generally keep account, profile, relationship, safety and service records while your account is open. Relationship records include held likes, which do not expire on their own. Some data has a shorter operational life, including short-lived call credentials, voice-note audio scheduled to expire after three days, the words of typed messages, which are deleted three days after they are sent, goodbye messages left when someone unmatches, which are deleted once read or after 30 days, and hidden copies of messages deleted for both people, kept for 30 days (section 7) or until either account is deleted. When you remove a photo, its file is deleted from storage, usually within about ten minutes. When you switch on a Spotlight, we keep the area you were in when you switched it on (rounded to about a kilometre) and your distance setting at that moment, so it is shown to people near there for its 24 hours, with the distance they see measured from that area; we delete that area soon after the Spotlight ends, usually within an hour. We keep the result of each photo age check (whether it passed, found no clear face or suggested you could be under 21, the estimated age range and the date) while your account is open; we do not keep a copy of your photo for it. We keep the result of the quick selfie (whether it passed and when, and how many times you tried that day) while your account is open; we do not keep the selfies. We keep the record of which days you used the app, and which sign-up pages you opened, while your account is open. We keep the area you signed up in while your account is open; the totals per area hold no individual members and are kept for two years. Sentry keeps crash and error reports for up to 90 days. Your voice prompts stay until you replace or delete them. The song on your profile stays until you change or remove it; we do not keep what you type into the song search. Your "Met in person?" code stays until you get a new one, when the old code is deleted, or until you delete your account. The time it stops working is cleared when you leave the page, and otherwise simply runs out about 90 seconds after your phone last told us the page was open. We keep these codes out of our server logs. A saved match that wasn't used is deleted soon after its 48 hours end. On the phone that saved it, CheckIn forgets the random number once it has used it. One that became a match is kept while both accounts exist, and is deleted when either person deletes their account. A bio or voice intro you added stays with your account, not shown to anyone, until you delete your account or ask us to delete it. We keep the record that a call between two members connected (when it first and last did) for safety and report checks, while both accounts exist; it is deleted when either member deletes their account. If an ID check shows someone is under 18, we keep a hashed copy of their sign-in identifiers until they turn 18, as explained in section 15. Account deletion removes user-linked first-party records from our active systems, with the limited exceptions in section 12. Some copies may remain until their normal deletion cycles or legal retention periods end: backups, records held independently by providers, emails in our support mailbox, and payment records that must be kept by law, including records of past Stripe web purchases. Retention therefore varies by record and provider.
12. Account deletion
You can start account deletion in Settings. This removes your account and user-linked first-party active records, including profile, relationship, communication, support, contact-sharing, media, notification, purchase-link, analytics and safety records. It also cancels any remaining Stripe web subscription, deletes your Stripe customer record, asks Stripe to erase the information from your ID checks, and asks Clerk to delete your sign-in record. We keep seven limited kinds of record after deletion. First, if your account was banned or suspended for a safety reason, we do not ask Stripe to erase your ID checks. If that happened after identity verification, we also keep the Stripe verification-session identifier, the one-way identity code described in section 6 and an internal account reference, so the same person cannot simply sign up again; this stops applying if the decision is reversed. Second, we keep the under-18 sign-up block described in section 15. Third, we keep referral records the other person still relies on, such as a free month they earned. In these, your account identifier is replaced with an anonymous marker, but they keep the one-way codes made from your phone number and app installation that stop a reward being claimed twice. Fourth, if you used any of your free welcome Spotlights, we keep one-way codes made from your verified email addresses and Apple or Google account IDs, with how many you used, for one year, so a new account doesn't get them again. They cannot be turned back into your email address or account. Fifth, if your account was closed (banned) when you deleted it, we keep one-way codes made from your verified email addresses and Apple or Google account IDs, so the same sign-in can't be used to join again. From the moment an account is banned, we also keep one-way codes made from the phones it used CheckIn on (the random ID the app keeps on the phone and its notification token), so a new account on the same phone is refused. They cannot be turned back into your email address, account or phone, and we delete them if the ban is lifted. Sixth, if your account was paused, or waiting for an ID check, when you deleted it, we keep one-way codes made from your verified email addresses and Apple or Google account IDs, with when the pause ends and the warnings and pauses already on your record, so a new account carries on where this one left off. We delete them when the pause would have ended, or, for an ID check, when you pass it. Seventh, if a friend's referral code earned you a free month, we keep one-way codes made from your verified email addresses, Apple or Google account IDs and ID check for one year, so a new account cannot claim another. None of these can be turned back into your details. Other members' Reveals and rewinds that involved you keep only a marker showing the account was deleted. None of these contain your ID document, selfie, photos or messages. Emails in our support mailbox, records of past Stripe web purchases kept for legal reasons, provider records and backups may not be deleted straight away. Email us if you want your support emails deleted too, if deletion does not complete, or if you want help with data held by a provider.
13. Your choices and rights
You can edit profile information, pause your profile at the bottom of Profile, get a new "Met in person?" code at any time, change notification choices, turn off camera, location or notification permissions in your phone's settings, disconnect optional features, download the CheckIn data available through the automated export, or delete your account in Settings. Depending on where you live, you may also have rights to access, correct, erase, restrict, port or object to use of your information, to ask for a person to review an automated decision, and to complain to a regulator such as the UK Information Commissioner's Office at ico.org.uk. Email contact@checkin-chicken.com to make a request. We may need to verify the request and will respond within the period required by applicable law.
14. International processing
CheckIn and its providers may process information in the United Kingdom, European Economic Area, United States and other countries where they operate. Privacy laws in those countries may differ. Where applicable law requires a transfer safeguard, we or the relevant provider use an approved mechanism or another lawful basis for the transfer.
15. Age restriction
CheckIn is for people aged 18 or over. If we learn that an account belongs to someone under 18, we will investigate and remove it where appropriate. New members' profile photos are also checked by an automated age estimate, as described in section 3. If an ID check shows someone is under 18, their account is suspended, and from then on, including after they delete their account, we keep a one-way scrambled (hashed) copy of their sign-in identifiers (their verified email addresses, their Apple or Google account IDs and a code from the ID check) and the date they turn 18, or a date one year after the check if we do not know their birthday. We use it only to stop them signing up again before then, and we delete it on that date. It cannot be turned back into an email address. If you give a date of birth under 18 when signing up, we ask you to confirm it; once you do, your account is held as under 18 until your 18th birthday, wherever you sign in. We record only the date you turn 18, not your birthday, and if you delete the account we keep the sign-in block described above until that date. Report a suspected underage account to contact@checkin-chicken.com.
16. Changes and contact
We may update this policy as the service or law changes. For material updates, we will provide an in-app notice and ask you to review the changes when appropriate. Privacy questions and requests, and safety reports, can be sent to contact@checkin-chicken.com.

