CARP TYCOONLake Manager
Request data deletion

Carp Tycoon: Privacy Policy

Last updated: 12 November 2026

This notice explains how Carp Tycoon: Lake Manager handles personal information in the native Android game and its supporting services. It also explains how to contact us about records from the older web game and Android web-wrapper versions; it does not mean an iPhone version is available.

Who is responsible

Carp Tycoon is operated by Matthew William Emerson, trading as Carp Tycoon Games, a sole trader based in Evesham, England, United Kingdom. Matthew is the controller responsible for the processing described in this notice.

For privacy questions, access, correction or deletion requests, email matthew@carp-tycoon.uk. You do not need to reinstall the game or make a purchase to contact us.

Your career and optional online features

Native Android careers, settings and progress are stored on your device. Uninstalling the game, clearing its storage or losing the device can remove that progress; the leaderboard is not a backup of your complete career, and restoring a purchase does not restore a career.

If you export a save, the file is stored in the destination you choose. Keep that file private and retain your own safe copy.

The online service uses a player identifier and authentication token to associate requests with your installation. If you choose to join the leaderboard, it receives your chosen nickname and gameplay information used for rankings, including virtual money, owned lakes and acreage, fish weights and completed matches.

Other players can see the nickname and ranking information displayed on the board. Use a nickname rather than a real name, email address, school, phone number or home address.

Leaderboard uploads require your choice to share. You can stop future uploads through the privacy controls; requesting that the server hide your public name requires an internet connection and may need a retry.

Withdrawing leaderboard sharing is not the same as erasing every stored record. Browsing the board also contacts the server, and online connections involve technical information such as an IP address.

Native versions 19 and 20 do not offer working email-based identity recovery or full-career cloud synchronisation. Older test builds may display email/code controls without providing working recovery; do not rely on those controls to recover your identity or career.

Purchases, support and technical information

Google Play handles Android checkout. RevenueCat processes purchase history, product and transaction information, subscription status and app-user identifiers to validate purchases, provide access and restoration, and support purchase-related reporting (RevenueCat disclosure guidance).

Payment-card details entered into Google Play are separate from the purchase/access records used by the game. A randomly generated player or purchase identifier is not necessarily anonymous, especially when linked to a support request or receipt.

Approved testers may privately provide a Support ID so that we can locate their purchase-service record and apply temporary access. Store reviewers use separate restricted credentials; this is not an ordinary player sign-up system.

If you contact us, we receive your email or messaging identity, your message and any attachments you send. We use them to answer your request, investigate problems and verify ownership where necessary; the native support control opens an external email application rather than collecting an address in an in-game recovery form.

Our online service processes authentication, security, abuse-prevention and operational records. Native gameplay does not require access to your contacts, microphone, camera or GPS location, but purchase providers, hosting services and the mobile platform process their own technical information.

Google Play Billing includes technical logging about API operation and service connections for performance improvement and error support. This is separate from optional leaderboard sharing, and the game does not provide a switch for it (Google Billing release notes).

Native Android releases up to and including version code 23 do not include our separate general usage-analytics integration. Version code 24 adds optional Google Firebase Analytics, which is off until you explicitly allow it in Privacy & purchase information. Playing and purchases do not require analytics consent. This update does not add a separate crash-reporting service.

If you allow analytics, Google processes app activity and broad screen categories, app version, Android device and operating-system information, approximate location derived from network information, and a resettable app-instance identifier. Firebase can also collect automatic in-app purchase and subscription event metadata, including product and price information. We do not send your email, nickname, career contents or raw payment receipts to Analytics. The app does not request Advertising ID access and keeps advertising-storage, advertising-user-data and advertising-personalisation consent denied.

Turning analytics off stops new app events and requests a local SDK reset. SDK processing is asynchronous: this is not a guarantee that an already-running upload is cancelled, and it is not a request to erase information already held by Google. It does not delete careers or cancel subscriptions.

To help with analytics access or deletion requests, the app keeps up to twenty recent analytics references privately on this device, outside career saves and automatic backups. These remain available after analytics is turned off. Open Analytics data requests to copy saved references into a private request to matthew@carp-tycoon.uk. Copying places them on your clipboard; it does not send a message. Do not publish these references. You can separately forget their local copies, but doing so does not erase Google's records and may make older analytics harder to identify. If analytics stays on, a reference may be saved again when you next start the app.

References may be unavailable, and older, forgotten or uninstalled references may not be recoverable. Contact us even if you have no reference; explain the version and approximate usage dates. Do not turn analytics back on to try to recover a previous reference. We will explain what records we can identify and any limitations rather than claim that an email or purchase Support ID locates analytics.

Why we use information

We use information for the following purposes and lawful bases where UK data-protection law applies:

  • Optional public leaderboard: Your consent for publishing the nickname and gameplay statistics you choose to share. You can withdraw that choice through the privacy controls.
  • Optional usage analytics: Your consent, to understand app activity and improve the game. You can withdraw consent in the privacy controls without losing game access or purchases.
  • Paid access and requested support: Performance of the service contract where necessary to provide purchases, access, restoration and support.
  • Security and essential operations: Our legitimate interests in authenticating requests, preventing abuse and maintaining fair, reliable services, balanced against players' rights.
  • Purchase reporting: Our legitimate interests in understanding and administering the game's business, limited to information necessary for that purpose.
  • Rights requests and legal obligations: Compliance with applicable obligations, including handling requests and retaining specifically required records.

Withdrawing consent does not make earlier lawful processing unlawful. We do not sell personal information or use it for third-party targeted advertising.

Providers and international processing

Google Firebase Analytics provides optional usage reporting. Analytics processing is separate from our London-hosted gameplay backend and can involve international processing under Google's applicable terms and safeguards. You may contact us for information about those arrangements.

The native online backend is hosted in Google Cloud's London region, and Cloudflare provides DNS for its API domain. Google Play handles store transactions, RevenueCat provides purchase/access services, Microsoft 365 provides our support mailbox. Google Cloud hosts this native privacy page, while Perplexity hosts the legacy website.

Some providers process information internationally; a London server does not mean every purchase, support or technical record stays in the UK. Relevant provider terms describe their processing and transfer arrangements, including Google Cloud's data-processing terms, RevenueCat's DPA and UK transfer provisions, and Microsoft's data-protection terms.

Google's independent service and billing records are subject to its own privacy practices. You may contact us for information about safeguards relevant to processing on our behalf (Google privacy policy).

How long we retain information

We review continuing retention needs monthly and use the following criteria rather than applying one period to every record:

  • Local careers and exports: Remain in your device or chosen storage until you or that storage remove them. We cannot recover them from the leaderboard.
  • Optional analytics: The property's ordinary event-level retention is set to two months and user-level retention to fourteen months, with new activity refreshing the user-level period. These controls do not impose a universal deletion deadline on all analytics information or standard aggregated reports. Device-private request references remain until forgotten, displaced by newer references beyond the twenty-reference limit, or removed with app storage.
  • Online identity and ranking information: Kept as needed to provide those services, subject to withdrawal, deletion requests and review of inactive or unnecessary records.
  • Purchase and entitlement records: Kept as needed for access, restoration and purchase support. Any separate accounting or dispute retention must be justified by the applicable obligation or claim.
  • Support correspondence: Kept as needed to resolve the issue and retain a proportionate record of its outcome, with longer retention justified by a specific obligation or dispute.
  • Security and deletion evidence: Limited records may be retained to investigate abuse, document a rights request and prevent erased identities being restored.
  • Backups: New routine backend backups become eligible for deletion after 30 days, followed by the storage provider's seven-day soft-delete recovery period. Processing is asynchronous, so this is not an exact final-erasure deadline; older restricted deployment copies and the minimal deletion register are handled separately and reviewed against continuing need (Google lifecycle handling).

We do not promise automatic deletion of every record after 90 days, 12 months or 24 months. If information is retained following a request, we will explain its scope, reason and applicable period or criteria.

Request account or data deletion

For optional analytics, include saved analytics references if available and say that the request concerns Firebase Analytics. A reference is not a password, but it is personal request information: send it privately. We assess requests proportionately, submit applicable requests to Google and distinguish acknowledgement from completed processing. Analytics references are different from leaderboard IDs, purchase Support IDs and Firebase app registration IDs. Requests concerning those other services are handled separately.

Email matthew@carp-tycoon.uk with the subject Carp Tycoon data request. Tell us whether you want full online-identity deletion or a specific category removed, such as a leaderboard entry; you can also use this route for access or correction.

If available, include your current or previous leaderboard ID. For purchase-related records, include your private Support ID; if you do not have an identifier, explain which version you used and when.

In the native app, open Privacy & purchase information → Request access or deletion of data → Open email draft. These controls are available from the privacy information, including while subscription access is locked; review the email and send it yourself.

Opening an email draft does not send the request, delete server data, remove local careers or cancel a subscription. Do not send passwords, authentication tokens, payment-card details or unredacted bank statements.

We may ask for proportionate information to verify ownership and scope. A public nickname or copied Support ID alone is not proof that the records belong to you.

Where deletion applies, we remove relevant online identity, leaderboard, associated gameplay, authentication and other personal records within the verified scope, and take appropriate action with processors. We separately assess relevant purchase/support records and explain any information retained for a lawful reason.

We keep a restricted deletion record outside player-database rollback and reconcile applicable erasures before an older backup is returned to live use. We distinguish completed live deletion from processor or backup work still pending; local careers and exported files remain in your own storage unless you remove them.

Providers may retain information temporarily in recovery storage or process deletion asynchronously. We will not treat acceptance of a request as proof of completed erasure, or claim to control every independent Google record (Microsoft deletion handling, RevenueCat's asynchronous deletion API).

Deleting personal data does not cancel a Google Play subscription. Manage cancellation through Google Play; RevenueCat customer deletion does not automatically cancel a mobile-store subscription (RevenueCat deletion guidance).

Your rights and complaints

Depending on the circumstances, you may request access, correction, erasure, restriction or portability, object to processing, and withdraw consent. These rights have conditions and lawful exceptions.

An erasure request normally requires a response without undue delay and within one calendar month. We will explain any necessary identity checks or permitted extension rather than promising that every request is completed within 48 hours (ICO erasure guidance).

Please contact us if you have a concern about our handling of information. You can also complain to the Information Commissioner's Office or another applicable supervisory authority.

Younger players

Carp Tycoon is intended for teenagers and adults aged 13 and over, not children under 13. A store content rating is separate from this intended audience, and we do not claim to verify every player's age.

You can play without joining the public leaderboard. Avoid personal or school details in a nickname, and ask a parent or guardian before making purchases; parents and guardians can contact us about a child's information.

Older game versions and changes to this notice

The older web game and Android web wrapper differ from the native app. Depending on the version and features used, legacy records can include full server-save data, email-linked recovery or entitlement information, gameplay events and historical Payhip purchase references; browser versions also use local browser storage for game state and settings.

These records are not silently migrated into native careers. Use the same privacy contact for legacy requests and tell us that your request concerns the older game; closing the web game does not remove your ability to request information or deletion.

We will keep the privacy/deletion resource available and update the date when this notice changes. Material changes will be communicated through an appropriate available channel, without implying that an automatic in-game or email notification system is already installed.