AI EMPIRE - PRIVACY POLICY
Effective 20 September 2026 · Version 4
1. About this policy and who is responsible
rstdwoo, Romania, is responsible for the app's processing described here. Contact mariusmuntensky@gmail.com for privacy questions and rights requests. This policy explains how information is used in the AI Empire iOS game and when you contact us for support. "We" means rstdwoo; "you" means the player or person contacting us. Personal information means information relating to an identified or identifiable person. There is no separate AI Empire account, mandatory app login or developer-operated gameplay server. Apple separately operates your Apple Account, iCloud and App Store under its own privacy terms. This notice describes our practices; merely playing the game does not give blanket consent to new processing or waive your privacy rights.
2. Cookies, automatic collection and tracking
This version has no advertising, analytics SDK, cross-app tracking, location collection, social account, chat, or developer-operated gameplay server. We do not sell personal information, share it for cross-context behavioral advertising, profile users for marketing, or make decisions with legal or similarly significant effects about them. We do not receive your payment card details or Apple Account password. The native game does not use website cookies, advertising identifiers, browser fingerprinting or clickstream analytics. It uses local app storage to remember progress and preferences. It does not collect browsing history or IP addresses for a developer analytics service. Apple and Google may process connection and device information when you use their services under their respective policies. Browser Do Not Track and Global Privacy Control signals do not change the game’s behavior because it does not perform cross-site tracking, sell personal information or share it for targeted advertising. External websites opened from links have their own cookie and privacy practices.
3. Information categories, sources and purposes
On your device: fictional Credits, Compute, Research Points and Quantum Cores; machines and infrastructure; locations, managers, training and assignments; research and contracts; offline reward claims; Technological Breakthrough progress and lifetime records; daily missions, calendar claims and achievements; settings, save times and completion notices. Purchase-related records can include product and transaction identifiers, saved-game identifiers, entitlement state, inventory and delivery/spending records used to avoid duplicate rewards. Device time and elapsed active time support production, timers and daily availability. Records stay local unless you enable optional iCloud saving; the game has no developer-operated server receiving them.
Legal choices: Settings stores a separate acceptance record for each document, containing its identifier, version, content fingerprint and acceptance date. These records remain in local app preferences, outside the game save. A fingerprint identifies the document text, not your device or identity. Opening or closing a document does not accept it; accepting one does not accept the other. Acceptance is not tracking consent or permission to start cloud saving. Updated document content requires fresh acceptance. Local play is available without accepting these optional cloud prerequisites.
Audio: bundled music and completion sounds run on the device. The game stores separate music and sound preferences. It does not stream these music files, record audio, use the microphone or send listening activity to us. Technical error messages may appear in local Apple system logs; the app does not upload them to a developer service.
Optional iCloud saving: after your explicit opt-in, the game stores a complete progression checkpoint in your private CloudKit database, hosted by Apple. The encrypted payload includes balances, machine/research/location/manager/contract progress, offline rewards, prestige and daily records, remaining inventory, purchase delivery and spending records, a saved-game ID, random installation writer ID, revision/parent identifiers and a save date. Saved entitlement flags are historical game data, not proof of current purchase ownership. Agreement records, cloud consent, age confirmation and local audio/display preferences are not included in the cloud game. There is no user-facing encrypted export/import feature. Apple's device backups are separate and follow your device/account settings.
The random installation ID identifies a game installation, not device hardware or a person, and is not used for tracking or advertising. Its local file is excluded from device backup; a fresh installation generates a new ID. On loading an existing cloud game, the new installation claims the save with its own ID and a new revision. CloudKit change tags prevent overwriting a concurrently changed record. An app-scoped iCloud user-record identifier is retained locally to detect account changes; we do not obtain your Apple Account email or password. Apple necessarily processes account, service and connection information to provide iCloud.
Cloud save attempts occur at game start, every 30 minutes while active, on manual request and after purchase delivery. When cloud saving is enabled, checkout checks cloud ownership before requesting payment and delivery checks it again. Network or ownership failures preserve local data and stop checkout/delivery from completing until resolved. Conflicting saves are not merged automatically; local recovery files preserve both snapshots before a confirmed replacement. Availability depends on the build's CloudKit configuration and Apple's services. Development StoreKit sessions do not upload their simulated purchases to the normal cloud save.
Purchases: optional real-money purchases in the App Store game are processed by Apple. Xcode and App Store sandbox testing, including TestFlight, do not charge real money. StoreKit provides product and verified transaction information, such as product and transaction identifiers, saved-game purchase tokens, environment and revocation status, to deliver content, prevent duplicate delivery and restore eligible permanent purchases. The app requests finished consumable history to verify saved purchase records and reconcile refunds; reading that history does not regrant consumed items. Pending Core-spend records stay in the local app container until the saved operation is recovered. Apple handles billing, purchase records and refund processing. Restore Purchases does not recreate remaining consumable balances; those belong to the saved game. Apple may provide developers with store sales/financial reports under its services; these are not in-game tracking. We do not receive payment-card details or your Apple Account password.
Test environments: Sandbox/TestFlight and production games use separate local save directories, preferences, recovery files and CloudKit records. The sandbox can use Apple's Production CloudKit service, but cannot write the real-money game's record. Xcode-local testing has no real cloud store. A test game is not transferred automatically into a production game. Each environment has its own optional cloud consent. The Starter skin's equip preference is local; purchase ownership remains in the saved game.
If you email us: we receive your email address, any sender name, message content, attachments and correspondence metadata supplied with your email. You are the source of this support information; gameplay information comes from your actions and the device, and purchase verification comes from Apple. Avoid sending passwords, payment-card details, sensitive information or information about children. Apple and your device may separately process diagnostics according to your OS and account choices; the game does not include its own telemetry SDK.
4. Purposes and EU/EEA legal bases
Local progress, requested features and purchase delivery are necessary to provide the game and features you request (GDPR Article 6(1)(b), where applicable). Local legal records document your explicit choices. Optional cloud storage uses a separate freely given, specific choice (Article 6(1)(a), where applicable); local play remains available if you decline. Withdraw this choice by turning iCloud Save off in Settings. Withdrawal does not affect processing lawfully performed before it, and an already sent request may finish. Accepting a privacy notice is an acknowledgement, not a waiver of rights or blanket consent.
Support correspondence is used to answer your request and troubleshoot (contractual necessity where applicable; otherwise legitimate interests in responding to users). We may retain records required by law (Article 6(1)(c)). Apple determines its own legal bases for account, store and platform processing. We do not seek consent for tracking because this version does not track you.
5. How long information is kept and how to delete it
Local game data and legal preferences remain while the installation retains them, subject to Apple's device-backup and restoration behavior. Removing the installation removes its local app data, but separate device backups may remain under your control. Technological Breakthrough is a gameplay reset, not a personal-data deletion request: it retains lifetime records, managers, legal preferences and purchase-related records as described in the Terms of Use. This build has no separate in-app erase-all-data control. Apple may retain purchase history under its own legal obligations and policies.
Cloud progress remains until replaced or removed using Settings > iCloud Save > Delete Cloud Save, subject to Apple's service behavior. Turning sync off alone does not delete an existing cloud copy. Deletion clears the saved-game payload and leaves an empty marker and CloudKit system metadata for conflict detection; it stops syncing and keeps local progress. Deletion requires connectivity and unchanged ownership, and failures are reported. Another installation can upload a new save following an explicit choice. Local conflict recovery copies remain in the app's storage until that app data is removed; they are not uploaded as a separate cloud archive. Apple backups and independently controlled billing records follow Apple's policies, and we cannot promise to delete them through game controls.
We use Gmail at mariusmuntensky@gmail.com for support. We delete support emails from our mailbox immediately once the case is resolved. This describes our mailbox deletion practice; any copies retained by Google in its systems follow Google's applicable retention policies. Contact us for help exercising applicable access or portability rights for information we hold; we will explain device and Apple controls for information stored only there.
6. Recipients, external services and international transfers
Apple operates the App Store, device services and optional private iCloud game storage; Google provides Gmail for support messages you send. We do not disclose game saves to advertising brokers. Data may be processed outside your country through Apple or email services. We do not claim that all data stays in the EU. Google's published transfer information describes adequacy decisions, its EU-US Data Privacy Framework participation and standard contractual clauses where required. Apple's published privacy information describes its international processing and applicable transfer safeguards, including standard contractual clauses. These are the providers' published arrangements, not a claim that rstdwoo holds a Data Privacy Framework certification or has a separately negotiated Google Workspace agreement. Links to their privacy, retention and transfer information appear below; contact us for help obtaining relevant information about safeguards. We do not share information with advertising partners or corporate affiliates for marketing. We disclose information we hold only to the providers described here, recipients you choose, or where required by applicable law. If the game changes ownership and information we hold needs to transfer, we will give any required notice and apply applicable legal safeguards; a transfer is not permission for unrelated new uses.
7. Security
Ordinary local autosaves, recovery files and preferences rely on app sandboxing and device protections. Save validation and a local backup help handle damaged or unsupported progress; they do not guarantee recovery or prevent replay of an older valid save. Cloud checkpoints use CKRecord encrypted fields in the private database: CloudKit encrypts values on the device before uploading and decrypts them after fetching. Apple manages the keys; we do not implement a custom key service or export encryption. With Advanced Data Protection, eligible encrypted CloudKit content has additional end-to-end protection; this is not a claim that all service metadata is end-to-end encrypted or that Apple processes no service data. No storage method is guaranteed perfectly secure, including on a compromised device.
8. EU/EEA privacy rights and requests
Subject to applicable law, you may request access and a copy of personal information, correction, deletion, restriction and portability. You may object to processing based on legitimate interests. You may withdraw optional cloud consent in Settings without losing local play or affecting the lawfulness of earlier processing. Stopping sync and deleting stored cloud data are separate choices, as described above.
Email mariusmuntensky@gmail.com to exercise a right. Describe your request and the information involved; do not send passwords, full payment-card details or unnecessary identity documents. We may request only information reasonably necessary to verify your identity and locate the information. We normally respond within one month under GDPR. Where a lawful extension is necessary, we will explain the reason and timing within the initial period. If we cannot fulfil a request, we will explain why and the available complaint options. We do not make solely automated decisions with legal or similarly significant effects on you.
We can help with information we actually hold, such as unresolved support correspondence, and explain device and Apple controls for data stored there. We cannot retrieve already-deleted correspondence or a game save that has been lost from all available copies. There is no developer account to close.
You may complain to a competent EU/EEA supervisory authority, including the authority in your habitual residence, place of work or the place of an alleged infringement. In Romania this is ANSPDCP: https://www.dataprotection.ro/. You do not have to contact us first to exercise that right.
9. California and other US state privacy rights
Where applicable state law grants these rights, you may request to know/access the categories and specific pieces of personal information, obtain a portable copy, correct inaccurate information, or request deletion, subject to lawful exceptions. The categories, sources, purposes, recipients and retention practices are described in sections 3–6. We do not sell personal information, share it for cross-context behavioral advertising, use it for targeted advertising, or conduct profiling that produces legal or similarly significant effects. We do not use sensitive personal information to infer characteristics about you. We do not offer financial incentives in exchange for personal information.
Send requests to mariusmuntensky@gmail.com. An authorized agent may contact us with evidence of authority; we may need appropriate verification of the request or authorization. We will not unlawfully discriminate against you for exercising privacy rights. We respond within the deadline required by the applicable law; for covered California access, correction and deletion requests this is generally 45 days, with notice of any legally permitted extension. Where a state law provides an appeal, reply to our decision at the same email address stating that you wish to appeal; we will review the decision, explain the outcome within the applicable deadline and provide the relevant regulator’s complaint route when required.
US state statutes have different eligibility rules and exceptions; this policy does not claim that every statute applies to this business. You can contact us about your information regardless of your location. There is no sale or targeted-advertising activity to opt out of in this version. Mandatory privacy rights and access to competent regulators or courts are not restricted by this notice.
10. Children and teenagers
This game is intended for ages 13 and up, not children under 13. Optional cloud saving requires a local confirmation that you are 16 or older. We do not request your date of birth or implement a parental-verification system. We do not knowingly solicit personal information from children under 13. If you believe a child has sent us information, contact us so we can investigate and delete information we control where appropriate. Parents should use Apple's family purchase and device controls. An age confirmation is not a verified parental-consent process.
11. Changes and contact
The policy is always available in Settings, with its effective date and version at the top. We will give notice of material changes through the game before new processing begins, and request fresh consent where required. A new material cloud-processing purpose will require a new cloud choice before it starts. Continued play alone is not consent to such a purpose. Local play remains available if you decline optional cloud processing. Questions or requests: mariusmuntensky@gmail.com — rstdwoo, Romania.
[Apple privacy information](https://www.apple.com/legal/privacy/)
[Apple iCloud information](https://www.apple.com/legal/internet-services/icloud/)
[Google privacy information](https://policies.google.com/privacy)
[Google retention information](https://policies.google.com/technologies/retention)
[Google transfer information](https://policies.google.com/privacy/frameworks)
Prepared using the supplied Termify-based policy as a starting point and adapted to AI Empire's current features and practices.