Cookie Policy

Cookie categories and consent behavior

This page explains which cookies/storage keys are used, why they are used, and what changes when you accept or reject optional categories.

Last updated: March 22, 2026 Reject-all in first layer No non-essential tracking before consent

1. Categories used

Category	Mandatory	Examples	Purpose
Strictly necessary	Yes	`sc_cookie_consent`, `sc_cookie_consent_v1`, `sc_marketing_lang`, `sc_marketing_billing`, `sc_locale`, `sc_theme`	Security, language preference, theme preference, and consent memory.
Analytics	No	`sc_marketing_id`, `sc_session_id`, `sc_utm_payload`	Understand usage patterns and improve website performance/content quality.
Attribution	No	`mkt_id`, `session_id`, UTM bridge parameters	Measure campaign quality and onboarding source contribution.

We store your consent decision and version for compliance proof.
Optional analytics/attribution identifiers are generated and used.
Public marketing events can be sent to our API endpoint for aggregated reporting.
You can withdraw consent later from "Cookie settings" in website footer.

Consent decision events are logged server-side with event timestamp and consent version.
Network data in consent logs is minimized (hash/masked format) for abuse prevention and auditing.
Consent logs are kept per retention policy (see Privacy Notice).

If you block cookies in browser settings, parts of the website may not function as expected.