Cookie Policy

We use cookies, localStorage, and similar technologies for authentication, preferences, security, and — with consent where required — analytics.

• Per-product session/auth cookies (e.g. board_access / board_refresh, community_access, platform-identity SSO cookies).
• Theme preference: collabai-theme (localStorage).
• CMP consent record: collabai_cookie_consent_v2 (first-party cookie + localStorage; Domain=.collabai.ar in production when applicable).
• Security, load balancing, and technical fraud prevention.

• Google Tag Manager / GA4 via @collabai/platform-analytics, only after analytics consent. Consent Mode v2: default denied; analytics_storage granted only if you accept analytics; ads signals stay denied while no advertising tracking exists.
• Analytics attribution/session: collabai_analytics_attribution_v1, collabai_analytics_session_v1 (localStorage).
• PostHog (if configured by environment in Work/MVP): only after analytics consent; no marketing pixel.
• Legacy keys migrated automatically: collabai_analytics_consent_v1, collabai_cookie_consent, board_cookie_consent_v1, incubator_cookie_consent_v1.

The Marketing category exists in the CMP architecture but is not shown in the UI while Collabai does not use advertising pixels. ad_storage / ad_user_data / ad_personalization remain denied.

The CMP Preferences category covers non-essential experience choices. Light/dark theme (collabai-theme) is treated as necessary for coherent UI operation.

You can accept all, reject optional cookies, or configure categories in the banner. You can also open “Cookie settings” from each product footer to change or revoke preferences without clearing storage manually. Strictly necessary cookies cannot be disabled without affecting the Service.

We will update this policy when actually used tracking keys or providers change. Major consent changes (CMP major version) may require a new choice.