Privacy policy

Football

by Dzuma · DZUMA FOOTBALL

Data practices for offline play, controlled testing and publisher support.

Updated: · Android

1. Game, publisher and contact

This policy covers the Android game “DZUMA FOOTBALL”, presented on the website as “Football by Dzuma”. Publisher and data controller: Paweł Siodłowski — by Dzuma. This concerns support and testing data described in this policy. The brand may also appear as “by Dżuma” in the game.

For support, privacy or personal-data enquiries, email cgmklikersi@gmail.com. You can also use the publisher’s contact form. Game website: bydzuma.pl/en/football/.

2. Ordinary offline play

Matches and the tournament run locally, without registration or signing in. The game does not request player contact details. The current implementation has no advertisements, in-app purchases, chat, advertising analytics or automatic upload of progress to the publisher.

The game does not read the advertising ID or require access to location, contacts, microphone or camera. We do not sell player data. The separately activated test mode is explained in section 4.

Ordinary play does not require a child’s personal details and uses no behavioural advertising. For support involving a minor, a parent or guardian should contact us. Do not include a child’s information that is unnecessary to resolve the issue.

3. Data saved on your device

The app stores settings, selected teams and formation, and tournament progress or results in its private directory to support continued play. Supporting files, a previous-save backup and local technical information may be retained to read the save or investigate a fault.

This is not an online player account or a publisher-operated cloud-save service. Ordinary gameplay does not automatically transmit these files.

4. Test builds and Firebase Test Lab

The APK may include a Game Loop adapter for controlled testing. A test operator activates it through a separate test invocation, for example in Firebase Test Lab; launching ordinary gameplay does not activate it. Tests use separate saves.

A test report may include the build version and hashes, scenario and session, gameplay events, errors, logs, captured frames, and measurements of frame times, memory, app lifecycle and Android parameters. The test environment may also create recordings and additional device information.

To distinguish compatible runs, the adapter creates a pseudonymous hash from Android ID and device parameters, including model, system build and ABI. It is not an advertising ID and is not described as fully anonymous.

The adapter writes results locally and passes them to the results destination supplied by the test environment. Access to Firebase materials depends on Google project permissions. The publisher receives materials shared by the operator or tester and uses them for fault analysis, regression comparison and stability improvements, not advertising. This is not Firebase Analytics tracking ordinary play.

5. Optional support and reports

When you submit the form or send support materials, you provide a return contact address, message and chosen attachments. Logs or recordings may reveal technical information and on-screen content. Remove other people’s information, passwords and unrelated content.

The information is used to respond and investigate the issue. Providing it is optional; missing contact or diagnostic details may prevent support. A report does not subscribe you to marketing.

Routine correspondence and diagnostics rely on the controller’s legitimate interest in providing support and maintaining the game — Article 6(1)(f) GDPR. Where an enquiry concerns a contract or steps requested before entering into one, Article 6(1)(b) GDPR may apply.

6. Recipients and service providers

The website and correspondence may use providers identified in the portal privacy policy, including the Formspree contact form and Google email services. Google provides Firebase Test Lab and test-results storage. These providers and authorised subprocessors may process data to deliver their services.

Shared reports may also be analysed using AI tools, including ChatGPT/OpenAI. Provide only necessary material without unnecessary personal information. The service is described in the OpenAI privacy policy. This is not a player-tracking module in ordinary gameplay.

Submitted support materials are not intended for public publication. Information may be disclosed to authorised authorities where required by law. Providers may use infrastructure outside the EEA; their terms and transfer mechanisms are described by Google, Google data-transfer information and Formspree. You may ask the controller for information about safeguards.

7. Website links and platform services

Opening the policy or game website in a browser makes a separate connection to that site. Hosting and browser services may process an IP address and technical request information under the portal policy and their own terms. Following the link does not send the publisher your local tournament save.

Android, Google Play and services activated by the user may process data as part of their own operation. This policy does not replace their terms or mean that those services process no data.

8. Retention, security and deletion

Local saves remain on the device until app data is removed. In Android settings, select Apps → DZUMA FOOTBALL → Storage → Clear data; labels vary by device. Clearing data removes local progress and settings. The publisher does not operate a cloud-save recovery service. Clearing app data does not delete reports already shared with the test operator or publisher.

Correspondence and reports are retained for the time needed to handle the issue, investigate the fault and verify the fix. Material still needed for regression evidence or legal claims may be retained to the necessary extent; unnecessary personal information should be removed or anonymised. Retention in a test environment also depends on its operator’s settings and policies.

Access to received materials should be limited to people handling the issue. To request deletion of correspondence or a shared report, contact the controller and identify the relevant material.

9. Your rights

Where GDPR applies, you may request access, correction, deletion or restriction of your personal data, object to processing based on legitimate interests, and exercise portability where applicable. If consent is the basis for a particular processing activity, it can be withdrawn without affecting the lawfulness of earlier processing.

Use the contact form to submit a request. You may also complain to the relevant supervisory authority; in Poland this is the President of the Personal Data Protection Office. There are no player accounts that must be closed to delete a local save.

10. Policy changes

We will update this page and its date when functions, services or data practices change. The information concerns the described Android implementation and its separate test mode; new functions require the policy to be checked again before release.