Privacy

What we store

• Your account. Your name, the email or sign-in identity you used (an emailed code, a password, Sign in with Apple, or Sign in with Google), and anything you choose to add to your profile: a username, pronouns, a short bio, up to four photos, a home city, a prompt answer, and links to your other profiles. A password is stored hashed by our sign-in provider and we never see it. If you verify a phone number, we store the number and the fact that it was verified. The number itself is never shown to anyone.
• Your birthday.We ask for your date of birth once, when you set up the app, to confirm you meet fomo’s minimum age. It is used one other way, on our server: when a crew or a plan sets a minimum age, we check your date of birth against it. It is never shown to other people, we never hand it to anyone else, and we don’t use it for anything else.
• Your plans and RSVPs. The plans you host or join, including their time, place, and details; your response and any note you added; and, for people who RSVP from a link without an account, the name they gave and the note they wrote, so the host can plan.
• Chat. Messages you send in a plan or crew chat, photos you send, GIFs you pick, reactions, polls and how you voted, and a meetup spot when you choose to share one.
• Places on a plan. When you put a location on a plan, we store the place name, the address, and its coordinates, so the people you invited can see where to go.
• Location from your device. Only in the three moments described in the next section, and only when you ask for it.
• Your notification setup. If you turn on notifications, we store a push token for that device along with its platform, so we can send the pings you asked for, and your notification preferences so we only send the ones you want.
• Reports and blocks. If you report a message or a person, or block someone, we store that: the reason, anything you typed, and a copy of what was reported. Reporting is confidential and we never tell the person they were reported.
• Bug reports and error diagnostics. If you send a bug report from the app, we store what you wrote, any screenshots you attached, basic device information (app version, platform, OS version, device model, locale, time zone, screen size, network type), and a short trail of what you last did in the app. Separately, when something in the app fails, we record the failure itself: what broke, the error code and message, the app version, and the screen you were on.
• Emails you give us. If you ask us to email you the install link, or join the beta waitlist, we store that address. If you ask for a sign-in code so you can claim an RSVP you made as a guest, we store the address to send you that code.

Location

fomo never tracks your location in the background and never follows you around. The app takes a single reading, in the moment you ask it to, in exactly three places. If you never use those three, fomo never asks for location at all.

• Setting your Discover area. Tapping the use-my-location row takes one reading and uses it on your phone to pick the nearest city from a list that ships inside the app. Only that city is sent to us, to sort nearby crews. Your actual coordinates never leave the device.
• Setting a crew’s home base. If you make a crew discoverable, you can set its home base from your location. We round the coordinates to roughly a kilometer before storing them, so the crew turns up in the right area without pinning an address. It is the crew’s location, not yours, and only the rounded distance is ever shown to anyone else.
• Sharing a meetup spot in chat. When you share a spot, we take one reading and send it into that chat at full precision, because a vague pin is a useless meeting point. It is a message like any other: only the people in that chat can see it, and you can delete it.

Your calendar

If you let fomo add a plan to your calendar, that happens on your device, in the calendar app already on your phone. The app needs calendar access to find a calendar it can write to and to keep the event in step when a plan changes. Your calendar, and the events already on it, are never sent to us. Your calendar settings are stored on the phone, not on your account.

Photos

Profile photos, chat photos, cover art, and bug-report screenshots all live in private storage, never in a public folder. Chat photos are readable only by the people in that chat. Profile photos are resized on your phone before upload and the original never leaves it. We only ever receive the photos you pick or take for fomo, never your camera roll. Saving a photo out of a chat back to your library happens on your device.

Who can see what

• Plans travel along the friend graph: the people you invited, and friends or friends of friends when you pick that audience. A plan is never public and is never shown to a stranger.
• Crews keep their chat, member list, and plan details members-only, including a crew that has chosen to be discoverable. A discoverable crew shows only its name, description, tags, and the coarse area described above.
• Your profile page at joinfomo.app/u/your-username is public. Your display name, username, profile photo, and bio are visible to anyone with the link and can be indexed by search engines. Everything else on your profile needs an account, and your links are friends-only unless you widen them.

Who else handles your data

We use a small number of companies to actually run fomo. They handle your data on our instructions and are not allowed to use it for their own purposes, except where noted.

• Supabase hosts the database, the files, and sign-in.
• Vercel hosts the website.
• Expo, with Apple’s and Google’s push services, delivers notifications. The text of a notification (a plan name, a message preview) passes through them to reach your phone.
• Resend sends our email.
• GitHub is where reports and bug reports land, as private issues in our own repository, so a person reviews and acts on them. That includes the reported content, who reported it, and who was reported.
• Giphy powers the GIF picker in chat. What you type into that picker goes to Giphy, and the GIF is served from Giphy, under their terms rather than ours. Treat a GIF search the way you would a search engine.
• PostHog counts a fixed list of page events on the website. See Cookies and analytics below.
• Apple and Google sign-in tell us only what you approve at the moment you sign in.

What we don't do

We do not sell your data. We do not share it with advertisers or data brokers, and we do not use it for anyone’s advertising. The app carries no advertising SDK and no advertising identifier. We do not track you across other apps or websites, we never read or upload your contacts, we never read your calendar’s contents, and we never track your location in the background. Beyond running fomo and the two safety exceptions below, your data goes nowhere.

When we do hand something over

Two exceptions, both narrow, and both about safety rather than business.

• Child safety.When we find apparent child sexual abuse material on fomo, we remove it, disable the account, and report it to NCMEC’s CyberTipline as US law requires of us. We preserve the related records for that report rather than deleting them. Our Child safety standards set this out in full.
• Legal process and serious harm. We respond to valid legal process, and we may share information when we believe in good faith that it is needed to prevent serious harm to someone, or to investigate a breach of our Terms. We give the minimum the situation actually calls for, never more.

Cookies and analytics

The website sets a cookie to keep you signed in. That is the only cookie it needs. There are no tracking or advertising cookies, which is why you never see a cookie banner.

We use PostHog on the website to count a fixed list of page events, so we can tell which pages work and which are confusing (for example, how many people who open an invite go on to RSVP). It is set up without cookies and without persistent browser storage, with automatic capture turned off, so it records only those events, the page addresses they happened on, and the ordinary details any web request carries, including your IP address. The app itself has no analytics SDK at all.

Age

fomo is for people aged 13 and older. Don’t use fomo or give us your information if you’re under 13. The app asks for your date of birth during signup and won’t let an under-13 signup continue. That account and anything it gave us are deleted. If we learn some other way that we’ve collected information from a child under 13, we’ll delete it too. Our Child safety standards explain what is banned and how to report it.

How long we keep it

Your account and the things tied to it stay until you delete your account. Error diagnostics are pruned automatically after about a month. Reports and moderation records are kept longer on purpose: a report has to outlive both accounts to be worth anything, and records tied to a child-safety report are preserved as described above.

Encrypted database backups can still hold a copy of something you deleted until they age out on their normal schedule. We never use one to bring back a deleted account.

Getting your data deleted

You can delete your account any time in the app: go to Profile → Settings → Delete account. It happens immediately, with no waiting period, and it removes your profile and photos, your RSVPs and votes, your friendships and crew memberships, the invites you sent, upcoming plans you host, and the push tokens for your devices.

Three things stay behind on purpose. Messages you already sent stay in their chats with your name off them, so the conversation other people had doesn’t fall apart. A safety report you filed stays, also with your name off it, because a report is evidence about someone else. And anything the law requires us to keep stays, which in practice means records tied to a child-safety report and nothing else.

You can also ask us instead, including for RSVP responses you made without an account and for a waitlist email, by emailing hello@joinfomo.app from the address you signed up with, or telling us which invite you responded to. We may keep the minimum needed to meet legal obligations, but not for any other purpose.

How to delete your account walks through both paths step by step, including what to do if you already uninstalled the app or can’t sign in.

Contact

Questions about privacy? Email hello@joinfomo.app. We’ll do our best to answer quickly.