Mobile privacy

This policy describes HRS Digital Boardgame mobile services and, specifically, Chess 3D Android 3.3.7. Other games and already distributed versions can have different SDKs or policies. Updated: 2026-10-09.

Publisher and contact

The publisher and hosting details are listed in the legal notice. For Boardgame accounts and data, email boardgame@hrsdigital.net.

Data and features

• Account: for account-enabled sessions, Firebase assigns an identifier to the guest profile. An optional shared Boardgame account uses Google or an email/password. Firebase Authentication processes the identifier, account email and chosen name or nickname. The password is sent to the authentication service; the hub server does not store it.
• Continuity: technical identifiers link Core, World and World2 profiles across games and devices. The local central session is encrypted with Android Keystore. A Boardgame account is separate from CardVerse.
• Profile and online play: Firebase receives nicknames, player identifiers, positions, moves, dates, results and statistics for multiplayer and rankings. Other players may see nicknames and scores. Email is not written into the public nickname directory.
• Age choice in Chess 3.3.7: after language selection, the app asks only for an age band: under 13, 13–17, or 18 and over. This band is stored locally. The app does not request or store a birth date.
• Under 13: the app does not initialize a player account and hides multiplayer, profile, rankings, tournaments, external sharing and links to other apps. Computer, learning and local play remain available with the local classic room. An unresolved age is kept on the same protected path until a band is selected.
• Local data: language, preferences, themes, progress and offline games remain in this installation unless an online feature or export is used.
• Requested emails: address verification and account recovery send the email address and language to Boardgame, Firebase and Brevo for delivery. ImprovMX forwards replies to boardgame@hrsdigital.net into the publisher's mailbox. These operations support account requests, not advertising subscriptions.
• Security: Firebase App Check with Play Integrity checks the app and device. Authentication and hosting process IP addresses, technical metadata and request logs to operate the services and prevent abuse.
• Optional purchases: where available, Google Play processes payment. The game/server verify product, purchase reference and pseudonymous account identifier to retain access. HRS Digital does not receive card numbers. Availability depends on the store and server.

Advertising and choices

The game includes banners, interstitials at planned pauses and optional rewarded videos. An ad or additional room unlock is not guaranteed; optional access also depends on server features.

Chess 3.3.7 requests ads without personalization for every age band. Under 13 uses AdMob child treatment and ages 13–17 use AdMob teen treatment; both are limited to maximum ad content rating G. Yandex is not selected for a minor or unresolved age, including in Russia. Adults use Yandex in Russia and AdMob elsewhere, using the routing service and device country signals without GPS permission. Only one provider is selected per session. Google UMP receives the applicable under-age signal, obtains required choices and allows changes in Privacy settings where a regulatory privacy option is available.

Advertising SDKs may process IP-derived approximate location, advertising/installation identifiers, ad interactions, crash reports, diagnostics and other performance data for delivery, measurement and fraud prevention. Yandex includes AppMetrica components: documented defaults and SDK activation paths support this cautious disclosure; it is not a claim that a report was observed leaving this device. The optional Firebase Analytics setting does not control all ad SDK telemetry.

Chess 3.3.7 remains without the Mintegral and Pangle adapters and their transitive SDKs that were included in 3.3.5. Direct AdMob and adult-only regional Yandex remain. AdMob publisher personalization and Yandex personalization consent stay disabled in the app code; this does not disable all technical SDK data.

Chess 3.3.7 declares no precise-location, contacts, microphone, camera, photos or SMS permission. IP-derived approximate location and SDK identifiers may still be processed.

Google privacy · Yandex privacy · AppMetrica data disclosure

Optional statistics

Firebase Analytics is off by default for all users and remains disabled for minors, unresolved ages and development builds. An adult can enable it separately in Privacy settings. It may then measure use, installation, sessions and purchase events. Analytics advertising-ID collection and personalization remain disabled in app configuration. The app does not intentionally send email, nickname or match contents to Analytics.

Withdrawing this choice stops future collection and resets local Analytics data; it does not retroactively erase data already received by Google.

Providers, security and retention

Online features use Google Firebase and Google Cloud. App-owned network connections use HTTPS, direct ad providers document TLS, and AppMetrica documents transport encryption. Data can be processed in several countries. Exclusive European storage and end-to-end encryption of matches are not promised.

Preferences remain until erased. Online identities, profiles and histories remain until deletion or handling of the corresponding request. Advertising data follows provider retention periods. Security logs, purchase references and backups may need separate retention; the purpose and period must be explained when responding to a request.

Request deletion of your Boardgame account

Email boardgame@hrsdigital.net from the account’s email address. Guest players can name Chess and their displayed nickname, if known. You can request deletion without reinstalling the app.

Specify the whole Boardgame account or a particular game. Requests are handled manually after a proportionate identity check. Opening the email link does not itself delete data. Never send passwords, sign-in codes, tokens, payment details or identity documents in your initial message.

The review covers the Core identity, game profiles and public nicknames across Core, World and World2, server account links and associated gameplay. Completed matches may retain an anonymized participant to preserve the opponent’s result. Any retained purchase, security or backup records must be explained in the reply with their purpose and retention period. Immediate deletion of all backups is not promised.

This does not delete your Google, Google Play or CardVerse account. Personal exports and data on other devices require separate deletion.

Your privacy rights

You may request access, correction or deletion of personal data and withdraw consent. Portability, restriction, objection and response deadlines depend on the processing and applicable law. Withdrawing consent stops future affected processing; it does not invalidate earlier lawful operations.

Your interface language does not establish nationality or residence. Name the game, platform and affected data when contacting us. You may name your country if relevant. Never send passwords, cookies, access tokens, full payment details or identity documents in an initial message. A proportionate identity check may be needed.

Where applicable, EEA GDPR rights and a complaint to the competent supervisory authority apply. In France this is the CNIL; in the United Kingdom it is the ICO. Other countries may provide additional protections for children, advertising, sensitive information or international transfers. These pages do not ask you to waive mandatory protections.

Age and consent requirements depend on the country and feature. If you believe a child provided data without required authorization, contact us to review removal. Store audience declarations and ad settings must match the distributed version. A feature must remain disabled where it cannot lawfully be offered.