Publication pending. This page accurately describes the game’s data flow. The public contact email, retention policy and actual hosting/provider setup still need to be finalised before public collection starts. Use test data while the game is in preview.
Jacob Schmohl · Kolonnenstr. 8 · 10827 Berlin · Germany. The public privacy contact email will be added before launch.
Playing creates a browser cookie for your session. The server stores a random visitor identifier, challenge inputs, score, selected runner and timestamps. It also counts visits, campaign source tags, shared-link referrals and ticket-link clicks. We do not send these events to an external analytics service. A public leaderboard shows nicknames and scores, never email addresses.
If you enter your email to claim a perk or save a score, the server stores your email, any supplied nickname, related run and confirmation request. The discount step does not require email confirmation; leaderboard entry and account recovery do. Newsletter consent is a separate, unchecked choice. If chosen and confirmed, the exact consent wording, its version and timestamp are recorded. Entry without newsletter signup works the same way. Email addresses are not embedded in challenge or ticket links.
In local mode, confirmation emails are written to a private local test outbox; no email is sent. Local confirmations are marked as tests and excluded from the real newsletter export. If configured for live delivery, verification is sent through Resend. Mailchimp integration is prepared for separately confirmed newsletter signups, but is inactive until connected. Provider status is reported separately from consent being recorded.
To access an earned discount, enter your email address, open the Coffee Rave WhatsApp invitation and confirm that you have joined. Existing members can confirm in the same way. Before email confirmation, we store your email, invitation clicks and self-reported membership with this browser’s perk record. This does not sign you into an account. After email confirmation, the perk can be saved to your account. We cannot automatically verify membership, do not read WhatsApp messages and do not collect your phone number through this game. WhatsApp is a separate service. Playing, leaderboard entry and optional newsletter signup do not require this community step.
The proposed basis for processing requested game accounts, competition entries and ticket perks is Article 6(1)(b) GDPR. Optional newsletter marketing relies on consent under Article 6(1)(a). Security, abuse prevention and proportionate first-party performance measurement rely on the legitimate interests of operating a fair, reliable game under Article 6(1)(f). These purposes and the deployment configuration must be reconciled before this draft is published.
Subject to the applicable conditions, you may request access, correction, deletion, restriction and portability of your personal data. You may object to processing based on legitimate interests. Newsletter consent may be withdrawn at any time through the unsubscribe link, without affecting earlier lawful processing. You may lodge a complaint with a supervisory authority, including the Berlin Commissioner for Data Protection and Freedom of Information. You can also contact the controller by post at the address above.
Confirmation and account-access emails use Resend when live delivery is enabled. Separately confirmed newsletter signups use Mailchimp when connected. These services may process data outside the European Economic Area; applicable processing agreements and transfer safeguards must be verified for the accounts used before launch. Opening WhatsApp or Eventbrite takes you to a separate provider. The public game host and its retention of access logs must also be identified before launch.
Provider information: Resend data processing · Mailchimp data processing. Rights information: GDPR.
Game data is stored in a private server database. The current implementation retains it until the operator removes it. Confirmation links expire after 24 hours; unfinished submissions expire after two hours. These are link limits, not automatic deletion periods. A retention and deletion policy must be defined and implemented before public launch. Eventbrite is a separate service and handles ticket checkout under its own terms.