Cookie & Tracking-Technology Policy
This policy describes the cookies and similar browser-storage technologies (localStorage, sessionStorage, pixels, beacons, SDKs that read or write to terminal equipment) that Parkmo and its sub-processors set when you use our websites.
For the wider data-protection context see the Privacy Policy.
1. Legal basis
- Strictly-necessary cookies (session, CSRF, load-balancer routing, consent state): Art. 6(1)(f) GDPR + § 25(2) TTDSG exception for “strictly necessary” technologies. No consent required.
- All other cookies and SDKs (analytics, marketing, session-replay, A/B testing): Art. 6(1)(a) GDPR consent + § 25(1) TTDSG prior consent. We must obtain freely-given, specific, informed, unambiguous opt-in before the cookie is set or the SDK is loaded.
1.1 What qualifies as “strictly necessary”
§ 25(2) Nr. 2 TTDSG exempts storage of, and access to, information on terminal equipment when it is “unbedingt erforderlich” for a telemedia service the user has expressly requested. The test is narrow:
- Necessary for the service the user asked for, not necessary for our business.
- No banner is needed for items that pass this test.
- The exemption covers all storage and access, not just cookies —
localStorage,sessionStorage, IndexedDB, service-worker caches, and fingerprinting techniques are subject to the same test.
Passes the test on Parkmo surfaces today:
- Ory Kratos session cookie on
app.parkmo.io— without it the user cannot remain signed in. - CSRF token — required by the user’s own form submission.
- Consent state itself — required to honour the user’s choice.
- Language toggle the user clicked.
- Cloudflare
__cf_bm— strictly-necessary security/anti-bot. - Booking-form draft state in
sessionStorageonbooking.parkmo.io— preserves a partially-completed booking the user has explicitly started.
2. Categories
We classify cookies and tracking technologies into four categories. The consent banner exposes a toggle per category.
2.1 Strictly necessary
Set without consent.
| Name | Set by | Purpose | Storage | Lifetime |
|---|---|---|---|---|
ory_kratos_session_* |
Parkmo / Ory Kratos | Session authentication for app.parkmo.io |
HTTP cookie, Secure, HttpOnly, SameSite=Lax |
21 days (fixed) |
csrf_token |
Parkmo | CSRF protection on form submissions | HTTP cookie, Secure, HttpOnly, SameSite=Strict |
Session |
cookieconsent_status |
Parkmo | Persist the user’s consent choice across pages | localStorage |
Until cleared or revoked |
2.2 Functional (preferences)
Set after consent in this category.
| Name | Set by | Purpose | Storage | Lifetime |
|---|---|---|---|---|
lang |
Parkmo | Remember language selection and its regional date and number formatting across visits | HTTP cookie | 12 months |
| Booking-form draft state | Parkmo | Preserve a partially-completed booking on page reload | sessionStorage |
Tab session |
2.3 Analytics (statistics)
Set only after explicit opt-in to this category. No analytics tool is currently deployed on the marketing site.
| Name | Set by | Purpose | Storage | Lifetime |
|---|---|---|---|---|
_ga, _ga_* |
Google Analytics 4 (gtag.js) | Distinguish unique visitors; aggregate page-view statistics | HTTP cookie, first-party | 24 months |
2.4 Marketing
Set only after explicit opt-in to this category. Currently none are deployed.
3. Consent banner UX requirements
The banner must satisfy:
- First load: no non-essential cookie or SDK is set, and no consent-bearing third-party request is made, before the user has acted on the banner.
- Equal-weight choices: “Accept” and “Reject” presented with the same visual prominence (size, colour, position).
- Granular toggles: at minimum one toggle per category above (strictly necessary is locked on). Bulk “accept all” and “reject all” are also offered.
- Withdraw consent as easily as it was given: a persistent “Cookie settings” link in the footer that reopens the banner.
- No nudging dark patterns: no pre-ticked boxes, no implicit consent via “continuing to use the site”, no auto-dismiss on scroll.
- Record of consent: log the user’s choice with a timestamp, the banner version, and the cookie categories accepted. 90-day retention after withdrawal.
- Per-locale text: at minimum DE, EN, FR, IT, NL, ES, PT, DA, SV, PL.
4. Google Consent Mode v2
Where Google Analytics 4 is deployed we use Google Consent Mode v2. Default state:
analytics_storage: deniedad_storage: deniedad_user_data: deniedad_personalization: deniedfunctionality_storage: deniedpersonalization_storage: deniedsecurity_storage: granted(the “strictly necessary” leg for Google’s own anti-fraud)
When the user opts in to the Analytics category in our banner, we update analytics_storage to granted. No other Consent Mode signal is granted unless the user explicitly opts in to the Marketing category (none active today).
5. Booking app & tenant app
booking.parkmo.ioand its country-TLD variants currently set no analytics cookies and load no third-party SDKs. The only storage issessionStoragefor the partially-completed booking — strictly necessary, the user expressly started a booking.- From the launch of paid bookings, the payment step of the booking flow loads Stripe.js (Payment Element), which sets Stripe’s fraud-prevention cookies
__stripe_mid(approx. 1 year) and__stripe_sid(approx. 30 minutes). They are loaded only on the payment step, after you have chosen to pay, and are strictly necessary for secure payment processing (fraud prevention integral to the payment you requested). The setting party is Stripe Payments Europe, Ltd. — see the Privacy Policy § 3.2.2 and Stripe’s privacy policy. app.parkmo.iois authenticated and the user is on notice via the tenant’s terms; it sets only the strictly-necessary session and CSRF cookies above. No analytics, no session-replay.
6. How to control cookies
- In our banner at
parkmo.io(and country-TLD equivalents): click “Cookie settings” in the footer to reopen and change your choices. - In your browser: every modern browser allows blocking or deleting cookies. Blocking all cookies will break the authenticated app’s sign-in flow.
- Browser-level signals: the Global Privacy Control signal (
Sec-GPC: 1) is not currently honoured. Nothing on our sites reads the header, so sending it does not change what is loaded. An earlier version of this policy said the opposite; that was incorrect and is corrected here. Until it is implemented, please use the cookie banner or your browser’s cookie settings described above — both of which do work.
7. Changes
This policy is versioned alongside the master privacy policy. Material changes (new categories, new vendors, new lifetimes) will cause the consent banner to re-prompt all visitors and reset their previous choice for the affected category.