Effective and last updated:
1. Who is responsible
CyberWiz operates these services from Yucaipa, California, United States. Send privacy and legal requests to [email protected]. This policy includes the Android app with package identifier io.cyberwiz.adminer.
2. Information we process
| Information | How it is obtained and used |
|---|---|
| Account information | Email address, account/provider identifiers, display name, authentication tokens and account timestamps support sign-in and recovery. Email/password credentials are handled by Firebase Authentication. Google sign-in passes authentication and profile information to Firebase; we do not receive your Google password. |
| Game and account activity | Rigs, upgrades, quests, credits, energy, experience, preferences, balances, entitlements, account status and operation history let us save, synchronize and verify your game. The backend, rather than your device alone, determines confirmed results. |
| Leaderboard information | If you enable visibility, other players can see your display name, score, rank and public account reference. Visibility starts off for new accounts. Regional queries can send the country code from your device locale; this is not GPS positioning. |
| Purchases | When purchases or restoration are used, Google Play provides product, purchase-token, order and subscription information for verification, restoration and replay prevention. We do not receive your payment-card details. |
| Google advertising | The Google Mobile Ads SDK processes IP addresses (which can indicate approximate location), advertising/app-set or other device/account identifiers, interactions and diagnostic/performance information. Reward verification, when available, sends an account-linked identifier and a one-time ad-session value to Google and receives its verification callback. |
| Service and security information | Firebase services, App Check and Play Integrity process installation identifiers, authentication/integrity tokens and technical request information. Hosting and network services receive IP addresses and request metadata. Deletion-status rate limits use a keyed digest of a network address. |
| Optional product events | After an effective analytics opt-in, our own backend can receive session start/end times, duration, lifecycle reasons and ad-event properties, with account/session and event identifiers and platform information. These events are separate from Google's advertising measurements. Firebase Analytics collection is deactivated in this app version; it has no Crashlytics integration. |
| Privacy and deletion records | Choices, disclosure versions, timestamps, request identifiers, status and retained-record exceptions support consent controls and deletion requests. Protected tracking references are stored on the device; do not email those references. |
| Wallet and eligibility records | New withdrawals and payout-destination collection are disabled in the current configuration. Historical records may include payment destinations, invoices, amounts, fees and settlement status. The candidate payout flow stores an encrypted Lightning address and a masked display copy. An administrator can record supplied age, region, device-count and evidence-reference facts for payout eligibility; the app does not collect a date of birth. |
| Support messages | We receive your email address and the information you choose to send. The app can include platform and locale information in a message you review. Opening the email composer or copying text does not send a message. |
| Website visits | Azure and Cloudflare process requests to deliver and protect this website. Cloudflare Web Analytics measures page visits and loading performance through its browser beacon. |
The supported Android flow does not request GPS location, contacts, photos, microphone recordings or health information. Some dependencies declare biometric permissions, but no app feature collects biometric information. We do not offer player chat or a content-upload feature.
3. Why we use information
We use information to provide accounts and gameplay, synchronize progress, verify and restore purchases, serve and verify ads, enforce privacy choices, prevent fraud and duplicate transactions, maintain security, handle obligations and deletion requests, and answer support messages. Optional product analytics helps us understand use of the game after opt-in.
Where applicable privacy law requires a legal basis, the relevant basis depends on the purpose: providing the service you request, legitimate interests in support and service protection, consent for processing that requires it, or an applicable legal obligation. Optional analytics and personalization choices are separate from accepting the Terms.
4. Providers and other recipients
- Google Firebase and Google Cloud: Authentication, Cloud Firestore, Cloud Functions, App Check, Remote Config and associated hosting, task, notification-processing and logging infrastructure. Functions use the US Central region. Firebase privacy information.
- Google Sign-In, Google Play and Play Integrity: optional Google sign-in, purchase verification/billing and app-integrity checks. Google Privacy Policy.
- Google AdMob and User Messaging Platform: advertising, measurement, verification and advertising privacy choices. We use ordinary AdMob, with no additional mediation integration. How Google uses information from apps.
- Google Workspace: receives and stores email sent to our support mailbox, including privacy and deletion requests.
- Microsoft Azure: hosts the public website. Microsoft Privacy Statement.
- Cloudflare: delivers and protects the public website and provides Cloudflare Web Analytics. Cloudflare Privacy Policy.
- Lightning services: the candidate payout integration uses LNbits and the receiving Lightning-address service to obtain and pay an invoice. No payout provider is active in the current release configuration. This is not a claim that current users can withdraw.
Other players receive the leaderboard information you choose to make visible. We may disclose relevant records when needed to comply with an applicable legal requirement, resolve a dispute or protect users and the service. We do not use a separate support-ticket or third-party product-analytics service.
5. Ads and your privacy choices
The app requests Google's UMP privacy information before initializing the advertising SDK and offers the Google privacy form when it is required and available. The SDK can initialize after sign-in, before you choose to watch an ad. Google's permission to request ads is separate from your account's personalized-advertising choice.
Personalization starts off and is used only when the applicable choices permit it. Non-personalized ads still process some information. Turning off our own analytics does not turn off Google's advertising measurements or essential security processing.
- Open Profile → Privacy to review product analytics, personalized advertising and leaderboard visibility.
- Use the ad privacy/Google privacy-options entry when available to revisit Google's choices.
- Use Android's advertising settings to reset or delete the advertising ID.
- Email support for help with a privacy or California sale/sharing opt-out request.
CyberWiz does not sell data through a separate data-broker service. Google advertising disclosures may be treated as a “sale” or “sharing” for cross-context behavioral advertising under California law, depending on the applicable processing and settings. We therefore do not make a blanket claim that no sale or sharing occurs.
A choice normally affects future processing, not records already collected or records retained for obligations and security. A public website visit does not identify your app account or change its settings; use the app controls or contact us for an account-specific request.
6. Cookies and device storage
The public website code does not set advertising or analytics cookies, use browser local storage, load advertising SDKs or collect form submissions. Fonts and artwork are served with the website. Cloudflare Web Analytics uses a cookieless beacon; hosting and security services can still process technical request information.
The app stores appearance, language, accessibility and onboarding preferences locally. It also retains pending ad identifiers and protected operation, purchase-proof and deletion-tracking records so interrupted actions can be recovered. Signing out does not necessarily erase unresolved recovery records. An operating-system permission declared by a library is not by itself evidence that the app collects that information.
The restricted administration portal uses Firebase sign-in, essential session/security cookies and local recovery metadata. Those controls are separate from browsing the public website.
7. Retention
We retain information for the purpose for which it was collected, then remove or minimize it when it is no longer needed, subject to outstanding obligations, replay prevention, security, recorded holds and recovery requirements. Some cleanup is automated and some requires a manual support request. We do not promise that all copies disappear when a request is submitted.
| Record | Retention approach |
|---|---|
| Account, profile and game data | Kept to operate the active account. Deletion removes eligible personal and gameplay fields through the tracked cleanup process; retained obligations and incomplete steps can require manual review. |
| Optional product events | The implemented expiry schedule is 30 days from the original event. Holds or incomplete processing can require manual handling. This is not a guarantee that every related record or provider copy is erased in 30 days. |
| Purchases, financial records and proof identities | Minimal records may remain to reconcile obligations, substantiate accounting/disputes or prevent a consumed purchase from being reused. Raw evidence and destinations should be minimized after reconciliation; deletion does not automatically remove required proof ownership. |
| Consent, security and support records | Kept as needed to substantiate choices, investigate misuse, answer requests and resolve follow-up or retained obligations. Ask support about removal; no fixed automated mailbox purge is promised. |
| Deletion tracking and recovery | Tracking references expire after 30 days. Expiry does not prove that cleanup completed. Minimal tombstones and recovery records may outlast the account so erased information or used proofs are not restored. |
| Provider logs and backups | Provider retention and backup cycles can outlast a live record. Restoration must respect recorded deletion restrictions. No immediate erasure of every provider or backup copy is promised. |
8. Account and data deletion
In the app, open Profile → Settings → Delete account, read the notice, reauthenticate through your sign-in method and confirm the request. The request is tracked; “requested,” “in progress,” “unresolved” or “needs support” does not mean completed.
If you cannot sign in or no longer have the app, use our public account deletion page or email [email protected]. You do not need to reinstall the app to send a request. We may need to verify ownership before processing it.
Deletion freezes new financial actions and removes eligible account data. Minimal financial, proof-ownership, security and recovery records can remain for the reasons above. Some cases need manual processing. Google Play subscriptions must be canceled separately in Google Play.
9. Privacy requests and rights
Depending on applicable law, you may have rights to know or access information, obtain a copy, correct it, request deletion, restrict or object to processing, withdraw consent, or opt out of sale/sharing. Where available, California residents may use an authorized agent and exercise rights without unlawful discrimination. These rights can have exceptions.
Email [email protected] with your request and enough information to locate the relevant account or conversation. Do not send passwords, one-time codes, payment credentials, private keys or protected deletion-tracking tokens. We may request appropriate ownership or agent verification. If applicable law gives you the right, you may complain to your data protection authority.
10. Children and availability
The game is for people 18 and older and is not directed at children under 13. Its Android distribution is intended for the United States. The age declaration is not identity or age verification. Contact support if you believe a child has provided personal information so we can assess and handle the account.
11. Processing locations and security
CyberWiz operates in California. Our backend uses US-region Google Cloud services, and the public website uses Azure and Cloudflare. Providers may process information in other locations under their applicable terms. We do not claim that every copy stays in one country or that a particular international-transfer arrangement has been established for every service.
Inspected service connections use HTTPS. Account authorization, access controls and protected storage help limit access; some records are retained in encrypted storage. No method of storage or transmission is guaranteed completely secure.
12. Policy changes
We will update the date when this policy changes and provide additional notice where appropriate. Material changes to data collection or optional purposes may require updated disclosures and choices. Questions: [email protected].