Privacy Policy
Draft disclosure of account, repository, connected-app and operational processing.
Who decides why data are used
For account administration, billing, security and operator analytics, CMP's contracting operator may act as controller. For customer-controlled repositories, sessions, connected-source material and records, the customer organization may be controller and CMP a processor under an executed DPA. The role depends on the operation. Self-hosted CMP Core does not automatically transmit data to CMP Cloud.
Information collected
Depending on enabled services: name, email, identity and OAuth provider IDs, account/organization memberships, repository and Markdown Context content, metadata and revision history, evidence/source references, connected-app grants, agent events, support communication, IP/device/security telemetry, appearance/cookie preferences and billing/payment references. A final verified data inventory is required.
Purposes and lawful bases
Purposes include authentication, access control, providing requested context workflows, collaboration, support, fraud and abuse detection, incident investigation, service reliability and authorized payment administration. Optional analytics or AI processing require a documented basis and, where required, consent. Controller legal bases require a processing register before approval.
Connected services and OAuth
Integrations may request documented scopes and retrieve selected external material on a user's or organization's instructions. Revoking a token may stop future retrieval but does not by itself delete previously created context, version history, external exports or provider-held records. Credential vaulting and retention need operational verification.
AI-assisted processing
Selected prompts or Context may be sent to enabled AI services, subject to applicable provider settings and agreements. No universal guarantee is made about provider training, processing country, retention or model behavior. Outputs may be inaccurate; users should independently verify important results.
Service providers and cross-border recipients
The active subprocessor register is pending review for hosting, authentication, edge delivery, inference, messaging and analytics. Actual vendor names, scopes, purposes, support locations, contracts and transfer mechanisms must be reconciled before publication. Applicable international transfers need valid legal safeguards and appropriate assessments.
Data location and security limitations
The primary database is hosted in the United States. EU data-plane infrastructure, region-scoped keys, inference, telemetry, queues, backups and support access are planned or unverified. The presence of a regional model project is not proof of strict regional processing. CMP does not claim certified GDPR compliance, proven EU-only hosting or universal customer-held encryption keys.
Retention, backup, export and deletion
Different categories, revisions, backup snapshots, logs and legal holds may have different retention. Exact live windows and deletion completion are not yet verified. Cryptographic erasure across all data and restore paths remains unverified. Individuals and customers may request handling subject to lawful exceptions and role verification.
Individual rights and contacts
Applicable law may provide access, correction, erasure, portability, objection, restrictions and withdrawal of consent, or regulator complaint rights. For customer-controlled data, requests may need routing to the customer controller. Verified intake contacts, identity validation, response procedures and a complete privacy rights workflow are pending approval.
Changes and account notice
Approved future policy versions should carry an immutable digest, version, effective date, change summary and appropriate notice. A user merely reading or dismissing an Inbox notice is not evidence of legal acceptance; acceptance of updated Terms requires a separate explicit authenticated action where applicable.
Document history
Version 0.1-draft · updated 2026-11-16.