Privacy

Who runs the game

The Pub League game and the publeague.eu website are run by the operator of Pub League. You can write to hra@publeague.eu or on Instagram at @publeague.game.

What the game stores on the server

The game is played in a shared world, so your club lives on the server. If you only open the game and never enter the world, the server stores nothing about you.

Anonymous account

When you enter the world, the game creates an account for this installation: a random number, with no name, e-mail or password. The server remembers when it was created and when you last connected. The sign-in is saved on your phone.

Your club and what you make up

The village name, club name and coach name you type, plus the region, colours, crest and the look of your coach. Other players see these in tables, on your club's card and in search. So don't put anything there that you don't want to reveal about yourself. Names go through a profanity filter.

The game itself

The state of your club (squad, money, buildings, results, chronicle) and your decisions for the day: lineup, cards and actions. Other players can see your squad, league table and ground, but not your money.

Auctions and messages

Your club's auctions and bids are visible to other clubs. You can only send an opponent a ready-made line from a list; you cannot write them your own text. The server remembers which club sent which line to whom.

Club backup (optional)

So that your club survives a lost or replaced phone, you can link the account to an e-mail or to Google. With e-mail, we store your address and send a code to it. With Google, you sign in in the browser and Google passes your e-mail and basic profile details (name, picture) to the sign-in service. The game only uses the e-mail, and only you see it, in Settings. Its one purpose is to let you get back to your club from another phone. You can also sign in this way before you set up a club; the account is then created by signing in.

Notifications (optional, Android only)

Morning reminders and the kick-off reminder are scheduled by the phone itself and sent nowhere. Messages from the server are delivered by Firebase Cloud Messaging (Google). Its library in the game asks Google for a delivery address for the phone, called a token, and may do so as soon as the game starts. The token only reaches our server if you turn notifications on: the game stores it with your account together with the app language, and the server can then tell you that someone has outbid you, that an auction has ended or that an opponent has sent you a message. The notification text travels to your phone through Google. When you turn notifications off, the token is cancelled and we delete our copy.

Technical connection data

Whenever your phone or browser talks to a server, the server sees technical connection data, mainly the IP address and the type of device or browser. The service providers need it to run the service and protect it from abuse, and may keep it in their operational logs. The game does not record it with your club and does not track anyone by it.

What stays on your phone only

Game settings (language, sound, appearance, font), the sign-in to your account, a copy of today's club state, and your progress through the guide and the coaching licence. The offline career for testing is saved on the phone only. If Android backup is turned on, your phone may back the game's data up to your Google account; you control that in the phone's settings.

The publeague.eu website

• Sign-up list. The e-mail from the form goes straight to the mailing service Brevo, which sends you a confirmation e-mail. We will only use it to tell you that the game is out. You can unsubscribe at any time: use the link in the e-mail, or write to us.
• Friendly invite. The website only shows the club code from the link and hands it to the game on your phone. It does not store it.
• Language. If you switch the language by hand, the website remembers the choice in your browser's storage. The website has no cookies of its own.
• Hosting. The pages are served by Cloudflare and the fonts are loaded from Google Fonts. Both see technical connection data when they do.

Who helps us run it

The game and the website run on other companies' services. They only get what they need to do their job.

Supabase

Accounts and sign-in, the shared world's database (clubs, decisions, auctions, messages, notification tokens) and the notification sender.

Google

Firebase Cloud Messaging delivers notifications to Android phones. Google sign-in only if you back your club up with it. Google Fonts supplies the fonts on the website.

Brevo

The sign-up list on the website, and sending the e-mail with the code for the club backup.

Cloudflare

The publeague.eu website and its domain.

GitHub

A job runs here every evening to play the round: it reads the clubs and the day's decisions from the database and writes the results back.

Neither the game nor the website sends data anywhere else, and we do not sell it to anyone. The Instagram link is just a link; what you do there is covered by Instagram's own rules.

How long we keep it

• The account (and the e-mail, if there is one on it) stays until you delete it.
• A club without a coach. At present, if you don't turn up for 14 days in a row, the chairman (a bot, that is the computer) takes the club back. A club in League 10 can then be taken over by someone else. Your account stays.
• Messages older than a week are deleted.
• Notification tokens. We keep at most three phones per account. A token that has not been heard from for 90 days is deleted.

How to delete or correct it

You delete the account, together with the e-mail and tokens, yourself in the game: Settings, right at the bottom, Leave the world and delete account. Exactly what goes and what stays with the club is on the Delete your account page. Without the game, write to hra@publeague.eu.

Write to the same address if you want to know what we hold about you, or want it corrected.

Changes

When what the game or the website does with data changes, we will update this page and the date below it.

Last changed: 13 November 2026