NextUp — Privacy Policy
Last updated: 1 September 2026
NextUp helps you find and join local pickup sports. This policy says exactly what the app collects, why, and what it never does. It is short because the app collects little.
Using it without an account
You can open the app, scan, read every session and get directions with no account at all. In that mode nothing on this page is collected, because there is nobody to attach it to — only the local preferences described below, on your own device. An account is needed to join or host a session, and nothing above it applies until you make one.
What we collect
Your account. Your email address and the display name you choose. The name is what other players see on a roster — the app asks for a first name and a last initial, which is enough to recognise someone and not enough to identify a stranger. If you sign in with Apple or Google, we receive the email and name those services return, and nothing else.
Your location, while the app is open. Used for three things: centring the map on you, deciding whether you have arrived at a session you joined, and — if and only if you turn alerts on — deciding whether a newly posted session is near enough to be worth telling you about.
For the first two, your position is never stored. What gets saved is a single flag: arrived, or not, on the sessions you are actually on the roster for.
For the third, one approximate position is stored alongside your notification address, so we can tell whether a session posted tonight is two streets away or two countries away. It is a single point that is overwritten each time it changes, never a trail, and it is deleted the moment you turn alerts off or sign out. Without it we could only send you everything or nothing.
The app never requests background location and cannot see where you are when it is closed.
Sessions you create or join. Title, sport, venue, time, and the coordinates of the pin. These are visible to other signed-in users, which is the point.
Your departure plan, if you make one — the time you said you would leave and how you are travelling. This is visible only to people on the same session's roster, so a host can see who is on their way. Nobody else can see it.
Basic app storage. Your appearance choice, your other preferences and a local cache of your own sessions, kept on your device so the app works before the network answers. On the web that is your browser's own storage, and clearing site data clears it.
A notification address, if you turn alerts on. To reach you with the app closed, your browser or your phone issues an anonymous address, and we store it against your account so we know which sessions to send you. On the web that is a push endpoint from your browser; on a phone it is a token from Apple's and Google's notification services.
It is not a tracking identifier: it only accepts messages we send, it never leaves our database, and it is deleted the moment you sign out, turn alerts off, or the service tells us it has expired.
Reports and blocks, if you use them. If you report a session or a person we keep what you chose, anything you typed, and who you are — a report we cannot attribute is one we cannot act on. The person reported is never told who reported them. If you block someone we store that the two of you are blocked; neither of you can see the other afterwards, and the person blocked is never told.
Alerts, if you turn them on. When someone posts a session, the app tells everyone who has it open. On the web you can also let the browser show that as a notification — permission you grant to your browser, not to us, and can withdraw there at any time. Two things send one: a session being posted, and somebody joining a session you are on. A notification contains the sport, the title, the place and the time of the session, plus the display name of whoever just joined — nothing else, and nothing about you.
What we do not do
- No tracking. No advertising identifiers, no cross-app or cross-site tracking, no data brokers, no ad networks.
- No selling or sharing your data with third parties for their own purposes.
- No analytics profiles. We do not build a picture of you from your behaviour.
- No background location. Ever.
- No location history. The one position we store for alerts is a single point that gets overwritten, not a trail. We cannot reconstruct where you have been.
Sharing a session
The link you share, …/?s=<id>, contains the session's identifier and nothing about you. Anyone who has it can see that session — which is the point of sending it — and can look at the map without an account.
Who processes data for us
- Supabase — hosts the database and handles authentication. Your account and session data live here.
- Apple / Google — only if you choose to sign in with them.
- OpenStreetMap (Nominatim) — when you search for a venue by name, the text you type is sent to their geocoding service to look it up.
- CARTO — serves the map tiles the app draws.
- Your browser's push service (Google, Mozilla, Apple, depending on the browser) — delivers web notifications you have asked for. They receive an encrypted payload they cannot read.
- **Firebase Cloud Messaging (Google) and, through it, Apple Push Notification service** — deliver notifications to phones. They receive your device's notification token and the text of the notification. We use Firebase only to deliver messages: no Firebase Analytics, no advertising product, no profile.
Each receives only what it needs to do its job.
How long we keep it
Sessions are deleted ten hours after their scheduled start, automatically, along with their rosters and departure plans. This is enforced by the database, not by the app. A session that was called off is kept for 24 hours instead, so the people who were going can find out why it is gone, and is then deleted the same way.
Reports are kept while they are open and for a reasonable period after they are dealt with, because a pattern across several reports is often the only way to see a real problem. Blocks are kept until you undo them.
Signing out clears everything about you from that device immediately — the session, the cached rosters, your history and your departure plans — leaving only device settings such as the theme.
Your account and profile are kept until you ask us to delete them. Ask at the address below and we will remove your account, your profile, and everything attached to it.
Your rights
You can ask us to show you what we hold, correct it, or delete it. If you are in the EU or UK, the GDPR gives you these rights explicitly; we extend them to everyone. Write to the address below and we will respond within 30 days.
Children
NextUp is not directed at children under 13, and we do not knowingly collect their data. If you believe a child has created an account, contact us and we will remove it.
Changes
If this policy changes in a way that affects what we collect or who receives it, we will say so in the app before the change takes effect.