QUADROP / LEGAL DOCUMENT
Privacy Policy
This Policy explains how quadrop handles account, gameplay, item, advertising, purchase, invitation, diagnostic, and website access data, and how users may exercise their rights.
Scope and controller
This Privacy Policy applies to the quadrop mobile application, the public website at https://www.quadrop.party, and directly related online services. The data controller or operator is quadrop. It does not govern services independently operated by third parties that you reach through a link.
Key definitions
A “guest account” is not linked to a Google or Apple identity and relies on a recovery credential stored locally on the current device. A “formal account” uses a supported identity provider. A “diagnostic device ID” is a random installation-level identifier created by the App, not an IMEI, MAC address, or advertising identifier. “Platform store” means Google Play or the Apple App Store.
Data we process at a glance
We process data needed to provide accounts, games, leaderboards, items, ad rewards, invitations, purchases, refunds, support, security, and diagnostics. The exact scope depends on your account type, platform, enabled features, and actions. The availability of a field does not authorize unrelated use.
- Account and identity data;
- App, language, region, installation, device, and network data;
- Game, checkpoint, leaderboard, inventory, ad, invitation, and order facts;
- Diagnostic, security, and support information you choose to submit.
Account and sign-in data
We process an internal user_id, account sign-in type, account status, and stable provider identifiers returned by Google or Apple and verified by our server. A provider may return an email after authorization; it may be absent, hidden, or relayed. Formal sign-in relies on server verification of the provider ID Token, including issuer, audience, time, nonce, and subject.
Guest accounts and local credentials
The raw high-entropy guest recovery credential is stored only in secure storage on the device; the server stores only a digest that cannot directly reconstruct it. We do not place the raw credential in cloud backup, account synchronization, or a manual recovery code. Uninstalling, clearing data, changing devices, resetting the system, or platform storage behavior may permanently prevent recovery and lead to a new guest account.
App, region, and language information
We save user-selected settings such as game sound effects with the account, along with the app version, modification time, and platform and country or region snapshots from the user profile, for settings synchronization and related statistics. Devices may cache settings for that account. Game sounds use bundled local assets. Playback does not record audio, access the microphone or personal music library, or send data to the audio library provider.
Server timestamps, business days, and months use UTC. These values support compatibility, localization, and business-day calculations, but do not by themselves prove a trusted device, purchase, ad reward, or account ownership.
Installation, device, and network information
To operate and diagnose the service we may process an installation UUID, separate device_id, App version and build, operating system, device model, IP address, request time and path, response status, and network failures. We do not use an IMEI or MAC address as the identity for this module.
Gameplay and checkpoints
An online game may create a run ID, game and mode code, seed, state, pause, retry, active-time, checkpoint metadata and payload, final level, score, and line count. Offline local games do not create server runs. Checkpoints are short-lived recovery state: local storage and Redis may hold compressed recovery data, while terminal runs remove recoverable state under the current retention policy. We do not upload a complete action history capable of replaying the whole game, and checkpoint integrity hashes do not prove that a client did not cheat.
Leaderboards and seasons
Eligible ranked games for formal accounts may produce normalized rank values, achievement time, leaderboard snapshots, season eligibility, risk review, and reward records. BLOCKS / Endless is designed to submit eligible scores; BLOCKS / Classic is currently a non-ranked mode unless a released configuration says otherwise. Season and fixed-period boards use the server cycle, UTC boundaries, frozen run ownership, settlement grace, qualification rules, and reward configuration. A displayed rank or reward tier is not proof that a reward has been granted.
The current server accepts a mode-controlled final result and checks identity, ownership, state, idempotency, and basic ranges; it does not perform action-level server verification of the entire game, so we do not claim that every score is fully verified. Simulation users can appear only in approved non-production test data, occupy test ranking positions without being real people, and never receive user rewards.
Inventory and item data
We process item definitions, holdings, quantities, validity periods, acquisition and usage records, source orders or events, refund freezes, and revocation status. These facts display inventory, prevent duplicate delivery, support retries, and revoke the precise source entitlement. They do not represent transferable property.
Daily items, ads, and AdMob
When rewarded ads are enabled, Google AdMob and its underlying services may process advertising identifiers, IP address, approximate region, device and ad diagnostics, consent status, and ad interactions. Quadrop servers process placement, ad call ID, transaction identifier, SSV verification, and business status. A reward exists only after a valid server-confirmed callback and committed transaction. Consent choices depend on actual release markets.
Invitation relationships and rewards
For formal accounts using invitations, we process the invitation code, inviter and invitee user_id, binding time, ad reward count, purchase-acceleration state, and related acquisition records. Rewards come from server configuration and verified ad or official purchase facts. The client cannot submit an inviter ID or declare a reward successful.
Purchases, orders, restoration, and refunds
We process product code, platform, SKU, internal order number, store transaction identifier, actual amount and currency, paid_at, verification result, entitlement holding, restoration, refund request, and platform refund or revocation status. Purchase tokens or signed credentials are sent only to our backend for official verification and are excluded from ordinary application logs and error messages.
App error and diagnostic logs
To diagnose errors on real devices, the App may report module_type, error_type, operation_code, error_code, user_id (which can be absent before sign-in), device_id, App and device information, exception type and message, stack trace, breadcrumbs, and necessary full request URL, ordinary parameters, or request and response summaries. All content undergoes double redaction on the client and server.
Raw access or refresh tokens, cookies, passwords, nonces, guest recovery credentials, purchase credentials, ad receipts, and complete credential objects are prohibited. When email is relevant, only controlled forms such as a mask and irreversible fingerprint may be retained. Diagnostics are not authoritative proof that sign-in, purchase, ad, or reward processing succeeded.
Information submitted for support
When you contact [email protected], we process the email address, issue description, error-log ID, and necessary attachments you choose to provide to investigate, respond, and prevent abuse. Do not send passwords, reusable tokens, nonces, complete purchase credentials, or ad receipts. We may remove sensitive material unrelated to the support request.
Sources of data
Data may come directly from you, be generated by the App during an action or error, be produced by our backend state machines, or be returned by Google Identity, Apple, AdMob, Google Play, or the App Store when you use the related feature. A client-reported purchase, ad, or reward result never replaces official and server facts.
Purposes and legal bases
We process data to deliver the service, authenticate accounts, preserve game progress, publish leaderboards, manage items, verify ads and purchases, process refunds, provide support, prevent fraud, and meet legal duties. Release markets are US. Contract, consent, legitimate-interest, and legal-obligation grounds must follow the market-specific legal review before release. The configured privacy-obligations statement is: Android Google Play internal testing only. Before public release, legal review must confirm the operator and contact address, US target-market privacy rights, retention and deletion periods, AdMob disclosures and consent, purchase and diagnostic data handling, vendor DPAs, and international-transfer safeguards..
Recipients and service providers
We share relevant data only when needed for an enabled function, such as with actual cloud hosting and object storage providers, Google Identity, Apple, AdMob, Google Play, and the App Store. Each provider may process data under its own policy. Final provider name, location, purpose, and contractual safeguards must match the deployment inventory. We do not sell personal data.
Advertising consent and choices
Personalized or non-personalized ads, consent in the EEA, UK, or Switzerland, iOS App Tracking Transparency, and restrictions for younger users depend on actual release markets and platform behavior. Advertising consent is not bundled with acceptance of the Terms. Withdrawing consent does not affect lawful earlier processing, but may change available ads and related reward entries. The configured advertising-consent statement is: Android Google Play internal testing only. Rewarded ads use AdMob; production UMP consent management, personalized/non-personalized ad choices, consent withdrawal, and any iOS ATT flow are not finalized. Complete the applicable regional consent review before public release..
International transfers
Identity, advertising, store, and infrastructure services may involve cross-border processing. Storage locations, receiving regions, adequacy decisions, standard contractual arrangements, or other safeguards must be confirmed against the final deployment and target markets. This draft does not present an unconfirmed transfer mechanism as an existing one.
Retention
We retain data for the shortest reasonable period needed to operate the service, protect security, resolve disputes, and meet legal obligations. Sessions, online checkpoints, ordinary and risky runs, leaderboard snapshots, order and tax records, ads, invitations, diagnostics, and support data have different periods. Redis checkpoints are intended for short-term recovery and have a fixed expiry; command idempotency records are eligible for bounded cleanup after their retention window. Exact release values must be checked against current cleanup jobs, platform rules, and applicable law and cannot be inferred as permanent or immediate deletion.
Security
We use measures such as transport encryption, access control, server-side credential digests, secret isolation, double redaction, least privilege, transactional idempotency, and security monitoring. No system can guarantee absolute security. If an incident affects user rights, we will investigate, mitigate, and notify as required by applicable law.
Your rights and requests
Depending on your location, you may have rights to access, correct, delete, restrict, object, withdraw consent, port data, and complain. Contact [email protected]. We verify the requester, ask only for necessary information, and respond within the applicable period. Some data may remain for security, disputes, or legal duties.
Retaining, Modifying and Deleting Your Personal Data
You may request access to the information you have provided to us. If you wish to make a request, please contact us using the details in the Contact Us section below.If you would like to update, correct, modify or delete from our database any Personal Data you previously submitted to us, please let us know by logging in and updating your profile. If you delete certain information you may not be able to order services in the future without re-submitting such information. We will comply with your request as soon as reasonably practicable.Also, please note that we will maintain Personal Data in our database whenever we are required to do so by law, for necessary operational reasons, or to maintain uniform business practices.Please note that we need to retain certain information for recordkeeping purposes and/or to complete any transactions that you began prior to requesting such change or deletion (for example, when you enter a promotion, you may not be able to change or delete the Personal Data provided until after the completion of such promotion).We will retain your Personal Data for the period necessary to fulfill the purposes outlined in this Policy unless a longer retention period is required or permitted by law.
Children and minimum age
The first release is not directed to children and does not target mainland China. The release-configured minimum age is 16; the service cannot be formally released while this remains a draft value. If we confirm that a child below the applicable age supplied personal data, we will act under applicable law and a verified guardian request.
Third-party links
The website and App may link to official app stores, Google, Apple, or other third-party pages. Those parties independently determine their processing and security practices, so review their privacy notices before use. A link does not mean that we control or endorse every third-party action.
Changes to this Policy
We publish the version, effective date, and update date on this page. If a change materially affects user rights, we will provide prominent notice through the App, website, or available contact channel as required by law. Where fresh consent is required, continued use alone will not replace that consent.
Contact, complaints, and regulators
For privacy questions, rights requests, or complaints, contact [email protected]. The operator is quadrop. You may also complain to a competent regulator where you live. Specific authorities and channels will be listed after release markets and legal review are confirmed.
Effective date: 2026-09-27. Document version: 0.0.6. Last updated: 2026-09-27.