Cookie Policy

1. What are cookies?

Cookies are small text files stored on your device. Similar technologies include local storage, pixels, and scripts that read device identifiers. We use them to run the site, remember preferences, and—only with consent—measure and improve marketing surfaces.

2. Consent categories

Our cookie consent mechanism (CMP) stores preferences under keys such as akashic_cookie_consent and exposes categories matching the product constants:

2.1 Necessary

• Required for basic site operation, security, load balancing, and remembering your cookie choices.
• May include theme preference and essential session/authentication cookies on signed-in surfaces.
• These do not require consent under ePrivacy frameworks where they are strictly necessary; they remain enabled.

2.2 Analytics

• Help us understand aggregated traffic and usability (for example page views and interaction patterns).
• When enabled by consent, marketing/docs may load Google Analytics and/or Microsoft Clarity (including heatmaps or session insights as configured by those vendors).
• On marketing pages, documentation, and the admin application, the CMP is live: analytics scripts load only after analytics consent. Admin reuses the same consent storage key and categories as marketing.

2.3 Marketing

• Reserved for optional advertising or cross-context marketing technologies if/when enabled.
• Not used to sell personal data. If marketing tags are not active in a given environment, enabling the category has no effect until tags are configured.

3. Examples of technologies we may use

• Consent record: first-party cookie/storage recording category choices and policy version.
• Google Analytics: measurement IDs configured per environment; loads after analytics consent.
• Microsoft Clarity: project ID configured per environment; loads after analytics consent.
• Documentation analytics: docs traffic measurement (for example a configured Google Analytics property) is subject to the docs CMP consent gate.

4. Managing preferences

• Use the cookie banner / preference controls on marketing and documentation to accept, reject, or customize non-necessary categories.
• You can also clear cookies and site data in your browser; you may need to set preferences again.
• Browser “Do Not Track” signals are not uniformly standardized; we rely on the CMP choices where implemented.

Privacy policy path used by the consent UI: /privacy.html (constant COOKIE_CONSENT_PRIVACY_PATH). Cookie details live at /cookies.html.

5. Retention

Consent preference storage is intended to persist for up to approximately 365 days (product constant), after which you may be asked again. Vendor cookies follow each vendor’s own durations as described in their documentation.

6. Updates and contact

We may update this Cookie Policy when technologies or law change. Continued use after the effective date, together with CMP choices you make, governs cookie use on our sites. Contact channels: /admin Contact dialog · Discord.