Privacy
Updated 29 September 2026
Berlin Runner is operated by Tamás Szőke, Switzerland. For privacy questions or account requests, email support@berlin-runner.com.
You can play as a guest without an account. Your saved guest progress stays on this device; aggregate usage statistics are described below. Unless you open sign-in, the game does not contact our sign-in provider. When you sign in with Google, your account progress is saved online and synchronized across devices. The game shows when a cloud save has completed or is waiting for a connection.
Google sign-in and your account
If you choose Google sign-in, Google shares your account identifier, name, email address and, when available, profile picture with our authentication provider, Clerk. Clerk stores your Berlin Runner account and manages authentication, verification and sessions, and may run a Cloudflare Turnstile check to stop automated sign-ups. Berlin Runner uses your name and email to show your signed-in account.
We do not receive your Google password. We request basic identity permissions only, without access to your Gmail messages, contacts or Google Drive. Google account information is used to provide sign-in, account support and security; it is not sold or used for advertising.
Progress, settings and browser storage
When signed in, we store your game progress, learned words, results, streaks and custom learning decks in Cloudflare D1, linked to your Clerk account identifier. We use this information to restore and synchronize your game. The progress database is stored in the European Union. It does not contain Google passwords or payment details.
Your browser keeps an account-specific copy of your progress, pending saves for offline use, and a note that you signed in, so the game reconnects to your account next time. Guest progress is separate; we ask before copying it into an account. Signing out switches to guest progress but does not erase cached account saves. Someone with access to the same browser profile may be able to inspect its local data.
Game settings (sound, voice, speed, selected deck and chosen runner), the words shown while the game loads, whether you have finished the tutorial, and your guest choice also stay in this browser. This storage only makes the features you use work; it is not used for tracking or advertising.
Changes made offline or while cloud saving is unavailable remain on the device until successfully synchronized. Clearing site data before synchronization can permanently remove those changes and guest progress. You can download a progress backup from the account popup.
The site caches game files for faster loading and offline use. Once you open sign-in, Clerk uses cookies and related browser storage to maintain and protect sign-in sessions. Blocking this storage can prevent sign-in. This version does not implement purchases or in-game advertising.
Services used to deliver the site
Cloudflare hosts berlin-runner.com and protects it against attacks. The game’s fonts and software libraries are served from berlin-runner.com itself, so no other content provider is contacted. Your browser contacts Clerk only when you open sign-in, return from Google sign-in, or are already signed in on this device. If you play as a guest, the game itself contacts only Cloudflare; the exceptions are error reports, when enabled, and your device’s speech service, both described below. These services receive technical information such as your IP address, browser information, requested addresses and request times.
When enabled, Cloudflare Web Analytics counts visits, referring sites, countries and device types without cookies or identifiers stored on your device.
We also send aggregate game events to Cloudflare: practice and challenge starts, completions, score and mistake counts, tutorial choices, sign-in attempts, share actions, and approximate active and playing time. Reports use broad country, device, runner and campaign categories. We do not send word lists, names, email addresses, account identifiers, full referral URLs or recordings of your screen. We do not store a visitor identifier or follow guests between visits. Game events are retained for three months in Cloudflare Analytics Engine.
Clerk sends signed account-created, sign-in and account-deleted notifications to our Cloudflare server. It verifies the notification and retains only its delivery identifier, event type and date to count registrations and sign-ins without counting delivery retries twice. Account profile information in the notification is not retained in this analytics record. These aggregate account counts are kept long term.
Native sharing reports whether the device accepted or cancelled the share action; it does not tell us which app you chose, whether a post was published, or how many people saw it. Shared links contain general campaign labels so we can count visits from them.
You can turn this off on this device. We also respect Global Privacy Control and Do Not Track for browser analytics. Account and hosting records needed to operate the service are separate.
When error reporting is enabled and the site runs into an error, a technical error report is sent to Sentry. It contains the error message and where in the code it happened, the page address, browser and device type, and the app events just before the error. Nothing is sent to Sentry unless an error occurs, and reports never include your account details.
Read-aloud pronunciation uses your browser or device’s speech service. Depending on the selected voice, that service may process the words online. You can turn voice off in Settings.
Where your information is processed
Your cloud progress is stored in the European Union. Clerk, Google and Sentry are based in the United States, and Cloudflare runs servers worldwide, so information can also be processed in the United States and other countries where these providers operate.
All four providers are certified under the EU–U.S. and Swiss–U.S. Data Privacy Framework, which the European Commission and the Swiss Federal Council recognise as ensuring adequate protection. Where the framework does not apply, the providers rely on standard contractual clauses approved by the European Commission and recognised in Switzerland. Their terms describe how they handle data:
Why we use your information
Berlin Runner follows the Swiss Federal Act on Data Protection (FADP). For people in the European Union or European Economic Area, the General Data Protection Regulation (GDPR) also applies, and we rely on these legal bases:
- Sign-in, your account and cloud saves: to provide the service you ask for (GDPR Art. 6(1)(b)).
- Hosting, security, error reports and visit statistics: our legitimate interest in running a secure, working game and understanding how it is used (Art. 6(1)(f)).
- Support requests: to answer you, as part of the service (Art. 6(1)(b)) or in our legitimate interest in helping players (Art. 6(1)(f)).
We do not sell your information, use it for advertising, or make automated decisions about you.
Children
Signing in needs your own Google account, and Google sets a minimum age for accounts in each country. Children below that age can play as guests: guest progress stays on the device and is not sent to us.
Support and optional diagnostics
Support email is forwarded by Cloudflare to our dedicated Gmail inbox. We use your email address and message contents to answer your request. If you choose to share a diagnostic report, it can include device and browser details, game events, errors and performance timings. These optional diagnostic reports stay in your browser until you export or share them.
Retention and your choices
Account information remains with Clerk while your account exists. Cloud progress and save-request identifiers remain with Berlin Runner until you ask us to delete them. We keep up to ten previous cloud saves for recovery; save-request identifiers prevent duplicate updates. Cloudflare also keeps database recovery backups under its own retention terms. Support correspondence is kept for as long as needed to resolve your request and any follow-up; service providers keep operational logs and backups under their own retention terms.
You can stop future Google account sharing through your Google account connections. Disconnecting Google does not itself delete information already stored with Clerk or erase cloud or local game progress. Deleting an account through Clerk does not automatically delete our separate progress database; contact support for that deletion. Use your browser’s site-data controls to remove local progress and settings.
You can ask for access to your information, a copy of it, its correction or its deletion, and you can object to processing based on legitimate interests or ask us to restrict it. Email support@berlin-runner.com; we may need to verify that the account is yours. You can also complain to a data protection authority: in Switzerland, the Federal Data Protection and Information Commissioner (FDPIC); in the EU or EEA, the authority where you live or work.
Changes
We will update this notice when the service changes. Before using Google account data for a new purpose, we will explain the change and obtain any required consent.