Cookie Policy

This Cookie Policy lists every cookie set by greendotplay.org, explains what each one does, how long it lasts, and the legal basis under which we set it. GreenDotPlay uses only first-party cookies and does not embed any third-party tracker.

1. Data controller

GreenDotPlay d.o.o., ul. Slobode 27, 81000 Podgorica, Crna Gora. DPO: dpo@greendotplay.org. Supervisory authority: Agencija za zaštitu ličnih podataka (AZLP) reg. no. 05-030/24-2718.

2. The three cookies we set

2.1 gd_session — session cookie

Purpose: stores your signed Green Dot session token after a successful magic-link sign-in. Without it, you cannot stay signed in to your account. Retention: up to 90 days absolute expiry, extended by activity within that window. Legal basis: strictly necessary (Article 5(3) ePrivacy Directive exemption — necessary for the service explicitly requested by the user). Cross-site: no, first-party under greendotplay.org, SameSite=Lax. Access: HttpOnly, not readable by JavaScript.

2.2 gd_prefs — preferences cookie

Purpose: stores your cabinet preferences (dark-mode choice, keyboard-layout choice for the puzzle board, city-display opt-in/out). Without it, your preferences would reset on every sign-in. Retention: 1 year. Legal basis: consent under Article 6(1)(a) GDPR — you can decline in the cookie banner and Green Dot still works, minus these preferences. Cross-site: no, first-party, SameSite=Lax.

2.3 gd_cookie — consent record cookie

Purpose: records your choice in the cookie banner (accept or decline preferences). Without it, the banner would reappear on every page. Retention: 1 year. Legal basis: strictly necessary (records a legally-required consent state). Cross-site: no, first-party, SameSite=Lax.

3. What we do not set

We do not set advertising cookies. We do not set analytics cookies (we run server-side aggregation instead). We do not set social-media cookies (no share buttons). We do not use fingerprinting scripts, no browser-canvas fingerprinting, no WebRTC IP leakage. We do not embed any third-party iframe that could set third-party cookies.

4. Local storage and session storage

The magic-link flow briefly uses sessionStorage to hold the pending email so the "email sent" message survives an accidental page refresh — automatically cleared when the tab closes. The optional dark-mode preference may be cached in localStorage for instant application before the server cookie loads.

5. Withdrawing consent

Click the small "Cookie preferences" link in the footer of every page. Toggle the preferences cookie off; the gd_prefs cookie is deleted immediately. You cannot decline the strictly-necessary gd_session and gd_cookie without also declining to sign in — that is the nature of a strictly-necessary cookie.

6. Managing cookies in your browser

Every modern browser allows you to view and delete cookies. In Chrome: Settings → Privacy → Cookies. In Firefox: Settings → Privacy → Cookies. In Safari: Preferences → Privacy → Manage. Deleting the gd_session cookie signs you out of your Green Dot account immediately; nothing else is affected.

7. Why so few cookies?

Because every additional cookie is a small liability. Each cookie is a piece of state we have to reason about, document, defend to a regulator, and expose to you in this policy. We ship the three we need and no more. A game does not need analytics cookies to know how many players signed in today — a server-side counter incremented on the sign-in endpoint is more accurate, more private and cheaper to operate. A game does not need advertising cookies because we do not run advertising. A game does not need social-media cookies because we do not embed social share widgets on greendotplay.org. The absence of a cookie is not an oversight; it is a choice.

8. Third-party embeds and iframes

greendotplay.org does not embed any third-party iframe capable of setting cookies. The Google Fonts stylesheet is loaded from fonts.googleapis.com without cookies (the CSS response does not set any cookie in modern browsers). The font files themselves are loaded from fonts.gstatic.com, again without cookies. No YouTube embeds, no Twitter embeds, no Facebook widgets, no Google Maps embeds, no Stripe elements inline (payment happens in a redirected flow rather than an in-page iframe).

9. Cookies on the checkout flow

The subscription checkout flow redirects to our payment provider's domain to enter card details. On that provider's domain the payment provider may set its own cookies subject to its own cookie policy — we link to it clearly on the checkout page before the redirect. On return to greendotplay.org, no additional cookie is set on our side beyond the ones listed in Section 2.

10. Do Not Track and Global Privacy Control

Browser signals such as Do Not Track and Global Privacy Control indicate a user preference against tracking. Since we do not do cross-site tracking of any kind, these signals do not materially affect our behaviour. We still honour them where applicable: a browser sending GPC will have the "preferences cookie" defaulted to declined in the cookie banner, requiring an explicit opt-in for the gd_prefs cookie to be set.

11. Log data versus cookies

Cookies live in your browser. Server logs live on our servers. They are separate categories with separate legal bases and retention periods. See Section 16 of the Privacy Policy for our log-retention rules. No cookie is used to correlate log data across sessions for tracking purposes.

12. Changes to this Cookie Policy

Material changes to this Cookie Policy — the addition of a new cookie, a change of retention period, a change of legal basis — are notified to every active Green Dot account holder by email at least thirty days in advance. The historical versions of this Cookie Policy remain accessible on request to dpo@greendotplay.org. The cookie banner reappears on the next visit after a material change, allowing you to renew or update your consent.

13. How we test the cookie banner

The cookie banner is manually tested every calendar quarter across the four major browser engines (Blink, Gecko, WebKit, and their major mobile forks), in both light and dark colour schemes, at three viewport widths (mobile 375 pixels, tablet 768 pixels, desktop 1440 pixels), with and without an active Green Dot session. We verify that the banner cannot be dismissed accidentally by a keyboard user, that the decline button is at least as prominent as the accept button, that the "learn more" link genuinely leads to this page, and that a declined preference cookie is not silently set on a subsequent visit. Failures on any of these tests block a production release.

14. Cookie choices for the visually impaired

The cookie banner is fully keyboard-navigable, with a logical tab order and explicit focus outlines. Screen-reader labels are provided in English. Accept, decline and learn-more buttons are semantic HTML button and anchor elements — never divs pretending to be buttons. High-contrast mode of the operating system is respected: banner colours switch to the user's preferred palette rather than forcing our own. If any accessibility issue with the banner is observed, please report it to dpo@greendotplay.org — we treat such reports as high-priority bugs.

15. Cookie choices when signing in to a shared computer

If you sign in to a Green Dot account on a public or shared computer (a hotel business centre, a coworking desk, a friend's laptop), you should decline the preferences cookie (so your dark-mode preference is not saved for the next user), sign in normally, and remember to click "sign out" from the top nav before leaving the machine. Signing out invalidates the gd_session cookie on our server. Additionally you can visit Account → Sessions and devices from a different machine and remotely invalidate any forgotten session — full detail on /session-and-devices.

16. Contact

Any cookie-related question: dpo@greendotplay.org. Postal: GreenDotPlay d.o.o., ul. Slobode 27, 81000 Podgorica, Crna Gora. Complaints under the Montenegrin Personal Data Protection Act may be lodged with Agencija za zaštitu ličnih podataka (AZLP) reg. no. 05-030/24-2718; EU-domiciled users may lodge complaints with the supervisory authority of their country of residence.