Pool Party

Optional notifications · Android 0.8.9 and later

You can enable game news and updates in Settings and allow notifications in Android. This choice is separate from statistics and does not enable Analytics. We use Firebase Cloud Messaging (Google) to send Pool Party notices. If enabled, the app sends the notification token, a random installation identifier, language, app version and test or production environment over HTTPS to games.vertalix.com. The token is stored encrypted and used only for this game. Turning notifications off blocks them locally and requests removal on the server; offline requests are retried. Tokens expire after 90 days without refresh; an ownership record is retained to prevent stale registrations. Tapping a notice opens the game without changing progress or balance. You can also change permission in Android settings.

Optional analytics · new test versions

Starting with iOS 1.1.1 and Android 0.8.3, you may voluntarily enable Vertalix and Google Analytics for Firebase statistics in Settings. They are off by default, without a startup popup. An earlier iOS preference does not automatically enable this new collection. Declining does not affect gameplay or purchases.

When enabled, the Vertalix collector receives sessions, round starts, results and duration, Drops earned and spent, tools used and chests opened over HTTPS, with platform, version, date and random event and installation identifiers. The analytics identifier is separate from purchase and notification identifiers. We do not send names, email, IDFA, IDFV or the Android advertising ID. These data are pseudonymous, not fully anonymous.

Firebase receives usage statistics and may process an app-instance identifier, device, system and language information, approximate location derived from the connection, and purchase and interaction information. We do not enable advertising personalization or link these data to a player account. Google and collector reports are displayed separately to prevent double counting.

Disabling stops new transmissions and deletes the local analytics queue and identifiers; previously sent reports are not automatically deleted. The local queue holds at most 500 events for six days. Vertalix retains detailed collector events for up to 90 days, alongside aggregates and technical identifiers for reporting; private backups are retained for 35 days. Google applies the retention configured in its service. Contact support@vertalix.com for assistance or rights requests. Android notifications remain disabled.

Controller and contact

VERTALIX S.A.S., Uruguay. Avenida Luis Alberto de Herrera 1248 (WTC), Torre II, Oficina 1416, CP 11300, Montevideo. Privacy and support: support@vertalix.com. Mention “Pool Party Android”. Do not send passwords or banking details.

Progress and essential services

The app stores levels, Drops, tools, skins, records, passes, settings and purchase delivery records locally to prevent duplicate delivery. There is no VERTALIX account or cross-device progress sync. Uninstalling the app or clearing its data may delete progress. This version disables Android automatic backup; VERTALIX has no copy of your saved game to restore.

The app downloads the catalogue and compatible settings from our server over HTTPS without sending your saved game or a player identifier. It keeps the last validated configuration for offline play. Hosting processes technical connection data, such as IP address, request and date, to operate and protect the service. We do not request camera, microphone, contacts or precise location.

Google Play purchases

Google Play handles confirmation and payment. VERTALIX does not receive your card, Google password or Google email address. The app sends Google a random opaque installation identifier and a random offer identifier to associate and recover the transaction. Google also processes data needed to provide its payment service under its own policy.

Starting with version 0.7.10, before payment our server stores an offer with a random identifier, product, catalogue revision, contents and date, bound to this installation. Starting a purchase creates a private random credential on the device. The app sends that credential and the purchase token over HTTPS to our server, which checks payment status directly with Google and records delivery to prevent duplicates. It retains the opaque installation identifier, offer, token fingerprint, encrypted token, quantities, purchase or refund status and dates. It does not receive banking details or your Google account. Earlier versions verified transactions locally.

Delivery is saved before consumption is reported to Google. We check cancellations and refunds reported by Google and remove only unused purchased items. Gameplay rewards are preserved. This processing is necessary to handle the purchase and prevent duplicate deliveries, and does not enable Analytics.

Drops, fixed-content chests and passes are consumables, not subscriptions. Recovering a pending purchase does not restore resources already delivered or spent, nor sync progress. Passes are stored until activation; their timer then continues while the app is closed.

Ads, age and privacy

Compatible versions, starting with iOS 1.1 and Android 0.8.0, may show automatic ads after completed rounds, never before or during play. Frequency depends on game configuration. Videos to obtain a life or continue a round are always optional. The initial iOS 1.0 version does not show ads.

Starting with iOS 1.1 (build 140) and Android 0.8.1, we do not ask for your age or birth date. Every ad request uses Google’s restrictive treatment for users below the age of consent, non-personalized ads and a maximum G content rating. We do not use IDFA or the Android advertising ID. Ads may be prepared in the background; rewarded videos only open when you request them. This does not eliminate the technical data processing described below. The game remains intended for players aged 13 and older.

Earlier versions iOS 1.1 (139) and Android 0.8.0 ask once whether you are under 18; that choice stays on your device and disables ads for minors. Newer versions do not use that choice.

We use Google AdMob and UMP. Where applicable, privacy choices appear before ads are requested. You can review them in Settings → Ad privacy. Rejecting or closing the message does not prevent play. We request non-personalized ads; this does not mean no data is processed.

AdMob may process your IP address (including approximate location), technical identifiers such as App Set ID, ad interactions and diagnostic information to serve and measure ads and prevent fraud. We request non-personalized ads and exclude the Android advertising ID permission; this does not remove all technical data handled by Google. We do not request precise location. AdMob connections are encrypted. Google handles this data under its policy and applicable controls.

Rewards are granted only after the SDK confirms they were earned. Local counters record attempts and rewards without sending them to Firebase Analytics. AdMob provides its own advertising reports. QA builds use demonstration ads. Joining Google Play internal testing does not automatically make ads test ads; treat them as test ads only when explicitly labelled. Through Android 0.8.2, Firebase Analytics and push messaging are not included.

Remove ads

These versions offer a permanent purchase, not a subscription, that removes only automatic ads between rounds. Optional rewarded videos remain available. The final price is shown by the store before confirmation. Restore this purchase in Settings using the same store account; a refund may revoke ownership. It does not restore spent consumables or synchronize progress.

To verify and restore this entitlement, the app sends the purchase token over HTTPS to our server, which checks its status with Google Play. The purchase is not consumed and does not grant Drops or tools.

Retention and security

Local data is kept for as long as it exists in the installation. Server offers and purchase records currently have no automatic deletion. They support pending purchase recovery, duplicate prevention and handling cancellations or refunds; retention must be reviewed according to these needs and applicable obligations. Technical logs are kept for operations, abuse prevention and troubleshooting. Private database backups are retained for 35 days.

Our connections use HTTPS. Hosting providers and Google may process data outside Uruguay, including in the United States, under their service terms and transfer mechanisms. We use necessary data to provide the game and manage purchases, and technical logs for security and operations. We do not sell personal data.

Support and data requests

If you email support@vertalix.com, we receive your email address and the content you choose to provide so we can respond and resolve the issue. We keep the enquiry for as long as needed to handle it and meet applicable obligations.

You may request access, correction, deletion, objection, restriction or portability where applicable by emailing support@vertalix.com with the subject “Pool Party Android privacy”. We will request only what is necessary to identify the data and handle your request. We have no player account or copy of local progress; deleting server data does not automatically restore or delete your saved game on the device. Deleting the app does not delete records Google may retain. You may complain to the competent authority, including Uruguay’s Unidad Reguladora y de Control de Datos Personales.

Children and purchases

The game has no chat or user-generated content. Minors should have the supervision and permissions of their responsible adults for purchases and privacy choices. Purchases can be protected using Google Play authentication and parental controls.

Testing and this page

Participation in an internal Google Play test does not by itself make purchases free. Only operations identified as test purchases use no-charge test payment methods. Always check the payment screen.

This page has no analytics cookies, ads or third-party scripts. Hosting processes technical visit data. This policy describes the Android version currently being prepared; relevant changes will be published before new processing is enabled.