Last updated: 12 November 2026
This English text is a translation, provided for convenience. In the event of any discrepancy between this version and the French one, the French version prevails and is the reference text.
Application publisher: Yassin Ouider, non-professional publisher (natural person).
Data controller: Yassin Ouider.
Contact: contact.scorro@gmail.com
Scorro is a mobile football-following application: scores, standings, news, predictions between friends and a discussion space (the “Fan Zone”).
Following football requires no account. Scores, fixtures, standings, club pages, news: everything is available without signing up, and in that case we know neither your name nor your email address, and no account designates you.
Like any online service, your device sends its IP address to the servers it contacts: our relay server, and the providers of the images shown (crests, logos, flags, photos) — see section 4. And if you enable notifications, our servers keep what is needed to send them to you (section 2.7).
An account is only needed for the social features: commenting in the Fan Zone, making predictions, creating or joining a private league with friends.
| Data | Why | Legal basis (GDPR) |
|---|---|---|
| Email address | identify your account, sign you in, recover lost access | performance of the service |
| Password | sign you in. It is encrypted (hashed) by our provider: neither we nor they can read it | performance of the service |
| Username | identify you publicly in the Fan Zone and the leaderboards | performance of the service |
| Technical identifier | link your content to your account | performance of the service |
| Account creation date | account management | performance of the service |
| Acceptance of the terms of use: the date and the version accepted | to know which terms you accepted, and to ask for your agreement again when they change. Not public, kept for as long as your account exists | performance of the service |
| Data | Visibility | Why |
|---|---|---|
| Comments (Fan Zone) | public, shown with your username | to keep the discussion alive |
| Predictions (predicted scores) | your pending predictions stay private; once the match has started they become visible on your public profile and in the leaderboards | leaderboards and fairness |
| Private leagues: name, invitation code, join date | visible to the league’s members | how leagues work |
| Reactions to comments (“like” / “dislike”) | the total is shown under the comment; each member’s reaction is accessible to other signed-in members | to keep the discussion alive |
| “Who will win” votes | aggregated | match statistics |
| Reports and blocks | not public | moderation and comfort of use |
| “Likes” on “On this day” memories | only the total count is public; who liked what is visible only to you | to know which memories interest you |
| “Likes” on “Culture foot” posts | only the total count is public; who liked what is visible only to you | to know which posts interest you |
| Acceptance of the terms of use (date and version) | not public | see 2.1 |
You can report a comment and block a member: their messages then disappear from your view. Reports and moderation decisions are recorded in a moderation log, together with the content concerned, your identifier and the reason, for the purpose of fighting abuse.
Automated analysis before publication. Every comment is submitted to an automated analysis service (OpenAI, United States) that detects objectionable content, when that service is reachable. Only the text of the comment is transmitted — not your email address, not your identifier. A comment flagged by this analysis is not published.
Usernames go through the same analysis. When you choose or change your username, it is sent to the same service, for the same reason: it is shown on every one of your comments. A flagged username is refused, and you can choose another one. Nothing else accompanies that request — not your email address, not your account identifier.
⚠️ No decision is made about your account by this analysis: it applies to a piece of text, not to a person. Blocking an account remains a human decision. If a comment is refused wrongly, write to us — the address is in the legal notice.
Retention: 12 months at most, then automatic deletion. Twelve months correspond to a full sporting season, without keeping objectionable content attributed to a person indefinitely. This log is deleted along with your account if you delete it before that period.
This information is stored only in your device’s memory and disappears if you uninstall the application:
followed players · light/dark theme and colour · text size · display time zone · country · hidden competitions · created line-ups · home screen sorting.
One exception, and only if you enable notifications: your favourite teams, those whose alerts you have muted, your device’s language and your notification settings (alert types, sound, quiet hours — and your time zone if you turn quiet hours on) are then sent to our servers, because a notification comes from our servers: they need to know what to send you, when, and which language to write it in. See section 2.7.
If you enable notifications, your phone obtains, through Expo, a notification identifier issued by Apple or Google, and we keep it. It designates a device: it contains neither your name nor your email address.
If you are signed in to an account, that identifier is linked to your account: this is what lets us send you the results of your predictions. If you sign out, that link is removed; if you delete your account, the identifier and all the notification settings attached to it are deleted with it.
You do not need an account to receive notifications. The application can be read entirely without signing up, and so can match alerts.
Notifications are off by default. Until you turn them on yourself, no identifier is requested from Apple or Google, and nothing is sent to our servers.
You can turn them off at any time, in the application: More › Notifications. Your device’s identifier and the preferences attached to it are then deleted from our servers, and we stop writing to you.
If you uninstall the application or change device without turning them off, the identifier stops being valid on our first delivery attempt, and we permanently stop writing to you.
We do not collect your GPS location, your contacts, your photos, your address book, or any advertising identifier, and we do not build advertising profiles.
So that we only send you the alerts you asked for, our servers keep the list of the teams you follow and those whose alerts you have muted. Without that list, we could only send an identical alert to everyone.
Our servers also keep your device’s language, so that we write to you in that language. The text of a notification is written at sending time, by our servers: the application is closed at that moment and cannot translate it itself.
Finally, they keep your notification settings: the alert types you chose, the sound, and your quiet hours — with your time zone if you turn them on, so as to know when it is 10 pm where you are.
This information is attached to your device’s notification identifier — so it also works without signing up. If you are signed in, that identifier is also linked to your account (section 2.5). If you use two devices, each has its own settings.
It is kept for as long as the notification identifier, and no longer. If you turn notifications off in the application, the identifier and the list are deleted from our servers. If you uninstall the application or change device, the identifier stops being valid and we stop writing to you.
That list is used only to decide which notifications to send you. It is neither sold, nor shared, nor used for advertising, and we do not combine it with any other data.
If you leave your e-mail address on the "Get notified when Android is released" page, we use it only to write to you ONCE, when the app is released on Android. Giving your address is optional: the app and the website work the same without it. Data kept: your e-mail address, the page language, the date and time of your consent and the version of the text you accepted. Nothing else is asked. Legal basis: your consent (an unchecked box), which you can withdraw at any time. Retention: kept until the Android version is released (24 months at most), then deleted. Your rights: unsubscribe at any time with the link in the message and on the unsubscribe page (your address is then deleted immediately), or write to contact.scorro@gmail.com; you also have the rights of access, rectification, erasure, restriction of processing and portability, and may lodge a complaint with the CNIL (cnil.fr). Hosting and processors: the address is stored in our Supabase database, hosted in the European Union (Ireland), like your account. The release message will be sent by Resend (a US company): your address is then passed to it; the transfer outside the European Union is covered by the European Commission's standard contractual clauses (decision 2021/914) in Resend's data processing agreement. The address is not sold, shared or used for any purpose other than announcing the Android release.
Your account and all your content are hosted in the European Union, in Ireland.
They are stored with Supabase, on Amazon Web Services infrastructure, region eu-west-1 (Ireland): email address, hashed password, username, comments, reactions, likes, predictions, leagues, votes, reports and blocks, notification identifier and attached settings. This data is stored in the European Union; only the e-mail address goes through Resend (United States) to send a password-reset message or the Android release announcement.
| Component | Role | Location | Data concerned |
|---|---|---|---|
| Supabase (AWS) | account + all content | 🇮🇪 Ireland, EU | email, username, comments, predictions… |
| Relay server (Vercel) | protects our access keys to sports data | 🇫🇷 Paris, EU | no account data; the technical IP address of the request |
| News cache (Upstash) | avoids requesting the same news twice | 🇩🇪 Frankfurt, EU | no personal data — public news items, and an anti-abuse counter that identifies nobody (see the note below the table) |
Four exceptions, and they are limited:
| Service | Role | Where | What it receives from you |
|---|---|---|---|
| Supabase | accounts and content | 🇮🇪 Ireland, EU | email, hashed password, username, your content |
| Vercel | relay server | 🇫🇷 Paris, EU | no account data; the IP address of the request |
| Upstash | news cache and anti-abuse counter | 🇩🇪 Frankfurt, EU | nothing that identifies you — see the note below |
| Sportmonks | sports data; crests, logos, player and stadium photos, flags, weather icons | 🇳🇱 Netherlands, EU | for data: nothing (it goes through our relay); for images, loaded directly: your device’s IP address |
| football-data.org | sports data; competition emblems and crests | EU | for data: nothing; for images: your device’s IP address |
| API-Sports (media.api-sports.io) | club and competition logos | not specified | your device’s IP address, when the image is shown |
| flagcdn.com | country flags | not specified | your device’s IP address, when the image is shown |
| Press publishers (RSS feeds) | news headlines | varies | nothing — unless you open an article (see below) |
| GNews | fallback news source | varies | nothing |
| Expo | application technology, notification delivery | 🇺🇸 United States | technical operating data; if notifications are enabled: the notification identifier, the text and the image address of each notification (including the points of a settled prediction) |
| Apple (APNs) | notification delivery to the iPhone | 🇺🇸 United States | if notifications are enabled: the notification identifier, the text and the image address of each notification |
| Sentry | application error reports | 🇩🇪 Frankfurt, EU | the technical detail of an error: application version, device model, and the place in the code where it occurred — never your content, your email address or your identifier |
| OpenAI | automated moderation of comments and usernames | 🇺🇸 United States | the text of the comment and the chosen username — nothing else: no email, no account identifier |
| Resend | sending e-mails (password reset, Android release announcement) | 🇺🇸 United States | the e-mail address and the content of the message — nothing else |
When the application hits an error, it sends a technical report to Sentry, a service hosted in Germany. That report serves to fix the problem, and nothing else.
It is cleaned before it leaves. Identifiers, email addresses and session tokens are removed from it automatically, including inside any web addresses it might contain. If that cleaning fails for any reason, the report is not sent at all — we would rather lose a piece of diagnostic information than let through something that concerns you.
We enable neither performance monitoring nor session tracking: Sentry receives no information about what you do in the application, only about what broke.
To prevent a single device from saturating the service and making it unavailable for everyone, our relay server counts requests. That counting needs to tell devices apart, but not to know who you are.
The address of your request is therefore never recorded. It is transformed, at the very moment it arrives, into an irreversible fingerprint — a string of characters from which the original address cannot be recovered. It is that fingerprint, and only that, which is kept: for less than one hour, then automatically erased.
A direct consequence: we cannot know which pages a device has consulted, nor link this counting to your account, nor recover your address from what is kept — and we could not do so any more if we were asked to.
The same principle protects the registration of notification identifiers: when a device registers a new one, our servers count them by an irreversible fingerprint of the address, kept for about two hours.
The data (scores, standings, news) all goes through our relay server: Sportmonks, football-data.org, the news feeds and GNews only see our server. News thumbnails also go through our relay.
The images — crests, logos, flags, player and stadium photos — are however loaded directly by your phone from the providers listed in the table above, like any image on the web. They then receive your device’s IP address, and nothing else: not your account, not your email address, not what you do in the application.
The exception: if you open an article, you are taken to the publisher’s website, which then sees you like any other visitor. Their own privacy policy applies.
Under the GDPR, you have a right of access, rectification, erasure, restriction, objection and portability regarding your data.
Deletion is directly available in the application: More › Settings › Account › Delete my account. It erases your account and your personal data, including the notification identifier linked to your account.
If you do not have an account, the only data we hold about you relates to notifications. To erase it: open More › Notifications and turn the main switch off. Your device’s identifier, the teams you follow and your notification settings are then deleted from our servers. No procedure, no delay, no account required.
For any other request, write to contact.scorro@gmail.com. You may also lodge a complaint with the CNIL, the French data protection authority (cnil.fr).
Scorro is not intended for children under 13. We do not knowingly collect data concerning them. If you are a legal guardian and believe your child has sent us data, write to us: we will delete it.
Exchanges with our servers are encrypted (HTTPS). Passwords are hashed by our provider. Access to data is restricted at database level: each account can only read and modify what concerns it.
This policy may change along with the application. The date of the last update appears at the top of this page. In the event of a significant change, we will inform users in the application.