Privacy policy

Data controller

Pilovia (sole proprietorship), operated by Jacky Désirée — SIREN 102 268 588, RCS Agen — 283 Route de Charpeau, 47240 Bon-Encontre, France.

Data contact: contact@pilovia.fr. No data protection officer has been appointed to date; any question about your data can be sent to that address.

Local vs cloud data

Guest mode (no account): your matches are kept on your device (localStorage), and a technical anonymous session is created automatically to make sharing possible. The following is then copied to our servers (Supabase, EU): the match access code, the team or player names you type in, the match configuration and status, and the log of points. That is what makes the spectator view, the QR code and resuming the score on another device possible.

Two consequences worth knowing. First, the names you type are free text: they may constitute personal data, so avoid full names if you would rather not have them stored — a first name or a number is enough. Second, clearing your browser cache erases the local copy but NOT the copy on our servers: to have it deleted, write to contact@pilovia.fr quoting the match code.

With an account (email / magic link): your email and synced matches/teams/competitions are stored on Supabase (EU) so you can access them across devices.

Data collected (with an account)

Email address (account management, legal basis: performance of the Terms).

Content you create: matches, scores, teams, competitions.

Payment data (Android/iOS): we never receive your card details. For a purchase we only receive a transaction identifier / purchase token, the product id and its status.

Processors & hosting

App hosted by Vercel Inc. (United States, transfers governed by Standard Contractual Clauses, GDPR art. 46). Database, authentication and realtime sync by Supabase Inc. (European Union, AWS eu-west-3 region).

Payments: Apple (App Store) and Google (Play) for in-app purchases; Stripe for business offers on the web. Non-EU transfers governed by Standard Contractual Clauses (GDPR art. 46).

Your rights

Access, rectification, erasure, portability (JSON export), objection. Exercise them in-app (Account → Export / Delete) or by email. Reply within one month.

You may lodge a complaint with your data protection authority.

Cookies

ScoreZen only uses local storage strictly necessary to function. No advertising cookies, no cross-site trackers, no tracking pixels, no ad profiling — so no consent banner is required.

One exception, and it is up to you: if the scorekeeper has attached a live video to a match and you tap "Watch live", the YouTube (Google), Twitch (Amazon) or Facebook (Meta) player loads at that moment — not before — and may set its own cookies under its own rules. For an Instagram or TikTok live stream, no player is loaded in ScoreZen: the button opens the stream on Instagram or TikTok. Until you tap that button, no third-party content is loaded. See the "Live video" section.

Live video (YouTube, Twitch, Facebook, Instagram, TikTok)

The scorekeeper of a match can attach the link of a live stream they broadcast themselves on YouTube, Twitch, Facebook, Instagram or TikTok. ScoreZen does not host, record or relay any video: of the video, we keep only the provider name and the video, channel or account identifier — never the full pasted address — and we rebuild the player or link address ourselves. Added to that are the score delay chosen by the scorekeeper, the timestamp of their confirmation and their account identifier. Only YouTube, Twitch, Facebook, Instagram and TikTok are accepted. When the scorekeeper pastes a Facebook or TikTok short share link, our servers query Facebook or TikTok to read that link's redirect and extract the identifier: only that short link is sent to them, with no data about you, and nothing but the identifier is kept.

On the spectator side, nothing is loaded until you tap "Watch live"; the provider name and the cookie notice are shown under that button, before you tap. At that moment the player is provided by YouTube (Google Ireland Limited in the EEA and Switzerland, Google LLC elsewhere — in "privacy-enhanced" mode, youtube-nocookie.com), by Twitch (Twitch Interactive, Inc., an Amazon company) or by Facebook (Meta Platforms Ireland Limited in the EEA and Switzerland, Meta Platforms, Inc. elsewhere). Those companies then process your data (IP address, any cookies) as controllers of their own processing, under their own policies: we receive nothing from them and send them nothing about you. The score itself is still provided by ScoreZen, with or without the player.

Instagram and TikTok do not allow their live streams to be embedded in another service: for those streams, ScoreZen shows no player, only a link; under that button, the service name and a reminder that its own rules apply are shown before you tap. By tapping it, you leave ScoreZen for Instagram (Meta Platforms Ireland Limited in the EEA and Switzerland, Meta Platforms, Inc. elsewhere) or for TikTok (TikTok Technology Limited in the EEA and Switzerland), which process your data under their own rules.

The live video is visible exactly like the match: a match shared by link stays by link, a private match stays private, and removing the live video from the match screen removes it immediately for every spectator. Before enabling a live video, the scorekeeper confirms they hold the necessary permissions (image rights, minors); that confirmation is time-stamped.

To report a live video or request its removal, write to contact@pilovia.fr quoting the match code: we remove the link on our side without delay. The video itself is a matter for the provider and the person broadcasting it.

Audience and usage measurement

We measure how the product is used, so we know what works and what breaks. Four measurements, described here in full.

Site audience: visit counts, pages viewed, country and referring site, via Vercel Web Analytics. This measurement is COOKIE-FREE and uses no persistent identifier: it cannot recognise you from one visit to the next, nor follow you across other websites.

In-app journey: a few technical events (a match was created, the creation screen was opened and which door led there, the scoring screen was opened, a link was shared, the invitation to create your own match was tapped from a spectator page, a purchase was attempted). Each carries, where one exists, the identifier of the MATCH concerned — never yours — plus a handful of values drawn from a closed list. No email, no account identifier, no IP address, no device identifier. The match identifier is erased from those records after 90 days; the count itself is kept anonymously.

Spectators: for each shared match we count viewing sessions and the date of the first one. It is a plain counter attached to the match: watching records nothing about you, and de-duplication happens entirely inside your browser, without any of it reaching us. If you tap the invitation to create your own match, that produces one of the technical events described just above — attached to the match, never to you.

Printable score sheets: on the page itself, we count three things, and only those three — that a sheet was opened, that the print dialog was launched, that a PDF was downloaded. These records carry NO identifier: not yours, not a match's, not a device's. The page path is trimmed to two segments (for example "/fr/scoresheet"), and the team names you type on the sheet never leave your browser. If you follow the link to the counter, or scan the QR code printed on your sheet, the creation screen records only where you came from — "a printable sheet" — and nothing else.

The Pulse — PUBLIC BY DEFAULT since 27 August 2026: when you create a match, the "public" option is pre-selected, and "by link" is one tap away, right beside it. As long as you leave it on "public", the match appears on The Pulse, the public map of ongoing games, showing the team names exactly as you typed them, the sport, the live score, your approximate city and your country. That city and country are derived from your IP address at the moment of publication; the IP address itself is not retained. If you choose "by link", the match does not appear on The Pulse and no city or country is recorded — but it is copied to our servers, and stays readable by anyone who has the link or the match code.

You can leave The Pulse at any time, both when creating the match and during play from the match screen: the game leaves it immediately, and the city and country are erased from our records. To make a match unreadable by link as well, the "Private match" switch in the share sheet restricts it to your device alone: the server then refuses everyone else, and any live video is switched off. ⚠️ A page that has been public may nevertheless have been seen, copied or retained by third parties (search engines, caches, screenshots) while it was visible: what others kept is no longer within our control.

⚠️ Since publishing is now the default, check what you are letting out: the names you type may refer to real people, sometimes minors. If you enter a name that is not your own — a child, a player, a team —, make sure you are allowed to, or choose "by link" when creating the match — or even "Private match" from the share sheet. For any removal request, write to contact@pilovia.fr quoting the match code.

Legal basis: legitimate interest in measuring and improving a service we operate (GDPR art. 6(1)(f)). You may object by writing to contact@pilovia.fr.

Retention

Account data: for the life of the account, then deleted. Billing data: kept per legal accounting obligations. Game data deleted immediately on account deletion.