Donut Circuit Privacy Policy — Draft
Scope and developer
Althea Group Co., Ltd. develops and operates Donut Circuit. This draft covers the iOS and Android game. It describes reviewed implementation and separately identifies services awaiting release verification. Website visits are covered by the website privacy policy.
Local gameplay data
Core gameplay works offline. Device storage includes progression, coins, boosters, preferences, local account metadata, save backups and recovery journals. Unity PlayerPrefs is used by the storage layer. Removing app data may permanently lose progress; do not uninstall to troubleshoot. Device or operating-system backups may hold separate copies.
Firebase identity and security
The implementation can automatically establish an anonymous Firebase Authentication identity and use Firebase App Check when the build configuration permits, before a visible login or advertising consent prompt. Firebase assigns an account identifier (UID); the SDK persists credentials. App Check uses Apple App Attest or Google Play Integrity for eligible device builds. Do not interpret guest play as a promise of no network transmission.
Linked accounts and cloud saves — release verification pending
Google and Apple credential-linking adapters and Firestore cloud-save code exist. This does not establish that player-facing linking, recovery or cloud synchronization is operational. Live cloud access is gated. When enabled, cloud records would associate save content, revisions and synchronization metadata with an account identifier. The approved release must confirm exactly which features operate before this policy takes effect.
Purchases and RevenueCat
RevenueCat integration can initialize on supported configured builds even while purchase actions are disabled. Its customer identity is designed to use the Firebase UID. Automatic device identifier collection is explicitly disabled in the adapter; that is not a promise that the SDK sends no technical data. Purchase handling includes store transactions, customer information and entitlements. Apple or Google and RevenueCat may process purchase records when these services operate. Live purchases and restoration require release verification. This draft does not assert that paid subscriptions are offered.
Advertisements and choices
Google Mobile Ads code supports rewarded and interstitial advertisements, with Google UMP consent handling and separate iOS App Tracking Transparency controls. Test-ad operation does not establish production activation or production reward delivery. If enabled, advertising services may process advertising identifiers, device and ad-interaction data subject to configuration, permissions and consent. Use Ad Privacy Choices where available and your device privacy controls. Declining tracking does not itself remove all advertisements. Final SDK data categories and pre-consent traffic remain under review.
Analytics, diagnostics and testing
Reviewed gameplay analytics has local/test sinks and a future remote adapter seam; Firebase Analytics and Crashlytics integration is planned for later compliance work, not established as active here. Unity Analytics and cloud crash reporting are disabled in project settings, while an engine diagnostics flag remains enabled. Actual packaged-build traffic and SDK defaults still need verification. Application logs contain diagnostic state information. Apple may process TestFlight usage, crash and feedback data during testing under its own terms.
Purposes and recipients
Local data supports gameplay and save integrity. Configured identity/security services support account identity and abuse prevention; enabled purchase, advertising and cloud services would support their described functions. Support email is used to investigate and answer requests. Relevant recipients include Google/Firebase, Apple, RevenueCat and the support email provider when used. Final provider inventory, processing locations and contractual safeguards require confirmation.
Retention and deletion
Local records remain while retained on the device or in backups. No fixed off-device retention period has been approved. Account deletion and backend cleanup are not yet verified as operational. You can request account or data deletion by email; sending a request does not delete anything automatically. Ownership must be verified. We cannot remotely erase device-only saves or copies held in your own backups. Store transaction records may remain with Apple, Google or other providers under their own obligations. Any retained records, reason and duration must be established before approval.
Children’s privacy
The intended age audience and any parental-consent or child-directed service configuration require owner/legal review. Do not send children’s personal details unnecessarily. Contact support if you believe a child’s information has been provided. This draft makes no unverified minimum-age or child-safety certification claim.
Security, international processing and rights
No storage or transmission method is completely secure. Services may process information outside your country; destinations and safeguards require review. Depending on applicable law, you may have access, correction, deletion, restriction, objection, portability or complaint rights. Contact support to exercise applicable rights; proportionate verification may be needed. No jurisdiction, legal basis or response deadline is asserted without review.
Internal review markers and updates
REVIEW P1: verify release SDK traffic, identifiers and activation. REVIEW P2: confirm audience, providers, retention, international safeguards and applicable rights/legal bases. REVIEW P3: qualify identity verification and deletion before adopting this policy. These are unresolved draft items. An approved policy will include an effective date; changes will be reflected here.
Contact
Privacy inquiries: support@altheagroup.net. Include only information necessary for your request; never send passwords or authentication tokens.