Privacy

Who runs this

Urgent work Table Football is run by Dominik Veliký. For anything about your data, write to urgentworktfootball@gmail.com — that address reaches a person, not a queue.

What is held, and why

Your account: your email address. Sign-in itself is handled by Clerk — this service never sees or stores a password, and never has one to lose. The name Clerk asks for at sign-up stays with Clerk; this service does not keep it and nothing here shows it. If you sign in with Google or Discord, Clerk holds that link and this service only learns that it is you.

Your player profile: your #tag, display name, avatar if you upload one, language, time zone, rating and match counters. To signed-in players your tag, name, avatar and rating are visible — that is what a leaderboard is. Signed-in readers also see your statistics: your record over the last 365 days, your form and goals in recent matches, MVPs, how your rating has moved, which seat and side you take, and how you do against your own rating there and at each table, venue and town you play in. To anybody who is not signed in, and to search engines, you appear under a drawn fairy-tale name and a drawn figure instead, unless you turn your handle on in your profile. The fairy-tale name is yours: you can rewrite it, and what you write is part of your data. From your confirmed matches the app also hands out medals — gold, silver and bronze — for a week, a month, a quarter and a year: best player, attacker, defender, best team, MVP — the player of doubles voted MVP most often — and best player at a table. They show on your profile the way the leaderboard shows your rating, and a team medal names your teammate the way the leaderboard would; a medal at a table says where you play, so a reader who is not signed in sees it only if you turned your handle on. For completed tournaments of at least four entries the app also hands out cups — gold, silver and bronze for the placing, and a small gold cup for the tournament's best defender and best scorer. They show on your profile like the medals, and a doubles placing names your teammate; only a signed-in reader sees which tournament a cup is from.

Matches you take part in: who played, the score, goals, when and on which table, any note or nickname, and how each participant voted on the result including the reason for a rejection. A match is a shared record, and the people who played it see all of it. Every signed-in reader sees who played it, the score, and each player's goals and rating change; the note, the votes and the comments are for its players and the app's administrators only. Who sees a match's photos is described with the photos. In a game of doubles the players also vote for its MVP: whom you voted for is secret — nobody but you sees it, and it is in your copy of your data — and only the result is shown with the match.

Photos: an avatar if you upload one, photos of tables and of proposed places, and photos attached to matches. Table photos are public. Match photos are visible only to the people who played that match and to administrators of the place.

Notifications inside the app, and email about them: when a match waits for your vote, when one is disputed, when your rating changes, and the like. Which categories reach you by email is yours to set in the app — muting one silences the email, never the bell. On top of that come the transactional emails the service has to send, confirming your address and resetting your password. There is no newsletter and no marketing email.

Feedback you send through the bug and ideas form. It is linked to your account so we can reply; when the account goes, the link is removed and the text stays anonymous. A report may also carry what the app knows about itself — its version, the platform, the operating system version, the phone model and the identifier of the request that went wrong — so a crash can actually be found. We never collect logs from your device; the Android app's crash reports are described below. If you attach a screenshot, only we can see it, and it goes when your account does — do glance at it before sending, since it shows whatever was on your screen. A screenshot is deleted 90 days after the report was sent, and the whole report after a year.

Technical: your IP address is used to limit how often the same source may register, record matches, vote or send feedback. It is held in the running server's memory for a matter of minutes — up to an hour after you sent feedback — and is not written to our database. The server also logs each request — the time, the page and where you came to it from, the response and your browser's identification — and keeps the IP address in it only shortened to its network, never in full. Newer entries overwrite the oldest, after one to three weeks at today's traffic. The hosting provider keeps its own request logs.

Analytics and crashes in the Android app: the app includes Google Analytics for Firebase and Firebase Crashlytics. From its first start it sends Google when and for how long you use it and when the app and the system are updated, and with that the manufacturer and model of the phone, the versions of the system and of the app, the language of the system, the type of network connection and the store the app was installed from. When it crashes, it sends a crash report — the place in the code, the state of the app, the same details about the phone and what happened in the app just before the crash. All of it carries a random identifier of the installation, never your account, name or email, and the app does not read the advertising identifier. From the IP address Google estimates the country and an approximate place. Google keeps crash reports for 90 days and analytics tied to the installation for 14 months at most. Neither the website nor the iOS app sends anything of the kind.

What is not collected: no location from your device's location services (the approximate place Google estimates from the IP address is described under analytics above), no contacts, no device identifiers for advertising, and no profiling. Nothing is sold or handed to anyone for marketing.

Cookies

Only the cookies the service needs to run. While you sign in or are signed in, Clerk sets the sign-in session cookies (__session and __client_uat) and, at its own address clerk.urgent-work.eu, a cookie by which it recognises your browser; Cloudflare, which Clerk runs behind, adds its own cookies against bots. Signing out removes the session cookie and switches __client_uat to 0, the “signed out” marker; the browser cookie at Clerk stays. If you open a page in a language other than the one your browser asks for, the site remembers that language in the NEXT_LOCALE cookie until you close the browser. That you agreed to the content rules is kept in your browser's storage (localStorage), and signing out does not remove it; Clerk keeps its settings there too. There are no analytics or advertising cookies, which is why you are not asked to consent to any.

Who else touches it

Sign-in and account credentials are handled by Clerk. The mobile apps send Clerk a device identifier so that it knows which device you sign in from, and the iOS app adds the device model and the versions of the system and of the app; signing out does not change the identifier, only uninstalling the app or clearing its data removes it. Analytics and crash reports from the Android app are processed by Google (Firebase), as the paragraph on analytics above describes. Everything else — the application, the database and uploaded images — runs on one server rented for this purpose; the database is not a third-party service. Transactional email is delivered by Resend. Sign-in providers see only what you approve when you use them. Nobody else is given the data. Nightly backups are encrypted on that server before they leave it and stored at Cloudflare R2, so the backups Cloudflare holds are only archives it cannot read.

How long it is kept

For as long as you have an account. You can delete it yourself at any time, in your profile — and in the mobile apps — without asking anyone.

Deleting removes your address, display name, the fairy-tale name you wrote, tag, avatar, notifications, identity claims and place proposals, and your Clerk account with them. The matches you played remain, because they are also your opponents' matches, and deleting them would destroy other people's results, ratings and history. Your part in them is stripped of everything that identifies you, cannot be traced back to you, and cannot be claimed by anyone else. Nightly backups are kept for about two weeks, and the first backup of each month for three months — that one only encrypted, away from the server. So what you delete stays in the backups taken before the deletion until they age out, three months at most.

Your rights

You can ask what is held about you, have it corrected, have it deleted, object to how it is used, and receive a copy in a portable form.

Deletion and a copy of your data both work in the app, in your profile. For anything else, write to urgentworktfootball@gmail.com; you will get an answer within a month, as the law requires.

If you believe your data is handled wrongly, you may complain to the Office for Personal Data Protection (Úřad pro ochranu osobních údajů, uoou.gov.cz).

Children

The service is not aimed at children under 15 and is not knowingly used to collect their data. If you believe a child's data has ended up here, write to the address above and it will be removed.

Changes

If this policy changes in a way that affects you, the date above changes with it and the change is described in the application's changelog.