Cookie policy

Essential cookies keep the partner portal signed in. When PostHog is configured, analytics cookies and related storage (PostHog Cloud EU, ingested via our first-party host `e.hmd.digital`) load only after you accept them in the Silktide banner. Google’s booking calendar is not loaded until you ask for it on the contact page (or open it in a new tab). If PostHog is not configured on a deployment, we may use cookieless Umami instead (no banner). We do not use advertising cookies on this site.

• hmd-partner-token: partner portal session (HttpOnly cookie; `SameSite=Lax`; `Secure` in production; path `/partners/portal` only).
• stcm.consent.*: Silktide consent preferences in local storage.
• hmd:reduce-motion: footer “Reduce motion” choice in local storage; stays on your device.

When configured, product analytics use PostHog Cloud EU. The browser talks to our first-party ingest host `https://e.hmd.digital` (a PostHog-managed reverse proxy); the PostHog app UI remains on `https://eu.posthog.com`. Nothing loads until you accept analytics in the Silktide banner.

• ph_* cookies: PostHog distinct id and session (names include the project key prefix), only after analytics consent.
• PostHog localStorage (related `ph_*` keys): persistence mode `localStorage+cookie` for id/session and related SDK state, only after analytics consent.
• Session replay: when recording is enabled for the project, PostHog may buffer replay data in browser memory/storage during the session; completed recordings are stored in PostHog Cloud EU under the project’s replay retention setting. Only after analytics consent.
• Other PostHog client storage: the SDK may also use sessionStorage or similar short-lived browser storage for capture buffering and feature-flag/cache state tied to the same consent.

You can change or withdraw consent anytime via the Silktide preferences control (cookie icon). How long we keep analytics data is in the privacy policy.

If a deployment has no PostHog key, we may load Umami hosted by us instead. That fallback is cookieless (no Umami analytics cookies and no Silktide banner). It is described under analytics in the privacy policy.

The contact page does not load Google by default. If you click Book with Google (inline embed) or open the appointment page in a new tab, Google Calendar Appointment Scheduling runs on Google’s domains (`calendar.google.com` / `calendar.app.google`).

• Google cookies / storage (names controlled by Google, for example NID, CONSENT, __Secure-* and related identifiers): may be set or read by Google when their booking UI loads, to provide the schedule, security, and Google’s own services. These are third-party cookies/storage under Google’s control.
• What we receive: booking details you submit (name, email, phone, chosen slot) so we can hold the discovery call.

Google’s practices are described in Google’s Privacy Policy. You can avoid Google cookies on this site by not loading the calendar and using the contact form instead. How we handle booking data is in the privacy policy.

How we handle personal data is explained in the privacy policy. Contact [email protected].