Your data, clearly

Scope: this web version. The public playable pages remain closed for verification in this pilot. The features below apply only where enabled. Mobile apps can use different services; see the mobile policy.

The web advertising module is disabled. When configured, it does not contact an ad provider before a valid consent-platform signal.

Publisher and contact

Email boardgame@hrsdigital.net for Boardgame data requests. Publisher and host details appear in the legal notice.

Data used to play

• Local matches: positions, moves, results and difficulty are kept in a private server session. “Local” means no network opponent; it does not promise browser-only storage.
• Preferences: optional nickname, themes, sound, accessibility, computer difficulty, favorites, resume markers and learning progress stay in this browser's storage and are not account-synchronized.
• Archives: saved games are kept in a private server library, accessed by a browser key or the verified Boardgame account for copies you attach to it.
• Optional multiplayer: Firebase receives player identifiers, rooms, positions, moves and results needed for a match. Opponents see table data. Historical collections may also be read by other authenticated players; a private room does not guarantee board confidentiality.
• Optional account: Google/email sign-in uses Firebase Auth; the server does not store the password. Boardgame links technical Core, World and World2 identifiers to restore profiles across games/devices. Nicknames may be public. CardVerse accounts are separate.
• Security: IP addresses limit abusive attempts. PHP, web hosting and Firebase can create technical logs; retention and access must match the actual deployment.

Purposes

Data operates the requested match, restores sessions and archives, retains choices and protects the service. Email/password are needed only for the chosen account. This version does not implement unsolicited marketing or automated legal decisions. The controller must document the applicable legal basis, including requested service performance and necessary security interests where justified.

Cookies and browser storage

Optional usage statistics

When enabled on the public domain, Google Analytics measures visits and consulted games only after your separate optional agreement. The Google script is not loaded before acceptance. Hub email addresses, nicknames, match contents and URL parameters are not sent by this module. Account, profile, archive and payment pages are excluded.

The choice is retained for six months in this browser. Measurement cookies are limited to this period and removed by the hub when consent is withdrawn. “My statistics choices” changes the decision. Withdrawal stops future measurement, not data already received by Google.

Android previews

The HRS Digital registration form collects the Google Play account email, selected contact language and optional country to handle applications and prepare invitations. These remain in private administration and are not sent to Google Analytics. Applying is not an advertising subscription.

Messages sent to Boardgame

The Contact form collects the request reason, optional game, reply email, subject, message and interface language. A signed-in address can be suggested; guests can supply an address without an account. Data handles and tracks the request, not a marketing list. Never enter passwords, sign-in codes or tokens.

Messages enter the private project inbox in HRS Admin. Email, subject and text are encrypted in SQL storage; project/reason/game/language/status/dates remain private metadata. Authorized inbox administrators can view requests. These data do not appear in public catalogues, project cards or media.

A per-send reference and pseudonymous fingerprints detect retries and limit abuse. The central inbox does not store raw IP; hosting logs are separate. An acknowledgement may be queued using the request's language and a short reference, without repeating its text. Queuing does not guarantee email delivery.

The outbox stores encrypted recipient/language/acknowledgement content separately. After successful delivery that content is erased; a technical receipt without email/text remains. On permanent failure, a running worker removes acknowledgement content older than seven days. This is not a retention period for inbox messages.

The contact inbox has no automatic request deletion. An authorized administrator can permanently delete a message and its email in HRS Admin. Inbox, technical-receipt and backup retention must be defined for the deployment. Name “Boardgame Contact form” and its reference if known when requesting removal. Inbox deletion does not automatically cancel an already queued acknowledgement or erase a delivered email.

The configured hosting/mail providers process data for storage/delivery. Their locations, transfer safeguards and the request/security legal basis must be documented; sending a contact request is not blanket consent to unrelated processing.

Web advertising and privacy choices

No production web advertising provider is activated by this configuration. Local demonstration placeholders do not promise real ads or rewards. Activation requires real ad units, a certified consent platform, a published policy and verification on the production domain.

Consent requirements differ from the rules for storage necessary to deliver your requested service, including browser local storage. See CNIL guidance on cookies and tracking devices.

Deletion and retention

Archives are not automatically erased. Each private library is limited to 100 games or 32 MiB compressed. In My games, you can export, rename or delete an archive. Deleting the original does not delete copies attached to an account or your personal exports.

Signing out or clearing cookies does not erase server archives. Erasing the browser library key loses access to that browser's originals: export or delete the relevant archives first. Discovery progress can be reset separately for each game.

Browser data can be cleared in browser settings. Erasing cookies, signing out or uninstalling a mobile app does not erase the shared Boardgame account. Profiles, match history, purchase/security records and backups can have different retention needs; any retained scope and period must be explained in the request response.

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.

Providers and international processing

Optional support

PayPal processes contributions on its own site. If card payments through Stripe are enabled, Stripe processes payment on its secure hosted page. The hub retains only a technical reference, amount, currency, status and any refunds; it does not receive card numbers. Data used to prevent abuse are pseudonymized.

The retention period for payment references and accounting obligations must be defined with the publisher before Stripe is enabled.

Google Firebase and Google Cloud host/authenticate online features. The site serves its own graphical resources and explanatory animations, without an external video player. Where ads are enabled and accepted, Google AdSense and the configured consent platform also process the relevant technical data. Providers can process data in several countries; effective database regions, processors, contractual clauses and transfer safeguards must be checked for the actual deployment. Exclusive EU storage or compliance with an unverified foreign localization rule is not promised. See Firebase privacy information.

Your rights

Applicable law may provide access, correction, deletion, restriction, objection and portability rights. Name “Boardgame web”, the game and affected records. Never send passwords, cookies or access tokens. A proportionate identity check may be needed. Language does not establish nationality or residence.

Where applicable, contact the competent supervisory authority, including CNIL in France or ICO in the United Kingdom. Local protections for children, advertising, sensitive data and international transfers remain applicable. If a child provided data without required authorization, contact Boardgame to review removal. These pages do not ask you to waive mandatory rights.