Privacy policy

1. Publisher and scope

Airport Sprint is published by BrowTe Investments LLC (“we,” “us,” or “our”). This policy covers the Android game com.browte.airportsprint, communications with us about the game and this privacy webpage.

The game does not require a BrowTe account, email address or password. Google Play uses its own store account. The private purchase identifier described below connects purchase records without creating a BrowTe sign-in account. It is pseudonymous personal information, not anonymous data.

Privacy questions: contact@browte.com. This policy describes the Android release; it does not certify an unreleased iOS edition.

2. Information kept on your device

The game saves unlocked and completed flights, scores, ratings, achievements, lives and recovery times, chapter rewards, unfinished attempts and settings for sound, motion, touch controls and route guidance. It also stores a recovery copy, local engine logs, a private purchase-session credential, pending delivery requests and refill-delivery records.

These files use app-private device storage. Scores, flight results, gameplay history and preferences are not uploaded to our purchase service. There is no cloud gameplay-progress synchronization in this release. Android app backup is disabled; local files are not a custom encrypted vault.

3. Purchases and purchase verification

When the store needs a session, the game creates a random private purchase credential automatically. It sends that credential to our verification service over HTTPS; the service looks up a one-way hash and does not store the raw credential. Existing sessions can reconnect when the app starts or returns to the foreground. This identifier is not a hardware or advertising ID and is not used for behavioral tracking.

Browsing the store does not create a stored empty purchase wallet. A verified purchase creates a financial wallet, and verified recovery can store a hashed session alias. This wallet records purchase benefits, not your gameplay history.

Google Play handles payment. The game sends a wallet binding to Google Play when launching checkout. It sends the product identifier and Google Play purchase token to BrowTe’s verification service, together with the private authorization credential. Our service checks the purchase with Google’s Android Publisher API.

Google returns purchase state, product, quantity, purchase option, wallet binding, acknowledgment or consumption status, and refund information. Responses may also include an order reference, completion time, region or test context. Those additional fields are processed during verification but are not retained in the service’s current receipt-record format.

We store purchase tokens and their hashes, product and wallet associations, entitlement and credit references, fulfillment and refund/revocation status and times, delivery/deduplication identifiers, and recovery-session hashes or aliases. The app receives verified benefits and one-use refill grant identifiers. These records support fulfillment, restoration, refund handling and protection against duplicate delivery.

We do not receive your full card number, bank credentials or Google account password through the game. Free gameplay works offline; purchases, restoration and Premium verification require an internet connection. Google processes payment and store-account information under its own policies.

4. Google Play Billing diagnostics

The game automatically connects to Google Play Billing for product availability and localized prices, even if you do not purchase. Google’s billing components can send billing API results, errors and connection diagnostics with a randomly generated billing-session identifier.

Technical context may include app and library versions, device model and manufacturer, hardware and Android build information, language and locale, time zone, carrier code and network type. Google receives the connection IP address. Events can be queued persistently on the device before transmission.

Google uses billing diagnostics to operate, troubleshoot and improve its billing service. We have not established every field sent on every device, Google’s diagnostic retention and linkage practices, onward use, or whether Google derives approximate location from IP addresses. Billing diagnostics have no in-game opt-out.

No advertising, gameplay analytics, cross-app tracking, Firebase Analytics or separate crash-reporting SDK is integrated into the game. Billing’s technical diagnostics are separate from gameplay analytics.

5. How information is used and disclosed

• Local data operates the game, saves progress and preferences, and manages lives and rewards.
• Purchase information verifies, fulfills and restores purchases, prevents duplicate delivery and fraud, and handles refunds and disputes.
• Technical information supports reliable and secure operation and investigation of errors.
• Support correspondence lets us answer questions, review privacy requests and meet applicable obligations.

We do not sell game personal information or use it for targeted advertising. We may disclose relevant information where required by law, to protect users and our rights, investigate fraud or resolve disputes.

Where applicable law requires a legal basis, processing relies on providing requested game, purchase or support services, legitimate interests in reliable and secure operation, legal obligations, or consent where required.

6. Service providers and support

Google Play and Google Play Billing process product and transaction information, purchase verification, restoration, refunds and technical diagnostics. Google Play and Android may also process platform information under their own policies and your device settings. See the Google Privacy Policy.

Google Cloud hosts our verification service using Cloud Run, Firestore, Pub/Sub and Cloud Scheduler. Firestore stores financial records; authenticated purchase notifications and scheduled jobs trigger checks with Google. Cloud Run and Firestore are deployed in the United States (us-central1). See Google Cloud privacy information.

The infrastructure receives request information such as IP addresses, request paths, timestamps, response status, user-agent and connection details. Our application code does not deliberately log purchase tokens, authorization credentials or request bodies; this does not mean the infrastructure has no logs. Firebase Authentication is not used.

Our email provider processes messages sent to contact@browte.com, including your address, message and attachments you choose to send. Purchase support may require an order reference or other reasonable proof. Do not send passwords, session credentials, raw purchase tokens, full card/bank details or unnecessary identity documents.

Google and other providers may process information in countries other than where you live. Applicable safeguards depend on the services and locations involved; we do not promise that all information stays in a single country.

7. Retention and restoration

• Local data: remains until removed through Android’s app-storage controls or by uninstalling the game and removing its data. Progress and already delivered consumable refills, including locally saved refills, do not restore after removing that data.
• Purchase recovery: Premium and pending or unconsumed purchases can be recovered with the same Google Play account after verification. Restoration does not create duplicate refill deliveries or upload your gameplay history.
• Finalized consumable tokens: become eligible for removal after 180 days. Scheduled cleanup removes the raw tokens in bounded batches when operating; a processing backlog can delay removal. This does not delete all associated financial records.
• Financial and duplicate-protection records: minimal token hashes, product/wallet associations and delivery-operation records have no automatic expiry. They support duplicate-delivery protection, fraud prevention and financial disputes. Premium tokens remain as needed for verification and restoration.
• Cloud operational logs: the operational logging bucket is configured for 30-day retention. Required administrative audit logs follow Google Cloud’s separate retention requirements. This is not a 30-day deletion promise for purchase records or Google’s independent billing diagnostics.
• Support correspondence: is retained as needed to answer and follow up on requests, resolve disputes and meet applicable obligations. It has no fixed automatic deletion period.

Google controls its own payment and diagnostic retention. BrowTe cannot directly delete Google accounts or Google’s independently retained payment, store or diagnostic records.

8. Privacy and deletion requests

There is no BrowTe sign-in account to create or delete. You can erase local progress and settings through Android’s app-storage controls. Removing app data also removes the local purchase-session credential; it does not automatically delete purchase records held by BrowTe or Google.

This is a manual request channel, not an automatic erasure service. We assess requests under applicable law. Financial and security records may need to be retained for applicable obligations, fraud prevention or unresolved disputes. We do not promise immediate or complete erasure of every record. Requests about information Google holds independently must be directed to Google through its privacy controls or support channels.

9. Your privacy choices and rights

You can play without making purchases, remove local data and choose what to include in messages to us. A private purchase session is used when connecting to the store and can reconnect on later launches. Google Play Billing diagnostics are automatic and separate from the choice to buy.

Depending on where you live, you may have rights to access, correct, delete or obtain a portable copy of personal information, restrict or object to processing, withdraw consent where processing relies on consent, or complain to your local data-protection authority. Contact contact@browte.com. We verify requests as appropriate and respond under applicable law.

10. Children and families

Airport Sprint is intended for players ages 13 and up and is not directed to children under 13. The game does not ask for a birth date or verify age. We do not knowingly collect personal information from children under 13. Parents or guardians who believe a child has provided personal information can contact contact@browte.com so we can investigate and take appropriate steps. Higher local age or parental-authorization requirements may apply.

11. Security and this website

The identified app, purchase-service and Google network flows use HTTPS with certificate verification. Purchase-service requests do not use an insecure fallback or follow authenticated redirects. Server access controls protect financial data. Local storage is app-private, not a custom encrypted vault. No method of storage or transmission is completely secure.

The game does not request access to contacts, camera, microphone, photos, SMS messages or device location. A lack of location permission does not establish what a provider may infer from network information.

This webpage is hosted through ChatGPT Sites on Cloudflare. Visiting it sends ordinary request and connection information, including your IP address, to hosting and security services. Cloudflare may set security cookies such as __cf_bm. See Cloudflare’s cookie information.

We have added no advertising, analytics or tracking-pixel integration to this legal page. External links and email involve the relevant provider’s own practices.

12. Changes and contact

We will update the effective date when practices change and provide additional notice or obtain consent where required before material changes apply.