Last updated: November 22, 2026
Social Passport (the app, and the website at socialpassport.me) keeps your trips in one calendar and tells you when friends will be in the same place at the same time. To do that it has to know where you're going, and sometimes where you are. This policy explains what we collect, why, who else handles it, how long we keep it, and what you can do about it.
The short version:
•
We collect what the features you use need, and for most features less than that: places and days rather than coordinates, hashes rather than address books.
•
Friends see your whereabouts only as far as your location sharing setting allows. The default shows them only the trips that cross theirs.
•
We don't sell your data, show ads, or use trackers or analytics.
•
You can export everything or delete your account in the app, at any time: You › Your data and You › Account.
Who we are
The controller of your personal data is Kingstinct AB, a company registered in Sweden.
We haven't appointed a data protection officer. Write to the address above about anything in this policy.
What we collect, and why
Your account
•
When you sign in with Apple or Google: the provider's account identifier, your email address (Apple may give us a private relay address) and your name if the provider shares it. We check the sign-in token with the provider and never see your password.
•
When you sign in with email: your email address. We send you a six-digit code; we store only a scrambled (hashed) copy, for 10 minutes.
•
Your profile: the name you choose, a profile photo if you add one (stored as a small square image), your time zone, and an invite code for your QR code and invite link.
•
Your confirmation that you're 18 or older, and when you gave it (when you sign up, or once on your next launch for accounts made before we asked).
•
Sessions: when you sign in we give your device a token. We store only a hash of it, until you sign out or delete your account.
Trips and places
•
Trips you add: the place (a town, region, country or wider area), the dates (or none, for a "someday" plan), whether flights and stays are booked, and whether a trip is private.
•
Homebases you add, and your current place ("I'm currently in …").
•
Booking preferences you save for booking links: number of adults, the ages of any children, cabin class, bags and similar filters.
•
Interests you pick from our list.
•
Derived information we work out from the above and from the sources below: journeys, time probably spent at home between trips, days per country, how confident we are about each stop, and where your trips meet your friends' (crossing paths). Most of this is calculated when you ask for it and not stored.
Forwarded booking emails
Each account has a personal forwarding address. When you forward a booking confirmation to it:
1.
Cloudflare receives the email and keeps the raw message in temporary storage until it's delivered to our server: usually seconds, at most 7 days.
2.
A Cloudflare AI model (Clef, on Workers AI) reads the sender, the subject and the first part of the text, plus the text of any PDF attachments when needed, to judge whether it's a travel booking. It's never given your forwarding address.
3.
Our server reads the booking: places, dates and times, flight, train and ferry numbers, carrier, booking reference, and the name and address of a hotel or other stay. When the email has no machine-readable booking data, we send its text to Anthropic's Claude model to extract the same details. This is the only use of Anthropic, and it happens only for emails you forward.
4.
We store the bookings, not the email. We keep a hash of each email's content for 400 days so that forwarding it again does nothing, and a short note of what became of it (subject, sender's domain, time, outcome) for 90 days, shown in You › Imports › Email activity.
5.
If we're not sure an email is a booking, it waits in "Possibly a trip?" with its plain text until you add or ignore it, at most 30 days. The text is deleted when you decide.
6.
You › Imports › Remove imported trips and start over deletes everything your forwarded emails imported (trips, bookings, "Possibly a trip?" emails and the hashes that skip repeats), so you can forward them again. Trips you added or edited, and trips from photos, calendars or location, stay. Email activity notes stay until they expire, marked as cleared.
Booking emails can name other people travelling with you. We don't extract or store passenger or guest names.
To show a hotel on the map when the booking has an address but no coordinates, we look the address up with OpenStreetMap's Nominatim service. We send only the address (or the property name and town) and the country, never anything about you, and keep the answer so the same address is never looked up twice.
Photos, calendars and location (optional)
Each of these is off until you turn it on in You › Imports, asks for your phone's permission only when you do, and can be turned off there, which deletes what it sent.
•
Photos: your photos and videos never leave your phone unless you favourite them (below). For each one we receive the identifier your phone gives it, when it was taken, and its location rounded to about 100 m. We turn the location into the nearest town and then drop the coordinates. Screenshots aren't sent. We use this to fill in and confirm trips and to show each trip's album on your phone.
•
Favourite photos: a photo you mark as a favourite is resized on your phone (which also removes its embedded metadata) and uploaded, so it shows on your other devices and in links you share. We store resized copies only, without location or camera metadata.
•
Calendars (your phone's calendar, or Google Calendar): read on your device, a year back and a year ahead. Only events with a location, or with a flight in the title, are sent: their dates, the location text, the title for flights only, and a hash of the event's identifier. We turn the location into a place and store that, the dates and hashes. We don't store titles or location text.
•
Location history: a few times a day, also when the app is closed, your phone notes your location at about 1 km accuracy, using the phone's low-power location services. We turn each into the nearest town and store only the town and the day, never coordinates or times. It uses the "Always" location permission and is off unless you turn it on.
•
"Use my location": when you tap it, or when the app later refreshes your current place while open, we receive coordinates, find the nearest town and keep only that town and the day. Those days also count as evidence for your trips. You can delete them in You › Places.
Friends
•
Friendships: who you're friends with and since when; friend requests (kept until 30 days after they're answered, or 60 days if never answered).
•
Contact details you choose to add (phone, WhatsApp, Signal, Telegram, Instagram, an email). Only your friends see them.
•
Finding friends in your contacts: when you ask, the app reads your phone's address book on your phone. It sends us only a scrambled (SHA-256) version of each email address in it, at most 2,000. We compare them with accounts' verified emails, tell you who's already here, and keep nothing: the hashes aren't stored or logged. Names and phone numbers never leave your phone. "Find in my contacts" on a friend's profile is entirely on your phone.
Messages and community
•
Chats with friends and dating matches: the messages, when they were sent, and how far each of you has read. Deleting a message removes its text for both of you.
•
Place chats: public rooms for each place. Anyone signed in can read them. We store your membership, your messages and your notification choice.
•
Community groups: links to groups (WhatsApp, Telegram and others) you add for a place, and your votes. Others never see who added or voted on a group. Some groups, like a place's subreddit, are found automatically from Wikidata.
•
Reports: when you report someone or something, we store the reason, your note and, for a message, a copy of its text, so that deleting the message doesn't remove the evidence. The person you report isn't told. Our moderators review reports; if one warns you, we note when.
•
Blocks: who you've blocked.
Dating (optional)
Dating is off until you turn it on. When it's on we store your bio, your birth year (needed to turn dating on: dating refuses anyone it makes younger than 18), your likes, passes and comments, and your matches. People whose trips meet yours see your name, photo, bio, age, interests and the place and dates you'll share. We don't ask for gender or sexual orientation. You can hide your profile or turn dating off at any time, in Dating or You › Privacy.
Push notifications
If you allow notifications we store your device's push token and your notification choices (chats, dating, crossing paths, message previews).
Crash and error reports
When the app, the website, our server or our email service hits an error, it sends a report to Sentry so we can fix it: what went wrong and where in our code, the app version, the kind of device and operating system, the screens or requests that led up to it (as paths, without search terms or the secret parts of links), and, if you're signed in, your account's random id. Reports never contain your name, email address, messages, trips, booking emails, photos or anything you typed, and we don't record screens or sessions.
Shared links
When you create a share link for a trip, anyone with the link can see the places and dates you chose, your favourite photos from them and, if you choose, your name. Nothing else. Turning a link off makes the page and its photos disappear.
Who sees what
Location sharing (You › Privacy › Show my location) decides who sees where you are and will be:
•
Never: nobody. No crossing paths with anyone, in either direction, and dating matching is off.
•
Crossing paths (the default): friends see only those of your trips that meet one of theirs, and never your current place.
•
Friends: friends always see your current place and your current and upcoming trips.
•
Everyone: the same, also for anyone signed in who sees your profile, for example in dating or a place chat.
A trip you mark private is hidden at every level. Blocking someone hides your whereabouts from them at every level. Friends don't see your past trips, only the times you already crossed paths with them.
Other people see your name and profile photo where you interact with them: as a friend, in chats and place chats, on a dating card, in friend requests, and when someone finds you from their contacts. Your email address is never shown to other users, unless you add it to your contact details for friends.
Legal bases
Under the EU General Data Protection Regulation (GDPR) we rely on:
•
Performing our agreement with you (Article 6(1)(b)) for your account, trips, friends, crossing paths, chats, place chats, groups, dating, email import, photos, calendars, shared links and notifications: the service you asked for.
•
Your consent (Article 6(1)(a)) for Location history and for finding friends in your contacts. You can withdraw it at any time by turning the feature off; that doesn't affect what was done before.
•
Our legitimate interests (Article 6(1)(f)) in keeping the service safe and working: rate limits, preventing duplicate imports, handling reports and blocks, keeping technical logs, and processing the email addresses in other people's contacts when they search for friends (only as hashes, compared and dropped). You can object; write to us.
•
Legal obligations (Article 6(1)(c)) where the law requires us to keep or hand over data.
Who else handles your data
We use these service providers (processors) to run Social Passport. Each gets only what it needs for its task.
•
Hetzner Online GmbH (Germany): hosts our server and database, in Nuremberg, Germany. Everything we store is stored here.
•
Cloudflare, Inc. (USA): hosts the website; receives forwarded emails (Email Routing), stores them briefly and classifies them (Workers AI); provides our domains' DNS.
•
Anthropic PBC (USA): extracts bookings from forwarded emails without machine-readable booking data. Anthropic doesn't use our API data to train its models.
•
Expo (650 Industries, Inc.) (USA): delivers push notifications, through Apple (Apple Push Notification service) and Google (Firebase Cloud Messaging). They receive your device's push token and each notification's content: the sender's name and, with previews on, the start of the message, or a friend's name, city and dates.
•
Functional Software, Inc. (Sentry) (USA): receives crash and error reports from the app, the website, our server and our email service, with technical data only (see "Crash and error reports"), stored in the USA.
•
Resend, Inc. (USA): sends sign-in codes by email.
•
Apple and Google: Sign in with Apple and Google Sign-In; Google Calendar when you connect it (see "Google user data").
•
GitHub, Inc. (USA) stores our software's container images. It holds no user data.
We also use these services, which don't receive anything about you as a person:
•
OpenStreetMap Nominatim (OpenStreetMap Foundation, UK): addresses of stays, as above.
•
Wikimedia (Wikidata, Wikimedia Commons) and QLever: place photos and information. We ask about places only.
•
Event sites (Luma, Meetup, Eventbrite, Resident Advisor and, if enabled, Ticketmaster): our server looks up public events by place and date, never with anything about you.
Loaded directly by your device: map tiles from OpenFreeMap and satellite imagery from NASA, and event images from the event sites. These services see your device's IP address and which part of the map or which image is loaded, like any website you visit.
Booking links (Google Flights, Booking.com, Kiwi.com, Airbnb, Cruise Time Tables) open those sites with the place, dates and your booking preferences filled in. What happens there is covered by their privacy policies. Links may carry our affiliate identifier.
We don't sell personal data, and we don't share it for advertising.
We may disclose data if Swedish or EU law requires it, for example to answer a lawful order from an authority.
Transfers outside the EU
Our database and stored files are in Germany. Some providers above are based in the USA, so some data (for example a forwarded email's text, or a push notification) is processed there. Where a provider is certified under the EU–U.S. Data Privacy Framework we rely on that; otherwise on the European Commission's Standard Contractual Clauses. Write to us for a copy of the safeguards.
TODO (owner to confirm): data processing agreements are in place with each processor above, and which transfer mechanism each one uses.
TODO (owner to confirm): Sentry's retention on our plan (90 days above), and that "Prevent Storing of IP Addresses" is on in each Sentry project so reports keep no IP address.
How long we keep it
We keep your data until you delete it or your account, except:
•
Sign-in codes: 10 minutes.
•
Forwarded emails at Cloudflare: until delivered to our server, at most 7 days.
•
"Possibly a trip?" emails: until you decide, at most 30 days.
•
Email activity notes: 90 days.
•
Hashes of forwarded emails (to skip repeats): 400 days.
•
Rate-limit counters (keyed by a hash of your account, email address or IP address): 2 days.
•
Friend requests: 30 days after they're answered, 60 days if never answered.
•
Location history: days older than about 14 years (5,000 days) are dropped.
•
Typing indicators: a few seconds, in memory.
•
Crash and error reports at Sentry: 90 days.
When you delete your account, everything about you is deleted at once, including your trips, evidence, photos, favourites, shared links, chats in both directions, dating data, reports by and about you, and push tokens. Two things stay, without your name: community groups you added (others may rely on them), and cached lookups that don't refer to you (place photos, events, geocoded hotel addresses).
TODO (owner to confirm): whether the database is backed up, and how long backups are kept before deleted accounts disappear from them.
Your rights
Under the GDPR you have the right to:
•
Access your data and get a copy: You › Your data › Export my data downloads, as one file: your account and settings (profile, interests, booking preferences, notification choices, your 18+ confirmation, your forwarding address), how you sign in and your open sessions (when each began), trips, bookings, time you said you were or weren't at home, what your phone sent as evidence row by row (each photo's identifier, time and town; each calendar event's hash, dates and place; each location day's date and town; your favourites), "Possibly a trip?" emails with their text, Gmail forwarding confirmations, which senders you trust, friends, contact details, friend requests, your 1:1 chat messages sent and received, your dating likes, passes, comments and matches, the people you blocked, the reports you made, warnings a moderator sent you, shared links, email activity, groups and votes, place chats and their messages, and how many devices get your push notifications. Other people appear in it by name only.
•
Reports about you aren't in the export: a report's details could reveal who made it, and the GDPR lets us withhold that to protect them (Article 15(4)). If you ask, we'll tell you what we can without identifying anyone.
•
Rectify it: edit your profile, trips and settings in the app, or write to us.
•
Erase it: You › Account › Delete account… deletes your account and data immediately. Individual items (trips, places, photos, calendars, location history, messages, groups, share links) can be removed on their own.
•
Restrict or object to processing, including processing based on our legitimate interests.
•
Data portability: the export is a machine-readable JSON file.
•
Withdraw consent at any time by turning the feature off.
You don't need the app for any of this: email
[email protected] from the address on your account and we'll answer within a month.
You can also complain to the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten,
imy.se) or the authority where you live.
Children
Social Passport is for people 18 and over, because it includes dating and lets adults meet. Everyone confirms they're 18 or older when they sign up (accounts made before we asked confirm once, on their next launch), and dating can only be turned on with a birth year that makes you 18 or older. We don't check identity documents. If you believe someone under 18 has an account, tell us and we'll delete it.
Google user data
This section covers what Social Passport gets from Google, and applies on top of the rest of this policy.
What we access
•
Google Sign-In: your Google account identifier, your email address and your name. We use them for your account only. We don't use your Google profile picture.
•
Google Calendar, only if you connect it in You › Imports: read-only access, with two scopes: calendar.calendarlist.readonly, to list the calendars you have (only each calendar's identifier and whether it's hidden or selected), and calendar.events.readonly, to read events in the calendars you see, a year back and a year ahead. From each event we read its dates and times, its location, its title and its identifier. We never create, change or delete anything in your calendar, and we don't read calendar names, descriptions, attendees or sharing settings.
How we use it
Only to sign you in and run your account, and to turn your calendar events into trips on your timeline and map, which can then show friends who'll be in the same place as you (crossing paths) and fill in booking links and events for those trips. Nothing else.
What leaves your device, and what we store
•
Your events are read on your device, directly from Google (in the phone app, or in your browser on the website). The Google access token stays on your device; our server never receives it.
•
Events without a location and without a flight-like title never leave your device.
•
For the other events our server receives the dates and times, the location text, the title for flight-like events only, and a hash (SHA-256) of the event's identifier. It turns the location into a town using our own place data (GeoNames and OurAirports), then stores only the hash, the dates and the town. Titles and location text aren't stored, and nothing about them is logged.
•
No third-party geocoder sees your calendar data, and Google user data is never sent to AI providers (Anthropic, Cloudflare Workers AI or any other). The AI models described above are used only for emails you forward.
Who sees it
Trips made from your Google Calendar events are trips like any other:
•
They can be shown to your friends according to your location sharing setting (You › Privacy › Show my location): by default only where they cross a friend's trip; with "Friends", to all your friends; with "Everyone", also to other signed-in users who see your profile (for example dating matches); with "Never", to nobody. Marking a trip private hides it at every level.
•
They can be named in push notifications to you and to friends you cross paths with, for example "You'll cross paths with Ana in Lisbon" with the dates. Notifications go through Expo and Apple's or Google's push services (see "Who else handles your data").
•
They're stored on our server at Hetzner (Germany) like the rest of your data.
We don't transfer Google user data to anyone else, except as needed to provide these features, to comply with the law, or as part of a merger or acquisition with your notice.
What we don't do
•
We don't sell Google user data.
•
We don't use it for advertising, including personalised or retargeted ads, and don't transfer it to advertising platforms, data brokers or information resellers.
•
We don't use it to determine creditworthiness or for lending.
•
We don't use it to create, train or improve AI or machine-learning models, ours or anyone else's.
•
No person at Kingstinct reads it, unless you ask us to (for example for support), it's needed for security (investigating abuse or a bug), the law requires it, or it's aggregated and anonymised for internal operations.
Limited Use
How long we keep it, and how to remove it
•
While Google Calendar is connected the app syncs it when you open it, at most once an hour; each sync replaces the stored events for its window.
•
Disconnect in You › Imports › Google Calendar › Disconnect: we delete the stored events immediately, recompute your trips (those only the calendar made disappear), and the app revokes its access at Google.
•
•
Delete your account (You › Account › Delete account…) to delete everything at once. Export your data first in You › Your data if you want a copy.
•
Security
Calendar data travels over HTTPS (TLS), between your device and Google and between your device and our server. Our server and database are access-restricted and hosted in Germany. Google access tokens never leave your device.
Changes
If we ever want to use Google user data in a way this section doesn't describe, we'll update it, tell you in the app, and ask for your consent first.
Cookies and storage on the website
The website doesn't use cookies, analytics or advertising trackers. It uses your browser's local storage for what it needs to work: your sign-in session, an invite you opened before signing in, your notification choice, which email activity you've seen, and a cache of events. Signing out removes the session. On phones the same is kept in the app's secure storage. Cloudflare processes your IP address to deliver the website and protect it from attacks.
Security
Connections use HTTPS. Session tokens and sign-in codes are stored only as hashes. Our logs are built not to contain message text, email content, coordinates or tokens. No system is perfectly secure; if a breach puts your data at risk we'll tell you and the authority as the law requires.
Changes
We'll update this policy when the app changes how it handles data and change the date at the top. If a change matters, we'll tell you in the app before it applies.
Contact