STARFALL COLONY — PRIVACY POLICY
Effective 20 September 2026 · Version 7
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 Starfall Colony 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 Starfall Colony account or customer API. 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: colony resources, buildings, research, damage, defenses, missions, events, settings, save times, purchased-benefit state, and transaction IDs used to avoid delivering purchases twice. The protection timer counts active play using device time; elapsed system uptime helps maintain a local time reference. Expedition progress, journal discoveries, planet choices, weekly goals and cosmetic selection are also saved locally. Local cloud choices record the agreement version and date; they are not sent to us or synchronized by this game.
Audio and haptics: bundled music, completion sounds and vibration patterns run on the device. The game stores your sound and haptic preferences as settings. It does not stream these music files, record audio, use the microphone, or send listening/vibration activity to us. Technical audio-error messages may appear in local Apple system logs; the app does not upload them to a developer service.
With optional iCloud saving: an Apple-managed encrypted checkpoint is stored in this app’s private CloudKit database associated with your Apple Account, hosted by Apple. It contains colony progress and save time, generated game-account and save-revision identifiers, purchase transaction/product identifiers, remaining purchased supplies and protection, spending-operation records and refund markers. Legacy checkout tokens may remain in migrated grants for verification. It excludes payment-card details, Apple Account passwords and local consent records. Entitlements are verified with Apple rather than trusted from ownership flags in the checkpoint. We have no gameplay dashboard or developer server receiving these saves. Apple processes account, service and connection information to provide iCloud; private does not mean Apple cannot process data for its service.
Purchases: StoreKit provides product and verified transaction information, such as product and transaction identifiers and entitlement status, so the game can deliver content, prevent duplicate delivery and restore eligible purchases. Apple handles billing, purchase records and refund processing. Apple may provide developers with store sales/financial reports under its services; these are not in-game tracking.
Save and purchase safeguards: the app generates a persistent game-account UUID and separate installation/writer UUIDs. The game-account UUID is sent to Apple as an appAccountToken and follows the verified cloud colony across devices; it is not a login or advertising identifier. Local checkout records bind products and any required cloud account to delivery. Cloud checkpoints contain writer, colony, revision and parent-revision identifiers and time, including in deletion markers. Local storage records the CloudKit account identifier, known/pending revisions, unfinished transactions and pending supply operations so interrupted delivery can resume without duplicate rewards. TestFlight/sandbox, local StoreKit tests and production have separate saves and ledgers. Internal pre-conflict/deletion recovery copies contain progress and commerce history. Installation identity and recovery files are excluded from backup; ordinary saves and journals remain subject to Apple backup settings. Pending entries are removed after completion or reported cancellation; grant, revocation and applied-operation records remain to prevent replay.
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, purchase verification/delivery and spending safeguards are necessary to provide the game and purchased features you request (GDPR Article 6(1)(b), where applicable). Optional cloud storage of progress and commerce history uses your freely given, specific choice (Article 6(1)(a)); local play remains available if you decline. You may withdraw that choice in Settings at any time, without affecting processing lawfully performed before withdrawal. A privacy acknowledgement is not a waiver of rights.
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 remains until reset or removal of the installation, subject to Apple device-backup behavior. Reset preserves the local purchase ledger and permanent entitlements to prevent duplicate rewards, and preserves active protection and unredeemed purchased supplies. Apple may retain its purchase history under its own legal obligations and policy.
Cloud progress remains until you delete it using Settings → iCloud Save → Delete Cloud Save, available while iCloud saving is enabled, or Apple’s available storage controls. In-app deletion removes the progress payload but retains a revision/deletion marker with the identifiers and time described above to prevent automatic re-upload by stale devices. That marker remains until an explicit new save replaces it or Apple’s storage controls remove the app’s cloud data. Turning saving off alone does not delete existing cloud data. Deletion requires connectivity and reports failures; retained Apple backups and service records follow Apple’s policies. On-device recovery copies remain until a later conflict or deletion attempt replaces them, or the installation is removed; resetting progress does not erase these copies. Pending-delivery entries are removed after successful confirmation, while the on-device delivered-transaction ledger remains to prevent replay. We do not promise deletion of Apple’s separately controlled billing records.
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 hosts iCloud and operates payments; 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
Cloud checkpoints use private database access controls and Apple-managed encrypted CloudKit fields. Conditional revision checks prevent blind overwrite; purchase history must be verified with Apple before recovery grants benefits. Progress and delivery/operation journals stored on the device use atomic file writes and device data protection. No storage method is perfectly secure, and a client-side ledger does not guarantee prevention of tampering or concurrent offline use on compromised or disconnected devices.
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. Turning off cloud saving does not itself delete an existing cloud save; use the deletion controls 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. The generated game-account UUID is not a developer login account; there is no developer account to close. Applicable access and portability rights remain available as described above.
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 is limited to ages 16 and up in this version; no parental-verification system is implemented. 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 policy as a starting point and adapted to Starfall Colony’s actual features and practices.