Data and privacy
What CoreValue stores, what it encrypts, where the hosted cloud runs, and what it does not yet certify.
What is true today
Everything below is a control the code enforces, named so you can check it.
Provider keys are stored as written; column encryption is in progress. In the hosted cloud, provider keys — and the upstream credentials you register for MCP servers and agents — are stored in Cloud SQL, which Google Cloud encrypts at rest by default with Google-managed keys, and are readable only by the platform's own service accounts. They are not yet encrypted inside the database column: an earlier version of this page said they were, and that was wrong. Encryption in the column, with the key held outside the database, is being built and this paragraph will change when it ships. Proxy keys are stored as hashes and cannot be recovered.
Members see what they are allowed to see. Role-based access control is enforced on the API — every route names the permission it requires, and Roles and permissions lists them, generated from the code — and an organisation owner can narrow request visibility so members see their own traffic rather than everyone's.
Cached responses are encrypted. The response cache is encrypted with AES-GCM and supports key rotation.
Where the hosted cloud runs. One region: Google Cloud us-central1, in
North America. Additional regions will be added as customers need them.
Security questionnaires, compliance documentation and data-processing terms are available on request on the Enterprise plan. Contact support@corevalue.dev.