Cookie Policy

Cookies = small text artefacts placed on your device browsers send back (first-party under our hostname or strictly scoped subdomains versus third‑party trackers under remote domains blocked by modern defaults except where knowingly accepted).

Equivalent technologies encompass HTML5 storages retaining consent flags or ephemeral session correlation tokens — technologically similar legal treatment often applies albeit UX messaging sometimes still loosely says «cookies» broadly.

• Session & authentication continuity: e.g., NextAuth/secure-session cookies enforcing login — absolutely necessary transporting security attributes (HttpOnly wherever framework defaults allow).
• Traffic safety / CSRF state.

Our minimalist cookie-banner records your choice («accepted» vs «rejected» non-essential marketing/analytics placeholders) purely via browser local persistence — verifying again when you revisit if you voluntarily clear browsing data resets decision prompts.

These entries do not correlate server-side dossiers profiling individuals cross-site — they instantiate UI compliance.

If activated later distinctly (with separate affirmative toggles honouring granular consent granularity), analytic metrics could measure aggregated traffic anonymously — presently ensure such deployment would reference updated consent logs & processor policies before turning live.

Until then, treat analytic statements as illustrative architecture only rather than asserting active trackers.

Payment providers redirecting externally may leave strictly operational fraud-screening cookies wholly under their contractual universe — inspect their disclosures when leaving AgentChain-hosted checkout overlays.

You may revoke localStorage banners by clearing browser site data individually or resetting general cookie allowances — beware strict necessary removal may forcibly logout sessions.

Issues specifically about tracker deployment: privacy@agentchain.com.