Last updated: 5 October 2026
Avsitory is a single-player game for iPhone and iPad published by Arsenii Dorogin, based in Spain ("we", "us"). This policy explains how the iOS app handles data, including during its public TestFlight beta. Contact us at support@avsidev.com for privacy questions or requests. Our website is https://avsidev.com.
Data we handle
- On your device: game saves, game progress, language preference and your telemetry choices. These are stored locally. The app does not require an account.
- Optional usage analytics: if you enable usage analytics, Google Firebase Analytics may collect app interactions (such as screens opened, missions completed, research, and building actions), app-instance identifiers, device and operating-system information, app version, approximate location inferred by Google, and usage statistics. Our custom events do not send save names, map coordinates, inventory contents or text entered by you.
- Optional crash and error diagnostics: With your separate consent, Firebase Crashlytics may receive crash reports, stack traces, technical error codes and descriptions, installation identifiers, device and operating-system information, and app version. We do not add our own logs of missions, research, building actions or session duration. When usage analytics is also enabled, the Firebase SDK may attach Analytics event breadcrumbs to crash reports. We use these reports to investigate defects and improve stability. It does not read your save files.
- Messages you send us: if you contact support or submit feedback, we process the contact details and message you provide to reply and investigate your report. Please do not include passwords or payment details.
The app does not request access to your camera, microphone, contacts or precise device location. We do not currently use these services for advertising or sell your data. Playing the game does not require enabling either usage analytics or crash reporting.
Game Center
The app initializes Apple Game Center automatically when the main menu opens. If you are signed in, it sends campaign achievement progress to Apple, linked to your Game Center profile. If sign-in is needed, Apple may show its sign-in screen. You can decline sign-in and keep playing. The app stores your game-specific player identifier and pending achievement progress locally to retry delivery. Saves are not uploaded or synchronized. Signing out of Game Center in the device settings stops new submissions; requests already sent may finish. Achievements already held by Apple are not erased. Manage your account and privacy in the device’s Game Center settings.
Why and on what basis
We process local game data to provide the game you choose to use. Sending optional usage analytics and crash/error reports to Google is based on your separate consent for each purpose. We use analytics to improve the game and diagnostics to investigate defects and improve stability. We process support messages to respond to your request and, where applicable, fulfil legal obligations. The basis for handling a support message depends on its purpose, such as steps requested by you in connection with the game or a legitimate interest in responding to general enquiries. If you are in the European Economic Area, these bases are governed by the GDPR. You can withdraw either telemetry consent in the app without losing access to the game.
Your choices about analytics and crash reporting
Both choices are off by default on a fresh installation. At first launch, the app presents two independent switches and a way to continue without sharing. You can change your choices at any time in Settings → Analytics / Error reports. Existing analytics choices are preserved when upgrading; old builds' automatic Crashlytics setting is not treated as consent.
Turning analytics off stops future analytics collection on that device, clears local analytics data and resets its app-instance ID. Crash reporting starts from the next app launch after you enable it. Turning it off stops new submissions and our custom error recording; a request already submitted may complete. Reports from a session in which crash reporting was declined or revoked are not submitted later just because you enable reporting again.
Crashlytics automatic report uploads stay disabled. The SDK can still cache technical crash data locally; eligible reports from a previously consented session are submitted only while crash-reporting consent is still enabled. Ineligible pending reports are discarded through the SDK. Enabling an option does not release reports from sessions before consent.
Changing a choice does not automatically delete data Google has already received. For questions or deletion requests, email support@avsidev.com.
Earlier TestFlight builds may have collected usage analytics and crash/error diagnostics before these choices were introduced. If you used one of those builds and want to ask about that data, contact us at the address above.
Service providers and transfers
We use Google Firebase Analytics and Firebase Crashlytics as service providers. Their processing may occur outside Spain or the European Economic Area, subject to Google's applicable data-processing terms and transfer safeguards. For details about Google's Firebase processing, see Firebase privacy and security. Apple may process TestFlight distribution, downloads, device backups or feedback under Apple's own terms and privacy notices; those activities are separate from our in-app Firebase collection.
Retention and deletion
Local saves remain on your device until you delete a save or uninstall the app. Device backups may follow your Apple backup settings. According to Google's current documentation, the removal process for Crashlytics data begins after 90 days. Our current Google Analytics property settings retain event-level data for 2 months and user-level data for 14 months; the user-level period resets when that user has new activity. These settings do not govern the lifespan of most standard aggregated reports. We keep support messages for as long as needed to resolve the request and meet applicable legal obligations, then delete them. We will update this page if these settings or practices change.
Your rights
Where applicable, you may request access, correction, deletion, restriction, portability or object to processing, and withdraw analytics or crash-reporting consent at any time without affecting the lawfulness of earlier processing. Some diagnostic data may not be directly attributable to you; we will explain any technical limitation when responding. Contact support@avsidev.com. You may also complain to the Spanish Data Protection Agency (AEPD) or your local supervisory authority.
Children
Avsitory is not specifically directed at children. The App Store age rating is determined through Apple's age-rating questionnaire; we do not set a separate age threshold in this policy. If you believe a child has provided us personal information through support, contact us.
Changes
We may update this policy as the game develops, including if we introduce a new monetization feature. We will publish the revised date here and provide any additional notice or choice required by law before materially changing data use. This policy covers the iOS app; the website hosting this page may require a separate notice for its own hosting logs, cookies or analytics.