Privacy

Ride Amsterdam is a prototype, and it collects as little as it can. You can play the whole game without an account. This page says plainly what is stored and how to get rid of it.

Signing in is optional

You never have to sign in to play. If you press Sign in with Google, we use Firebase Authentication to sign you in with your Google account. From that account we only take your basic profile — display name, email address and a user identifier — so that your progress and your feedback can be attached to you. We do not post anything to Google or anywhere else on your behalf.

What we store

Local storage

The game keeps preferences, drafts, caches and signed-out progress in your browser’s local storage (for example canalRecall.preferences.v1 and mapRecall_reviewStates_v1). It is not a tracking cookie. Clearing site data in your browser removes it; guest progress is only uploaded if you later sign in.

Error monitoring

We use Sentry to catch crashes and collect performance traces, so bugs get found and fixed. Reports contain technical detail such as the page, build and browser. We do not run advertising or sell data, and there are no advertising or third-party tracking cookies.

Abuse prevention

Requests to our backend pass through Firebase App Check, which uses reCAPTCHA to confirm the request comes from the real app rather than a bot. Google describes how it works in its own privacy policy; it is not used for advertising.

Deleting your data

Email [email protected] to ask for a copy or a deletion of the data tied to your account. Say which account you signed in with, and we will delete your stored progress and feedback. Data kept only in your browser can be removed at any time by clearing site data.

Questions about the sources and licences themselves? See Credits & data licences. To report something inside the game, use the Feedback button.

Last updated 2026-10-17.