Permissions and privacy
CMP Cloud authentication, public/private visibility and repository trust boundaries.
CMP Cloud uses Firebase identity verification and PostgreSQL repository/organization membership checks.
- Public repositories can be read by anonymous visitors.
- Private and internal repositories require verified authentication and appropriate membership.
- Client-side hiding is not an authorization mechanism: APIs check access on every request.
- Writes are separately feature-gated while the production identity and authorization flow is validated.
- Skill, agent and instruction content is untrusted data unless a host explicitly approves its use.
- Personal session history is not archived automatically. Capturing organization-covered sessions requires both an approved organization policy and a local SDK/plugin opt-in setting, with per-session exclusions and deletion.
Development limitation: managed multi-tenant write workflows, KMS-backed archive encryption and derived search/index deletion propagation are not production-certified.