D-Bounce — Privacy notice

PB-1.0 · 24 September 2026

Who is responsible?

Nathan BERTRAND, acting in his own name in Belgium, is the controller responsible for D-Bounce. Contact: privacy@d-bounce.com. This notice covers the Android game, optional first-party analytics, d-bounce.com and privacy/support correspondence.

The first external closed beta is limited to at most 99 adults for a maximum of three months in Belgium, France, Luxembourg, Germany, the Netherlands, Brazil and the United States. This notice does not open registration or authorize collection. Internal QA data are kept separate from BETA.

Your choice and your game

Analytics are optional and based on consent. Before collection, the instrumented app offers three independently selectable purposes, initially unchecked. You may refuse all, choose some or enable all. Refusal changes neither gameplay nor rewards. Settings → Privacy / Analytics lets you change or withdraw your choice. The OFF edition performs no gameplay analytics. A closed server prevents analytics activation even if you accept locally.

The authoritative game state — record, stats, achievements, Dot Coins, cosmetics and settings — remains on the device. If F2 is enabled, selected events about claims, virtual-currency amounts, catalogue references and cosmetic changes may be sent; the full save is never uploaded. The current beta includes no advertising, real-money purchases, cloud save or online leaderboard, and requires no player account. Past save history is not uploaded. A choice during a run starts run observation only at a later run, without reconstructing earlier activity.

Legal bases

Optional F1/F2/F3 analytics rely on your consent. Privacy-rights handling and the minimum evidence needed to meet data-protection obligations rely on those legal obligations. Necessary service security, abuse prevention, ordinary support and limited beta administration rely on our legitimate interests in protecting the service, responding to requests and organizing the beta, subject to your rights and freedoms. You may object to processing based on legitimate interests. For optional analytics, you may withdraw consent at any time.

What is measured, and why?

F1 — Gameplay and progression: sessions and attempts, including short false starts; run duration/score, reference record, timings and bounces, streak, deaths/revive, end reason and bounded difficulty/pattern context. This helps diagnose rhythm, difficulty and repeated play. Equipped cosmetics and redundant timing percentages are excluded from F1 storage.

F2 — Features and customization: visited game screens, new achievements/claims, successful virtual currency amounts and catalogue references, cosmetics purchased/equipped and language/sound/vibration changes. This helps understand feature use. F3 — Score sharing: opening the Android share sheet and its origin, not whether sharing completed or who received it.

Events use random analytics-period/session/run identifiers, event IDs, timestamps, game build and schema. They are pseudonymous, not guaranteed anonymous. We do not collect names/emails in game events, advertising/hardware identifiers, location, detailed device model, contacts, installed apps, individual tap/position traces, seeds, full saves or share recipients/content. There is no automated decision affecting your access, rewards or gameplay, and no sale or advertising use of analytics.

Withdrawal and separate rights proof

Full withdrawal immediately stops local collection and clears queued events. A minimal command waits for connectivity; once acknowledged, the server revokes collection and removes behavioral data for that period. Offline commands expire after at most 90 days. Removing one purpose clears its pending data and sends the updated choice for server enforcement. Reaccepting creates a new random period; we do not join periods to identify you.

A separate secret retained on the device proves possession for rights requests, including after withdrawal while the receipt is retained. It is not an analytics event or public player identifier. Minimal consent/rights evidence is held separately from behavioral history. Withdrawal does not erase local game progress and does not invalidate processing lawfully performed before withdrawal.

Retention and backups

Local progression lasts until removed through local app/data management. Queued analytics expire after 72 hours and are limited to 1 MiB/1,000 events. Raw server events expire after 30 days. Derived analytics and the active tracking link end at withdrawal, 90 days of inactivity or beta end plus 30 days, whichever comes first. Server expiry jobs run daily, with catch-up after downtime; technical removal may lag one scheduled interval.

Minimal consent/rights proof is retained while needed during the active period and for up to 12 months after its end/withdrawal; rights case evidence for up to 12 months after closure. Request codes expire after 30 minutes and are single-use. Technical operational logs are limited to seven days and exclude event payloads and tokens. There is no separate long-term anonymous analytics archive.

Recovery backups expire after 30 days. Copies leaving the VPS are encrypted before transfer to Nathan's PC, with the recovery key held separately. PC rotation runs when the PC is available; expired archives are rejected for restoration. Restores are isolated and replay current deletion/revocation instructions before reopening. If the current instructions cannot be established after total VPS loss, restored analytics are removed rather than reopened. Backups are not used for renewed analysis.

Hosting, website and correspondence

OVHcloud hosts the API, private databases and private self-hosted dashboard in France. Nathan operates the project from Belgium. Microsoft 365 processes privacy/support correspondence, with European data storage selected for the service. Storage location does not by itself exclude access from other countries by provider support teams or subprocessors. Any applicable international-transfer arrangements depend on the service, recipient and country concerned. Contact privacy@d-bounce.com to obtain information about the providers, processing locations and safeguards applicable to your data, including a copy where available.

Google Play, when used for distribution, processes store/account information under its own terms; D-Bounce does not send its first-party gameplay events to Google Play. Invitation channels such as LinkedIn and Instagram operate under their own privacy notices. Recruitment correspondence is not joined to game aliases.

Nonselected applicant details are removed within 30 days of the decision; tester administration within 30 days after beta end; ordinary support within 90 days of closure. Rights correspondence follows the separate limit above. A specifically justified legal retention must be restricted and documented, not reused for analytics.

This website uses no analytics, advertising cookie, tracker or login. Network communication necessarily exposes IP addresses to service providers for delivery/security; they are not added to game event payloads. Ordinary email similarly involves sender/recipient addresses and message contents. Please send only what your request requires.

Your rights

You may request access and a copy, correction, erasure, restriction and, where applicable, portability or objection. Consent can be withdrawn at any time without losing game benefits. In Settings → Privacy / Analytics → Your privacy rights, select a retained consent period and choose Request my data or Delete my analytics data. Send the temporary code to privacy@d-bounce.com; keep it private. Generating a deletion code alone does not delete data: the verified request is handled through the contact channel.

If the code expires or you lose the app, you can still contact us. Expiry does not remove your legal rights. We assess proportionate alternative proof, without automatically asking for a civil ID or linking your email to all players. We cannot disclose another person's data on the basis of a player alias or UUID alone. Access covers the verified period and available retained data, excluding secrets and other players. Delivery is arranged privately, without a permanent public download.

We respond without undue delay, normally within one month. Where legally permitted for complex or numerous requests, an extension of up to two further months is explained within the first month. You may complain to the Belgian Data Protection Authority (autoriteprotectiondonnees.be) or your competent supervisory authority. Contact us about this notice or material changes; a new optional purpose requires a new choice.