Current Data Scope

What The Game Handles Today

Dust to Dust is a browser-first quick-draw game. The public launch build runs as a local-first experience: your progress, settings, and local profile stay in your browser unless a later release explicitly adds an online feature back.

Information stored on your device

  • campaign progress, duel records, settings, and unlocks saved with browser storage
  • your optional local browser profile, including display name and handle if you choose to save one
  • cache files used to load the site and game assets faster between visits

What the public build does not send

  • no ad-tech identifiers, purchase requests, or payment data
  • no remote crash reports, no ad personalization, and no payment telemetry during normal public play
  • no live ranked, leaderboard, friends, ghost, or cloud-save traffic in the public launch channel

How information is used

  • to save your progress and restore the local browser build between sessions
  • to render the game site and cache assets needed for play
  • to review and reply if you submit the support form

Third-party services

The public site is served through Firebase Hosting, which processes the standard request data needed to deliver pages and assets. The site fonts are bundled with the game and served from the same Dust to Dust origin. Google Analytics 4 measures page traffic and a small set of gameplay interaction events such as game starts, duel starts and completions, Armory opens, support-page visits, and support-form submissions. If you submit the support form, Formspree processes the form fields and standard request data needed to forward that request to the private support inbox.

Player Choices

What Players Can Control

The public build keeps the game playable without asking for sign-up, purchases, or live-service participation.

Optional local profile

You may save a display name and handle for this browser. That profile is local to your device in the public launch build and is not published to live boards or cloud services.

Clearing local data

You can remove browser-stored progress and profile data by clearing site storage for the game in your browser settings. This also removes cached assets and local preferences for Dust to Dust.

Support form submissions

If you use the support form, the information you enter is sent to Formspree so the request can be forwarded to the private Dust to Dust support inbox. Do not submit passwords, payment data, or other sensitive information through the support form.

Basic traffic analytics

The site uses Google Analytics 4 for basic traffic and product-usage measurement. That includes standard page views plus a small set of custom events tied to starting the game, opening the Armory, starting and completing duels, visiting the support page, and submitting the support form. The site does not use Google Tag Manager, ad pixels, or ad-personalization signals.

Changes to this notice

If the game later adds broader analytics, payments, ads, or online competitive systems, this notice will be updated before those features go live in the public channel.

Quick summary: the public Dust to Dust browser build is still local-first. No ads, no payments, no live social systems, and only basic Google Analytics traffic measurement are active in the public launch channel.

Read Terms