Last updated: October 11, 2026
Tales of Elatora collects the minimum data needed to run the game.
- Account info. Email address and password for authentication, handled through Supabase Auth. We also use your email for account related messages, such as a password reset. We do not see or store your password in plain text.
- Game data. Character progress, inventory, quests, stats, and equipment. This is stored server-side so your progress is saved across devices. The character or account name you choose may be shown to other players, for example in a leaderboard.
- Preferences. Local settings like volume levels, vibration toggle, and active character selection. These stay on your device.
- Purchase data. If you buy gems through the App Store or Google Play, our payment processor shares limited purchase information with us. See Purchases below.
- Analytics and crash reports. First-party gameplay analytics and crash diagnostics, collected through our own backend, no third-party analytics SDK. See Analytics and Crash Reports below.
- Support requests. If you email us or submit an in-game bug report, we collect what you send us, such as your description of the issue and, if you choose to include it, recent app diagnostics.
- No location data.
- No contacts or phone data.
- No advertising identifiers.
- No third-party analytics or advertising SDKs. Our diagnostics pipeline is first-party, see below.
- No third-party data sharing or sale, ever.
Your data is used to run the game, including saving your progress, authenticating your account, syncing between devices, processing purchases, and diagnosing bugs and crashes so we can keep improving the game. We don't sell, share, or monetize your data in any way.
Tales of Elatora offers optional in-app purchases of gems, our premium currency, through the Apple App Store and Google Play. These purchases are processed by RevenueCat, a third-party subscription and purchase management platform, not by us directly.
- We never see or store your payment card or billing details. Those are handled entirely by Apple or Google.
- RevenueCat receives your purchase and transaction information from the App Store or Google Play, such as the product purchased, price, and transaction ID, along with an internal account identifier we assign you. It does not receive your email address or password from us.
- RevenueCat may also collect a device identifier and other technical information to process purchases, as described in its own privacy policy at revenuecat.com/privacy.
- We keep a record of your purchases, such as what was bought and when, to grant your currency, support refund and restore requests, and meet our own accounting and legal obligations.
We collect a limited set of first-party analytics and crash data to understand how the game is used and to find and fix bugs. This is an ongoing part of how we operate the game, not only during testing.
- Device and app context. Device model, OS version, locale and language, app version and build number, and platform, Android or iOS.
- Session identifiers. A per-session identifier tying related events together. This is a random session ID, not an advertising identifier. It is tied to your account and is never sold or shared with anyone else.
- Gameplay and behavioral events. In-game actions and screens, such as what you interacted with and how a session progressed, so we can see where players get stuck or drop off.
- Crash reports. When the app crashes or hits an unexpected error, we collect the exception type, message, and stack trace, plus recent app log lines and the device and app context above, to help us reproduce and fix the issue. Log lines are automatically screened to remove email addresses, authentication tokens, and verification codes before they are attached to a report.
- Bug reports you submit. If you use the in-game "Report a Bug" feature, we collect the category and description you write, and, if you choose to include it, the diagnostics described above.
This data is stored in our own Supabase project, the same backend that stores your game data, not a third-party analytics vendor. It is used only to operate and improve the game and is not sold, shared with third parties, or used for advertising.
Retention. Crash reports are kept for up to 90 days and then deleted. Raw gameplay analytics events are kept for up to 14 days, or 7 days for simple screen views, and then deleted. We keep a small per-account summary, such as which days you played and milestones you reached, for as long as your account exists, and delete it when you delete your account, as described below. We may keep aggregated statistics that cannot be linked back to you, such as daily counts of how many players did something, indefinitely, to help us understand trends over time.
Game data, account data, and diagnostics are stored using cloud infrastructure provided by Supabase. Authentication is handled by Supabase Auth. All communication uses HTTPS.
You can delete your account and all associated data directly from the game. Go to Settings → Danger Zone → Delete Account and type DELETE to confirm.
Deleting your account permanently removes your account, all characters, all game data, and all analytics and crash diagnostics tied to your account from our servers.
Some records may be retained after deletion where we are required or permitted to keep them, such as purchase and transaction records needed for accounting, tax, fraud prevention, or App Store and Google Play compliance. RevenueCat also keeps its own copy of your purchase history under its own privacy policy. Deleting your Tales of Elatora account does not automatically delete RevenueCat's records, and you can contact us if you would like help requesting that separately.
You can ask us to access or delete your data at any time, or delete your account directly from Settings in the Game.
If we update this policy, we'll update the date at the top. Continued use of the game means you accept the updated policy.
Questions? Email us at talesofelatora@gmail.com.