Tables for iOS & dfomin.com
Last updated: 7 September 2026
This policy explains what personal data is processed when you use the Tables iOS app or visit dfomin.com, on what legal basis, and what rights you have. It is written to meet Articles 12–14 of the EU General Data Protection Regulation (GDPR).
No data protection officer has been appointed. This is not required: fewer than twenty people are regularly engaged in automated processing here (Art. 37 GDPR, § 38 BDSG).
Everything you enter into the app — tournament names, team names, scores, dates, locations and referees — is stored only in the app's local storage on your device. It is never transmitted, never stored on a server, and is not accessible to anyone else. There is no account and no cloud sync.
Because of this, deleting the app deletes your tournaments permanently, and they cannot be recovered.
The app uses Google Firebase Analytics to understand how it is used, so that problems can be found and features prioritised. The following is collected:
| Data | Examples |
|---|---|
| App instance identifier | A randomly generated ID assigned to your installation of the app |
| Device and system | Device model, iOS version, language, approximate country |
| Usage events | App opens, screens viewed, session length, actions such as creating a tournament or adding a team |
| App state | Number of tournaments, teams and games you have; selected colour theme; app version |
| Diagnostics | Errors while saving or loading data, including error codes and available free disk space |
Team and tournament names are never transmitted. They are treated as personal data, because teams are often named after real people, and they stay on your device.
This data is pseudonymous, not anonymous: it is tied to a random identifier for your app installation rather than to your name, but it remains personal data under the GDPR.
Legal basis: legitimate interest in understanding how the app is used, in finding and fixing defects, and in deciding which features to build, Art. 6(1)(f) GDPR. You have the right to object to this processing at any time under Art. 21 GDPR — see section 9.
Recipient: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland, and Google LLC in the United States. Retention: 14 months.
The About screen has a Feedback form. If you use it, the message you write is transmitted to a private channel on Telegram. The same channel receives automatic technical reports when data migration fails, which contain error descriptions but no tournament or team names.
The feedback form is anonymous — it carries no identifier and cannot be replied to. Please do not include personal details in it. If you want an answer, use email instead, which is covered in section 6.
Legal basis: your consent through the voluntary act of sending the message, Art. 6(1)(a) GDPR. Recipient: Telegram FZ-LLC, Dubai, United Arab Emirates.
Donations are made through Apple's in-app purchase system. Payment and billing data is processed entirely by Apple; it is never received here. Only the aggregated fact that a purchase completed is visible, with no identifying details. See Apple's privacy policy for how Apple handles that data.
If you email the address in section 1, your message, your email address and any details you include are processed for the purpose of answering you. The legal basis is legitimate interest in responding to enquiries, Art. 6(1)(f) GDPR, or Art. 6(1)(b) where your message concerns the use of the app. Messages are deleted once the matter is settled and no retention obligation applies.
These pages set no cookies, use no tracking, and load no external resources — no fonts, scripts or images from third-party servers. Apart from the hosting described below, nothing about your visit reaches anyone else.
The website is hosted on GitHub Pages and delivered through the Fastly content delivery network. The host is:
GitHub, Inc.When a page is requested, GitHub's servers automatically record standard access log data: the IP address, the date and time, the file requested, the amount of data transferred, the HTTP status code, the referring page and the browser identification. This is technically necessary to deliver the page and to protect the servers against misuse.
These logs are created and held by GitHub on its own infrastructure. They are not accessible to the controller named in section 1, and the retention period is determined by GitHub. Please refer to GitHub's privacy statement for how GitHub processes this data.
Legal basis: legitimate interest in operating and securing the website, Art. 6(1)(f) GDPR. GitHub's Data Protection Agreement, which incorporates the European Commission's Standard Contractual Clauses, applies through the GitHub Terms of Service.
Google LLC is located in the United States. Transfers are covered by the European Commission's adequacy decision of 10 July 2023 for the EU–US Data Privacy Framework, under which Google LLC is certified.
Telegram FZ-LLC is located in the United Arab Emirates, for which no adequacy decision exists. Transfers therefore rest on your explicit consent for the specific transfer, Art. 49(1)(a) GDPR, given by choosing to send a feedback message.
GitHub, Inc., which hosts this website, is also located in the United States. Transfers are covered by GitHub's Data Protection Agreement, which incorporates the European Commission's Standard Contractual Clauses.
Under the GDPR you have the right to:
To exercise any of these, email the address in section 1. Note that analytics data is tied to a random installation identifier, so to act on a request it may be necessary to ask you for that identifier — otherwise your records cannot be located.
To stop analytics: turn off Share usage data in the app's Settings. Collection stops immediately, the analytics identifier already stored on your device is deleted, and the setting stays off after restarts. Deleting the app has the same effect.
You have the right to lodge a complaint with a data protection supervisory authority, in particular in the EU member state where you live or work (Art. 77 GDPR).
This policy may be updated when the app changes or the legal position does. The date at the top always shows the current version.