BalozaPrivacy notice
Last updated: 11 October 2026
Baloza exists to organise a league between friends. To do that it handles data about people: names, photographs, appearances, goals. This page says which data, why, for how long, and how to make it disappear. It is written to be read, not to be scrolled past.
1. Who handles your data
The data controller is Curzio Pinnelli, reachable at info@baloza.it.
Baloza is a personal, free project. There is no Data Protection Officer: none of the cases that make one mandatory under Article 37 GDPR applies here.
2. What we collect
Account
- Email address. It is the only credential: you sign in with a code sent to your inbox, or with Google. Baloza has no passwords, and we store no credential of any kind. Up to 3.32.0 a league imported from the previous version carried over the PIN its players used there, kept encrypted, so they could claim their historical profile. That is now done by the invitation, so the PIN is neither read nor stored any more, and the column that held it has been dropped.
- Name. The one you choose on first sign-in. Until you change it, Baloza suggests the first part of your email address.
- Preferred language.
Profile inside a league
- The name shown in the table, an optional photograph, preferred position, favourite club, and your playing career if you choose to fill it in.
Playing activity
- Availability and withdrawals, selections, teams, goals, assists, own goals, appearances, awards and achievements.
- Notes written by the organiser about a match, and the manual adjustment to your rest count, if they choose to apply one.
- Being unavailable, if you mark it from your profile. It is a yes or a no, and nothing else: we do not ask for a reason and there is nowhere to write one, so none exists anywhere. It is only there so we stop asking about your availability while it lasts, and you can remove it whenever you like, from the same place.
Post-match votes
This deserves to be precise: a vote is stored together with the identifier of whoever cast it, because the system has to prevent voting twice and voting for yourself. Inside the app, though, it is shown to no one: only the totals are visible. No player can find out who voted for them — but the vote is not technically anonymous, and you should know that.
Push notifications
- If you turn them on, we store the delivery address your browser generates and the two keys it needs. They carry no name and work only for that browser on that device.
- That address belongs to your browser's push service — Google, Mozilla, Apple or Microsoft, depending on which one you use — and that is where the notification is delivered. The content travels encrypted with your two keys: that service knows an alert from Baloza reached that device, and when, but cannot read which league or match it is about.
Technical data
- The providers hosting Baloza keep ordinary service logs (IP address, time of the request) for security and troubleshooting.
3. What we do not do
- No profiling cookies, no analytics tools, no advertising.
- We do not sell or share data with anyone for marketing purposes.
- We handle no payment data: the service is free.
On artificial intelligence we cannot write a line that clean, and we would rather say so than bury it: match reports go through Gemini, and on the plan we use that content feeds Google's models. Section 6 sets out exactly what is sent and how to stay out of it.
4. Why we process it
| Purpose | Data | Legal basis |
|---|---|---|
| Creating and maintaining your account | Email, name, language | Performance of a contract — Art. 6(1)(b) |
| Running the league: availability, teams, results, tables | Profile and playing activity | Performance of a contract — Art. 6(1)(b) |
| Delivering an invitation to join a league | Email address of the person invited | Legitimate interest in connecting two people who already know each other — Art. 6(1)(f) |
| Alerting you about selections and results | Push delivery address | Consent, withdrawable at any time — Art. 6(1)(a) |
| Generating the automatic match report | Player names, match data and season statistics | Performance of a contract — Art. 6(1)(b) |
| Protecting the service from abuse and diagnosing faults | Technical logs | Legitimate interest — Art. 6(1)(f) |
| Seeing how the service is doing, from a read-only console reserved to the controller | Number of leagues and matches; the list of accounts with name, email and date of last sign-in | Legitimate interest in keeping the service running — Art. 6(1)(f) |
5. Cookies and browser storage
Baloza uses strictly technical storage — the kind without which what you asked for cannot work. That is why there is no banner: there is nothing to consent to.
- Sign-in session — kept by the browser so you stay signed in without repeating the code every time.
- Language preference — stored on the device; where local storage is unavailable it falls back to a cookie lasting one year.
- Installed-app storage — lets Baloza open as an application and keep working on a shaky connection. It holds the app's files and the latest copy of the leagues you have opened, with the names and numbers you see on screen, so you can see them offline too. It stays on your device and is deleted when you sign out.
None of it follows you outside Baloza.
6. Who processes data on our behalf
Baloza relies on providers acting as processors:
- Supabase — database, authentication and photo storage.
- Vercel — hosting for the site and its service functions.
- Resend — delivery of sign-in and invitation emails.
- Google — only if you choose to sign in with Google, which then passes us your email address.
- Google (Gemini API) — automatic writing of the match report. It receives the match data, including player names, and only when the organiser asks for it.
- Your browser's push service (Google, Mozilla, Apple or Microsoft) — delivers notifications, if you turned them on. We do not choose it: it is whichever your browser uses. It receives the alert already encrypted, as described in section 2.
Some of these providers are based or run infrastructure outside the European Economic Area. Where that happens, the transfer relies on European Commission adequacy decisions or on the standard contractual clauses under Article 46 GDPR.
The match report deserves an extra line. Baloza uses the free tier of the Gemini API, and on that tier Google states that it uses submitted content to provide, improve and develop its products — so, to train its models too — and that human reviewers may read it, once it has been disconnected from the account and the API key.
What is sent is only this: player names and their roles, the league and team names, the date and place of the match, the score, goals, assists, own goals, the match awards, the standings and season statistics up to that match (points, appearances, goals, streaks and milestones), and the “moments worth telling” the organiser writes themselves. Your email address, the photographs and the account identifiers are never sent.
And staying out of it is easy: if no match report is requested, nothing is sent to Google. No other part of Baloza goes through a language model.
7. Photographs, worth reading
Player photos and team badges live in a public store, under unpredictable file names. That means anyone who knows the exact address of a photo can open it, even without a Baloza account.
This is deliberate, and it is worth saying why: a protected address would expire after a while, and change every time it did. Photos would stop staying in the browser's cache, and every address already saved somewhere would break. The addresses cannot be listed and appear on no page a search engine can read, but they are not password-protected: anyone who knows one can open it. Do not upload photographs you would mind seeing circulate.
The cards shared outside the app are a separate matter: those are images drawn on your own device and sent as files. Whoever receives one is looking at a picture, not fetching anything from our store.
If you upload a photograph of someone else, you need their consent: for that processing, the controller is you, not Baloza.
8. How long we keep it
For as long as the account exists. You can delete it yourself, from the side menu of the app, without asking anyone. What happens next depends on how much you played:
- You already played closed matches in a league. Your profile is anonymised: the name becomes “Player removed”, the photograph is genuinely deleted, the link to your account disappears. Goals, appearances and results stay, with your name no longer on them: they are the history of a league that belongs to the others too, and erasing it would make everyone's tables unreadable.
- You never played. The profile is deleted.
- You were the only member of a league. The league is dissolved with everything in it, photographs, logo and badges included.
- You founded a league where other people remain. Deletion stops and asks you to hand the league over first, so a group is never left without an administrator.
One case does not depend on you: a league's founder can delete it, and matches, tables and the photographs of every member go with it, yours included. Your account and the other leagues you belong to are untouched. It is why founding is not handed over lightly, and why the backup exists.
Providers' technical logs follow the retention periods of their own services.
9. Your rights
At any time you can ask for access to your data, its correction or erasure, restriction of or objection to processing, and portability. Some of it you can do yourself, without waiting for a reply:
- name, photograph, position and language are changed from your profile;
- notifications are switched off from the league settings or from the browser;
- the account is deleted from the side menu;
- the organiser can export a full JSON backup of the league from the management screen.
For everything else, write to info@baloza.it. We reply within one month, as Article 12 GDPR requires.
If you think something is wrong, you can complain to the Italian data protection authority, the Garante per la protezione dei dati personali, or to the supervisory authority of your own country.
10. Minimum age
To use Baloza on your own you must be at least 14, the threshold set in Italy by Article 2-quinquies of the Privacy Code. Below that age, the consent of whoever holds parental responsibility is required.
11. Changes
If this notice changes, so does the date at the top. Changes affecting how we handle data are announced inside the app.