01 Definitions
Cookies are alphanumeric strings written to your browser’s cookie jar when a server sends Set-Cookie headers or when scripts operating under our domain invoke storage APIs. Equivalent technologies include HTML localStorage entries that persist consent bitmaps and sessionStorage keys that expire when you close the tab.
First-party cookies belong to shoulderuewasher.ddd. Third-party cookies belong to embedded domains (for example analytics endpoints) and load only after consent.
02 Purpose overview
Experience continuity
Remember that you dismissed or customised the banner so it does not loop endlessly.
Security signals
Rotate lightweight anti-forgery hints when you submit forms.
Optional insight
Aggregate statistics about scroll depth or outbound clicks when analytics toggles are enabled.
Campaign measurement
Attribute visits to creative variants only where marketing consent exists.
03 Strictly necessary cookies
These satisfy GDPR Recital 30 exemptions for storage strictly needed to deliver a service explicitly requested by the user. Examples include:
- Consent state persistence (tallennus of toggles in localStorage).
- Load-balancer affinity cookies keeping your HTTPS session pinned to healthy nodes.
- Brief security cookies verifying form submission tokens.
Cannot be switched off
Without necessary cookies the preference centre cannot prove what you selected, which would violate accountability duties.
04 Analytics cookies
When enabled, analytics cookies may collect pseudonymous identifiers, coarse geography derived from IP truncation, device category, and engagement metrics. They do not intentionally fingerprint individuals across unrelated sites beyond standard vendor documentation.
You may disable this category at any time; historical aggregated logs may remain in anonymised dashboards.
05 Marketing cookies
Marketing cookies support frequency caps, conversion pixels, and creative rotation experiments for promotional campaigns advertising informational nutrition programs. No profiles are sold to data brokers.
06 Local storage parallels
We may mirror consent preferences inside localStorage because some static hosting stacks lack dynamic cookie injection. Keys remain first-party and expire when you clear site data.
07 Indicative durations
- Session cookies: expire when the browser closes.
- Consent archives: up to twelve months unless regulations demand longer evidentiary retention.
- Optional analytics: vendor defaults frequently span thirteen months but honour shortened periods when vendors support deletion APIs.
08 Browser-level controls
Beyond our banner, major browsers let you block third-party cookies outright or delete stored data daily. Refer to Mozilla, Apple, Google, or Microsoft documentation for version-specific steps.
09 Updates
When we introduce materially different vendor stacks, we refresh this Cookie Policy’s effective date and may prompt you to reaffirm consent where required by ePrivacy guidelines interpreted alongside Finnish enforcement priorities.
Continue to the Terms of Use for behavioural rules while browsing.