Privacy

Account and organization data

Human sign-in is handled by Clerk. The CAPYDB backend stores organization metadata that is mapped from the active Clerk organization, along with project, cluster, job, and API-key records.

Database and operational data

Customer database content lives on the managed Postgres hosts. Control-plane metadata lives in a separate Postgres database. Backups, restore records, preview metadata, and import jobs are tracked by the control plane.

Access controls

• >>Clerk session tokens can authorize normal dashboard requests
• >>Organization API keys authorize programmatic access
• >>API keys are stored as hashes in metadata
• >>Organization scoping is enforced in the backend