Game progress and preferences are stored on the device by default. Data is sent to Google or Firebase only when the relevant account, purchase, restore, or advertising feature is used.
1. Scope and operator
This policy applies to Danta Championship, also published in Korean as 천하제일 단타대회, an Android game operated by Binarytech. All stocks, prices, and returns in the game are fictional. The game does not provide real trading, investment advice, cash rewards, withdrawal, exchange, or cash-out.
- Operator: Binarytech (바이너리테크)
- App: Danta Championship (천하제일 단타대회)
- Android package: com.binarytech.dantagame
- Privacy contact: binarytech804@gmail.com
Linking a Google account is optional. It is used for the server-side diamond wallet, paid cosmetics, purchase verification and restoration, and account deletion. Local game progress is not uploaded to the linked account.
2. Data processing summary
| Data | Purpose | Location / processor | Disclosure | Retention and deletion |
|---|---|---|---|---|
| Game progress, recent results, free achievements and cosmetics, preferences, local profile ID | Gameplay, state recovery, and preferences | App-private storage on the device | Not transmitted off the device | Deleted when app data is cleared or the app is removed; up to 20 recent results |
| Google email address, Firebase UID, short-lived authentication token, IP address, user-agent and device metadata, and App Check integrity token | Optional sign-in, account management, security, and abuse prevention | Google Account and Firebase Authentication | Processed by Google to provide the service; not sold | Account data is deleted on account deletion; limited security logs and backups follow Google's retention rules |
| Firebase UID, diamond balance, debt and revision, paid cosmetics, spend operation records | Server-authoritative wallet, state recovery, and prevention of duplicate use | Cloud Firestore and Cloud Functions | Processed by Google as a service provider; not sold | Deleted with the account, except the minimum records required for refunds, fraud prevention, security, or legal obligations |
| Product ID, purchase-token identifier, purchase, consumption and acknowledgement state, restore, refund, and void records | Diamond delivery, ad-removal entitlement checks, purchase verification and restoration, refund and duplicate-credit prevention | Google Play Billing, Google Play Developer API, and Firebase backend | Processed by Google for payment and verification; not sold | Raw tokens are processed temporarily; the server uses a hashed token key. Minimum integrity records are retained while their stated purpose or a legal obligation continues |
| UMP consent choice, IP address, app interactions, diagnostics, advertising ID, app set ID, and applicable device/account identifiers | Ad delivery and measurement, consent management, fraud prevention, and SDK reliability | Google Mobile Ads (AdMob) and User Messaging Platform | Shared with Google to provide advertising; not sold by Binarytech | Subject to Google advertising rules and the user's consent and Android advertising settings |
| Result card, result text, and challenge code | User-initiated sharing | Created on-device and passed to the Android Sharesheet | Sent only to the app chosen by the user | Not stored on Binarytech servers; the chosen app's policy applies after transfer |
| Support email address, message, and attachments provided by the user | Support and response | Email providers | Processed by email providers for delivery | Retained only as needed to resolve the request and meet related obligations |
3. Google sign-in, Firebase wallet, and Google Play purchases
Attendance rewards use the account and campaign identifiers, reward dates, claimed-day count, grant times, diamond amounts, and wallet revisions. Cloud Firestore and Cloud Functions process these records to check daily rewards using Korea Standard Time and prevent duplicate grants. Attendance history is retained while account features are provided and deleted together with the wallet during account deletion.
When a user chooses Google sign-in, Google Sign-In and Firebase Authentication process the Google email address, Firebase UID, authentication tokens, IP address, user-agent strings, Firebase Android App ID, and Firebase user-agent device metadata. Firebase App Check may process Play Integrity attestation material and App Check tokens to verify app and request integrity and prevent abuse. Binarytech does not receive or store the user's Google password. Identifiers, full email addresses, and tokens are excluded from normal diagnostic output.
The account-linked wallet stores the Firebase UID, diamond balance, adjustment debt, state revision, paid cosmetic ownership, and spend-operation details. The backend is authoritative and uses account-generation checks, revisions, and idempotent operation IDs to prevent duplicate credit, duplicate spending, and stale-account access.
Google Play Billing provides four diamond packs and a one-time Remove Ads purchase. Remove Ads cannot be purchased with diamonds. Once a valid entitlement is verified, banner, end-of-game, and retry ads are not shown. Paid cosmetics are purchased with server-authoritative diamonds rather than directly with cash. Purchase processing may use the package name, product and purchase-option IDs, purchase token, purchase state, consumption and acknowledgement state, completion time, and an obfuscated account binding.
The raw purchase token is used only as needed for Google Play verification. The server stores a SHA-256 token key instead of the raw token. Binarytech does not receive card numbers, payment passwords, or other Google Play payment credentials.
Firebase states that authentication IP logs may be retained for a few weeks. Other authentication information is retained until the developer initiates deletion of the user, after which removal from live and backup systems may take up to 180 days under Firebase's published policy.
4. Advertising and UMP consent
The app uses Google Mobile Ads (AdMob) for banner ads on the Home and Library screens and interstitial ads when returning to Home after a normal result or starting another round. End-of-game ads are limited using a threshold of two normal rounds or four one-minute rounds; actual display depends on ad availability and consent. These ads are not shown once a valid Remove Ads entitlement is verified. The app does not use rewarded ads or app-open ads.
The Google Mobile Ads SDK may automatically collect and share IP address, app launches, taps and ad interactions, app and SDK diagnostics, Android advertising ID, app set ID, and other applicable device/account identifiers for advertising, measurement, analytics, and fraud prevention. Google states that this data is encrypted in transit with TLS.
Where required, Google's User Messaging Platform presents consent and privacy options. Ad personalization or limited ads depend on applicable law, the user's consent state, and Google settings. Users can reset or delete the Android advertising ID through Android settings.
The app does not use Firebase Analytics or Firebase Crashlytics. This does not exclude interaction and diagnostic data processed by the Google Mobile Ads SDK for its own stated purposes.
6. Retention and deletion
- Local data: retained until app data is cleared or the app is removed. Recent results are limited to 20.
- Firebase account and wallet: retained while the connected account is active and deleted when account deletion is requested.
- Attendance and Remove Ads: reward history and account-linked ad-removal entitlements and processing records are retained while account features are provided and removed during account deletion. Google Play maintains its own purchase records separately.
- Purchase integrity: duplicate-notification records are cleared on a 30-day basis. Minimum hashed purchase, refund, void, fraud-prevention, and security records may remain until their purpose or a legal obligation ends.
- Advertising: governed by Google policy and the user's consent and advertising-ID controls.
- Support email: retained only as needed for the inquiry and related obligations.
Delete an app account through Settings → Account & Purchases → Delete Account, or use the public account and data deletion page without signing in. To delete local progress, clear Danta Championship's storage in Android settings or uninstall the app.
Signing out, temporarily disabling access, and deleting an account are different actions. Account deletion removes account-linked data. Minimum records may be segregated and retained only when required for refunds, security, fraud prevention, or legal compliance. Account deletion does not automatically refund a Google Play purchase.
7. Security measures
- HTTPS/TLS for Google, Firebase, Google Play, and AdMob communications
- Android app-private storage and exclusion of local progress from standard Android cloud backup and device transfer
- Restricted Firebase client access, account-scoped permissions, and server-authoritative wallet and purchase verification
- Revisions, idempotent operation IDs, and account-generation checks for stale or duplicate requests
- Hashed purchase-token identifiers and redaction of UIDs, email addresses, and tokens from normal logs and UI
- Operational access restricted to the people and scope needed to provide and support the service
8. Audience, website, updates, and contact
The game is intended for a general audience aged 13 and over and is not designed for children under 13. Where parental consent or another requirement applies, Binarytech follows applicable law and Google Play policy.
The official website is a static GitHub Pages site. It does not use its own contact form, advertising, external analytics, or tracking cookies. Material changes to data practices will be reflected by updating this page's date and providing an appropriate notice in the app or on the official website.
For privacy questions or deletion requests, email binarytech804@gmail.com. Do not send passwords, two-factor codes, recovery codes, card details, identity documents, or purchase tokens.