Privacy Policy

Who is responsible

GotNext, operated by Denis WebStudio, is the data controller for the data described here. For any privacy question, or to exercise any of your rights, contact us at the email in the Contact section below.

What we collect and why

Account identity (required). When you sign up we collect your email address and a username, and you set a password. These are handled by Supabase Auth, our authentication system, hosted with the rest of our data in the EU. Your account is assigned an opaque user identifier (a random string, not your name or email) that GotNext uses internally to link your data to you. If you choose to turn on two-factor authentication, codes from your authenticator app are verified by Supabase Auth; we never store them. We use this data to create and secure your account and to sign you in. You can also sign up or sign in with Apple or Google. When you do, we receive your name and the email on your provider account (or a private relay address if you use Apple's Hide My Email), and we never see your Apple or Google password. If you sign out a device from the Devices screen, we record which devices are signed in (platform, model, and when each was last active) to show you that list.

Date of birth (required, asked once). Before you can create an account we ask when you were born, and we check it on our server. GotNext is for people aged 13 and over, and an age you type on your own phone is the only way we can ask without demanding an ID document, which would be out of proportion for a free app. We store it apart from the rest of your profile, where only you can read it: it is never shown to other players and never appears on your player card. You can change it once a year, from Account information in Settings, so a typo is fixable without leaving the date open to editing on a whim. It is deleted with the rest of your data when you delete your account.

Profile content you add. Your display name, profile photo, a short bio ("your game"), height, playing positions, playstyle tags, your home courts, a vibe, and the goals you pick ("what you are here for"). You choose what to add, and you can edit or remove it at any time in Edit profile. We use it to build your player profile, which other signed-in users can see.

Check-ins. When you check in to a court we store the court, your status (for example "here now", "on my way", "shooting around", "want a run", or "game going"), how many players you still need for a full court, and the times you choose to share (such as when you are arriving). A check-in is the core of the app: it powers the live map, the who-is-here and who-is-coming lists, your run history, and your reliability score. A check-in records the court you picked, not your device's coordinates (see "Location" below).

Run history. When you become present at a court, we log a court visit (the court and the time) so your profile and the court can show run history. This is derived from your check-ins.

Teams and runs you create or join. Team names, descriptions and team identity (colour and crest), run names, descriptions and prize text, who is on a lineup, challenges between teams, and game results. This content is shared with other signed-in users because that is the product (a team that holds a court, a run other people can find and join).

Messages. The content of the direct messages you send another player, and the messages you send in a run's group thread, along with who sent them and when. A direct message is visible to you and the other person. A run thread message is visible to everyone on that run. Messages are stored on our server and are not end to end encrypted: if a message is reported, a moderator can read that message and the messages around it to review the report (the same reviewer access described under Reports and feedback below). The word filter that checks your other posts also runs on message text before it sends. Whether another player can message you at all depends on a setting you control (Friends, Anyone, or No one) in Settings; if you are under 18, only friends can message you. Run thread messages are deleted 30 days after the run ends. Direct messages are kept until you delete your account. Deleting your account deletes your messages and your direct message conversations (see Deleting your account below), and a data export includes the messages you sent.

Courts you add. If you put a court on the map, we store what you tell us about it: its name, its position, a rough address or area, and the facts other hoopers need (how many hoops, the surface, whether it has lights and nets, whether it is a full court). We also store that you are the hooper who added it, so we can tell you if it is confirmed or removed, and so you can correct the details while it is still unconfirmed. All of this is public: a court only works if everyone can see it.

Reports and feedback. If you report a user or a piece of content, we store the report (what was reported, the reason, any details you add, and who filed it) so our moderators can act on it. If you send feedback from Settings, we store your message, your account identifier, and your app version and platform so we can act on it.

Notification token. If you turn on notifications, we store a push token from Expo's push service so we can deliver run and court alerts to your device. On Android, delivery uses Firebase Cloud Messaging (Google) as the transport for the push.

Location (used for nearby courts, check-in and adding a court, never stored). With your permission, GotNext uses your phone's precise location in the foreground (while you are using the app) for three things: to center the map on where you are and show nearby courts, to confirm you are actually at a court before you post a "here now" style check-in (this keeps the live map honest), and to confirm you are standing at a court you are adding to the map. We do not collect your location in the background. When you post an at-the-court check-in, or add a court, your coordinates are sent to our server once, only to check you are close enough, and are never stored. Adding a court also sends how accurate your phone reports that reading to be, so we can turn down a weak signal and keep the pin honest. The only thing a check-in records is the court you chose, not your position. The only thing adding a court records is the court's own position, which is public on the map. You can deny or turn off the location permission in your phone settings; the map will still work, but you will not be able to post an at-the-court check-in or add a court.

Photos. The image you pick for your profile photo, and the photos you take of a court: one when you add a court to the map, and any you add to a court's gallery while you are standing at it (up to six per court, each of which you can delete). Before any photo leaves your device we resize and re-encode it, which strips embedded metadata such as EXIF location (GPS) tags. A court photo is public: it is shown on that court's page to anyone using GotNext, without your name on it. We check you are at the court when you add one, in the same way we check a check-in, and that check does not store your position. We never access your microphone, and we never access your wider photo library beyond the single image you choose.

Camera. With your permission, GotNext uses the camera for two things: to scan another hooper's QR code so you can open their profile, and to photograph a court, either when you add one to the map or when you add a picture to a court you are standing at. Scanning happens on your device only: the camera frames are read on your phone to detect the code, and we do not store them, upload them, or keep any image from scanning. A court photo is different, and we want to be plain about it: you take it deliberately, and it is uploaded and stored so it can appear on that court's page. Court photos are camera only, so nothing from your photo library is used for them. You can deny or turn off the camera permission in your phone settings; you will just not be able to scan a code, add a court, or add a court photo (you can still add hoopers by searching, and still suggest a court for us to add).

Crash and error diagnostics. When the app crashes or hits a technical fault, a crash report is sent to Sentry (see below). It contains the technical details needed to fix the fault: the error and where in the code it happened, your device model, operating system version, and app version. It does not include your name, email, account identity, or IP address (IP addresses are scrubbed on Sentry's servers).

Contact messages. When you use Contact us in the app, we store your message, the category you choose, and, if you give it, an email address to reply to. We use it only to answer you, and we delete it when you delete your account. You can also send us the same message from the contact form on our website (gotnext.uk/contact): that stores the same things (your message, the category, and an optional reply email), handled the same way, except it is not linked to an app account.

Product analytics (only if you opt in). If, and only if, you turn on "Share usage analytics" (asked once during onboarding, changeable any time in Settings), we record a small set of in-app actions with PostHog (see below): a check-in, completing an onboarding step, creating a run, registering a team, issuing a challenge, filing a report, submitting feedback, sending a contact message, selecting goals, and a session where the map showed zero live courts. These events are linked to your opaque account identifier, never your email and never your location. Nothing is collected or stored before you opt in, not even an anonymous identifier. Turning the toggle off stops collection immediately.

We do not collect your contacts, your calendar, your browsing history, your advertising identifier (IDFA / Android Advertising ID), or your background location.

Cookies and this website

This website (gotnext.uk) sets no cookies. That is why there is no cookie banner: there is nothing to consent to.

Two things are stored or measured, neither of which needs consent under UK law (PECR):

• Your theme choice. If you switch the site between light and dark, that choice is saved in your browser's local storage so the site remembers it. It stays on your device and is never sent to us.
• Anonymous, cookie-free analytics. We use Cloudflare Web Analytics to count page views. It sets no cookies, stores nothing on your device, and does not fingerprint or track you across sites. We see aggregate numbers, never you.

If you dismiss a banner on the site (for example the get the app strip), that dismissal is also remembered in local storage on your device, so the banner does not keep coming back.

How your data is shared

GotNext does not sell your data, and there is no advertising in the app.

With other users. Your display name, your username (shown publicly on your profile and in search), profile photo, profile details, your check-ins and presence, your run history, and the teams and runs you take part in are visible to other signed-in users. That visibility is the product. Your messages are visible only to the people in that conversation: the other person in a direct message, or everyone on the run for a run thread. You can hide yourself from another user by blocking them (Settings and the report flows), which stops the two of you seeing each other across the app and hides your messages from each other.

With service providers (processors) who act on our behalf. We use the following providers to run GotNext. They process data only to provide their service to us, under their own security and data terms:

• Supabase (database, file storage, and realtime infrastructure): your profile, check-ins, court visits, teams and runs, friendships, blocks, reports, feedback, contact messages (including any reply email you give us), your messages, push tokens, and your uploaded profile photo. Our Supabase data is hosted in the EU (AWS eu-west-1, Ireland).
• Expo (push notification delivery): your push token and the notification content, when notifications are enabled.
• Sentry (crash and error monitoring): the crash diagnostics described above, hosted in the EU (Germany).
• PostHog (product analytics, only if you opt in): the in-app events described above and your opaque account identifier, hosted in the EU (Germany).

With Google Maps. The map in GotNext is powered by the Google Maps SDK. For the map to work, the SDK shares some data with Google, including a pseudonymous identifier and basic request and device information. Google may use this for its own service operation and improvement, as described in Google's Privacy Policy and its Maps SDK disclosure. This is separate from the location handling described above: GotNext does not send your check-in or device coordinates to Google.

For legal reasons. We may disclose data where we are legally required to, or where it is necessary to protect the safety of users or others (for example, responding to a credible threat or a report involving a minor in danger), or to establish, exercise, or defend legal claims.

Where your data is processed

Our primary infrastructure (Supabase, including authentication, plus Sentry and PostHog) is hosted in the EU. Expo and Google operate globally and may process data outside the UK and EU; where they do, they rely on their own appropriate safeguards (such as standard contractual clauses) for international transfers.

Legal bases (UK GDPR / EU GDPR)

• Account identity, profile, check-ins, teams, runs, push delivery: performance of our agreement with you to provide the app, and our legitimate interest in operating it.
• Crash and error diagnostics (Sentry): our legitimate interest in keeping the app working and detecting technical faults. Because it is strictly limited to fault detection (no IP address, no account identity, no tracing, no session replay), it runs without a separate consent prompt.
• Product analytics (PostHog): your consent, which you give by turning on "Share usage analytics" and can withdraw at any time.
• Reports and moderation records: our legitimate interest in keeping the community safe and in the establishment, exercise, or defence of legal claims (see Data retention).

Data retention

• While your account is open, we keep your profile, run history, and the content you have created for as long as you use GotNext.
• Check-ins are short-lived: an inactive check-in is automatically removed about 4 hours after your last activity, because presence is meant to reflect the court right now.
• Messages: a run thread's messages are deleted 30 days after the run ends. Direct messages are kept until you delete your account.
• Notifications: notices you have read are automatically deleted after 60 days; unread ones are kept until you see them.
• When you delete your account, your personal data is deleted as described in the next section.
• Reports are an exception. A report you file, or a report filed about you, may be kept after account deletion as part of our moderation audit trail (what was reported and what action a moderator took), on the legal basis of our legitimate interest in safety and in the establishment, exercise, or defence of legal claims. These records are kept no longer than necessary for that purpose.
• Crash diagnostics are retained by Sentry for a limited period under Sentry's own retention settings and contain no account identity.
• Opt-in analytics are retained by PostHog while you remain opted in; see your rights below.

Deleting your account and your data

You can delete your account and your data at any time, directly from the app, without reinstalling:

In the app: Settings > Delete account.

Deleting your account does the following:

• It deletes your login (your email, password, any linked Apple or Google sign-in, and any two-factor authenticators), so you can no longer sign in.
• It deletes your GotNext data held in our database: your profile, your check-ins and court-visit history, your friendships, your blocks, your place in any run lineups, your feedback, your notification tokens, and the notices created about you. If you are a team captain, captaincy passes to another member first so a team is never left stranded; a team left with no members is deleted.
• It deletes your messages and your direct message conversations. A run thread you were part of still exists for the other people on the run until its own 30-day deletion, but your messages in it are gone.
• It deletes your uploaded profile photo, and every court photo you took, from our storage.
• A court you added that no other hooper has ever checked in at is deleted with you. One that other hoopers have used stays on the map, because it is part of everyone's scene by then, but your name comes off it and your photo of it is removed.
• It turns off product analytics on your device and stops any further collection.

What is not deleted, and why.

• Shared scene history. Content that is part of other people's history (the runs that happened, game results, and challenges) is not torn out of their records. Where these reference you, the reference becomes an inactive identifier with no profile attached.
• Moderation records. Reports you filed or that were filed about you may be retained for the moderation audit trail, as explained in Data retention.
• Opt-in analytics held by PostHog. If you had opted into analytics, the analytics records held by our processor PostHog are not erased instantly by the in-app deletion. We erase them on request: see "Your rights" below, or email us and we will action it (within 30 days).

If you cannot use the in-app route for any reason, you can request deletion by emailing us at the Contact address below, and we will verify your request and delete your account and data. There is also a step-by-step guide on our Delete your data page.

Your rights

Subject to UK and EU data protection law, you have the right to access the personal data we hold about you, to correct it, to delete it, to restrict or object to certain processing, to data portability, and to withdraw consent (for analytics) at any time. You can exercise most of these directly in the app (Edit profile to correct your data, the analytics toggle to withdraw consent, and Delete account to erase it). For anything else, including erasure of opt-in analytics held by PostHog, contact us at the email below. We aim to respond within 30 days.

You also have the right to complain to a data protection regulator. In the UK that is the Information Commissioner's Office (ico.org.uk).

Security

We use providers that encrypt data in transit (TLS) and at rest, restrict access to your data with per-user database security rules, and store authentication credentials hashed, never in plain text. No system is perfectly secure, but we take reasonable measures to protect your data.

Children

GotNext is for users aged 13 and over. We do not knowingly collect data from children under 13. A credible report that a user is under 13 results in account closure and deletion of their data.

Changes to this policy

We will update this page when our practices change and revise the effective date above. Significant changes will be communicated in the app where appropriate.

Contact

For any privacy question or to exercise your rights, email [email protected].

This policy is published at https://gotnext.uk/privacy.