Privacy Policy
Effective date: October 31, 2026
This Privacy Policy describes how Strayward ("we", "the app") handles your information when you play the game. We aim to collect the minimum data required to operate the service.
What we collect
Local storage (Hive, on your device)
- Your save lives in Hive on the device and is the source of truth while you play. If a cloud upload or download fails, local progress is not rolled back.
- Device-only preferences (not mirrored): selected character, mute setting, run counter for interstitial cadence.
- Progress also stored locally (and mirrored on mobile — see below): coin balance, consumable item counts, equipment instances, Boss entry ticket count, crystals, best depth reached, unlocked characters, and owned / equipped cosmetics.
Progress mirror (Cloud Firestore — profiles/{uid})
- On supported mobile builds, after local wallet or inventory changes the
app uploads a full snapshot to Firestore at
profiles/{uid}and reconciles once at launch (newer snapshot wins; ties merge wallet totals then upload). - Keyed to the same anonymous Firebase Auth id used for leaderboard and Creative challenges, unless you link Google or Apple in Settings — then that account id is used so you can restore on another device.
- Snapshot fields: coin balance, consumable counts, equipment instances, Boss entry tickets, crystals, best depth, unlocked characters, owned / equipped cosmetics, and a last-updated timestamp.
- Purpose: cross-device restore only. This mirror is not shown to other players and is not an anti-cheat or audit log. Web play does not use this collection.
- We do not collect your name or email in this document unless you choose to link a sign-in provider (Google / Apple handle progress restore only).
Anonymous analytics (Firebase Analytics + Crashlytics)
- Aggregated, non-personal events such as session start, run end, milestone reached, ad shown, purchase attempted.
- Crash reports that include stack traces and device model / OS version.
- We do not collect your name, email, or location.
Leaderboard (Cloud Firestore)
- An anonymous device id generated by Firebase Anonymous Auth.
- The display name you choose (free-text, up to 24 characters).
- Your best depth, coins earned, and character used per run.
- This data is stored server-side so other players can see it on the leaderboard. It is not linked to your name or email.
Creative challenges (Cloud Firestore)
- Optional published challenge configs: title (≤24 characters), layout seed, threat id, Door on/off, start depth, and the anonymous author device id.
- Other players can browse and play published challenges. Share codes can also be copied locally without uploading. Challenge configs do not include chat, images, or free-form messages.
Advertising (Google Mobile Ads / AdMob)
- AdMob may use a device advertising id to serve relevant ads. Reset it from your device's privacy settings at any time.
In-app purchases (RevenueCat)
- An anonymous RevenueCat id links your purchase to your device. We do not see your payment details — those are processed by Apple / Google.
Third-party services
- Firebase (Google LLC) — analytics, crash reporting, leaderboard, Creative
challenge backend, and optional mobile progress mirror (
profiles/{uid}). - Google Mobile Ads (Google LLC) — advertising.
- RevenueCat — purchase entitlement management.
Children's privacy
The app does not knowingly collect personal information from children under 13. The app is suitable for ages 10+ but does not request age.
Your rights
- Email [email protected] to request deletion of your anonymous
leaderboard entries, your
profiles/{uid}progress mirror, and any Creative challenges you published. We will remove rows keyed to your Firebase Auth uid (anonymous or linked account).
Changes
We will update this page if our practices change. Continued use after a change constitutes acceptance.