GLOOPOST
Loky Games

Privacy policy

Last updated: 11 October 2026

This policy covers Gloopost on Android, including the public production release. Features depend on the installed version and service availability. Earlier test versions may have purchases or Analytics disabled and may use sample advertisements. The production configuration supports optional Google Play purchases, optional rewarded advertisements and separately consented gameplay Analytics.

Request deletion of your Gloopost online identity and associated data — instructions and contact details.

Who is responsible

GLOOPOST is developed by Zvonimir Lolić, using the name Loky Games, in Croatia. For questions about personal data or to exercise your rights, email gloop.official@outlook.com.

Game progress on your device

The game stores settings, progress, achievements, cosmetic selections and test-ad reward counts locally on your device. Offline gameplay does not require a separate GLOOPOST account. Google Play Games sign-in is used for online rankings and account-bound purchase verification. Most gameplay progress remains local; online records are described below. Clearing the app's storage removes these local records and resets progress. Device backup and restore may depend on your Android settings.

Development builds may also keep local diagnostic files about gameplay sessions. These are not automatically sent to us by the game's development logging system. If you send logs to support, they become part of your support request.

Optional cloud gameplay backup

Where Cloud Save is available, choosing “Sync & enable backup” enables backups tied to your verified Play Games identity. Gameplay still works locally without enabling backup.

The backup contains your Sparks balance, gameplay achievements and career counters, locally earned ships and hangar, best distance, cosmetic selections and displayed trophies. It uses the derived account identifier already described below, without requesting your email address. It does not confer purchase ownership or advertising rewards and is not a verified leaderboard score. The app sends backups over HTTPS to Cloudflare Workers and stores them in Cloudflare D1. Automatic synchronization takes place in the main menu; conflicting copies require your choice.

Turning automatic backup off stops automatic uploads but retains the cloud copy. “Delete backup” removes the current and previous gameplay payloads from the active database and turns automatic backup off on the requesting device. Other devices learn of deletion when they reconnect. A minimal derived-account deletion marker, revision, operation identifier and timestamp remain to prevent stale devices from silently recreating deleted progress. Only an explicit “Create new backup” action can resume backup. Local gameplay, purchases, ad rewards and Google rankings are separate. You can request deletion of the broader online identity through the support procedure below.

The current backup remains until you replace or delete it. We keep at most one previous accepted version; scheduled cleanup removes that previous payload after 30 days without replacement, subject to the cleanup schedule and service availability. Cloudflare's recovery system can retain older database versions for up to seven days on our current free plan; these are not served as live game progress. See Cloudflare D1 recovery documentation.

The device keeps a pending upload until it is acknowledged or resolved, plus the last completed restore journal for recovery. Confirmed cloud deletion clears the pending payload and completed restore journal on that device; an incomplete restore must first be recovered. Other devices remove their completed recovery copy when they next observe the deletion. Local gameplay and settings remain until cleared separately. Never clear app storage during an unresolved restore unless you accept losing local data.

Optional gameplay analytics

In versions with Firebase Analytics enabled, we ask separately for your permission before collecting gameplay analytics. Earlier test versions may keep this feature disabled. You can decline without losing access to gameplay, rewards or purchases, and change your choice through Settings > About > Privacy. Advertising consent and optional gameplay analytics are separate choices.

If enabled with your consent, Google Analytics processes an app-instance identifier, app version, device details (such as model, brand, operating-system version and screen resolution), approximate location (country, region and potentially city) derived from the connection, and interactions such as runs, distance, active play time, causes of death, game phases, achievements, hangar actions, optional rewarded-ad completions and verified purchase events. The SDK may also record purchase or subscription events automatically, including product identifiers and prices, when Analytics is enabled. These are separate from our verified-purchase event and are not treated as authoritative payment records. We use these measurements to understand engagement and improve the game across different devices. This Analytics feature does not request GPS or precise-location permission. We do not intentionally send names, email addresses, Play Games identifiers, payment-card details, purchase receipts or authentication tokens to Analytics. An app-instance identifier is pseudonymous personal data; these records are not described as anonymous.

Our Analytics configuration disables Google signals, user-provided data collection, optional account data sharing and use of Analytics data for personalised advertising. The app is configured not to collect advertising IDs for Analytics. This does not change the separate Google Mobile Ads service described below. We have not connected this Analytics property to Google Ads or BigQuery.

Individual Analytics user and event data retention is configured to two months, without extending the user retention period on new activity. This setting does not apply to all aggregated standard reports, which may remain longer. Turning analytics off stops future collection and resets local Analytics data; it does not itself erase information already received by Google. Clearing app storage or deleting a Gloopost online profile is also separate from Analytics deletion. Contact us for privacy requests; do not send Google passwords or sign-in codes. See our deletion information.

We rely on your consent for this optional analytics. Google processes Analytics information for this purpose under its applicable data processing terms; international processing and safeguards are described in Firebase privacy information and Google's privacy policy. To request deletion of Analytics records, use the installation references and support procedure on our deletion page.

Age-related advertising protections

The game does not ask new players to select an age group or collect a date of birth. It applies Google teen age-restricted treatment to eligible ad requests, including players whose age is unknown, and requests non-personalized ads. This is not age verification and does not replace applicable consent requirements. Google privacy forms may still appear when required.

An earlier test version stored a self-declared age group locally. Existing Under 16 or Prefer not to say choices continue to block advertising. Other existing choices no longer change the advertising treatment. This legacy record is not uploaded to Loky Games. Clearing app storage removes local records and game progress. Contact support for help with an incorrect earlier choice.

Google advertising and privacy services

Gloopost includes Google Mobile Ads and Google's User Messaging Platform (UMP). The production configuration requests optional rewarded ads. Earlier test versions may request sample ads; test mode does not mean that no technical information is processed by Google.

Depending on configuration, consent and the service used, Google's SDK can process IP addresses (which can indicate approximate location), device or advertising identifiers, app and ad interactions, and diagnostic information. Google uses SDK data for ad delivery, measurement and fraud prevention. SDK network data is encrypted in transit.

UMP checks the applicable privacy-message requirements and manages available consent choices. The app requests ads only when its consent flow permits them. Where required, the game provides “Ad privacy options” in Settings to revisit those choices. Withdrawing consent does not affect processing that was lawful before withdrawal.

More information: Google Privacy Policy and Google's use of information from apps that use its services. Google's retention and privacy controls apply to information it processes; we cannot directly erase Google's independently held records.

Play Games, purchases and online rewards

Google Play Games processes your game profile and, in earlier versions, scores and leaderboard participation. Online rankings can show your Play Games display name, rank and submitted distance to other participating players. Google profile visibility controls Google social features; it does not hide a score you submit to the separate Gloopost leaderboard described below.

For purchase verification, the game sends a one-time Google authorization code to our Cloudflare-hosted service. The service verifies the game identity with Google and derives an account identifier without requesting your email address. The service stores purchase-token hashes, product identifiers, purchase status, verification times and the derived account identifier in Cloudflare D1. Purchase tokens are retained server-side to recheck ownership and refunds and to recover interrupted purchase acknowledgements. We do not receive your payment-card number.

Session credentials expire after up to 15 minutes. Short-lived hashed connection identifiers and counters help limit abusive requests. Temporary authorization-code hashes are used to prevent replay. Expired session and request records are removed by scheduled cleanup. Purchase records support restoration and refund handling; contact support for access or deletion requests. Clearing app storage does not delete server-side purchase records.

Sample-ad versions use a separate local preview reward count and do not convert sample views into production rewards. The production server-verified advertising flow uses a random ad-attempt identifier, the derived account identifier and a signed Google reward transaction to prevent duplicate or forged rewards. It is not active for sample ads.

Cloudflare provides hosting and database services for these features. See Cloudflare privacy information and the Google privacy links above.

Support messages

If you email us, we receive your email address, message and any attachments you choose to send. We use them to answer your request, investigate problems and handle privacy requests. Email is handled through Microsoft Outlook. Please share only what is needed to describe the issue.

Purposes and legal bases

We use necessary local game information to provide the features you request. We handle support communications on the basis of our legitimate interest in answering and resolving requests, and where necessary to meet legal obligations. Where consent is legally required for advertising-related storage or processing, we rely on the choices obtained through the consent flow. The precise processing by Google is explained in its notices and privacy information.

Sharing and international processing

Support messages are handled through our email provider, advertising and Play Games information is processed by Google, and the verification records described above are handled through Cloudflare. We do not sell support messages. We may disclose information where legally required or necessary to protect legal rights. These providers may process information outside your country, including outside the European Economic Area, using the safeguards described in their privacy terms. See also Microsoft's Privacy Statement.

Retention and deletion

Local records remain until removed by the app or by clearing its storage. We keep support information only as long as needed to resolve the request and related follow-up, or to meet applicable legal obligations and handle legal claims. You can request deletion of support correspondence using the email above; if some information must be retained, we will explain why. Provider-held data follows the provider's retention policies.

Where offered by your installed version, online-profile deletion and explicit new-profile creation are available in the game. Support requests remain available through our deletion page. Full profile deletion removes active-database gameplay copies, ad attempts and rewards, raw purchase verification tokens, temporary support proofs and existing sessions. It does not erase device storage, Google's records or all provider recovery copies immediately, and does not issue a refund.

A limited purchase ledger remains: token hash, product, derived account identifier, state and creation/verification timestamps. We retain it while needed for legitimate purchase restoration and to prevent duplicate or revoked purchases being restored. Closure records and derived profile links remain while needed to block delayed writes or old devices from recreating deleted data and to distinguish a new profile of the same game identity. These are pseudonymous personal records, not anonymous statistics. They are not used for advertising or gameplay analytics. We reassess necessity for deletion requests and service retirement, and explain the applicable retention period or criteria and any specific legal exception in our response.

In the return flow, only an explicit choice creates a new, empty online profile. Old gameplay and ad rewards are not copied; paid content requires a fresh Google verification. Keeping the old local save or starting fresh is a separate device choice. A confirmed fresh start keeps a local recovery journal with before/after values until replaced by another fresh start, removed by confirmed backup deletion, or app storage is cleared. It is not uploaded. Incomplete recovery must be resolved before deleting its recovery copy.

Temporary protection records have limited validity: game sessions up to 15 minutes and used authorization-code hashes one hour. Support ownership proofs expire after 24 hours; a hashed support-deletion receipt expires after 30 days to let support safely retry the same request. Expiry prevents further use; physical removal takes place through scheduled cleanup. Short-lived counters limit abuse. Signing in to check deletion status can create fresh temporary security records without reopening the closed profile.

Database recovery copies expire under Cloudflare's applicable recovery window; completed deletions must be reapplied before a restored database serves players. We do not restore erased gameplay from these copies for ordinary player requests. Support mail and independently held Google records have separate deletion procedures. There is no single statutory retention duration asserted for all of these categories.

Optional Gloopost friends

Where this feature is available, selecting Enable Friends creates a random friend code linked to your derived game identity. Cloudflare stores the code, Play Games gamer name, your verified online score and its verification time (earlier versions use a score copy from Google), friend requests, accepted relationships and blocks. We use these records to provide the social feature you request. A fresh Google authorization code is exchanged to verify identity and fetch your name and score; the Google access token is not retained.

People who exchange codes can send requests and see each other's gamer names. The Friends view shares scores with accepted friends; the separate global leaderboard is visible to participating players. In versions with server-checked rankings, the Friends view uses the same accepted runs as the global leaderboard. Earlier versions refresh a Google score copy when Friends is opened or refreshed. There is no chat, contacts upload or public gamer-name search. Pending requests expire after seven days and are physically removed on later relevant access. Removing a friendship deletes the relationship; blocking also prevents further requests. Profile data and blocks remain until removed through the feature or an online-profile deletion request. Full profile deletion removes your friend profile and incoming/outgoing social records from the active database; recovery copies follow the existing Cloudflare retention period. A new empty profile does not recover old friendships. Google's own social graph and scores are separate.

Service protection and recovery

For cloud-save recovery and correction of confirmed errors or abuse, we keep a limited history of accepted gameplay backups. Historical payloads are removed after 30 days by scheduled cleanup. Recovery holds and audit records identify the affected derived account, revision, correction and operator action so that corrections can be checked and stale devices cannot overwrite them. Full online-profile deletion removes the associated gameplay history; minimal closure and security records follow the retention criteria above. Necessary security and purchase records are separate from optional Firebase Analytics.

Your rights

Depending on applicable law, you may request access, correction, deletion, restriction or portability of your personal data, object to processing, and withdraw consent where processing relies on it. Contact us using the support address. You may also complain to your local supervisory authority; in Croatia this is AZOP.

Age and intended audience

GLOOPOST is intended for players aged 16 and over and is not directed to children under 16. This intended audience is separate from a store's content rating. If you believe that a child has supplied personal information to us, contact us so that we can investigate and address it. Selecting an intended audience does not by itself verify a player's age.

This website

These support pages contain no advertising, analytics scripts, contact forms or embedded third-party fonts. Opening the site still requires its hosting provider to process technical connection information such as your IP address to deliver and protect the service. Clicking an email link opens your email application; no message is sent until you choose to send it.

Changes

We will publish updates on this page and change the date above. Material changes to data processing will be communicated in the game where required.

Server-checked online rankings

Where enabled, online ranking uses a server-issued run identifier, the derived account identifier, app version, server timestamps, active play duration, distance and periodic sequence-numbered checkpoints. We use these operational records to provide rankings, limit forged or duplicate submissions and review disputed results. This is separate from optional Firebase Analytics and does not depend on Analytics consent. Offline runs remain local and are not imported into the verified ranking.

We store these records in Cloudflare D1. Your Play Games display name, accepted distance and rank can be shown to other players on daily, weekly, all-time and accepted-friends lists. Google profile visibility does not control these Gloopost lists. We do not request your email address for this feature. Run tickets and checkpoint state are removed by scheduled cleanup after seven days; accepted results and any linked correction audit remain until removed through online-profile deletion or service retirement. Invalidating a result excludes it from ranking but retains the linked audit while that result is retained. Full online-profile deletion removes these records from the active database; recovery copies follow the Cloudflare retention period above.