PocketPet privacy policy

Last updated: 22 October 2026

PocketPet is operated by Andrew Karaev, United Kingdom. For privacy questions or requests, email arex.theyooos@gmail.com.

Information we use

Why we use it

We use account and game information to provide the service you request, synchronize progress, deliver paid content and restore ownership. We use limited technical and support information to keep PocketPet reliable, prevent misuse, resolve problems and handle requests. Payment and deletion records help us investigate delivery, refunds and disputes.

For core account, game and purchase services, our basis is performing the service contract with you. Necessary service security and support rely on our legitimate interests, taking your rights into account. We comply with applicable legal obligations and use consent where it is legally required. Contact us to ask about a particular use or to object to a use based on legitimate interests.

Service providers and transfers

We use Supabase for authentication, the database and account storage; Google Cloud for hosting and operational logs; Google Play for purchases; and Firebase/Google Analytics for diagnostics, usage measurement and configuration. They receive information needed for their respective services. Our application database is hosted in Ireland, and the web services use a European Google Cloud region. Providers may also process information outside the UK and EEA under their applicable data-processing terms and transfer safeguards.

Google manages its own Google-account and payment information under its policies. See Supabase privacy, Google privacy and Firebase privacy and service retention. You can contact us for information about recipients or applicable transfer arrangements.

Request account deletion

Open pocketpetwears.com/account/delete and choose the Google account you use in PocketPet. Opening the link does not delete anything. A request receipt is not confirmation of completed deletion.

We require fresh sign-in confirmation and aim to complete verified requests within 7 calendar days. After confirmation, new item grants are stopped and unfinished payments go to manual review. We explain delays and confirm completion.

Completed deletion removes your sign-in account, pet, game inventory, coins, rewards, cosmetic ownership and account files. Deletion does not automatically refund a Google Play purchase. Limited records described below can remain. Keep your deletion status code private; it lets you check the outcome after sign-in is removed. If you cannot sign in, contact support. We do not ask for your Google password, payment card or access tokens.

Retention after deletion

While your account is active, we keep information needed to provide and restore the game. After deletion, the following schedule applies to the limited records we still need:

Minimum linked payment records
12 calendar months from Google purchase completion. For a cancelled order without that date, we use its first registration on our server. An encrypted purchase token has a separate deadline of 30 days after confirmed account deletion. Linked information needed for that token cannot be removed before its separate deadline; it is not kept for a new 12-month period after deletion.
Account authentication audit stored by us
Up to 30 days from the event. Database audit writing is currently disabled; Supabase still has its separate service logs.
Support cases
Up to 90 days after a case is closed. An open or reopened case is reviewed rather than treated as closed by its creation date.
Deletion completion and compensation audit
Minimum technical evidence for up to 12 calendar months after completed deletion, including information necessary to prevent an erased account from reappearing after recovery.
Our encrypted recovery snapshots
Up to 30 days from snapshot creation. They are restricted to recovery. Before serving a restored system, completed erasures and payment-retirement restrictions must be reapplied. A backup does not make an erased account available for normal use again.
Google Cloud logs
Ordinary application/request logs are configured for 30 days. A separate provider-controlled administrative audit class is kept for 400 days; this is not the retention period of every player log.
Analytics and diagnostics
Our Google Analytics property is configured for 2 months of event data and 14 months of user data, with the user period reset by new activity. These controls do not cover most aggregated standard reports. Google signals is off; Google Ads and BigQuery are not linked. Crashlytics begins its removal process after 90 days under Firebase's published service terms. These provider records are not all deleted by removal of a Supabase account.

A particular unfinished payment, dispute, security incident or legal obligation may require limited necessary evidence for longer. We record a reason and review date rather than keeping a whole game profile indefinitely. Providers have their own operational retention and deletion processes. The current Supabase Free plan does not include scheduled project backups; its dashboard log-access window is not a guarantee that every internal provider copy is erased at that time.

Your choices and rights

Depending on the applicable rules, you can request access, correction, deletion, restriction or a portable copy of your information, object to certain processing, and withdraw consent where processing relies on it. Contact us using the email above. We may need proportionate information to confirm your identity and locate installation-scoped data; we do not assume a different Google account owns your records.

Parents or guardians can contact us about a child's information. You can also raise a concern with the UK's Information Commissioner's Office or your local data-protection authority. We will explain any applicable exception or delay in responding to a request.

Changes

We update this notice when our practices change and show the revision date here. Material changes will be communicated through an appropriate app or service channel.