Privacy policy

• No ads, no advertising identifier, no tracking across other apps or websites, and no third-party analytics.
• Location stays on your phone. The venue map can use it, only when you ask it to (Centre on me, Directions) and only while the map is open; it is never sent to us. Match times use your phone's time zone setting.
• You do not need an account. Without one, your follows and pass are linked to a random number the app makes for your phone, not to you.
• The camera is only used when you choose: to read the venue QR code (the image stays on your phone) or to take a photo you decide to add, such as your player photo.
• Registering for an event shares the names and contact details you enter with the organisation running it. Online payments are made on the payment page of our payment provider, XPay; Move Score never sees your card.
• We never sell your data.

1. Your phone (every user)

When the app first opens it creates a random installation ID and registers your phone with our server together with: the platform (iOS or Android), the app version, your time zone and language setting, and when the app was last used. This lets the app keep your follows and pass, and send alerts to the right phone. It contains no name, email, phone number or device serial.

If you turn alerts on, we also store the push token Apple or Google gives the app, and your alert choices (for example “starting soon” or “results”). If you keep a match on your iPhone lock screen, we store a separate push token for that one Live Activity, so its score can be updated; it ends when the match does.

2. What you follow

The players, nations, matches, ties, tournaments and events you follow or star, linked to your installation ID (or to your account if you sign in). We use them to show your Following feed and to decide which alerts to send you.

3. Your event pass

Each event can give you a collectible pass. We store its number and edition, the nation you choose for it (optional), the name you type on it (optional, up to 40 characters; a first name or nickname is enough), the days it was stamped and the nation pins you collected.

To stamp a day you scan the code shown at the venue. The camera image is processed on your phone; only the code it reads is sent to us. To check the code was scanned at the event, our hosting provider tells us the country your network connection comes from; we compare it with the event's country and do not store it.

4. Cheers

When you tap to cheer for a team we add your taps to that team's total. Only the totals are stored. Your installation ID is used for a short time to limit how many cheers one phone can send.

5. An account (optional), and players

If you sign in with Apple or Google, the provider gives us an account identifier, your email address (Apple may give a private relay address instead) and, if you choose to share it, your name. We keep the name you share as your display name and which provider you used. Your email is held by our sign-in provider and is not shown in the app or used for marketing. For Sign in with Apple we also keep an encrypted Apple token whose only use is to revoke your Apple sign-in when you delete your account. Your follows and pass then move with you to a new phone.

You can also sign up with your email address and a password. Your email and password are held by our sign-in provider (the password only as a one-way hash) and the email is used only to confirm your address, reset your password and send you account notices. A player can also sign in with the player code the organiser sent them; they are then asked to add an email to complete their registration. Until that email is confirmed, the password they chose is kept encrypted and is deleted as soon as it is set.

Players can link their account to their tournament profile with the private player code the organiser sends them. The app then shows them their name, nation and matches, and lets them add a phone number and a photo. The phone number is seen only by the player and the organisers, never in the app's public screens or on public pages. The photo is shown publicly only at events where the organiser shows player photos. Unlinking the player, or deleting the account, removes a photo the player added; organisers can reset a code, which unlinks the account.

Your player profile. One account speaks for one player profile: your name, the tournaments, sessions and leagues you played, your results and points. Besides a player code, you can link it with a one-time code sent to your phone by WhatsApp (or, if you agree, by email), with your confirmed email when an organiser recorded the same address, or by accepting an organiser's offer. Codes are stored only as one-way hashes and expire. Each organisation sees your contact details only if it added you or you shared them with it (My profile → Organisations); an organisation that only matched you by a number typed on its form sees the name it typed.

6. Organisations, registrations and payments

Events and leagues are run by organisations (clubs, academies and organisers). Their staff sign in with their own accounts; what they can see is limited to their own organisation's events and players.

When you register for an event (in the app or on the event's web page) we store the registration: the event, the names you enter, the mobile numbers and email you give, whether you register as a team or alone, its status, and what is due and paid. The organisation running the event sees these details to manage its entries. When you register in the app, your own entry is linked to your account so its matches show up for you; the other players you name are not linked to your account. We send you messages about your registration by email only, and only to a confirmed address: your account's confirmed email in the app, or, on the web page, the email you entered once you have opened the confirmation link we send to it.

Online payments (Move Beyond's own events only) are processed by XPay, our payment provider, on its own checkout page. Move Score sends XPay the amount, the event's name and reference numbers for your registration and payment; it never receives your card details, and what you enter on the payment page goes to XPay under its own terms. XPay tells Move Score whether the payment succeeded, failed or was refunded. We keep the amount, the date and XPay's references for the event's accounts and for refunds.

About a day after an event ends, the link between your account and that event's entry is archived: your history stays, but the event no longer sends you alerts.

7. Event officials

Referees and umpires sign in with an access code from the event organiser. Scores they enter, with the time and the official role that entered them, become part of the event's public results and audit trail.

8. Crash reports (when enabled)

If crash reporting is switched on for a release, the app sends error reports to Sentry: what went wrong, the app version, the screen, and the phone model and operating system version, plus timing data for a small sample of sessions. Sending personal data is turned off: reports contain no names, emails, codes or tokens, and web addresses are stripped of their parameters.

Move Score Stories

A story you post is public for 24 hours, with your account's name and photo, the time and the match or event it came from; then it and its picture are deleted. We keep who liked, viewed (as a one-way code, never your phone's id), and reported a story for the story's life only; whom you blocked stays until you unblock them. Only you see your story's view and like counts. Deleting your account deletes your stories.

9. Abuse protection and server logs

To stop automated abuse, our server counts requests from each network address over short windows (minutes to an hour) for sign-in, phone registration, one-time codes and event registration; the counters are deleted soon after. Our hosting provider keeps standard request logs (address, time, page requested) for a limited period for security and troubleshooting.

• Location (precise or approximate): the venue map uses it on your phone only. Contacts, or photos and files from your phone other than a photo you choose to add.
• Microphone or audio. The app has no microphone permission.
• Advertising identifiers (IDFA / Android advertising ID) or any data for advertising.
• Health information, or card and bank details: Move Score has no in-app purchases, and online entry fees are paid on XPay's payment page, never in Move Score.

When you share a score card, the image is made on your phone and goes only to the app you pick (for example Instagram or WhatsApp). That app's own privacy policy then applies.

Move Score does not track you. We do not link data from the app with data from other companies' apps, websites or offline sources for advertising or measurement, and we do not share data with data brokers.

Only the service providers needed to run Move Score, each bound to use the data only on our instructions:

• Supabase: database and sign-in (data stored in the European Union).
• Vercel: hosting of the Move Score server and website.
• Expo, Apple Push Notification service and Google Firebase Cloud Messaging: delivering alerts and lock-screen scores to your phone.
• Apple and Google: Sign in with Apple and Google Sign-In, only if you use them.
• Resend (email) and Meta's WhatsApp Business platform: confirmations, codes and organisers' announcements.
• XPay, our payment provider: online entry fees for Move Beyond's events, only if you pay online.
• Sentry: crash reports, only when enabled for a release.

Some of these providers process data outside your country, including in the United States. We rely on their contractual safeguards for those transfers. We may disclose data if the law requires it.

• Phone registration, follows and pass: while you use the app. A push token is removed as soon as Apple or Google tell us it no longer works (for example after you delete the app).
• Account data: until you delete your account. Deleting it removes your follows, passes and account record straight away and revokes Sign in with Apple; the sign-in identity itself is removed within 30 days.
• Lock-screen tokens: until the match ends.
• Cheer totals and officials' scores: kept as part of the event's results.
• Registrations and payment records: kept with the event for the organisation's records, accounts and refunds. You can ask us to remove your contact details from a registration once the event and any refund are over.
• Request counters for abuse protection: deleted within a day or two. Crash reports: up to 90 days.

• Alerts: turn any kind off in Account, or turn them all off in your phone's settings.
• Camera, photos and location: each is asked for only when you use the feature that needs it, and can be withdrawn in your phone's settings at any time.
• Delete your account in the app (Account → Delete account). See how to delete your account and data, including without an account.
• You can ask us for a copy of your data, to correct it, or to delete it, and you can object to how we use it.

Write to mohamed.wahid.gm@gmail.com. We answer within 30 days. If you are unhappy with our answer you can complain to the data protection authority where you live.

All traffic is encrypted (HTTPS). Session tokens and the installation ID are kept in your phone's secure keychain. Access codes are checked on the server and never stored in the app.

If we change this policy we will update the date above, and tell you in the app if the change is significant. Questions: mohamed.wahid.gm@gmail.com, Move Beyond, mbeg.org.