COPADERBY Beta

Privacy Policy

COPADERBY is a football career game. Most of what you do in it stays on your device. This page explains the small amount of information that reaches our servers, why, and for how long.

Effective date: 29 October 2026 · Updated: 29 October 2026

Who is responsible

The operator and controller of COPADERBY is Oliver Mehring. Full operator details are in the Imprint.

Contact for privacy questions: support@copaderby.com

On your device

Your careers, saves, settings, achievements and similar game progress are stored locally on your device. They are not uploaded to us unless you use an online feature that needs them, such as submitting a score to a leaderboard. Notifications you opt into are scheduled on your device.

Daily and 1V1 leaderboards

When you submit a score to the Daily board or a 1V1 board, our backend may store:

  • your display name
  • your score
  • your nationality code or nation, where supplied
  • your tier
  • your club, where supplied

Why: to run the Daily and 1V1 leaderboards. These entries are shown to other players on the same board, so choose a display name you are happy to share.

Board and group records currently expire after 21 days

Optional product analytics

Analytics is optional and off until you agree. The app asks once, with Allow analytics and No thanks as equal choices. If you decline, nothing is sent and the game works exactly the same. You can switch Analytics on or off in the app's menu at any time; switching it off stops sending immediately and removes the analytics identifier from your device.

If you agree, the app sends usage events to PostHog Cloud EU, a product-analytics service whose EU infrastructure is hosted in the EU. The events describe how the game is used, for example:

  • app opened, and a random session identifier
  • careers started and completed, and the game mode (free play, Daily, 1V1)
  • major progression milestones, such as seasons completed and the first decision
  • career summary numbers, such as the final score, number of clubs and titles
  • use of the Daily, 1V1, leaderboards and sharing
  • app version, language and platform

Events are linked to a random installation identifier that is created only after you agree. It is not derived from your name, account, device or advertising identifiers.

We do not send your display name, email, club or career history, free text, 1V1 codes or an advertising identifier to PostHog. There is no session replay, no screen recording and no automatic capture of taps. PostHog receives the IP address of the connection, as any internet service does, but our project is set to discard it: IP addresses are not stored with the analytics events, and we switch off PostHog's IP-based location lookup.

Because the identifier is persistent, this data can still count as personal data under the GDPR. Legal basis: your consent, which you can withdraw at any time in the app.

Why: to understand how the Beta is played — where players continue, where they stop and which modes they use — and what to improve.

Kept only as long as needed for Beta product analysis; you can ask for deletion at any time

Earlier anonymous usage counters

Earlier Beta builds sent anonymous daily event counters (for example app opened or career started) to our backend, stored as daily totals per event and app version, with no name, account or identifier. The current app no longer sends them; existing totals expire automatically.

Usage records currently expire after 60 days

Crash diagnostics

If the app hits an error, our backend may receive:

  • the error message
  • the source file and line number
  • the stack trace
  • the app version

Why: to diagnose and fix crashes.

Crash records currently expire after 21 days

Where it is processed

Our backend runs on Cloudflare Workers and stores data in Workers KV. The production storage is configured for the EU jurisdiction. Like any internet service, Cloudflare handles the network connection (including your IP address) to deliver requests. Our backend uses the IP address only briefly, in memory, to limit abusive request floods; we do not write it into the leaderboard, usage or crash records.

Optional product analytics (see above) is processed by PostHog on its EU Cloud.

What we don't do

  • The app contains no advertising network and does not access your device's advertising identifier.
  • We do not track you across other companies' apps or websites, and analytics is not used for advertising.
  • There is no session replay or screen recording.
  • We do not sell personal data.
  • This website sets no cookies and uses no analytics or tracking.

Your choices

Local data

You can remove your local COPADERBY data at any time with the app's built-in delete option (Delete all data).

Analytics

Switch Analytics off in the app's menu at any time. To have analytics data deleted, contact us with the request; we can find your events once you tell us, from the same device, when you used the Beta.

Server-side data

For questions about, or deletion of, leaderboard entries or diagnostic information held on our servers, contact COPADERBY support at support@copaderby.com (see also the Support page). Without any action, these records expire automatically after the periods listed above.

Changes

COPADERBY is in Beta and this policy may change as features change. We will update the effective date above when it does.