PopIn — Privacy Policy
Last updated: 2026-11-19
This policy explains what the PopIn app for iPhone and Android ("PopIn", "the app") collects, why, who can see it, and how to remove it. PopIn is made by Lowkey AI ("we", "us"). If you have any question about it, write to lowkey9.ai@gmail.com.
PopIn helps adults who are nearby and free right now meet for a coffee. That only works if some information about you is shown to other people, so this policy is specific about exactly what is shown and what is not.
The short version
- PopIn is for adults aged 18 and over only.
- Your exact GPS position never leaves your phone. Other people only ever see a blurred point a few hundred metres from where you are, and only while you choose to be visible. The same blurred point, never the exact one, is used for cafe suggestions and for nearby alerts if you turn them on.
- Your date of birth and email address are private. Other people see your age, never your date of birth.
- There are no ads, no analytics SDKs and no tracking across apps or websites. We do not sell or share your data for advertising. We keep anonymous daily totals, such as how many coffees were agreed, that cannot be traced to anyone.
- If you allow notifications, PopIn tells you when someone pings you, says yes, or writes to you, and, only if you ask, when someone near you is free. You can switch each kind off in Me → Notifications. Crash reports, which are not linked to your account, help us fix problems.
- Profile photos are checked automatically for nudity and violence, and removed if they break the rules.
- Huddles (group activities such as football or padel) are public: anyone verified can see a Huddle's place, time and the names and photos of the people in it. The place is the venue the host pins on a map, never anyone's GPS position.
- Ratings are private. After a coffee or a Huddle you can give a thumbs up or down and a few fixed tags. Nobody is shown who rated them: others see only totals, and only once there are enough of them to mean something.
- Safety kit. If you choose to, you can share a live link to your position with up to three people you name, for at most six hours. It is the only place PopIn shows a real position, only to people who have the link, and it disappears when the trip ends.
- You can delete your account inside the app at any time: Me → Delete account.
Who processes your data
PopIn has no servers of its own. Your account and app data are stored using Google Firebase, a service provided by Google: Firebase Authentication (your sign-in, including Sign in with Google and Sign in with Apple if you use them, and, only if you choose to verify your phone, sending a code by SMS and holding the number you confirm), Cloud Firestore (your profile, pings, chats and reports), Cloud Storage for Firebase (your profile photo, and the photos, videos and voice messages you send in chats or post to stories), Cloud Functions for Firebase (sending notifications, handling moderation and creating calendar files), Google Cloud Vision (checking profile photos, see "Your profile"), Firebase Cloud Messaging (delivering notifications, through Apple's push service on iPhone) and Firebase Crashlytics (crash reports). This data is held on Google Cloud infrastructure and may be processed in countries other than your own. Google acts as our data processor under its Firebase terms. As part of providing these services, Google may also process technical information such as your IP address and device information, for example to keep sign-in secure. See https://firebase.google.com/support/privacy for how Google handles this.
Cafe suggestions come from OpenStreetMap, through its public Overpass service (run by volunteers, at overpass-api.de and, as a fallback, overpass.kumi.systems). When you open "Suggest a coffee", the app asks it for named cafes within about 1.5 km of your blurred point, the same one a map pin would show, never your exact position. Nothing else about you is sent: no name, account or device identifier. Like any website, the service sees your phone's IP address. See https://wiki.osmfoundation.org/wiki/Privacy_Policy.
We do not use any other third-party service, SDK, advertising network or analytics tool. Two buttons open other services only when you tap them: Share with a friend opens your phone's share sheet with a message you can edit before sending, and Add to calendar opens a calendar entry (on Android, Google Calendar's "new event" page; on iPhone, a calendar file made by our Cloud Function from the place, time and the other person's first name, which is not stored).
Notifications
If you allow notifications, your phone gives PopIn a notification token, which is stored in your private record so we can deliver notifications to that phone. A notification is sent when someone pings you, when someone accepts your ping, when someone sends you a message, and for the Huddle, story, reminder, check-in and match updates described below. It shows the other person's name and the start of the ping or message. We also notify you if your profile photo is removed by the automatic check. You can switch pings and messages off separately in Me → Notifications; the switches are stored in your private record. The token is removed when you sign out and deleted with your account. You can turn notifications off at any time in your phone's settings; nothing else in the app changes.
Nearby alerts are off unless you turn them on (on the map when nobody is around, or in Me → Notifications). Turning them on stores your blurred point and its map cell in a record only you can read or change. When someone goes visible within about 3 km, you get a notification saying that someone nearby is free, without saying who, at most once every three hours, and not while you are visible yourself or if either of you has blocked the other. The point is updated when you have moved about a kilometre. Turning alerts off deletes the record.
Crash reports
When the app crashes or hits a serious error, Firebase Crashlytics sends a crash report: what went wrong in the code, the app version, the phone model and operating system version, and a random installation identifier. Crash reports are not linked to your account: no name, email, user ID or message content is attached. We use them only to find and fix bugs. Google keeps them for 90 days.
What we collect and who can see it
Account information
- Email address and password. Used to create your account, verify your email, sign you in and confirm account deletion. Your password is handled by Firebase Authentication; we never see it. Your email address is also stored in a private record that only you can read. It is never shown to other users.
- Sign in with Google or Apple. If you choose one of these instead of a password, Google or Apple confirms who you are and shares your email address with us (with Apple you can choose "Hide My Email", and we then receive an Apple relay address that forwards to you), and, the first time, your name. We use the email exactly as above, and the name only to suggest a display name during setup, which you can change. We do not receive your Google or Apple password, contacts or anything else from those accounts. To confirm account deletion, you sign in with the same provider again; for Apple, deleting your account also revokes PopIn's access in your Apple ID settings.
- Date of birth. Asked once, at signup, to confirm you are 18 or over. It is stored in your private record, cannot be changed afterwards, and is never shown to anyone else. Only your age, worked out from it, appears on your profile.
- When you accepted the Terms of Use. A timestamp stored in your private record.
Your profile
- Display name, profile photo, bio (up to 160 characters) and up to three interests chosen from a fixed list, plus your age.
- Your profile can be opened by other signed-in, email-verified PopIn users who come across you on the map, in a ping or in a chat. Your photo can be loaded by signed-in users. Profiles cannot be searched or listed; people find each other only through the map.
- Automatic photo check. Every profile photo you upload is checked by Google Cloud Vision's SafeSearch, which estimates how likely the image is to contain nudity or violence. The image is analysed and not kept by Google for this purpose. If it is likely to break our rules, the photo is deleted, removed from your profile and pin, and you are notified; only a daily count of removed photos is kept. People can still report a photo the check missed.
- Photos are resized on your phone (to about 1200 pixels) before upload. If you take a photo with the camera, it is not saved to your photo library. When you choose from your library, the system photo picker gives PopIn only the one photo you pick, not access to your library.
Your location, and only while you are visible
PopIn asks for location permission "while using the app". Here is exactly what happens to your location:
- Your exact GPS position is used on your phone to centre the map and to work out how far away other people are. It is never sent to us or to anyone else, with one exception you switch on yourself: "Find each other", described below.
- When you choose to be visible, the app first moves your position by a fixed offset of between 150 and 350 metres in a random direction that is unique to you, and then snaps the result to a grid of roughly 250 metres. Only that blurred point is uploaded. Because the offset is fixed rather than random each time, watching your pin over time does not reveal your real position. The offset itself is stored in your private record so it stays the same.
- While you are visible, the blurred point is shown on the map to other verified users nearby together with your display name, photo, age, interests and an optional status message (up to 60 characters). Distances are shown in rough bands, such as "about 1.2 km away", never exactly, and never with a direction.
- Where you are shown. When you go visible you can choose to be shown "around me" or around a different area that you pick on the map, within 3 km of where you are (for example a busy square rather than your street). The app reminds you not to pick your home or workplace. A chosen area is blurred in exactly the same way as your GPS position, and it stays put while you move. You can also choose "Wider area", which snaps your point to a grid of about 1 km instead of 250 m. Your own map shows you the blurred area others see.
- Your status message cannot contain a street address, a flat number or phrases like "my place", because it is shown to everyone nearby. The database refuses such statuses too.
- You choose how long you stay visible (30 minutes to 4 hours). The maximum is 4 hours, enforced by the database itself. While the app is open your blurred point is refreshed every few minutes.
- When you go offline, your pin is deleted. When your chosen time runs out, the app hides your pin from everyone; if your phone was offline or the app was closed at that moment, the expired record is deleted from our database within about an hour.
- Cafe suggestions use the same blurred point, sent to OpenStreetMap as described above, and only when you open "Suggest a coffee". The distance to each cafe is worked out on your phone.
- Nearby alerts, if you turn them on, store the same blurred point as described under "Notifications".
- Venue suggestions for a Huddle work like cafe suggestions: the blurred point, never the exact one, is sent to OpenStreetMap to find pitches, courts, parks and similar places within about 5 km.
- Searching for a place when you start a Huddle uses Google Maps Platform. As you type, the text you typed and your blurred point (never your exact position) are sent, through our Cloud Function so that our Google key never sits in the app, to Google's Places service to list matching places; picking one fetches that place's name, address and position. Nothing else about you is sent: no name, account or device identifier. Google sees the request as coming from our server. The map showing a Huddle's place is a Google map, drawn on your phone by Google's Maps SDK, which, like any map, sends Google your phone's IP address and the map area you view. See https://policies.google.com/privacy. The distance to each place is worked out on your phone.
- "I'm here". On the day of an agreed coffee you can tell the other person you have arrived. If the cafe came from the suggestions, your phone checks that you are within about 150 metres of it before sending. That check happens on your phone: only the message "I'm here at …" is sent, never your position.
- "Find each other". If you are both at an agreed cafe and cannot spot each other, either of you can turn this on from the coffee card. While it is on, your position, rounded to about 11 metres, is stored in your chat so that only the other person in it can see it, and only while they share theirs too. The database itself only accepts it from 15 minutes before to 30 minutes after the agreed time, for a cafe you both confirmed, and within about 300 metres of that cafe, so it cannot show your route there or your home. It switches off as soon as you leave that screen or the app, walk away, end the chat, or block the person. Each position is deleted when you stop, or automatically within about an hour of the window ending, and no one can read it once the window has passed. It uses your location only while the app is open on that screen.
- If you never go visible, never open the cafe or venue suggestions, never turn on nearby alerts and never use "I'm here" or "Find each other", no location of any kind leaves your phone. A Huddle's place is separate from your location: it is the spot you choose for the venue, and the map you choose it on starts from your blurred point, not your real one.
Pings, chats and meetups
- Pings. When you ping someone, we store who sent it, who received it, your short message (up to 140 characters), its status (pending, accepted, declined or withdrawn), when it was sent and answered, and both people's names and photo links as they were at the time. Only the two people involved can see a ping.
- Chat messages. When a ping is accepted, a one-to-one chat opens. We store your messages (up to 1,000 characters each, with photos, videos and voice messages described below), who sent them and when, plus the chat's last message and read status for unread badges. Only the two participants can read a chat. Messages cannot be edited or deleted once sent, by you or the other person, so that a report can always point to what was actually said.
- Photos, videos and voice messages. In a one-to-one or group chat you can send photos, short videos (up to 60 seconds) and voice messages (up to 5 minutes). They are uploaded to Cloud Storage for Firebase, into a folder for that conversation, and only the people in that conversation can open them: the storage rules check the chat's own participant list on every request. Photos are resized, and videos are shrunk, on your phone before upload. A photo or video you take with the camera is not saved to your photo library. When you choose from your library, the system photo picker gives PopIn only the items you pick. These files are not scanned automatically. As with text, a file cannot be deleted from storage once sent, so that a report can still point to it; if you unsend a message, it disappears from the conversation for both of you but we keep the file for moderation. Files stay with the conversation if your account is deleted, in the same way your messages do. A push notification for a photo, video or voice message says only that one arrived (and any caption), never the file.
- Meetup proposals. If you suggest a coffee, we store the venue name you type or pick, the time, who proposed it and who has confirmed it, as part of the chat. If you picked a cafe from the suggestions, its public map position is stored too, for the directions link.
- Ending a chat. Either person can end a conversation without blocking. It then reads "This conversation has ended" for both of you, exactly as after a block, and no more messages can be sent.
- "Did you meet?" After an agreed coffee's time has passed, the app asks whether you met. Your answer (yes or no) and when you gave it are stored; only you can read it, and the other person is never told. We use only the anonymous daily totals, to see whether PopIn actually leads to coffee.
Huddles (group activities)
A Huddle is a game or outing that anyone can organise for a group, for example five-a-side football, padel doubles, a run or a dinner. Unlike a one-to-one ping, a Huddle is public to every verified PopIn user, because its purpose is for people you have not met yet to join.
- What is shown to everyone: the activity, title, level, note and cost text the host writes; the venue name and the position the host pins for it; the start and end time; how many places there are; the host's name and photo; and the names and photos of everyone in it, on its waitlist, or (for the host only to act on) asking to join.
- Joining. When you join, ask to join or join a waitlist, your name and photo are added to the Huddle and stay on it, so that its group chat still shows who said what, even if you leave later. If the host removes you or says no, that is recorded so you cannot rejoin that Huddle.
- Roll call. About two hours before the start, members are asked "still in?". Whether you answered is visible to the others in the Huddle. Seats of people who did not answer may be given to people on the waitlist.
- Group chat. Members of a Huddle can message everyone in it. Only current members can read it. It closes a day after the Huddle ends. Photos, videos and voice messages can be sent in a group too. As in one-to-one chats, messages cannot be edited or deleted (you can hide a message from your own view). If you block someone, their messages are hidden from you and you are not sent notifications for them, but other members can still see them.
- Limits. To stop spam, your private record keeps the time of the last Huddle you started and how many you started today.
Stories
- Your story. You can post a photo or a short video (up to 60 seconds) to your story, with an optional caption (up to 200 characters) and an optional place name in your own words (up to 60 characters). It stays up for 24 hours and is then deleted automatically, with its file. While it is up, any verified PopIn user can watch it, from your profile or from your pin on the map, except people you have blocked. Your pin carries only the time of your newest story and when the last one ends, so other people's maps can draw a ring around it; it carries no picture. Like a status, a caption or place name cannot name a home, a room or a car, or look like a street address. A story's location is never taken from your phone: it is only what you type.
- A Huddle's story. The host of a Huddle can post photos and videos of it to the Huddle's story, and can let everyone in the Huddle post too, either straight away or only after the host approves each post. Anyone who can open the Huddle can watch its story. A post waiting for approval is seen only by the person who posted it and the host; if the host declines it, it is deleted. The host and the person who posted it can delete a post at any time; otherwise it is deleted automatically 24 hours after it went up.
- Text, stickers, drawings, looks and music. Anything you add on top of a story in the editor (words, stickers including a time, date or place you type, emoji, a drawing, a colour look, and a PopIn Originals music track) is saved with the story, is seen by the same people, follows the same rules on homes and addresses as the caption, and is deleted with it. The music is bundled in the app: playing it sends nothing anywhere. If a story is reported, the words on it are kept with the report's copy.
- Who watched. When you watch someone's story, your name, photo and the time are recorded for that story so its author (and only its author) can see who watched. This is deleted with the story. You can turn this off with Story views in Me → Privacy: while it is off, nothing is recorded when you watch a story, and you can't see who watched yours either. Which stories you have already watched is otherwise remembered only on your phone.
- Files. Story photos and videos are stored in Cloud Storage for Firebase. Any signed-in PopIn user who is shown a story can load its file. Photos are resized, and videos are shrunk, on your phone before upload, and a photo or video you take with the camera is not saved to your photo library. Stories are not scanned automatically. If a story is reported, we keep a copy of it for review, even after it comes down, for as long as we keep the report.
Ratings, badges and Verified
- Ratings. After an agreed coffee (when you answer "did you meet?") or after a Huddle, you may give a thumbs up or down and up to three tags from a fixed list, such as "on time" or "friendly". Your answer is stored under your own account where only you can read it. A server then adds it to the other person's totals (thumbs up, thumbs down, how many times they met up, joined or hosted a Huddle, and a count per tag). No one is shown who rated them, and no one can read the individual answers. On a profile, others see only the badges earned, the share of thumbs up (once at least three people have rated) and the kind tags that at least two people gave, never how many thumbs down or the concern tags (such as "late", "rude" or "felt unsafe").
- "Felt unsafe". If you choose that tag about someone you met, we also file it as a report so a moderator can look at it, exactly as if you had used Report.
- Verified. If you choose to verify your phone, Firebase Authentication sends a code by SMS and links the number to your sign-in account so the same number cannot verify many accounts. PopIn never shows your number to anyone and never copies it into its own database; the database records only that a number was confirmed, which other people see as a ✅ Verified mark. Standard message rates may apply.
- Badges (such as "Regular host") are worked out from those counts.
Safety kit: trusted contacts and "Follow my trip"
- Trusted contacts. You may type in up to three names and phone numbers. They are stored in your private record, which only you can read. PopIn never reads your phone's contacts, and your contacts do not need the app.
- Follow my trip. When you start a trip, the app creates a long random link and opens a text message to your contacts with it. Anyone who has the link can open a web page, with no account, showing your first name, the place you said you were meeting, and your real position as the app sends it every 30 seconds while PopIn is open on screen. The trip ends when you tap "I'm safe" or stop it, or after six hours at the latest; the page then stops showing a position, and the trip is deleted. Only you can read or change the trip in the database; the page is served by our Cloud Function. The page asks search engines not to index it and is not cached.
- Check-in. If you ask to be checked on, your phone asks "are you OK?" at the time you chose. If you do not answer, the page tells your contacts they have not heard from you, and you get a notification. SOS marks the trip as an emergency on that page, opens your phone's dialler on the local emergency number, and opens a text to your contacts. PopIn does not call anyone or send any text for you.
- No background tracking. The position is sent only while the app is open. If you close it, the page shows how old the last position is.
Saved places, polls and "on my way"
- Saved places. Places you save (a name, address and position of a venue) are stored in your private record.
- Polls. A poll in a Huddle's group chat, its options and who voted for what are visible to the members of that Huddle, like a show of hands, and stay with the Huddle.
- On my way / running late / I'm here. The status you set in a Huddle is visible to its members. A rough arrival time is worked out on your phone from the distance to the venue; your position is never sent, only the number of minutes. "Running late" also sends the other members a notification.
- Weekly Huddles. If a host asks for a Huddle to repeat every week, the server plans the next one, with the same details and only the host in it, when each one ends; people who were in are told and join again by choice.
- Reminders, quiet hours and matches. Reminders an hour and ten minutes before a Huddle or coffee you joined are created on your phone. Your quiet hours, with your phone's time-zone offset so the server knows when they are, are stored with your notification switches. If you turn on "Huddles that fit you" (it needs nearby alerts), a new Huddle within about 5 km whose activity fits your interests can send you one notification at most every six hours; this uses the same blurred point as nearby alerts.
- Venue details. When you tap for a place's rating and opening hours, the app asks our Cloud Function, which asks Google Places for them; only the place's id is sent.
Safety: blocks and reports
- Blocks. When you block someone, we store that fact in a list only you can read. The other person is not told. The block closes any chat between you and stops either of you from pinging or messaging the other. It also hides you from each other's map: while you are visible, your pin carries a short scrambled code for each person you have blocked (never their name or user ID), which their app uses to leave your pin out.
- Reports. When you report someone, we store who reported, who was reported, the reason you picked, any details you add (up to 500 characters), where the report came from (a profile, a ping, a chat or a Huddle) and the ping, chat or Huddle it concerns. No user can read a report, including the person who sent it, and the reported user is not told who reported them, or that they were reported. Reports are reviewed manually by us, within 24 hours, in an internal moderation tool, and may involve reading the reported conversation and ping. If we find the Terms of Use have been broken, we may suspend the account. A suspended account is signed out, removed from the map, and its pending pings and open chats are closed, Huddles it hosts are cancelled and it is taken out of any others; we keep a record of the suspension and the reason so the account cannot simply come back.
A rate-limit counter
To stop spam, the database keeps a small private record for each account with the time of your last ping, how many pings you sent today and the date. It holds nothing else.
Stored only on your phone
Some things never leave your device:
- Your exact GPS position (see above).
- The trip you are currently sharing (so it can be picked up again after a restart) and your "blur my area wider" preference.
- Small app preferences kept in the phone's local storage, such as whether you have already seen the safety reminder, whether you have already sent "I'm here" for a coffee, and the end time, status message and chosen area of your current visibility window, so the app can restore it after a restart.
- Local notifications scheduled on your phone, if you allow notifications: when your visibility ends, an "everything OK?" check-in a little over an hour after an agreed meetup (tapping it opens help: call the emergency services, tell a friend, report or block), a "how was coffee?" reminder a couple of hours after an agreed meetup, and the "still free?" reminder for a coffee you planned for later. They are created and delivered by your phone; nothing is sent from a server for them. A planned time is not shown to anyone.
What we do not do
- No advertising, and no advertising identifiers.
- No analytics or tracking tools. Crash reports (above) are the only diagnostic data, and they are not linked to you.
- No tracking of you across other companies' apps or websites.
- No selling, renting or sharing of your personal data with third parties for their own purposes.
- No background location: PopIn only uses your location while the app is in use.
- No contact list or other device data is accessed. The camera and microphone are used only while you are taking a photo or video, or recording a voice message, in a chat or for a story, and nothing is sent until you tap send or share.
Why we use your data
We use the data above only to run PopIn: to create and secure your account, confirm you are an adult, show you to people nearby when you ask to be shown, deliver pings and messages, keep users safe, enforce the Terms of Use and respond to reports and requests. Where data-protection laws such as the GDPR or UK GDPR apply, our legal bases are: performing our contract with you (providing the app); your consent (location and camera permissions, which you can withdraw at any time in your phone's settings); and our legitimate interest in keeping the service safe and free of abuse (rate limiting, blocks, reports and moderation).
How long we keep it
- Account, profile and private record: until you delete your account.
- Location pin: only while you are visible, as described above, and removed when you go offline or delete your account. Expired pins left behind by a closed app are deleted automatically within about an hour.
- Notification tokens: until you sign out on that phone or delete your account.
- Notification switches: in your private record, until you delete your account.
- Nearby-alert area: until you turn alerts off or delete your account.
- "Find each other" positions: until you stop sharing, and in any case deleted automatically within about an hour after 30 minutes past the agreed time. They cannot be read by anyone after that time.
- "Did you meet?" answers: for as long as the chat exists (see "Deleting your account").
- Ratings you gave: for as long as the chat or Huddle exists. Totals about you (thumbs, tags, counts and the Verified mark) are kept by the server and, because they are only numbers with no names, are not removed when you delete your account.
- Trusted contacts and saved places: until you remove them or delete your account.
- A shared trip: until it ends, or six hours at the latest, and in any case deleted automatically within about a day after it expires.
- Stories and who watched them: 24 hours from when they went up (or from the host's approval), then deleted automatically with their files, usually within the following hour. You, or the host of a Huddle, can delete one sooner. A copy of a reported story is kept with the report.
- Anonymous daily totals (coffees agreed, yes and no answers, photos removed): kept indefinitely; they contain no personal data.
- Crash reports: 90 days.
- Suspension records: for as long as needed to keep a suspended person off the service.
- Pings and chats: for as long as the account of either participant exists, so that the other person keeps their conversation history.
- Huddles and their group chats: kept after the Huddle ends or is cancelled, so that its members keep their history and a report about it can still be reviewed. You appear in them as "Deleted user" once you delete your account.
- Reports: for as long as needed to review them and to protect users, including after the accounts involved are deleted.
- Rate-limit counter: see "Deleting your account" below.
Deleting your account
You can delete your account inside the app at Me → Delete account. Email accounts confirm with their password; Apple and Google accounts confirm by signing in with Apple or Google again. This:
- deletes your sign-in account, and for Sign in with Apple accounts also revokes PopIn's access with Apple;
- replaces your public profile with a placeholder named "Deleted user", removing your name, photo, bio and interests (your age stays on the placeholder but no longer identifies anyone);
- deletes your profile photo;
- deletes your private record, including your date of birth, email address, location offset and notification tokens;
- removes you from the map and deletes your nearby-alert area;
- deletes your stories, and the posts you added to the stories of Huddles you are in;
- deletes your block list, saved places, trusted contacts and any trip you are still sharing;
- withdraws or declines any ping that was still pending;
- closes all your chats and shows you in them as "Deleted user";
- cancels the Huddles you host, takes you out of the ones you joined, and shows you in all of them as "Deleted user".
Some data is not removed by the in-app deletion, and we want to be upfront about it:
- Messages you have already sent stay visible to the other person in their closed conversation, shown as from "Deleted user". The same applies to a meetup you proposed in that chat.
- The record of a past ping stays in the other person's history, marked as withdrawn or declined, and may still contain the name you had when it was sent.
- Your ratings, thumbs and tags totals (numbers only, with no names) and the votes you cast in Huddle polls (stored under your former account ID) are not removed.
- The rate-limit record (two timestamps and a counter) cannot be removed by the app.
- Your "did you meet?" answers (a yes or no and a time, stored under your former account ID) cannot be removed by the app.
- Reports you made or that were made about you are kept as described above.
If you want any of this erased as well, email lowkey9.ai@gmail.com from the address you signed up with, and we will remove it unless we need to keep it to deal with an open safety report or a legal obligation.
Your rights
Depending on where you live (for example under the GDPR, the UK GDPR or California's CCPA/CPRA), you may have the right to access the personal data we hold about you, get a copy of it, correct it, delete it, restrict or object to how we use it, and withdraw consent. We do not sell or "share" personal data as those laws define it, and we do not use it for targeted advertising or profiling. You can edit your profile in the app at any time and delete your account as described above. For anything else, including a copy of your data, email lowkey9.ai@gmail.com. We will answer within 30 days, may need to confirm the request comes from the account owner, and will not treat you differently for using these rights. You can also complain to your local data-protection authority.
Children
PopIn is for adults only. You must be 18 or over to create an account, and the app refuses signup if the date of birth entered is under 18. We do not knowingly collect data from anyone under 18. If we learn that an account belongs to someone under 18, including through a report, we remove the account. If you believe a child is using PopIn, report the profile in the app or email us.
Security
Access to data is enforced by database security rules, not just by the app: profiles cannot be listed, private records can only be read by their owner, chats and pings can only be read by their two participants, Huddle group chats only by the Huddle's members, map pins can only be fetched in small batches near a location, and reports cannot be read by any user. Email verification is required before you can appear on the map or contact anyone. Data is sent over encrypted connections. No system is perfectly secure, so please do not put information in your profile or messages that you would not want the person you are talking to to see, such as your home address.
Changes to this policy
If we change this policy, we will update the date at the top and publish the new version at this address. If a change materially affects how your data is used, we will let you know before it takes effect, for example in the app or by email.
Contact
Lowkey AI — lowkey9.ai@gmail.com