astervex-legal

Astervex Privacy Policy

Effective date: August 23, 2026

Astervex is developed and published by Dmitrii Kryzhanovskii. Beatroot Development is the project and brand name used for Astervex. This policy explains what data Astervex stores and how that data is used.

Contact: beat.root.dev@icloud.com

Data Astervex Stores

Astervex stores the following data to provide the game:

• Account data: Astervex profile ID, internal account identifiers, salted and hashed password verifier data, active session metadata, device name, and device/session identifiers used to sign in and prevent account conflicts across devices.
• Gameplay data: player profile, pilot nickname, selected character, high score, games played, balances, unlocked content, inventory, ship configuration, map progress, and related saved-game state.
• Purchase delivery data: StoreKit transaction identifiers, original transaction identifiers, product identifiers, crystal amount, purchase date, and delivery date. This is used to deliver in-app purchases and prevent duplicate delivery.
• Account deletion data: after an account is deleted, Astervex retains a minimal generation-specific deletion marker containing the profile ID, internal account/profile identifiers, deletion operation identifier, and deletion date. It does not contain gameplay progress, password verifier data, or active session data. Creating a new account with the same profile ID clears the current-name marker but does not remove markers for older internal profile generations.
• Feedback data: the message text and photos or videos selected by the user, plus the sender address when feedback is sent through a mail app. At the user’s choice, a report may also include the app version, device model, iOS version, language, and current game location. Account identifiers, nickname, and balances are not added to the user feedback report.

Astervex does not ask for a real name, phone number, precise location, contacts, camera, microphone, health data, or payment card details. An email address and selected attachments are shared only when the user chooses to send feedback.

How Data Is Collected and Stored

• For a standard account, the profile ID and password are entered by the user when creating or signing in. If the user chooses Play as Guest, Astervex creates or restores a full guest account in the user’s private CloudKit database and generates a cryptographically random password during creation. Astervex never stores either kind of password itself; it stores only a randomly salted password verifier derived from it. The generated guest password is not shown or persisted in plaintext.
• Gameplay data is created from the user’s actions and progress in the game.
• Device and session identifiers are generated by the app. The device name is provided by iOS and is used only to identify an active session to the user and resolve session conflicts.
• Purchase delivery data is received from Apple StoreKit when the user starts or restores an in-app purchase.
• Feedback data is provided voluntarily through the Feedback screen. Astervex does not request access to the entire photo library; it receives only photos or videos explicitly selected by the user.

Account and gameplay caches, settings, active authentication state, and pending purchase or deletion recovery state are stored locally in the app’s private storage. The app-generated device identifier is also stored in the iOS Keychain so sessions remain consistent across launches and reinstalls. Account, gameplay, purchase delivery, and deletion marker records are synced to the user’s private CloudKit database when iCloud is available.

How Astervex Uses Data

Astervex uses the stored data only for app functionality:

• creating and signing in to an Astervex game account;
• syncing saved-game progress with iCloud through Apple CloudKit;
• keeping one active account session consistent across devices;
• saving gameplay progress, balances, inventory, and unlocked content;
• delivering StoreKit in-app purchases and preventing duplicate crystal delivery.
• receiving bug reports, suggestions, and other messages from the user.

Astervex does not use this data for third-party advertising, developer advertising, data broker sharing, or cross-app tracking.

Data Sharing and Apple Services

Astervex does not sell user data and does not share it with advertising, analytics, or data broker services. App data is processed through Apple services required for its functionality: CloudKit for private iCloud storage and StoreKit/App Store for in-app purchases. Feedback is sent only after an explicit user action through the configured mail app or an app selected by the user in the system share sheet; the selected service’s terms then apply. Apple processes data under Apple’s privacy policies, service terms, and security protections.

iCloud and CloudKit

Astervex uses Apple CloudKit to store game account, gameplay, purchase delivery, and account deletion marker records in the user’s private iCloud database. This lets the same Astervex account and progress work across the user’s devices signed in to iCloud and prevents an old offline device from restoring a deleted account.

Data stored or processed by Apple services is also subject to Apple’s privacy policies and iCloud terms.

In-App Purchases

Astervex uses Apple’s StoreKit for in-app purchases. Apple processes payment and App Store transaction infrastructure. Astervex stores limited purchase delivery records, such as transaction identifiers and product identifiers, so purchased crystals can be delivered once and not duplicated.

Astervex does not store payment card numbers or other payment method details.

Account Deletion

The user can request deletion from the account management interface inside Astervex. No email or external website request is required.

When account deletion succeeds in the app while iCloud is available, Astervex deletes the app’s game account record, player profile record, known purchase delivery ledger records for that account, and local cached account/profile data from the device. Astervex retains the minimal deletion marker described above in the user’s private CloudKit database to prevent a stale copy of the account on another device from recreating the deleted account.

If iCloud or the network is temporarily unavailable, deletion does not report success and local account/profile data is preserved so the user can retry. If an interruption happens after deletion has started, Astervex keeps a local durable recovery operation and resumes the remaining cleanup when the backend is available.

Deleting an Astervex account does not delete App Store purchase history, StoreKit transaction records, iCloud backups, or other records controlled by Apple.

Data Retention and User Choices

• Account and gameplay records are retained while the Astervex account exists and are deleted as described above when account deletion completes.
• Purchase delivery records are retained while needed to deliver purchases and prevent duplicate delivery, and known records linked to the account are deleted when account deletion completes.
• Local recovery operations are retained only while needed to complete or recover a purchase delivery or account deletion and are removed after the operation is resolved.
• Generation-specific account deletion markers are retained in the user’s private CloudKit database to prevent delayed purchase delivery or stale devices from reviving an older internal profile. Recreating the same profile ID does not remove older generation markers.
• Received feedback messages and attachments are retained only as long as needed to respond, diagnose the issue, and maintain the related correspondence, unless longer retention is required by law.
• The app-generated device identifier is not account-specific and remains in the iOS Keychain after deleting an individual Astervex account. It is used only for session consistency and is not used for tracking. The user can request assistance concerning this identifier through the contact address above.

Astervex does not collect optional advertising or tracking data, so there is no advertising or tracking consent to revoke. A user can stop future account and gameplay collection by deleting the account and discontinuing use of the app. Questions or deletion assistance can be sent to the contact address above.

Children

Astervex is not designed to request personal contact information from children. If you believe a child has provided personal information through Astervex, contact beat.root.dev@icloud.com.

Changes

This policy may be updated when Astervex changes its data practices. The effective date above will be updated when the policy changes.