Firebreak Grove Privacy Policy

Current release: anonymous and on-device

No login or account is required to play the current release.

Mission progress and saved sessions: Mission progress, action history, and saved sessions stay only on your device. They are not uploaded to us or associated with a server account.

In Settings, Clear game progress and saves deletes the active watch, campaign progress, lesson history, and recovery records. Appearance settings remain on mobile. Removing Firebreak Grove or clearing its browser or operating-system app data also deletes this local information. Because we do not receive it, we cannot recover it for you.

Information you choose to send

If you choose to send us an email, we receive your email address, message, and anything you choose to attach. We use that information to answer you and investigate the issue.

The current Contact support action opens an email draft addressed to support. Before you choose whether to send it, the draft shows technical context: app version, build number, platform, operating-system version, and device model. It does not attach your local mission state or action history. Nothing is sent unless you choose to send the email from your mail app. If no mail app opens, the game displays the support address and context on your device so you can copy them.

Operational error reports

If production code fails, the app may automatically send a compact operational error report to our own service logs. It can include the app platform and version, the current page path without its query string, the error name and message, and a shortened stack trace. Email-like text, detailed URL parameters, and long token-like values are redacted.

An operational error report does not include your save or action history, support email, or a device identifier. Reports are rate-limited and used only to diagnose reliability and security failures.

Optional connected services

The current player journey does not use accounts, purchases, or push notifications. Our retained operations service can support those features, but that capability does not mean the current game sends player data to it.

If optional connected services are introduced, we will explain the relevant collection before or when you enable them and update this policy. Depending on the feature, those services could use hosting and database providers, Resend for account email, Stripe or an app store for purchases, or Expo for push delivery. Sentry and Umami integrations are inert unless explicitly configured and enabled; the first-party operational error report described above remains the fallback when Sentry is not configured. If enabled, product telemetry accepts only allowlisted lifecycle fields; it does not upload your save, action history, email address, or a device identifier.

Retention and deletion

On-device game data remains until you use Settings → Clear game progress and saves, remove the app, or clear its browser or operating-system data. The current release does not create a player account, so there is no player account to delete.

We keep operational error logs and direct support correspondence only as long as reasonably needed to diagnose issues, respond, maintain a record, and protect the service. You can ask us about or request deletion of information you sent directly by emailing hello@endpaperlabs.com. If a future release introduces a connected account, its data and deletion controls will be explained before that feature collects player information.

Your choices

You can play without logging in or sharing your mission history. You decide whether to contact support, and you can remove local game data as described above. If an optional connected service is added, you can choose whether to use it unless it is necessary for the feature you request.

Changes and contact

We may update this policy as Firebreak Grove changes. We will revise the effective date on this page when we do. For privacy questions or requests, contact hello@endpaperlabs.com.