Cookie policy — what philipsloth.com stores in your browser, and why.
Short version: this site uses no first-party cookies and no third-party trackers. Anonymous analytics state lives in your browser's localStorage and never leaves your device tied to personal data. Because nothing requiring consent is set, no Cookieloven-style consent banner is required. The site does show a discreet first-visit privacy notice — a small glass card at the bottom of the viewport — as a transparency disclosure of the analytics pipeline plus an opt-out toggle. It is not a consent gate; see § 2 below for the full explanation of why.
1. What is stored where
| Storage | Key / value | Purpose | Lifetime |
|---|---|---|---|
| localStorage | philipsloth.visitor_id — random 128-bit hash | Anonymous returning-visitor detection for aggregated analytics. Not tied to personal data. | Until you clear site data |
| sessionStorage | philipsloth.session_id — random per-session hash | Per-session pageview deduplication. Not tied to personal data. | Until you close the tab |
| localStorage | philipsloth.lang — "en" or "da" | Remember the language flag pill in the navbar. | Until you clear site data |
| localStorage | philipsloth.optout — "1" if set | Records that you have opted out of analytics. Set by the toggle below. | Until you clear site data |
| cookies | none | N/A | N/A |
You can verify this in your browser's DevTools (Application → Storage on Chrome, Storage on Firefox). The cookies table for philipsloth.com is empty; the localStorage / sessionStorage entries above are what you'll see.
2. Why cookieloven does not require a banner here
Cookieloven (the Danish implementation of the EU ePrivacy Directive Art. 5(3)) requires informed consent before storing or accessing information on a user's device — but only for storage that is not strictly necessary for a service the user has explicitly requested. The localStorage entries above qualify under the "strictly necessary" carve-out:
- The language preference is necessary to show the site in the language the user picked.
- The opt-out flag is necessary to honour an opt-out preference the user has actively set.
- The visitor / session IDs are anonymous, never linked to personal data, and used solely for aggregated first-party analytics. Datatilsynet's 2024 guidance on similar setups (cookieless first-party analytics) treats them as out-of-scope of the consent requirement.
Even though no Cookieloven consent is required, the site shows a one-time privacy notice on first visit (a small glass card at the bottom of the viewport, gated by a localStorage acknowledgement key). That notice is a transparency disclosure of the analytics pipeline plus an analytics opt-in / opt-out toggle — not a Cookieloven consent banner. It exists because Datatilsynet's 2026 guidance encourages proactive disclosure of even consent-exempt processing. You can dismiss it ("Accept analytics"), opt out ("Reject analytics"), or click "Learn more" to read this page. Either choice is recorded in your browser only — never shared with a third party.
3. Third-party iframes & redirects
When you reach a payment bridge at philipsloth.com/p/... and the embedded Stripe checkout iframe loads, Stripe sets its own cookies on its own domain (stripe.com) for fraud prevention and session continuity. Those cookies are governed by Stripe's cookie policy — I do not control them and they are not first-party to philipsloth.com. The iframe loads only when the user explicitly initiates a payment, which is the "strictly necessary" trigger under Art. 5(3).
No other third-party iframes or scripts run on the public site. No Google Analytics, no Meta Pixel, no Hotjar, no advertising networks, no social-share widgets.
4. Opt out of analytics
Three independent ways to opt out, each takes effect immediately:
- The toggle below — one click, persists across visits.
- Set the browser
Do Not Trackheader — the analytics tracker becomes a no-op for this site regardless of the toggle state. - Clear site data in DevTools or your browser settings — wipes all localStorage / sessionStorage entries; you appear as a brand-new visitor on next pageview.
5. If this ever changes
If a future feature introduces a real cookie or third-party tracker (for example: a logged-in client portal that needs a session cookie), this page is updated with the cookie name + purpose + lifetime + lawful basis, a banner is deployed at the same time, and the privacy notice is updated to match. Material changes affecting active engagements are also notified by email.
Contact
Questions about cookies, storage, or analytics — email [email protected].