Privacy policy

Account details you give us at signup (name, email, workspace name). Content you create in Cadence: decisions, specs, opportunities, and their outcomes. Content from any source you explicitly connect (GitHub, Slack, Linear, and similar), scoped to the permissions you grant at connect time and shown to you before you grant them. Usage data (page views, feature interactions) so we can tell what is working.

Cadence never merges code, ships a release, or takes an irreversible action without your explicit approval. The merge gate is always human-reviewed. We do not read sources you have not connected, and we do not expand a connection's scope without asking again.

Your decisions, specs, code, and outcomes are not used to train a shared or public AI model. When Cadence calls an underlying model provider to do its work, your data is sent for that request only, under that provider's standard API terms, not their consumer product terms.

In your workspace's own Postgres database (hosted on Supabase), isolated from other workspaces by row-level security. You can export your data in open formats at any time from Settings. The third parties that process data on Cadence's behalf, and what each one receives, are listed publicly on the sub-processor disclosure.

If you prefer, you can run Cadence against your own model provider key instead of ours. Nothing about your data handling changes either way. This is a routing choice, not a trust boundary.

Disconnect any connected source from Settings → Connected accounts at any time. Access ends immediately; nothing further is read from that source.

Members of your workspace, per the role you grant them. We do not sell your data. Cadence staff access production data only to operate the service (debugging, support you have requested) and that access is logged.

Questions about this policy or a request to export or delete your data: reach us through the contact address on your account, or see the security page for how to report a concern.

Cadence is in beta and this policy will get more detailed as we add capabilities (billing, more connectors). We will date every revision here; material changes get a notice inside the product, not a silent edit.