TIC TAC TOE / ANDROID
Privacy policy
Effective date: [publication date]
Policy URL: [planned public URL]
Pending confirmation: legal operator and contact details; guest-account retention; logs and backups; SDKs, ads and purchases; audience and countries; deletion process; security and opponent access; website collection.
1. Who operates this game
Tic Tac Toe is an Android game operated by [your legal name] under the Voxxlate brand. Voxxlate is a brand name, not a registered company. In this policy, “we,” “us,” and “our” mean [your legal name].
Privacy contact: [working email address].
2. Offline play
You can play against the computer or with another person on the same device without an internet connection. These modes do not require online matchmaking.
[To confirm: whether moves, results, or settings are stored on the device; whether Firebase initializes or signs in during offline-mode use; and whether any SDK collects or later uploads information. Do not assume that offline play means no collection.]
3. Online play and information collected
Online matchmaking uses Google Firebase. Online players automatically receive an anonymous Firebase Authentication guest identity. You do not enter a name, email address, or password to play.
“Anonymous” means you do not provide those account details. It does not mean no information is collected. A guest identifier distinguishes your account and associates it with online activity.
The backend stores guest identifiers, matchmaking assignments, game moves and results, timestamps, and connection presence (whether a player is connected).
Firebase services also process technical information, such as IP addresses and information identifying the connecting software, for service operation and security. This is separate from the game records listed above.
[To confirm: additional SDK collection and the contents of application and server logs.]
4. Why information is used
Online information identifies guest players, matches opponents, synchronizes game state, processes moves and results, tracks connections, and supports removal of stale matchmaking entries and old game rooms.
[To confirm: any additional purposes, such as diagnostics or abuse prevention, if implemented.]
5. Service providers and data location
We use Google Firebase Authentication, Realtime Database, and Cloud Functions for online play. Google processes information needed to operate these services.
The game’s Realtime Database is hosted in us-central1, United States. This describes the game database location only; it does not establish that all authentication information, logs, or other service data are processed only there.
[To confirm: additional providers, relevant processing locations, and information accessible to opponents, including any advertising or purchase services.]
Firebase privacy and security information ↗6. How long information is kept
Waiting-room entries expire after approximately 90 seconds without refresh. [Confirm whether expiry also removes the stored entry and when.]
A scheduled job removes game rooms older than 24 hours in batches. This is not a guarantee of deletion at exactly 24 hours: removal depends on the job running and processing the room.
Guest-account retention: NOT YET VERIFIED. Server-log contents and retention: NOT YET VERIFIED. Backups, separate matchmaking records, other copies, and provider-held information: retention requires confirmation.
Game-room cleanup does not mean that all information associated with a player is deleted after 24 hours.
7. Deletion requests
Privacy and deletion enquiries can be sent to [working email address].
[Before publication: specify a working request process, how players obtain or submit their guest identifier, how ownership is verified, which records are deleted, response and completion times, and any retained information with its reason and retention period.]
Because players do not provide an email address to play, an email request alone may not identify the relevant guest account. Uninstalling the game should not be treated as a request to delete server-side information.
8. Security
[Before publication: describe verified safeguards, including secure transmission, database access restrictions, and administrative access controls. Do not claim measures that have not been checked.]
No method of transmitting or storing information can guarantee complete security.
9. Analytics, crash reporting, ads, and purchases
[Before publication: confirm which of these features are included and enabled at launch. For each service, describe its collection, purposes, provider, retention, and available choices. State that none are included only after verifying the release build.]
10. Children and intended audience
[Before publication: confirm intended ages, whether children are targeted, and distribution countries. Describe applicable age-related collection practices and safeguards based on the actual implementation.]
11. Website information
This draft describes the Android game. Visiting the Voxxlate website may involve separate information processing.
[Before publication: explain website theme/language preference storage, Google Fonts requests, hosting logs, and other collection here or link to a separate website privacy notice. Hosting behaviour still requires confirmation.]
12. Changes and contact
We may update this policy as the game or its information practices change. The revised policy will appear at [planned public URL] with an updated effective date.
For privacy questions: [your legal name], operator of Tic Tac Toe under the Voxxlate brand. Email: [working email address].