I'M HERE

Privacy Policy

I'M HERE · Version 1.10.2 · Effective: 12 November 2026

This app helps people who are in the same place at the same time meet briefly. Location is the most sensitive data we handle, which is why we keep it for the shortest time. Below is what we collect, why, and how long we keep it — without overstating any of it.

1. Who is responsible

The controller of your personal data is VELIOFLOW LTD, based in the United Kingdom. We are registered with the Information Commissioner’s Office, the UK data protection regulator, under registration number ZC289979. You can reach us at info@useimhere.com about anything in this policy.

I'M HERE is run from the United Kingdom and is for people aged 18 and over. It is distributed through Google Play and Apple's App Store and can also be downloaded in other countries; wherever you use it, this policy applies. This policy also covers this website, the invite list on it and our adverts (sections 14, 15 and 16).

2. The short version

3. What we collect

DataWhat it isWhy
AccountYour email address, a random identifier we assign you, account status, language and time zone, and a record of when you agreed to our Terms: which versions of our Terms and Privacy Policy were in force, when, and whether it was when you set up your account or from our in-app notice about a changeSo your account exists, you can sign in, and we can send you emails about your account (section 8); and so we can show which terms you agreed to
ProfileDisplay name, the text you write about yourself, your photo, interests, languages you speak, a link to your LinkedIn profile if you add one, and who you let see it. If you have Premium or Ultra, a thin gold ring is shown around your profile photoSo others can decide who they want to meet. The gold ring shows others that you have Premium or Ultra, not which one
Private profileDate of birth, gender, your job title if you add one (chosen from our list, or "Other" in a group from our list with your own words), and your visibility choices for eachThe 18+ check, letting you choose what is shown, and Nearby filters (section 3)
CommunityWhich communities you belong to (Networking, Friendship or both), the one you are using now, when you last changed it, and a number that goes up each time you changeSo you see, and are seen by, only people in the community you are using, so a change made on one phone does not clash with another, to limit how many changes you can make in 24 hours (three, or up to 15 with Premium and 30 with Ultra), and so our safety team can check it when reviewing a report about you
LocationYour coordinates, measurement accuracy, an area code, the community you were using, and a technical flag for spoofed locationFinding people near you, and counting activity by city in our aggregate statistics (the counts do not identify anyone). See section 4
Map areaThe edges of the map area on your screenWorking out the coloured density for the area you are looking at. Not stored in our database. See section 4
SessionWhen you said you were here, when it ends, and the community you were usingRunning the session, which lasts up to 2 hours, and showing you only to people in the same community
InteractionsRequests sent and received, connections made, the community each was made in, your continue decision, your blocks and a record of people you reported (section 6), and, while a request you sent is waiting for an answer, a note that hides that person from your Nearby list. Requests and connections from earlier versions of the app may also hold the purpose or the friendship, networking or both intention chosen thenCore functionality. A connection may show the community it was made in. An intention chosen in an earlier version of the app is shown to the other person only once you are connected
Daily hellosHow many hellos (requests) you have used on the current day, and which day that is. A day starts at 04:00 London time. Only the latest day is keptTo apply the daily number of hellos for your plan, including the free plan (section 5). It is not used for our statistics, and it is never shown to other users
SubscriptionIf you buy Premium or Ultra: your plan, whether you are in a free trial, when it started and when it renews or ends, whether it is set to renew, which store you bought it from (Apple's App Store or Google Play), the store's reference for the purchase, and the random code we created to match it to your account. Apple or Google take the payment: we do not receive your card details, billing address or the name on your store account. Other users see only the gold ring on your profile photo while your plan is active (section 3, Profile); they do not see which plan you have, whether you are in a free trial, or any other details of your subscriptionSo the plan you paid for works on your account, on any phone you sign in on, and stops when it ends; and to answer your questions about a purchase
Team accessOnly if you are a member of our team or help us test the app, and we give your account Ultra for that: that your account has team access, when it was given, and which of our administrators gave it. You do not pay for it, it is not a subscription, and other users are not told you have team access; as with Ultra, they see the gold ring on your profile photoSo our team and testers can use and check paid features, and so we have a record of who gave this access and when
EventsYour choice for an event (Interested or Going) and when you made or last changed it. If you withdraw your choice, it is deleted; and, if you host an event, what is described under Member events belowSo you can plan to go, and so we can send you reminders and tell you if an event changes or is cancelled. Only you see your choice; our team sees only how many people chose each event
Event suggestionsWhat you send when you suggest an event (title, description, category, start and end time, venue name and address), the community you were using when you sent it, when you sent it, its status, when we decided, and any short internal note our team adds (not shown in the app)So our team can review your suggestion and, if we accept it, prepare an event from it and decide which community it is for. Only you see your suggestions and their status. Other users are never shown who suggested an event
MessagesThe text of your messagesThe chat. Message text is never written to any log
Contact cardThe phone number, email address or Instagram handle you save on your card, and a record of which of them you sent to whomKept privately so you can send it in a chat with one tap. Shown to no one until you send it. You can change or remove what is on your card. If you block someone before any report is made, the contact card copies sent between you are deleted straight away (your messages are not; see section 7). If a report is made first, those copies are kept with the report (section 6), even if one of you then blocks the other.
ReportsWho or which member event you reported, the category, and your noteSafety. No user can read these files
Intimate image removal requestsIf you ask us to remove an intimate image: your name, how to contact you, where the image is on I'M HERE, your statement, your signature and, if you act for someone, their name; if you start from a profile or photo in the app, which one it is. Never a copy of the image you reportTo review the request, remove the image and its known copies, and stop it being uploaded again. See "Requests to remove intimate images" below
Technical recordsOperation receipts, abuse counters (these use fingerprints of network addresses and email addresses instead of the addresses themselves; see below), notification limit counter, invitation code records, clean-up records for unfinished sign-ups, the times of your community changes in the last 24 hours, a short record of when request notifications were last sent to you and how many arrived within a few minutes (used only to group them into one notification), a one-time note that you have opened the app since communities started (used only so that each person is counted once in our aggregate statistics), and how many requests you sent on the last day you sent any (used only for our aggregate statistics on how many requests people send per day)Preventing duplicate operations and abuse; grouping request notifications; and counting, in aggregate only, how many people joined through each invitation code
Invite listIf you join the invite list on our website: your email address, the country you choose, whether you asked for event emails (and, once you confirm, when you agreed and to which wording), whether you have confirmed it, whether we have sent you an invitation code, when each of these happened, a fingerprint of your confirmation link while it is valid, and a fingerprint of the links in our emails that let you remove your address or stop event emailsSo we can send you an invitation code for your country when one is available and, only if you ask, emails about I’M HERE meetups and events in your country. See section 15

What we keep elsewhere, and what we do not keep

Your sign-in email address lives in the sign-in system, not in the app database, and is never shown to another user. Account emails — confirming your email address, resetting your password and confirming a new sign-in email address — are sent either through our email provider, Amazon Web Services, or by Google's sign-in system (sections 6, 8 and 9). If you put an email address on your contact card, that copy is kept in the app database, privately, only so you can send it when you choose. If you start signing up but do not verify your email address, the sign-up is deleted after about an hour (section 6).

Your IP address is not stored in the app database. For abuse counters we keep only a short fingerprint of it, and we do the same for the email address that an account email is requested for, or that is entered in the invite list form on our website (section 15). A fingerprint is not the address itself, but it is not anonymous: someone with access to our systems could check it against an address they already know. The sign-in system, run by Google, keeps the network addresses of sign-in requests for a few weeks, and our server logs, kept for 14 days, record the network address of each request to our servers (section 6). To suggest your country in the invite list form, our website uses the country that Cloudflare works out from your network address. We do not store this suggestion; only the country you leave selected is sent with the form (section 14).

Hidden photo data is stripped. When your photo is published, it is re-processed on our server; embedded capture information — including the coordinates where the photo was taken — is stripped at that step and is not present in the published photo.

Unfinished uploads. If you upload a photo but publishing does not complete, the uploaded file is scheduled for deletion after one day; our target is to complete the deletion within two days. This file has not been through the clean-up step above: your device drops most capture information before uploading, but the coordinates where the photo was taken may remain in the file. It is never shown to any user.

Words we do not allow. Before a message is sent, and before your name, the text about you, a job title you write yourself or an event suggestion is saved, the app on your phone and our server check the words automatically against a short list of words we do not allow. If one matches, nothing is sent or saved, and you can change your text. We do not keep or log the text that was stopped or the word that matched; we only count how many times this happens each day, and that count is not linked to you.

We do not want special category data. We do not ask about your health, religious or political views, ethnicity or sexual orientation, and we ask you not to put them in your profile.

Events

Events are published by our team or, with Ultra, by members (member events), and each event belongs to one community: you see the events of the community you are using, and within a community they are the same for everyone. Event images are added by our team. If you change community, you keep getting notifications about events you said you are Going to. Some events start as a suggestion from a user. We may edit a suggestion before we publish it, and the event never shows who suggested it. Choosing an event does not use your location and does not check you in. We send event notifications only about events you have chosen — a reminder, a change or a cancellation — and we do not send notifications advertising new events. If you tap Add to Calendar or Open venue on map, your phone's own calendar or map app opens: only the event details are passed to the calendar app, and only the venue name and address to the map app. The app does not ask for permission to read your calendar, and we do not receive anything back from either app.

Member events. With Ultra you can host one event at a time. We keep what you enter (title, description, category, start and end time, venue name and address), the community it is for, and when you created or changed it. Before it is published, the words in it are checked automatically against a list of words we do not allow; if a word matches, the event is not published and you can change it. A member event is shown to everyone using that community, with your display name and profile photo as the host. As with our events, only you see your own choice to go to an event: as a host, you see how many people chose your event, not who. If people report an event, it may be hidden automatically until our team reviews it. Our team can see every member event and can remove it. If a member breaks the rules for events, our team can also stop them hosting events; we keep a record of that until we lift it or the account is deleted. When you create an event, we also record when you confirmed the rules for hosting (Terms, section 16).

Communities

I'M HERE has two communities: Networking and Friendship. When you sign up you choose Networking, Friendship or both. If your account was created before communities existed, the app asks you to choose the next time you open it; until you choose, you are not shown to anyone in Nearby or on the map. If you are checked in when you make this first choice, that check-in ends. We do not choose for you based on anything you did before.

You use one community at a time. Nearby, the map, requests, nearby notifications and events show only the community you are using. Only people using the same community can see you there, or see that you belong to it; they are not told whether you also belong to the other community. You cannot send a request to, or get one from, someone using the other community.

You can make up to three community changes in 24 hours, or up to 15 with Premium and 30 with Ultra; joining, leaving and switching each count as one, and your first choice does not count. Switching the community you are using ends your current check-in; joining the other community, or leaving one you are not using, does not. Chats you already have stay as they are, and blocks, reports and limits are not affected: changing community does not undo any of them.

Your community has replaced the purpose you used to choose when you said you were here. Records from before keep the purpose or intention chosen then until they are deleted under section 6. The 10-day rule for different purposes no longer starts for new requests; a 10-day period already running ends on its own date.

Job title and LinkedIn link

Default purpose. Earlier versions of the app let you choose a default purpose in Settings. It is no longer used or shown, and a value you set is deleted the first time you choose a community or the next time your profile is saved, or when you delete your account.

Job title. You can add a job title when you sign up or later in your profile. It is optional, and leaving it empty does not limit anything in the app. You choose it from our list; if yours is not there, you can choose "Other" in the closest group and, if you like, add your title in your own words. Our list leaves out titles that would reveal religious or political beliefs or trade union membership. When you choose a job title it is shown on your profile, and the same screen has a switch to hide it. In Networking, people who can see you in Nearby can see a job title you show, and it counts in Nearby filters. If you are the only person nearby showing your job title, people using filters can find you by it. It is not shown to people in Friendship. A title in your own words is shown only on your profile and is never used in filters or counts. If you hide your job title, it is no longer shown on your profile or counted in filters, and it stays saved; if you remove it, it is deleted. We do not check job titles, and we do not use them for statistics or advertising. If you wrote an occupation in an earlier version of the app, it stays on your profile as you wrote it, with the same show or hide choice; we do not match it to our list, and it is not used in filters unless you choose a job title from the list yourself, which then replaces it.

LinkedIn link. You can add a link to your own LinkedIn profile (a linkedin.com/in/ address) when you sign up, or later in Settings. It is optional, and you can skip it. The app checks only that the address has the right form, and asks you to open the link and confirm that it is your profile before you save it. This is a check you make yourself: we do not verify that the profile is yours, the app never marks it as verified, and our servers never open or read your LinkedIn page or contact LinkedIn about it. We keep only the address of your profile, without any extra parts added to it (such as tracking codes), your choice of who can see it, when the app showed you the three choices, and, if you changed the link in an older version of the app, a note to show them to you again. You choose who can see the word "LinkedIn" on your profile and open the link, and you can change this at any time in your profile. With Everyone, people you are connected with can see and open it, whichever community you connected in. Before you are connected, it is shown only in Networking: people using Networking who open your profile in Nearby while you are both checked in, and people you send a request to while your request is waiting for an answer and you are both using Networking, can see and open it, and people in Nearby can find you with the LinkedIn filter. In Friendship, it is not shown to anyone you are not connected with. With Only my connections, only people you are connected with can see and open it; it is not shown in Nearby or on requests, and you are not counted in the LinkedIn filter. With No one, it stays saved but is not shown to anyone, and you are not counted in the LinkedIn filter. When you add a link, the setting is Everyone; the screen where you add it shows all three choices. If you added a link before version 1.5.0 of this policy, it also starts as Everyone, which matches how it worked before, and the app shows you the three choices. One group is new: before version 1.5.0, the link was not shown in Connections or chats; with Everyone, people you are connected with, including people you connected with before, can now see it. In every setting, it is not shown to anyone you have blocked or reported, or who has blocked or reported you. People may already have seen it before you changed the setting. The link opens outside I'M HERE, in the LinkedIn app or a web browser. Your LinkedIn page may show your full name, photo and where you work, so people could find out who you are; think about this before adding it. Details you hide in the app, such as your job title or age, may also be visible on your LinkedIn page. The link is not part of your contact card. You can remove it at any time; if you remove it, it is deleted. Changing who can see the link, removing it, or blocking someone in the app cannot undo what they have already seen, and does not block anyone on LinkedIn. In some situations we may temporarily hide LinkedIn links from other people; your saved link stays saved unless you remove it.

Networking and friends slider. Earlier versions of the app had a slider on your profile showing how much you were looking for networking or for friends. We no longer show it to others or use it, and we no longer store new values from it. If you set it, the stored value is deleted the next time your profile is saved, from any version of the app, or when you delete your account.

Connection counts

Your profile shows how many connections you have made in Networking (N) and in Friendship (F). A connection counts once it is accepted, and it still counts after it ends. When this feature started, the counts of existing accounts began from the connections that were open at that time; connections that had already ended are not counted. If you block or report someone, that connection is taken off your own counts; it is not taken off theirs, so nobody can tell from their counts that they were blocked or reported. You always see your own counts. You choose who else can see them: Only me (the setting when this feature starts, also for existing accounts), My connections, or Everyone. Others never see both numbers. In an open chat with you, the other person sees only the count for the community that connection was made in; once the connection ends, the chat no longer shows it. Elsewhere (for example in Nearby), people see only the count for the community they are using. Nothing is shown if that count is zero. Counts are never shown between people where either has blocked or reported the other. The counts are numbers only: they do not show who you connected with, or when.

Nearby filters

In Networking you can filter Nearby by job title (up to five at a time; people with any of them are shown) and by LinkedIn link. Filters only narrow down the people you could already see in Nearby, under the same rules: the same community, blocks in either direction, and the other rules in this policy. The LinkedIn filter counts only people who let everyone see their LinkedIn link. A person who hides their job title, or who lets only their connections or no one see their LinkedIn link, is not counted, and the app shows no difference between a hidden detail and one that was never added.

Next to each option we show how many people match, up to "50+". When 50 or fewer people are visible to you nearby, an option or a result can be shown when only one person matches, so a filter can show a single person, and a change in the count can show that this person has arrived or left. In busier places, or when you choose a job title together with the LinkedIn filter, at least 3 people must match. When nobody matches, the app says so. This is not a promise of anonymity: anyone who can see you in Nearby can see what you choose to show on your profile, and filters can narrow the results down to one person.

If you do not want to be found this way, you can hide your job title, or choose Only my connections or No one for your LinkedIn link; you are then not counted in that filter. Someone you have blocked, or who has blocked you, does not see you in Nearby, and you are not counted in their filters.

Using filters does not change who can see you, and nobody is told that you used them. We do not store or log the filters you choose; they are kept only on your phone while you use them.

Requests to remove intimate images

You can ask us to remove an intimate image of you, or of someone you are authorised to act for, that was shared on I'M HERE without consent, including digitally altered images. You can open the request form from Settings. You can also start a request when you report a profile or photo. The form is in the app, and you need to be signed in to use it.

If you cannot use the form. If you do not have an account or cannot sign in, email info@useimhere.com, ideally with “Removal request” in the subject. Please include: your name, typed at the end of the email as your signature; where the image is on I'M HERE — a link if you have one, or a description such as the name shown on the profile, the town and when you saw it; a short statement that the image was shared without consent; and, if you act for someone, their name. We contact you at the email address you write from. Do not attach the image: we never ask for it, and if an email includes it, we delete it from our mailbox as soon as we see it. We ask for more information only if we need it to find the image or to check that you are the person shown or act for them, and then only what is needed. Our team opens a request for you from your email. If your email has this information, the 48 hours below count from when it arrives. We use your email only to handle the request (section 5). Your email and our replies are kept as section 6 says for emails to info@useimhere.com; the request we open from it is kept like any other request.

What we keep. What you enter in the form (section 3) and, if you start from a profile or photo, which one. Do not send us the image: we never ask for it and do not keep a copy. We do not link the request to an I'M HERE account of your own.

Who sees it. Only members of our safety team, on an admin screen that needs two-step sign-in. When a request arrives, we email our team only its number, the time it arrived, its deadline and a link to that screen — or, if many arrive within an hour, only how many arrived — never its content. These emails are sent through Amazon Web Services (section 8).

What we do. We compare the reported photo with photos on I'M HERE to find identical copies and, if our team confirms them, similar ones. If the request is valid, we remove the image as soon as possible and within 48 hours of receiving it, and make reasonable efforts to remove known identical copies. We record our decision, its reason and who on our team made it. For each removed image we keep a fingerprint: a short code calculated from the image, not the image itself. It is used only to stop the same image being uploaded again. If someone tries to upload it again, the upload is stopped and the uploaded file is deleted straight away; if that fails, it is deleted like other unfinished uploads (above). A fingerprint is not anonymous.

If your photo is removed. The request file records which photo was removed and which account it belonged to. This stays with the file for its full period, even if that account is deleted.

Misuse of the form. To limit how often the form can be used, we keep a fingerprint of the network address that sent it (for an IPv6 address, of its network part only), not the address itself. Like every request to our servers, the request also appears in our server logs, kept for 14 days.

How long we keep each of these is in section 6.

4. Location

Location is the most sensitive data here. Three things matter.

Nobody sees where you are

Your coordinates stay on the server. No user can see your point, their distance from you, or your direction. Others are only told you are nearby. The coloured density you see on the map reflects how busy an area is, not individual people. It shows only people using the same community as you, and an area is coloured only when at least two of them are there. This is not a promise of anonymity.

The map area you look at. To colour the map, the app sends our server the edges of the map area on your screen: when the map opens, after you move it, and from time to time while it stays open. Our server uses this only to work out the density for that area and does not store it in our database; like every request to our servers, it is covered by our server logs, kept for 14 days (section 6). The app keeps the last map area you looked at on your phone, so the map opens there next time. It is not sent to us, but it may be copied into your phone's own backup (for example to your Google account or iCloud) or to a new phone, if you use those features. If there is none and you have already allowed location, the map opens on a wide area around you, not on your point: your phone reads its location for this, and that reading is used only on your phone and is not sent to us or to the map provider. Only the edges of that wider area are sent. This first area shows roughly which area you are in, but not where exactly you are. Otherwise the map opens over London.

Location is deleted in three stages

StageWhat happensWhen
1Your coordinates are recordedWhen you say you are here
2Coordinates and area code are erasedDeleted when your session ends; our target is to complete this within 24 hours
3The remaining record, with no coordinates in it, is deleted entirelyAfter 7 days

If you end the session yourself or delete your account, this erasure is brought forward. It can never be postponed.

If you tap I'm still here before your session ends, your phone's location is read again and a new session starts.

The map provider never receives your precise location

Map imagery is served by OpenFreeMap. Your precise location, identity and account data are not sent to that provider. As with any map you look at, the map images are requested directly from the provider's servers, so those servers see your phone's network address and which map area was requested — nothing else. If you tap Show my area while you are checked in, the map centres on the area of your current check-in — a zone of roughly 5 km², not your point — and no new location reading is taken. If you are not checked in and you have allowed location, the map centres on a smaller area around where your phone is now, again not your point: your phone reads its location for this, and that reading is used only on your phone. This area shows more closely than the first map where you are, but not your exact point. Either way, the map images for that area are requested like any other area you look at, the edges of the area are sent to our server as described above, nothing is drawn on the map, and the area is shown only to you. There is no advertising or tracking software in the map component.

5. Why we process your data, and on what basis

PurposeLawful basis (UK GDPR)
Creating your account, keeping your communities, showing you the people nearby, map and events of the community you are using (section 3), Nearby filters and their counts, running the chat and events, handling event suggestions, publishing events that members host, and showing your connection counts to the people you choose (section 3)Performance of a contract — Article 6(1)(b)
Keeping your job title and LinkedIn link if you add them, with your choices of who can see them, showing them as described in section 3, and counting them in Nearby filtersPerformance of a contract — Article 6(1)(b)
Reviewing reports, enforcing blocks, limiting how often community can be changed, preventing spoofed location and abuse, checking messages, profiles, event suggestions and member events automatically against a list of words we do not allow, stopping a member from hosting eventsLegitimate interests — Article 6(1)(f): user safety
Enforcing the 18+ limitLegitimate interests — Article 6(1)(f): protecting children
Handling requests to remove intimate images, removing them and their copies, and stopping them being uploaded againLegitimate interests — Article 6(1)(f): protecting people from intimate images shared without consent, and meeting the US law that applies to these requests. Where a request includes information about someone's sex life, we also rely on Article 9(2)(g) and the Data Protection Act 2018, Schedule 1, paragraph 10: preventing, investigating or detecting unlawful acts, such as sharing an intimate image without consent
In the United States: asking for your consent to use precise location, and keeping a record of your choice (section 18)Legitimate interests — Article 6(1)(f): meeting US law on sensitive data and showing what you agreed to
In the United States: receiving your app store's adult age result (section 18)Legitimate interests — Article 6(1)(f): protecting children and meeting US law on age
Keeping aggregate, non-identifying usage statistics (for example, how many sign-ups are completed and how many check-ins, requests, accepted requests and contact cards sent there are each day)Legitimate interests — Article 6(1)(f): improving the service
Keeping past event records and images for event history, safety and report review, and aggregate, non-identifying statisticsLegitimate interests — Article 6(1)(f): running events safely and improving them
Keeping your entry on the invite list on our website, including your country, confirming your email address and sending you an invitation code (section 15)Steps you ask us to take before entering into a contract — Article 6(1)(b)
Emailing you about I’M HERE meetups and events in your country, if you ticked the box on the invite list form (section 15)Consent — Article 6(1)(a). You can withdraw it at any time
Suggesting your country in the invite list form from your network addressLegitimate interests — Article 6(1)(f): making the form quick to fill in
Limiting how often the invite list form can be used, and stopping automated or false sign-upsLegitimate interests — Article 6(1)(f): preventing misuse of our website and email
Responding to lawful requestsLegal obligation — Article 6(1)(c)
Giving you the plan you bought, showing the gold ring on your profile photo while it is active, applying the daily number of hellos and the number of community changes for your plan (including the free plan), and handling free trials, renewals and the end of a subscriptionPerformance of a contract — Article 6(1)(b)
Giving team and test accounts access to paid features, showing the gold ring on their profile photo while they have it (as with Ultra), and recording which administrator gave it and whenLegitimate interests — Article 6(1)(f): testing the service as members see it, and keeping control of who has paid features

You can withdraw your device's location permission at any time in your phone's settings. The core function of the app will not work without it. In the United States you can also withdraw your consent in the app (section 18).

You can withdraw your consent to event emails at any time with the link in each one; this does not affect emails we sent before.

6. How long we keep things

DataRetention
Precise location (coordinates)Deleted when your session ends; our target is to complete this within 24 hours
Unfinished photo uploadsScheduled for deletion after 1 day; our target is to complete this within 2 days
Session record without coordinates (including the community you were using; for sessions before version 1.5.0, the purpose you chose)7 days
Messages, continue decisions, shared contact details30 days after the chat stops being writable
Contact card (what you saved)Until you change or remove it, or delete your account
Contact card copies sent in a chatIf a report is made, kept with the report for 90 days and not visible to the other person, then deleted. If you block someone before any report is made, the contact card copies are deleted straight away; the messages themselves follow the 30-day rule in section 7. Otherwise, 30 days after the chat stops being writable
Ended meeting requests30 days
Record that two people who chose different purposes are hidden from each other (who the two people are and when the 10 days end; no purpose or reason)Deleted when the 10 days end; our target is to complete this within 24 hours. Deleted with the account if either of you deletes your account. No new records are created from version 1.5.0; any that exist end on their own date.
Your event choices (Interested / Going)30 days after the event ends or is cancelled; sooner if you delete your account
Event records, event images and event totals (how many people chose an event, no names)12 months after the event ends or is cancelled
Draft events (prepared but never published) and their images90 days after they were last updated
Event suggestions you sentIf you withdraw one, deleted straight away. If we do not accept it, 30 days after our decision. If we make no decision, 30 days after the start time you suggested. If we accept it, 30 days after the event prepared from it ends or is cancelled, or, if that event is deleted without ever being published, when it is deleted. The event itself follows the event rows above and does not record who suggested it
Event notification jobs (internal records that an event reminder, change or cancellation needs to be sent)7 days after the job is completed or no longer needed; a job still waiting to be processed is kept until it is processed
Notification queue (including event reminders, changes and cancellations)7 days
Notification replay protection24 hours
Notification limit counterUntil you delete your account; it is overwritten each time and the count starts again each new day
Your device's notification registration (the device record kept so notifications can be delivered)Until you delete your account (section 7)
Daily request countUntil you delete your account; it is overwritten each time you send a request and the count starts again each new day
Operation receipts24 hours
Server logs14 days
Map area sent to colour the mapNot stored in our database; used only to answer that request. Requests to our servers are covered by the server logs (row above)
Account emails, invite list emails and event emails at our email provider, Amazon Web Services (your address and the email itself)As long as Amazon Web Services needs them to deliver them and to block spam and harmful email; Amazon does not publish a fixed period. We keep no copy
Our email provider's do-not-send list (an address our emails could not reach, or where one was marked as spam, with details of that email)Deleted no later than 90 days after the address was added. This also applies if you delete your account in the meantime
Emails you send to info@useimhere.com, and our replies (held by Zoho, section 8)12 months after our reply. An email we do not reply to is deleted 12 months after it arrives
Network addresses of sign-in requests, kept by Google in the sign-in systemA few weeks, set by Google
Aggregate statistics (non-identifying)90 days
Content a report is about90 days after the report
Report file (category, note, outcome, parties)12 months after the report
Intimate image removal request (what was entered, which photos were removed and from which accounts, our decision and its reason), and a fingerprint used to recognise the same request sent twice12 months after the request. A request we are still handling is kept until it is closed, then deleted
Our team's record of who looked at or decided a removal request, and whyDeleted with the request it belongs to (row above). A record not linked to a request is deleted 12 months after it was made
Fingerprint of a removed image (used only to stop it being uploaded again)3 years after the image was removed. Each time an attempt to upload the same image again is stopped, the 3 years start again. Its link to the request is removed when the request is deleted
Fingerprint of the network address that sent a removal request2 hours; deletion normally completes within a day after that
In the United States: your precise location consent record (section 18)Until you delete your account. If you withdraw consent, the record is updated to show it
In the United States: the adult age result from your app store (section 18)Until you delete your account
An open connection (who you are connected with, the community it was made in, and any intentions chosen in an earlier version of the app)While the connection is open. After it closes, the record is emptied and only the empty trace below remains
Empty trace of a closed connectionIndefinite
An unfinished sign-up (an email address and password that were never verified, with no profile created)Deleted about 1 hour after the sign-up was started, usually within 65 minutes; our target is to complete this within 2 hours
Clean-up record for an unfinished sign-up (only the random identifier, when it was created and a retry count; no email address)Deleted when the clean-up is complete, normally straight away. If it fails, we retry; if it has still not completed after about a day, we stop retrying and the record, and anything not yet deleted, is kept until we deal with it by hand
Your profile and accountUntil you delete it
Your LinkedIn link, your choice of who can see it, when you were shown the choices, and any note to show them againUntil you change or remove it, or delete your account. Removing the link also deletes the rest
Your job title (from our list, or "Other" with your own words) and your choice to show or hide itUntil you change or remove it, or delete your account
Your communities, the one you are using, when you last changed it, and the change numberUntil you delete your account; replaced each time you change
Your connection counts (Networking and Friendship) and your choice of who can see themUntil you delete your account
Record that you blocked or reported someone (who it is, when, whether the block is on, and whether it came from a report; no category or note)Until either of you deletes your account
Times of your community changes in the last 24 hours (up to three, or up to 15 with Premium and 30 with Ultra; if your plan changes, changes you already made are kept until they are 24 hours old; your first choice is not recorded)Each time is kept for 24 hours; the record is deleted 24 hours after your last change, or when you delete your account
Nearby filters you chooseNot stored on our servers; kept only on your phone while you use them
A default purpose set in an earlier version of the app (no longer used)Deleted the first time you choose a community or the next time your profile is saved, or when you delete your account
A networking and friends slider value set in an earlier version of the app (no longer shown or used)Deleted the next time your profile is saved (from any version of the app), or when you delete your account
Account data after we close your account for breaking our rules30 days after closure (section 7)
Invite list entry not yet confirmed (your email address, when you joined, and fingerprints of the links in our email)Deleted 7 days after your latest request to join, and in any case no later than 30 days after the address was first entered; our target is to complete this within 1 hour after that
Confirmed invite list entry (your email address, your country, whether you asked for event emails, when you joined and when you confirmed, and fingerprints of the links that let you remove your address or stop event emails)Until we send you an invitation code, and no longer than 12 months after you confirmed
Invite list entry after we sent your invitation code (also when we sent it)30 days after we sent it. If you asked for event emails: until you stop them, and no longer than 12 months after you confirmed (or 30 days after we sent your code, if that is later)
Any invite list entry, if you remove yourselfDeleted straight away
Your entry, if you stop event emailsEvent emails stop straight away. If your entry was being kept only for event emails, it is deleted straight away; otherwise it follows the periods above
Abuse counters for the invite list form (fingerprints of network addresses and email addresses; not the addresses themselves)Deleted 24 hours after the counter was last used
Invite list email waiting to be sent (a fingerprint of your email address, not the address itself)Deleted as soon as the email is sent, and kept no longer than about 15 minutes
Event email waiting to be sent, used only to send it (a fingerprint of your email address, not the address itself, and which event email it is for)Deleted as soon as your email is sent or skipped, and kept no longer than about 48 hours
Your subscription record (section 3, Subscription)Until you delete your account; updated each time the store tells us about a change
Daily hellos used (section 3)Until you delete your account; it is overwritten each time you send a request, and the count starts again every day at 04:00 London time
Team access (section 3)Until we remove it or the account is deleted; deleted straight away in either case
The store's reference for a purchase, after you delete your account (no longer linked to your account in our systems)Deleted 90 days after you delete your account
Note that hides someone you sent a request to from your Nearby list (who it is and when the request ends)Deleted when they answer or the request ends; our target is to complete this within 24 hours. Deleted with the account if either of you deletes your account
Request notification grouping record (section 3, Technical records)24 hours after the grouping window opened; deleted with your account
Record that we have stopped you hosting events (when, and which of our team did it)Until we lift it or you delete your account
An event you host (Ultra)If you end it before it starts, its title, description and venue are deleted straight away, and its link to your account within 24 hours (we keep it for those 24 hours so we can apply the one-event-at-a-time rule); a record without them (category, start and end time, community) is kept for 12 months after it is ended or cancelled. Otherwise kept like our events: 12 months after it ends or is cancelled. If it was reported before you ended it, or before you deleted your account, its title, description and venue are instead kept, visible only to our safety team, until 90 days after the latest report, and then deleted; if you ended it, its link to your account is also kept until then and removed after they are deleted. If you delete your account, its link to your account is removed straight away

Repeat-request protection record. The record that prevents repeated requests between two people is not deleted on a timer — it is deleted based on state. Once there is no open connection and no pending request between you, any waiting period has expired and no 10-day purpose rule (section 3) is running between you, the record is deleted. It does not store who talked to whom or anyone's purpose; it only determines whether a new request can be sent and whether the two of you are hidden from each other.

Operation receipts: 24 hours. These are short-lived records that prevent the same request from being processed twice by accident; they are deleted after 24 hours.

The notification limit counter. To stop notifications about people near you arriving too often, we keep a single record attached to your account. It holds only the day, how many notifications were sent that day, the time of the last one, and when the record was last updated; no location, no message text, and nothing about the other person. It has no fixed deletion period: it is overwritten each time, the count starts again when a new day begins, and it is deleted when you delete your account.

Safety report files. When you submit a report, a safety file is opened. Content that a report is about is deleted 90 days after the report was made, whether or not the report file is still open. The file itself — the category, your note, the outcome and the identities of the people involved — is deleted 12 months after the report was made. It is kept for that period so that safety history remains traceable: if the same person is reported again, that history needs to be visible. Only an account with safety permissions can access this file. If you delete your account, your identity in the file is replaced with a pseudonym. If you block someone and report them afterwards, any contact card copies between you will already have been deleted when you blocked; the messages are still kept as evidence.

If the law requires it. If the law requires us to keep something, or the police or another public authority lawfully asks us to preserve it, we keep only what is required, only for as long as required, visible only to our safety team, and use it for nothing else. This can mean keeping it for longer than this section says, including after an account is deleted.

Backups. We do not keep a separate backup of your data. The infrastructure that hosts the service stores data in more than one place for its own durability; this is not a "restore archive" and we cannot roll back to an earlier day from it. Once your deletion request has been processed, we cannot bring your data back.

About the "empty trace of a closed connection" row: when a chat is cleared, the connection record itself is not deleted but is emptied. All that remains is the fact that a connection existed and closed; no identity fields and no content remain. It is never displayed anywhere in the app and exists to stop the same connection being reopened by mistake.

7. What happens when you delete your account

Plainly

When you delete your account, your messages remain in the chat on the phone of the person you spoke to. Your name, photo and profile are deleted and they can no longer reach you — but the text of what you wrote is part of their own chat history, so it is not deleted.

Those messages do not stay forever either. Messages are deleted 30 days after a chat stops being writable. A chat stops being writable in three ways: it closes (including when either of you ends the connection or blocks the other), it becomes read-only after both of you decide to continue, or the message allowance runs out. The clock starts at whichever happens first. No chat keeps messages indefinitely. You are warned in the app a week before messages are deleted. You are not shown an exact date or a countdown — only which stage the chat is at. We tell you something has been deleted only once it actually has been.

We do not tell you that the other side's copies were deleted, and we make no such promise.

The moment you request deletion, your access ends, any open session closes, your location is queued for erasure and pending requests lapse. We then delete, in order: your sign-in record and email address, your profile (including your job title, your LinkedIn link and your choices of who can see them), your community records (your communities, the one you are using and the times of your changes), and date of birth, your photo file, your location records, your requests, your continue decisions, your contact card and the contact details you sent, your operation receipts, your event choices, your event suggestions, and any 10-day purpose records involving you (section 3). An event we prepared from one of your suggestions is not deleted, because it is our team's event and does not record who suggested it. The other person's record of their connection with you, including the community it was made in, is not deleted with your account; it follows the connection rows in section 6. If your address is on our email provider's do-not-send list (section 6), it is not removed at that point; it is deleted no later than 90 days after it was added.

Also deleted. In addition to the above, your device's notification registration (the device record kept so notifications can be delivered), your account's activity day information (the day the account was created and the last day it was active), the one-time note that you have opened the app since communities started, the count of requests you sent on your last sending day, the count of hellos you have used today, your subscription record, any team access, any record that we stopped you hosting events, the notes that hide people you sent requests to from your Nearby list (including such notes on other people's accounts that refer to you), the record used to group your request notifications, your connection counts and your choice of who can see them, records that you blocked or reported someone and records that someone blocked or reported you (report files themselves follow section 6), in the United States your precise location consent record and the adult age result from your app store (section 18), and the record of when you agreed to our Terms are deleted. Any events you host that have not yet taken place are cancelled (people who chose them are told it was cancelled), and their title, description and venue are deleted, unless the event has been reported (section 6). These, and events you hosted that have already taken place, are kept as section 6 says, without any link to your account. If a purchase was linked to your account, the store's reference for it is no longer linked to you in our systems and is deleted 90 days later (section 6); we keep it for that time only so that we can recognise messages Apple or Google send about it, answer you if you write to us about that purchase, and move the plan to a new I'M HERE account if you restore the purchase there. Deleting your account does not cancel a subscription: cancel it in your App Store or Google Play account. Apple and Google keep their own records of your purchases under their own privacy policies. If a safety file has been opened about you, your identity in that file is replaced with a pseudonym; the file itself is kept for our safety history for up to 12 months. A request to remove an intimate image is not deleted with an account; it follows sections 3 and 6.

If we close your account. If we close your account for breaking our rules, your access ends straight away. We keep your account data for 30 days after the closure so that you can contest the decision or ask for a copy of your data — write to info@useimhere.com from the email address on your account. If you would rather we deleted it sooner, say so in the same email. After 30 days we delete your account data in the order described above, and your identity in any safety file is replaced with a pseudonym; the safety file itself is kept for 12 months from the report, as section 6 says. Two exceptions: if we close an account because the person is under 18, we delete the data without waiting (section 12); and if the law requires us to keep something, or a public authority lawfully asks us to preserve it, we keep only what is required, only for as long as required, and use it for nothing else.

The one thing that cannot be deleted. Aggregate counters that cannot be linked to anyone are not reversed, except that when your account is deleted, any event choices you still have are removed from those events' totals of people who chose them. For example, your contribution to a number such as "how many people joined that day" is not removed — because that number does not record who joined, only how many. It therefore does not point to you.

Your identity in report files

If there is an open report involving you, your identity fields in that file are not deleted but replaced with a pseudonym, so an open safety review can continue even if the reported person deletes their account.

We will also tell you the limit of that: this pseudonym is not anonymisation. Someone with access to the database could reverse it. It protects against an outside party and against someone using the admin screens; it does not protect against someone with access to the system itself.

8. Who we share data with

We do not sell your data. We do not share it with ad networks, data brokers or marketers. These are the providers we need to run the service:

ProviderForWhat is sent
Google FirebaseSign-in (including some account emails), database, photo storage, server functions and notifications, and the invite list on our website (section 15)The data described in this policy, and basic technical information the app sends so that these services work (such as device model, operating system version and app version). Your sign-in email address in the sign-in system; an email address you put on your contact card is kept in the app database
Amazon Web Services (Amazon SES)Sending account emails: confirming your email address, resetting your password and confirming a new sign-in email address; and invite list emails: confirming your address and sending your invitation code (section 15); and, if you asked for them, event emails (section 15)Your email address and the email we send you. An account email contains a single-use link; an invite list email contains a link to confirm or remove your address, and an invitation also contains your invitation code. An event email contains links to stop event emails or remove your address. Nothing else from your account or the invite list. Amazon may store and check these emails to block spam and harmful email
OpenFreeMapMap imageryRequests for the map area shown on screen (your phone's network address and the requested area) — including the wide area around you that the map may open on, and the area Show my area centres on (section 4). Your precise location, identity and account data are not sent

On iPhone, notifications are delivered through Apple's push notification service. Apple receives a device token, a fixed code that tells your phone which short notification text to show (for example "You have a new message") and, for chat and event notifications, a random reference so the right screen opens. Apple does not receive your name, your location or the text of your messages from us.

Email you send to info@useimhere.com, and our replies, are handled by Zoho, the email provider for that address (section 9).

We chose not to use another map provider because its tracking could not be switched off.

LinkedIn. We do not send your data to LinkedIn, and we do not contact LinkedIn to check or read anyone's LinkedIn page. If you add a LinkedIn link, the link that opens is only your LinkedIn profile address; we add nothing to it. When you or someone else taps a LinkedIn link in the app, the phone opens the LinkedIn app or website directly, and LinkedIn's own privacy policy applies to what happens there. For example, if the person who opens it is signed in to LinkedIn, LinkedIn may let the profile's owner see that they viewed it, depending on the viewer's LinkedIn settings.

Beyond this, we share data only where we are legally required to, in response to a valid legal request.

Apple and Google (payments). If you buy Premium or Ultra, you pay Apple (App Store) or Google (Google Play) under their own terms and privacy policies; we never see your card or payment details. When you buy, the app gives the store a random code that we create, so that the store's messages about your purchase reach the right account; Apple or Google keep this code with the purchase. The code is random: it is not made from your name, email address or account, and only our records connect it to you. To keep your plan up to date, our server asks the store about your purchase using the store's reference for it, and receives the details listed in section 3 (Subscription). We send the store nothing else about you.

Apple and Google (age result, United States). When you create an account in the United States, your phone asks Apple or Google for an age result (section 18). We send them nothing about you for this.

9. Where your data is held

Most of your data is held on servers in the United Kingdom, in the London region. The database, the file storage and the server functions that process your data are all located there — that data is not only stored in the UK, it is processed there. Emails we send through Amazon Web Services — account emails, invite list emails and event emails — also go out from its London region.

Exceptions. The sign-in system (Google's Firebase Authentication), which holds your sign-in email address and your password in protected form, is run by Google from data centres in the United States. Notifications are delivered through Google's worldwide network and, on iPhone, Apple's push notification service. Email you send to info@useimhere.com is held by Zoho in the European Union, and Zoho's support staff in India may access it.

Transfers to the United States rely on the UK–US data bridge: Google LLC is certified under the UK Extension to the EU–US Data Privacy Framework. Google may also access other data from outside the United Kingdom in the course of maintenance and support. Amazon Web Services keeps the data of the emails we send in its London region unless it has to move it to provide the service or the law requires it. Any such transfer relies on the safeguards required by the UK GDPR; for Amazon Web Services, these are part of its service terms.

10. Your rights

UK data protection law gives you the right to:

If you are on our invite list, you can remove yourself, or stop event emails, at any time with the links in our emails (section 15). You can also object at any time to our use of your data for event emails, which are direct marketing; we will then stop.

Write to info@useimhere.com. We respond within one month.

If you are unhappy with our response you can complain to the UK regulator, the Information Commissioner's Office, at ico.org.uk/make-a-complaint. We would prefer you came to us first, but you do not have to.

11. Security

The app cannot reach the database directly; every operation goes through checked server functions, and the database rules refuse direct access outright. Photos are held in private storage and opened only through time-limited addresses. Invitation codes are never stored in plain form.

No system is perfect. If a breach affects your personal data, we will make the notifications the law requires.

12. 18+ only

This app is for people aged 18 and over. Your age is calculated on our server from the date of birth you give when you sign up; the app on your phone cannot set or override that result. We do not check your date of birth against an identity document. If we learn an account belongs to someone under 18 we close it and delete the data, unless the law requires us to keep it. In the United States, the app also asks your app store whether you are an adult (section 18).

13. Changes to this policy

When we update this policy we change the version number and date on this page. For significant changes we will tell you in the app.

14. This website

This website is served through Cloudflare. To deliver and protect the site, Cloudflare, as our hosting provider, records your device's network address and technical details of each request, including the approximate country it works out from that address. Cloudflare keeps these records for a limited period that it sets; we can view them in our Cloudflare account to keep the site working and secure, but we do not copy, export or keep them. The site sets no cookies, runs no analytics or advertising, and loads its fonts from our own server rather than a third party. If you are shown a language switch, your choice is kept only in your own browser.

Links in our account emails. When a link in one of our account emails opens a page on this site (useimhere.com/auth/action), that page sends the one-time code in the link — and, if you are choosing a new password, that password — straight from your browser to the sign-in system run by Google, which completes the action. If you use the page to undo a change to your sign-in email and then ask for a password reset link, the page also sends your sign-in email address to the same system so that it can email you that link. Your new password does not pass through our servers. The page sets no cookies and stores nothing in your browser. If your email app loads the images in our emails, such as our logo, they come from this site and are the same for everyone, with nothing that identifies you or the email.

The invite list form. When you join the invite list, the form sends the email address you enter, the country you choose and whether you ticked the event emails box straight from your browser to our server functions in the London region (section 15); they do not pass through Cloudflare. To suggest a country, when you open the form the page asks our website once for the country that Cloudflare works out from your network address; we do not store this suggestion, and you can change it. The pages that open from links in our invite list emails (useimhere.com/invite/…) send only the code in the link, and act only when you press the button. The form and these pages set no cookies, and they do not store your email address or the code from the link in your browser.

15. The invite list

I'M HERE is invitation-only for now. On this website you can join our invite list so that we can send you an invitation code when one is available. You choose your country, so that we send invitations — and event emails, if you ask for them — for the right country. The invite list is not a newsletter: unless you tick the box for event emails, we do not use it for marketing, and we do not send you news, offers or anything else.

What we keep. Your email address; the country you chose (United Kingdom, Türkiye, United States or Other); whether you asked for event emails and, once you confirm your address, when you agreed and which version of the wording you agreed to, and when you stopped them if you do; whether you have confirmed it and whether we have sent you an invitation code; when you joined, when you confirmed and the day we sent the code; while your confirmation link is valid, a fingerprint of that link; and fingerprints of the links in our emails that let you remove your address or stop event emails (not the links themselves). Between your request and our email, a short-lived sending job holds a fingerprint of your email address, not the address itself; it is deleted as soon as the email is sent, and kept no longer than about 15 minutes. When we send event emails, a sending job holds the same fingerprint until your email is sent, and no longer than 48 hours; if you remove your address, we delete it straight away. To stop the form being misused, our abuse counters also keep short fingerprints of your network address (for an IPv6 address, of its network part only) and of the email address entered (section 3); a fingerprint is not the address itself, but it is not anonymous. Like every request to our servers, the network address of the form request is also recorded in our server logs, which are kept for 14 days (section 3). We keep nothing else: no name, no city or location and no information from your device.

Confirming your address. After you join, we send one email to the address you entered, usually within a minute, asking you to confirm it. This stops anyone adding someone else's address. If you join again before confirming, the new email's link replaces the earlier one. If the address is not confirmed within 7 days of your latest request to join, we delete it, and we never keep an unconfirmed address for more than 30 days after it was first entered. The form gives the same answer whether or not an address is already on the list, and we do not send another confirmation email to an address that is already confirmed.

Your country. We ask for your country because we open invitations and hold events country by country, so that, for example, an event in Istanbul does not reach someone in London. The form suggests a country based on the country Cloudflare works out from your network address (section 14); we do not store this suggestion, and you can change it. We keep only the country you choose.

Event emails (optional). If you tick the box, we also email you about I'M HERE meetups and events in your country. The box is never ticked for you, and you can join the invite list without it. Your agreement counts only once you confirm your address with the link in our email. These emails are only about I'M HERE meetups and events; we do not send offers from other companies. A member of our team writes each event email and chooses to send it to the people in one country who asked for them; we never send them automatically. After an event email is sent, we do not keep a record of who it went to. Every event email has a link that stops event emails straight away and keeps you on the invite list, and a link that removes your address altogether. You can also write to info@useimhere.com. If you joined the invite list before 4 November 2026, you did not choose event emails: we do not send you any, and we will not email you to ask. If you choose the United States, the event emails box is not shown and we do not send you event emails. If you choose Türkiye, the event emails box is shown. We do not send you event emails unless you tick it, and we are not sending event emails to Türkiye at the moment.

Your invitation. When an invitation is available, a member of our team sends you an invitation code by email. We send invitations ourselves, from our admin screen; they are not sent automatically. The code works once and expires after 7 days. It is an ordinary invitation code (section 3): we do not record which code went to which address, and we do not link your invite list entry to an account you may create later.

Why, and on what basis. We keep your entry because you asked us for an invitation: this is a step you ask us to take before you start using the app (UK GDPR Article 6(1)(b)). The abuse counters rely on our legitimate interest in preventing misuse of our website and our email (Article 6(1)(f)). Your country is part of the same step (Article 6(1)(b)). Event emails rely on your consent (Article 6(1)(a)), which you can withdraw at any time. Suggesting a country in the form relies on our legitimate interest in making the form quick to fill in (Article 6(1)(f)).

How long. An entry that is not confirmed: 7 days after your latest request to join, and no more than 30 days after the address was first entered. A confirmed entry: until we send you an invitation code, and no longer than 12 months after you confirmed; if we have not been able to invite you by then, we delete your entry without emailing you, and you are welcome to join again. After we send your code: 30 days, so that we can help if it did not arrive; then it is deleted. If you asked for event emails, we keep your entry after sending your code so that we can keep sending them, until you stop them and no longer than 12 months after you confirmed. If you stop them and your entry was being kept only for them, we delete it straight away. We check for entries that are due to be deleted every hour. These periods are also in the table in section 6.

Leaving the list. Every email we send about the invite list has the same link to remove your address, and it works for as long as your entry is kept. Event emails also have a separate link that stops only event emails. The page it opens asks you to confirm with a button, then deletes your entry straight away; after that, the link no longer works. You can also write to info@useimhere.com. Once you have left the list, we do not email you again.

Who handles it. The list is kept in our database at Google Firebase, in the London region, and only members of our team with administrator access can see it. The form sends your email address straight to our server functions there; it does not pass through Cloudflare, which serves the pages of this website (section 14). Confirmation emails, invitations and event emails are sent by Amazon Web Services (Amazon SES) from its London region; as with account emails, Amazon may store and check them to block spam and harmful email, and an address our emails could not reach may go on its do-not-send list (section 6). We do not share the list with anyone else.

Separate from your account. Your invite list entry is separate from any I'M HERE account. Creating an account does not change it, and deleting your account does not delete it; it follows the periods above.

Your rights. Your rights in section 10 also apply to your invite list entry. Write to info@useimhere.com from the address that is on the list.

18 and over. The invite list is for people aged 18 and over. If we learn that an address belongs to someone under 18, we delete it.

If you come from one of our adverts. If you reach this website from one of our adverts, for example on Instagram or Facebook, you join the invite list in the same way and we keep the same information described above. We do not record which advert you came from. Advertising platforms may add a code to the link you tap; our website does not store it, does not send it to our servers and does not pass it on. Like the rest of the web address, it is seen by Cloudflare, which serves this website (section 14). Joining the invite list does not mean you will receive an invitation by a particular date.

16. Our adverts

We advertise I'M HERE on social media, including Facebook and Instagram, which are run by Meta. We choose who our adverts are shown to using the advertising platform's own settings, such as people aged 18 and over in the United Kingdom or Türkiye; the platform uses its own information about its users to do this, under its own privacy policy. We do not give Meta, or any other advertising company, your email address or any other information about you, and our website and app do not use advertising cookies, tracking pixels or similar tools. If you comment on one of our adverts, Meta and other people can see your comment under Meta's rules; we do not copy comments or your profile into our own records.

17. Users in Türkiye

Information required by Türkiye's data protection law (KVKK) is in section 17 of the Turkish version of this policy.

If you are in Türkiye, we collect your data directly from you, as the data controller in the United Kingdom. Most of your data is held in the United Kingdom, in the London region. As section 9 explains, the providers that run the service may access or process data from other countries, including the United States, the European Union and India, only to provide and protect the service and to support you. Google, Amazon Web Services, Cloudflare and Zoho process this data on our behalf, under their service agreements with us. Apple and Google act on their own behalf for payments.

If you join the invite list, we collect your email address and country through the form on our website, including when you arrive from one of our adverts (section 16).

18. Users in the United States

This section adds to the rest of this policy if your App Store or Google Play account is in the United States.

Your store country. To know whether this section applies, the app asks your phone for the country of your App Store or Google Play account. It is checked only on your phone, while the app is open. It is not saved on your phone, sent to us or logged. If the app cannot read it, it treats you as not in the United States. We do not use your network address or location for this. Because we create the records below only when your store country is the United States, they show that it was when they were made.

Precise location and your consent. Precise location is sensitive information. Before the app uses it, it asks for your consent on a separate screen, as well as your phone's location permission. Section 4 explains how location is used and deleted. You can withdraw your consent at any time in Settings. Your active check-in then stops, its coordinates are deleted as section 4 says, and new check-ins and map location stay off until you consent again. You can also turn off location permission in your phone's settings. Withdrawing does not undo what happened before. Under UK data protection law our lawful basis for location stays as section 5 says; this consent is in addition to it.

Your consent record. We keep one record of your choice: whether you gave or withdrew consent, which version of the consent screen you saw, when you last gave it and, if you withdrew it, when, and a change counter. It contains no location. We keep it until you delete your account, so that we can show what you agreed to.

Age result from your app store. When you create an account, the app asks Apple or Google, through your phone, whether you are an adult. They decide what to share, and you may need to confirm your age in your app store first. If the answer is that you are an adult, we record only that, whether it came from Apple or Google, and when. We do not receive or keep your age range, the date of birth on your store account or any identity document. If the answer is that you are under 18, or a required answer is not available, you cannot create an account, and we keep nothing that identifies you from that attempt. The answer comes from your phone; it is not an identity check. We still ask for your date of birth (section 12). We use the answer only to apply our 18+ rule and laws on age, never for advertising, analytics or profiling, and we do not share it. We keep it until you delete your account.

No sale, no targeted advertising. We do not sell your personal information, including your precise location. We do not share it for targeted advertising, or use it to make decisions about you that have legal or similarly significant effects. So there is nothing to opt out of. We do not track you across other companies' apps or websites, so Do Not Track or Global Privacy Control signals change nothing here.

Your rights. Wherever you live in the United States, you can ask us to confirm whether we hold personal information about you, get a copy in a portable format, correct it or delete it. You can do much of this yourself in the app (sections 7 and 10). Write to info@useimhere.com from the email address on your account; someone you authorise can write for you. We may ask for information to confirm it is you or that they act for you. We respond within one month. We will not treat you differently for using these rights.

If we say no. We tell you why. You can ask us to look again by replying with "Appeal" in the subject. We answer within 45 days and explain our decision. If you are still unhappy, you can contact the attorney general of your state.

Intimate images. In the United States, requests to remove intimate images shared without consent are covered by the TAKE IT DOWN Act. Section 3 explains how we handle them.

Where your data is held. Your data is held and processed in the United Kingdom, with the exceptions in section 9.

19. Contact

For anything: info@useimhere.com

Privacy Policy · Version 1.10.2 · I'M HERE