Skip to main content
Recolor the Past

Cookie Policy

Last updated: 8 October 2026

We keep cookies to a minimum. We do not set non-essential cookies without your consent, and we do not use advertising or cross-site tracking cookies.

Strictly necessary (always on)

CookiePurpose
Session / authKeep you signed in securely
Anonymous demoTrack your free-preview allowance without an account
Consent choiceRemember your cookie preferences

These are required for the service to function and are exempt from consent under the ePrivacy rules.

Bot protection

We use Cloudflare Turnstile to protect the free-preview endpoint from abuse. Turnstile is privacy-preserving and does not track you across sites.

Managing cookies

You can also clear or block cookies in your browser settings; doing so may sign you out or reset your demo allowance.

Mobile version scope (English notice)

The reporting controls described below apply to Recolor the Past mobile version 1.0.8 (build 16), which introduces the reporting readiness gate. In this release candidate, reporting remains disabled until the documented readiness requirements are approved. These controls are not a statement about older installed versions.

Older installed versions may send SDK identifiers, native stack traces, error content and queued diagnostic data under their earlier settings and cache behavior. Use Settings controls where available and update when version 1.0.8 (build 16) becomes available. A switch in an older version does not guarantee that native SDK activity or previously queued reports have stopped.

Error monitoring (Sentry)

Limited technical crash reports default on only after current rules and 18+ confirmation in a reviewed reporting build. Disable them in Account settings; your saved opt-out persists. Age and terms agreement are not diagnostics consent. Reports exclude photos, messages, filenames, credentials, account/install identifiers, screenshots, sessions, replay, profiling and network breadcrumbs. Connection IP may still be processed; reports are not assumed anonymous. Operational reporting requires the documented legitimate-interest and device-access assessment. Unreviewed builds do not send reports.