ERTZU_PRIVACY_CONSENT
- Provider
- ERTZU (first party)
- Storage type
- Cookie
- Scope
- Entire ERTZU domain
- Purpose
- Stores the current consent version, the decision for or against optional analytics and the decision time so the choice can be respected and evidenced.
- Content
- Version number, “analytics” or “necessary”, and timestamp; no user identifier
- Trigger
- Making a choice in the consent panel
- Duration
- 6 months
- Attributes
- Path=/; SameSite=Lax; Secure over HTTPS; not HttpOnly
- Legal basis
- Section 25(2)(2) TDDDG; Art. 6(1)(c) GDPR together with Art. 7(1) GDPR – implementing and evidencing the privacy choice.
ERTZU_LOCALE
- Provider
- ERTZU (first party)
- Storage type
- Cookie
- Scope
- Entire ERTZU domain
- Purpose
- Remembers the language explicitly selected by the user and serves the corresponding German or English route.
- Content
- Language code “de” or “en”
- Trigger
- Selecting a language
- Duration
- 1 year
- Attributes
- Path=/; SameSite=Lax; Secure over HTTPS; not HttpOnly
- Legal basis
- Section 25(2)(2) TDDDG – providing the language version explicitly selected by the user.
theme
- Provider
- ERTZU (first party)
- Storage type
- Local browser storage
- Scope
- This browser on this device
- Purpose
- Applies the explicitly selected light, dark or system appearance without a visible colour flash during loading.
- Content
- “light”, “dark” or “system”
- Trigger
- Selecting the appearance
- Duration
- Until the choice is changed or browser data is deleted
- Attributes
- Local only; no cookie attributes
- Legal basis
- Section 25(2)(2) TDDDG – applying a display function explicitly selected by the user.
listings-cols
- Provider
- ERTZU (first party)
- Storage type
- Local browser storage
- Scope
- This browser on this device
- Purpose
- Remembers the explicitly selected number of product columns in the perfume catalogue.
- Content
- Column count from 1 to 5
- Trigger
- Selecting the grid view
- Duration
- Until the choice is changed or browser data is deleted
- Attributes
- Local only; no cookie attributes
- Legal basis
- Section 25(2)(2) TDDDG – applying a display function explicitly selected by the user.
ertzu:buy-checkout:<Produkt>:<Füllstand>:<Größe>
- Provider
- ERTZU (first party)
- Storage type
- Session storage
- Scope
- Current browser tab
- Purpose
- Allows a payment flow started by the user to be resumed for a short time after a reload.
- Content
- Product variant, amount, currency, order reference and short-lived Stripe client secret; no shipping address
- Trigger
- Starting payment in checkout
- Duration
- Technically valid for 15 minutes; also removed on completion or when the browser tab ends
- Attributes
- Current tab only; no cookie attributes
- Legal basis
- Section 25(2)(2) TDDDG; Art. 6(1)(b) GDPR – carrying out the purchase explicitly started by the user.
sb-<Projektkennung>-auth-token · sb-<Projektkennung>-auth-token.0, .1, …
- Provider
- Supabase / ERTZU
- Storage type
- Cookie
- Scope
- ERTZU authentication
- Purpose
- Maintains a sign-in started by the user, refreshes the session and protects authenticated areas.
- Content
- Encoded session and authentication data
- Trigger
- Sign-in, registration or session refresh
- Duration
- Until logout or session expiry; the installed library limits the cookie attribute to a maximum of 400 days
- Attributes
- Path=/; SameSite=Lax; Secure in production; technically not HttpOnly; may be split into multiple cookies
- Legal basis
- Section 25(2)(2) TDDDG; Art. 6(1)(b) GDPR – requested account and marketplace functions.
sb-<Projektkennung>-auth-token-code-verifier
- Provider
- Supabase / ERTZU
- Storage type
- Cookie
- Scope
- ERTZU authentication
- Purpose
- Protects the sign-in started by the user, in particular the Google OAuth callback, against tampering.
- Content
- Temporary PKCE code verifier
- Trigger
- Starting an OAuth sign-in
- Duration
- Until the sign-in flow completes or is cleared; technically no more than 400 days
- Attributes
- Path=/; SameSite=Lax; Secure in production; not HttpOnly
- Legal basis
- Section 25(2)(2) TDDDG; Art. 6(1)(b) and (f) GDPR – securely carrying out the requested sign-in.
__stripe_mid
- Provider
- Stripe
- Storage type
- Cookie
- Scope
- Payment and fraud-prevention environment
- Purpose
- Fraud prevention and secure processing of a payment flow started by the user.
- Content
- Technical browser identifier generated by Stripe
- Trigger
- Loading Stripe’s payment interface after payment is started
- Duration
- 1 year
- Attributes
- Set by Stripe; depends on the payment and browser context
- Legal basis
- Section 25(2)(2) TDDDG; Art. 6(1)(b) and (f) GDPR – payment security and fraud prevention.
__stripe_sid
- Provider
- Stripe
- Storage type
- Cookie
- Scope
- Payment and fraud-prevention environment
- Purpose
- Links security-relevant signals within the current payment flow started by the user.
- Content
- Technical Stripe session identifier
- Trigger
- Loading Stripe’s payment interface after payment is started
- Duration
- 30 minutes
- Attributes
- Set by Stripe; depends on the payment and browser context
- Legal basis
- Section 25(2)(2) TDDDG; Art. 6(1)(b) and (f) GDPR – payment security and fraud prevention.
ph_<Projekt-Token>_posthog
- Provider
- PostHog Cloud EU / ERTZU
- Storage type
- Local browser storage
- Scope
- This browser on this device
- Purpose
- Pseudonymous product analytics, minimised error diagnostics and individual-session screen recordings to detect usability problems (e.g. abandonment during checkout or selling), improving usability, reliability and marketplace flows.
- Content
- Random device/session identifier, sanitised page paths without query parameters, event names, public product references, browser/device characteristics and, for errors, the error class and non-personal digest. Additionally, screen recordings (clicks, mouse movement, page structure) of individual sessions on public pages: form input values (including address, contact and tax fields) are masked, as are selected displayed texts (e.g. email address, delivery name/city, tax ID); Stripe payment fields are never recorded; internal admin areas are fully excluded from recording. No names, email addresses, shipping addresses or payment secrets in plain text.
- Trigger
- Only after selecting “Accept”
- Duration
- In the browser until withdrawal or consent expiry after 6 months; server-side event retention according to the verified ERTZU PostHog project configuration
- Attributes
- Local storage only; autocapture, surveys, heatmaps, performance capture, feature flags and person profiles disabled; rage- and dead-click detection plus session replay active with masked form inputs and marked text fields, excluding the Stripe payment interface and admin areas; production limited to the Frankfurt EU endpoint or an ERTZU first-party endpoint
- Legal basis
- Section 25(1) TDDDG and Art. 6(1)(a) GDPR – voluntary consent that can be withdrawn at any time.
Vercel Web Analytics Script und Intake
- Provider
- Vercel Inc. / ERTZU
- Storage type
- Measurement request without browser storage
- Scope
- Cookieless audience measurement
- Purpose
- Aggregated measurement of page views, referrers and technical usage to improve the service.
- Content
- Sanitised page path without query parameters, referrer, timestamp, coarse geolocation, browser, operating system and device type; a daily hash instead of a cookie.
- Trigger
- Only after selecting “Accept”
- Duration
- Visitor hash 24 hours; reporting window according to the Vercel plan: 1 month (Hobby), 12 months (Pro) or 24 months (Plus/Enterprise)
- Attributes
- No cookies or local Vercel identifier; requests are not loaded before consent and paths are sanitised before sending; processing in the United States is possible
- Legal basis
- Art. 6(1)(a) GDPR – voluntary consent that can be withdrawn at any time.
Vercel Speed Insights Script und Intake
- Provider
- Vercel Inc. / ERTZU
- Storage type
- Measurement request without browser storage
- Scope
- Cookieless performance measurement
- Purpose
- Measurement of real loading, interaction and visual-stability metrics to technically optimise ERTZU.
- Content
- Sanitised path, route, Web Vital value and attribution, network speed, browser, device, operating system, country and timestamp.
- Trigger
- Only after selecting “Accept”
- Duration
- Reporting window according to the Vercel plan: 7 days (Hobby), 30 days (Pro) or 90 days (Enterprise)
- Attributes
- No cookies or persistent visitor identifier; requests are not loaded before consent and paths are sanitised before sending; processing in the United States is possible
- Legal basis
- Art. 6(1)(a) GDPR – voluntary consent that can be withdrawn at any time.