Privacy at Cohorly

Cohorly gives organizations controls to understand and manage the product analytics data they collect.

Cohorly stores product events and profiles in the project that received them. Each project belongs to an organization, and customer credentials are scoped to that organization. The dashboard and API apply this project and organization boundary before returning analytics data. Project tokens are for ingestion only; account credentials are required for administrative and query operations. Teams should treat every credential as sensitive and keep tokens out of client-visible source code whenever a server-side integration is available.

Organizations control their collection design. Event properties are defined by the integrating team, while data definitions and the lexicon help them make collection more deliberate. Cohorly documents the special event properties used for identity, timing, deduplication, and attribution so teams can assess what they send. Data retention is configured per organization, and the service removes events outside the selected retention period through its retention process.

Authorized owners can use the privacy API to locate a subject, export the related data, or request deletion. Those operations are scoped to the selected project and recorded for auditability. If you need to exercise a privacy request concerning a Cohorly workspace, contact that workspace's owner first. They can verify the request, select the correct project, and use the available controls. This page describes product behavior and does not replace an organization's own privacy notice or legal obligations.