Privacy Policy

Where Is Alex · last updated 14 November 2026

Where Is Alex helps a small group of friends see when their travel plans overlap. It is not advertising-supported. Nothing is sold, rented, or shared for marketing, there is no analytics or tracking SDK in the app, and no third-party code runs inside it.

This policy describes what the app stores, who else can see it, and how to get rid of it. It is written to be read rather than to be survived.


Who is responsible

The data controller is the operator of Where Is Alex, contactable at support@whereisalex.ai. That address reaches a person, not a ticketing system.

What is stored

Location: While Using only. This version of the app asks for location only while it is open, to work out which city you are in. It never asks for “Always” and cannot use your location while it is closed.

Travel Assistant (not in this version). A later update may add a feature that notices you have landed somewhere new so the orb can ask where you are headed. It would be off until you switch it on, and switching it on would mean granting Always location, the only part of the app that could use your location while it is closed. When it arrives, this policy will say so before the app asks.

What it does with that: your phone watches for arrivals at airports near you and nothing else, and the check happens on the device: no continuous trail of your movements is sent anywhere or stored by us. Nothing reaches the server until you answer the orb, and what gets stored then is an ordinary trip. Turning it off in Settings stops it completely and breaks nothing else.

Boarding passes, stated plainly. When you share a boarding pass with the app, your iPhone reads it itself (the barcode and the printed text), and the picture goes nowhere. That is where every pass starts, and for most passes it is where it ends.

If the phone cannot finish, the card offers a button that says Let the orb read it, and says beside it that the picture will be sent. Only if you tap that button is the whole image sent to Amazon Web Services, where the Kimi K2.5 model reads it on Amazon Bedrock in Tokyo. The whole image means everything printed on it: your name, your booking reference, your seat, a frequent-flyer number if there is one, and the flight. Our server holds the picture only for the length of that request and never writes it anywhere, and Amazon keeps none of it either. What comes back is the flight, the date and the airports, which you then check before anything is saved. Your name and booking reference are not among the fields the model is asked for and are not stored. If you have turned the orb off (below), the picture is never sent.

When a pass prints no landing time, the app asks the airline’s published schedule through AeroDataBox. That request carries the flight number and the date and nothing else (no name, no booking reference, no account), so the provider learns that somebody asked about a flight, not who is on it.

Google Calendar, stated plainly. Trips from Google Calendar is off until you switch it on in the Me tab and say yes on Google’s own screen. Then the app reads the events on the main calendar of each Google account you connect. Google’s screen asks for the calendars you own; the app only ever opens the main one. It can never add, change or delete anything there, and it cannot see anyone else’s calendar.

What it reads. The email address of each Google account you connect, so the Me tab can show which one it is. Then events from the last 12 months and everything ahead, and for each one only: Google’s id for it, the title, the place, when it starts and ends and in which time zone, whether it was cancelled or repeats, your answer to the invite, how many guests it has, and whether it has a video call. It never reads an event’s notes or attachments, or the names and email addresses of its guests. It reads all this to spot your trips, and for nothing else.

Where it stays. On your iPhone, in the app’s own storage, encrypted by iOS and left out of iCloud and computer backups. The phone looks for trips in it right there. The orb’s chat lines that bring up a calendar trip, a city and dates each, are kept the same way. What you write back, and the orb’s answers, are ordinary messages in your chat with the orb: they are in your backups like the rest of that chat, and are deleted from the phone when you sign out. Google’s key, which lets the app keep reading, and the email address of each account stay in the iPhone’s keychain, on that phone only.

Deleting it from the phone. When you switch the feature off, sign out or delete your account, the calendar copy and those chat lines are deleted from the phone, and the app asks Google to cancel its key. Removing one account does the same for that account. If you remove the app’s access on Google’s side instead, the app deletes that account’s calendar copy and those chat lines the next time it checks. Until Google answers, the key and its account’s email address wait on the phone, set apart from the calendar, where nothing can read your calendar with them, and the app asks Google again each time you open it, for up to six months, after which it deletes them. Erase my calendar answers deletes those chat lines too, on this iPhone at once and on your other iPhones the next time they check. Deleting the app works differently: iOS deletes the calendar copy and the chat with the app, but keeps Google’s key and its account’s email address on the phone, where no other app can read them. They stay there, unused, until you install Where Is Alex again, if you ever do. The first time the app opens after that, it stops using the key and asks Google to cancel it, as above, and you connect again if you want the feature back. Until that request reaches Google, Google keeps listing the app’s access at myaccount.google.com/connections, where you can remove it yourself. So switch the feature off before you delete the app.

What leaves the phone, and when. Only what you send. Log it sends a city, the dates and the scrambled codes. Skip sends the codes. Use or Keep, on a question about a trip you already have, sends the codes and, for Use, the new dates. Reply sends your words with that trip’s city and dates to the assistant, and the codes to our server, so the orb can log, change or skip the trip for you the way the buttons would. A message you type in the orb chat does the same while the orb’s last line is a question about a calendar trip, for up to a day after it asked. An event’s title or address never leaves your iPhone.

Checks while the app is closed. To notice a new event without you opening the app, our server sends a silent notification a few times a day to phones with Trips from Google Calendar on, which can wake the app to look. It carries a signal to check and nothing from your calendar. The orb’s questions about your calendar are written and shown by your iPhone itself, so they pass through neither our server nor Apple. The orb’s answer to a Reply reaches you as a push notification through Apple, like any other.

Who sees a calendar trip. A trip you log from your calendar is an ordinary trip on your Runway. The crews ticked in the CALENDAR column in the Me tab see it. The first time you switch the feature on, every crew you are in is ticked, and you can untick any of them. Followers never see a calendar trip, and a crew you join later sees nothing until you tick it. One exception: when you use the calendar’s dates on a trip you already had, that trip keeps its own audience, which can include followers. After you tap Erase my calendar answers, the trips you logged are ordinary trips: the crews that saw them still do, the CALENDAR column no longer changes that, and you can share one like any other trip.

AI. Once you log a calendar trip, Amazon Web Services, which runs the assistant, sees it like any other trip: when you talk to the orb, and when someone in a crew that can see the trip talks to theirs. Before that, it sees a calendar trip only when you write to the orb about it as above, and then only its city and dates. No event title or address ever reaches it. Nothing from your Google Calendar, and nothing worked out from it, is used to build, train or improve any AI model, ours or anyone else’s.

People. No person at Where Is Alex reads your calendar, and its events never reach our server. We look at a calendar trip on our server only if you ask us to, for example in a support email, to look into a bug or abuse, or when the law requires it.

Why we are allowed to store it

For users in the UK and EEA, the legal basis under UK/EU GDPR is performance of a contract (Article 6(1)(b)): the app cannot tell you when you overlap with a friend without knowing your trips.

Precise location is special-category-adjacent and always consent-based (Article 6(1)(a)): it is never collected unless you grant a specific person access to it, and consent is withdrawable at any moment by revoking the grant, which takes effect immediately.

Sending what the orb needs to the AI that runs it is also consent-based (Article 6(1)(a)): the app asks before anything goes, and turning the orb off in the Me tab withdraws that consent at once.

Counting how many people use the app (the days you open the app, above) is in our legitimate interest (Article 6(1)(f)): it tells us whether the app is used, and which versions of it are still in use. It is only ever counted, never shown to anyone, and you can object by writing to support@whereisalex.ai.

Trips from Google Calendar runs on your consent (Article 6(1)(a)): you switch it on and say yes on Google’s screen, and switching it off withdraws that consent at once.

Who else sees it

That is the entire list. The one other site that can see anything is Booking.com, and only when you tap Find stays (more on that below). There is no data broker, advertiser or analytics provider anywhere in the list, and nobody outside it ever receives a boarding pass, a drawing, or a message to the assistant.

Where Is Alex’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. It also follows the Google Workspace API User Data and Developer Policy. How to manage and delete what Trips from Google Calendar keeps is on its own page.

Links you open. On your own upcoming trip, Find flights and Find stays open Google Flights or Booking.com in Safari, outside the app (or in that site’s own app, if your phone opens the link there). The app sees nothing you do there. The link carries the trip’s city and dates (for a one-day trip, Find stays runs to the day your next trip starts, when that is 30 nights or fewer away), and for flights your home city, so that site sees them as if you had typed them there. A trip from your calendar, or one you gave your calendar’s dates, has no such buttons, and none of its dates goes into a link. After you tap Erase my calendar answers, it is an ordinary trip and gets them. We add no tracking or referral code, earn nothing from it and get nothing back.

About the assistant, stated plainly. When you talk to the orb, your typed message goes to Amazon Web Services together with the conversation so far, so the orb can follow it, and the part of your crews’ state it needs to answer a question like “who is in Lisbon in March?”: the names of your crews, and the names, home cities, trip cities and dates of the people whose trips you can already see. If you ask the orb about a boarding pass, the flight read off it goes too.

What Amazon does with it: the model reads the request and writes the answer, and that is all. Amazon does not use anything you send to train models and does not pass it to OpenAI or Moonshot AI, and with the setting we chose for our account (data retention none) it does not write any of it to storage. It is processed in Tokyo, so for anyone in the UK or EEA it is a transfer of personal data outside the UK/EEA.

One AI provider. The assistant’s standby runs on Amazon Bedrock too, so when the main model cannot answer, the request stays with Amazon.

You say yes first. Before anything of yours goes to the AI, the app asks, on a screen called “The orb runs on AI”: before your first message to the orb, your first @orb in a crew’s chat, your first Let the orb read it or your first drawing to be scored, whichever comes first. One yes covers all four. You can change your mind at any time with the switch for the orb in the Me tab, and if the models that read what you send change, the app asks again.

Saying no. With the orb off, nothing you type, no boarding pass and no drawing goes to any AI provider, and our server refuses any request to the AI from your account. You are also left out of your friends’ orb: when they talk to theirs, your name, home city and trips are not sent, and the orb tells them it can’t see some people’s plans, without saying whose. A drawing of your face is scored on the drawer’s phone instead. The map, the runway, crews, the card game and adding a trip by hand work just the same either way, and send nothing to any AI provider. With the orb on, the drawing game sends a drawing and a description of the face being drawn, and nothing else. Versions of the app from before this screen never ask: until someone answers on a newer version, the orb works for them as it always has, and their details go with their friends’ requests as described above.

The orb in a crew chat. Anyone in a crew can invite the orb into the crew’s chat, hush it for a day or show it out, and the chat says who did. It reads only messages that tag it with @orb. Only someone who said yes on “The orb runs on AI” can ask it; anyone else’s message stays an ordinary message and nothing is sent.

What goes to Amazon Web Services when you tag it: the message that tags it, the orb’s earlier answers in that chat with the questions they answered, the crew’s name, who asked, and the crew’s shared trips: the names, home cities, and trip cities and dates that the crew can already see. Nothing else anyone said in the chat goes, and nothing from anyone’s own conversation with the orb. It doesn’t read polls or votes, and your trip budget never goes to it.

Who is left out. Anyone in the crew who said no to the orb’s AI, or hasn’t answered yet, and anyone in the crew who has blocked someone else in it, or been blocked by them: their names, homes and trips are not sent, and the orb never names them in the chat. Its own note about two people overlapping follows the same rule.

Who reads the answer: everyone in the crew, as a message in the chat, kept like any chat message.

In a crew chat the orb only reads. It never changes a trip there, never messages anyone outside the chat, and never holds, pools or moves money.

Where data is held, and transfers

The database and server are hosted in Japan (Tokyo), since 24 September 2026. The copy they moved from, in the United States, is kept for a short while in case the move has to be undone, and is then deleted. Assistant requests, boarding-pass pictures you choose to send and drawings in the drawing game go to Amazon Web Services, a United States company, and are processed on Amazon Bedrock in Tokyo, Japan. Flight schedules are looked up through RapidAPI in the United States. All of these are transfers outside the UK/EEA. For the AI processing we rely on your explicit consent, the yes you give the orb in the app, which you can take back in the Me tab at any time; for the hosting, the standard protections offered by those providers apply.

If we ever add or swap an AI provider, that is a change to who reads your messages, so it gets a new entry in this list and a new date at the top, never a silent substitution.

How long it is kept

DataKept for
Trips, crews, display name, character Until you delete them, or delete your account
Exact location coordinates Until the one-hour grant expires, then deleted automatically
Your cityUntil you turn sharing off
Flight number and landing time Until the day after the flight lands, or until you stop sharing it, whichever is first; then deleted automatically
Boarding pass picture Not stored. Held by our server only while the read you asked for is in progress
Game scores and drawings Until you delete your account, or the crew is dissolved
Conversation with the assistant 90 days after your last message, then deleted automatically
Your answer about the orb’s AI (yes or no, the version of the question, when, and the app version) Until you delete your account. Answering again replaces it
Crew chat messages, the orb’s answers and notes among them 90 days after they are sent, then deleted automatically
Polls and votes in a crew chat With the poll’s message: 90 days after it is sent. Your votes and your budget go at once when you delete your account
Your trip budget Until you clear it or delete your account
The orb’s memory of a crew chat (its last twelve answers there, with the questions they answered) 90 days, then deleted automatically, and at once when someone shows the orb out
Your home cityUntil you clear it or delete your account
Card game hands, moves and end-game votes Until you delete your account, or the crew is dissolved
Push notification tokenUntil you delete your account
Usage counts Kept, with the link to you removed on account deletion
The days you opened the app, and the app version 90 days, then deleted automatically. A total for each day, with no link to anyone, is kept
Your calendar’s copy, and the orb’s chat lines that bring up a calendar trip, on your iPhone Until you switch Trips from Google Calendar off, remove that account, sign out or delete your account, or the app finds you removed its access on Google’s side. The chat lines also go when you tap Erase my calendar answers. Deleting the app deletes them too
Google’s key, on your iPhone Until you switch Trips from Google Calendar off, remove that account, sign out or delete your account. Then only until Google answers the app’s request to cancel it: the app asks again each time you open it, for up to six months, and then deletes the key. Deleting the app leaves the key on your iPhone until you install the app again, which then asks Google to cancel it the same way
Your answers to calendar trips (the scrambled codes, and which trip each one became) Until you tap Erase my calendar answers in the Me tab or delete your account, so the app never asks you the same thing twice
Calendar settings (whether it is on, the crews you ticked, the key behind the codes) Until you delete your account
What you write to the orb about a calendar trip, and its answers With your conversation with the assistant: 90 days after your last message. The answer to a Lock Screen reply is also held for up to 7 days so it can reach your phone, and goes sooner if you tap Erase my calendar answers

Deleting everything

Me › Settings › Account has Hold to delete my account. It removes your trips, your flights and landing times, your crew memberships, your location records, your crash reports, the days you opened the app, your push token, your sign-in identity, everything you said in a crew chat with the orb’s answers to you and its notes that name you, what you asked the orb in any crew chat, your trip budget, the polls you started and your votes, your whole assistant history and your answer about the orb’s AI from the server. It cannot be undone and nobody can restore it for you. If you run a crew that still has other people in it, hand it to someone else first, so the crew is not orphaned.

Deleting your account also erases your answers to calendar trips and your calendar settings, asks Google to cancel the app’s access and deletes the calendar from your iPhone. To stop the calendar part alone, switch Trips from Google Calendar off in the Me tab: the app asks Google to cancel its access and deletes the calendar from your iPhone. If Google can’t be reached just then, the app asks again each time you open it, and you can remove the connection yourself at myaccount.google.com/connections. Your answers stay on our server so that switching back on never asks you the same thing twice, until you tap Erase my calendar answers, which works with the switch off too. Your crew ticks stay until you delete your account. Trips you already logged stay on your Runway until you delete them.

Usage counts survive deletion with the link to you removed, because they are model and token totals rather than anything about you.

Your rights

If you are in the UK or EEA you have the right to access your data, correct it, delete it, receive a copy in a portable form, object to processing, and restrict it. Deletion and correction are built into the app: the Me tab edits your name and character, and deletes the account outright. For anything else, including a copy of your data, email the address above and you will get a reply within 30 days. You may also complain to your local supervisory authority; in the UK that is the Information Commissioner’s Office.

If you are in California, the app does not sell or share personal information as those terms are defined by the CCPA/CPRA, and it does not process it for cross-context behavioural advertising.

Security

Traffic is encrypted in transit. Sessions use signed tokens, sign-in identities are verified against Apple or Google directly, and one person’s trips are filtered out of another person’s view on the server rather than hidden in the app. No system is perfect; if you find a problem, the contact address above is the fastest way to reach someone who can fix it.

Children

The app is not directed at children and is not intended for anyone under 13. If you believe a child has given us data, email the address above and it will be deleted.

Changes

If this policy changes in a way that affects what is collected or who receives it, the date at the top changes. For an earlier version, email support@whereisalex.ai and we’ll send it to you.

Contact

Questions, a request for your data, or you want something removed by hand: support@whereisalex.ai