ClovieSecurity at Clovie.
Clovie sits in the path of your AI traffic and holds your provider keys. It is built to be trusted with both, and to prove what it did.
- Provider keys never leave the gatewayAgents never see provider keys.
- Your network, if you chooseRun every feature inside your own network.
- Every decision on recordAudit records can’t be edited or deleted.
Controls in the product, not only in a policy document.
Data protection
- Encrypted in transit and at rest, with an extra layer for provider keys
- Provider keys never reach agents: each agent has its own key, rotated or revoked on its own
- Sensitive data masked before anything is stored
- You choose whether prompts and responses are kept, and for how long
Tenant isolation
- Each organization’s data isolated in the database itself
- A second check in the application on every request
- Agent keys scoped to one organization
Access control
- SAML and OIDC single sign-on, SCIM provisioning and required MFA
- Organization and project roles, with access reviews you can export
- Clovie support enters only when you grant time-limited access, shown by a banner and recorded
Product safeguards
- Every policy starts in monitor mode and is simulated before it enforces
- Break-glass enforcement needs a written reason, is audited and can be turned off
- Kill switches per agent and for the whole organization
- Tamper-resistant audit log and evidence packs with checksums and signatures
Infrastructure and deployment
- Clovie SaaS stores data in the United States
- Customer VPC, on-premises and air-gapped installs with the same features
- Signed images you can verify before you run them, offline too
- Compiled images with no readable source; a licence checked offline
Secure development
- Automated tests, including security tests, must pass before any change merges
- Release images scanned for vulnerabilities and secrets; a critical finding with a fix available blocks the release
- Signed images with a software bill of materials and build provenance
- Pinned, hash-checked dependencies, updated on a regular schedule
What happens to a request, step by step.
The gateway checks every request in the path, in our cloud or inside your network. Provider keys never leave the gateway. Content is masked before it is stored, and you can choose to keep only metadata or nothing.
Where request data goes, and what is kept.
Who looks after what, when Clovie runs in your network.
| Area | Clovie | Your team |
|---|---|---|
| Releases | Signed images, release notes and upgrade notes | Verify and apply upgrades on your schedule |
| Infrastructure | Install charts and sizing guidance | Clusters or hosts, network, TLS and storage |
| Database and backups | Upgrade dry runs and backup checks before an upgrade | Run the database and take and keep backups |
| Secrets | Works with Vault, AWS, Azure, Conjur, Kubernetes secrets or environment variables | Run the secret store and rotate secrets |
| Identity | SAML and OIDC sign-in, SCIM and roles | Your identity provider and who gets which role |
| Licence | A signed licence, checked offline | Install it and renew it before it expires |
| Monitoring | Health checks, metrics and traces to export | Collect them and alert on them |
| Policies and data | Monitor-first policies, simulation and audit | Decide what is enforced and what is kept |
| Support access | Only with access you grant, recorded | Grant or refuse it, case by case |
Controls mapped for your own evidence.
Clovie maps its controls to the frameworks your auditors use and exports evidence packs from your own records.
- EU AI Act: EU Artificial Intelligence Act
- SOC 2: SOC 2 Type II trust services criteria
- NIST AI RMF: NIST AI Risk Management Framework
- ISO/IEC 42001: ISO/IEC 42001 AI management system
- OSFI E-23: OSFI Guideline E-23, model risk management (Canada)
- OWASP Top 10: OWASP Top 10 for LLM applications and agentic AI
Mapping and evidence support your compliance work. They are not a certification of Clovie or of your organization.
Found a security issue? Tell us.
Email hello@clovie.io with the steps to reproduce it. Our contact details are also in security.txt.
Please give us a reasonable time to fix an issue before you disclose it, and don't access other customers' data or disrupt the service while testing. We won't pursue research done in good faith within these guidelines.
Questions security teams ask
Do our agents ever see our provider keys?
No. Each agent calls Clovie with its own key. Only Clovie holds your provider keys and uses them to call the provider.
Where is our data stored?
Clovie SaaS stores data in the United States. For another location, or your own network, run Clovie in your VPC, your data center or an air-gapped network.
Does Clovie store our prompts and responses?
Only if your administrators choose to, for as long as they choose. Sensitive data is masked before anything is stored.
Can Clovie access our self-hosted install?
No. A self-hosted install never calls home, and its licence is checked offline. Support works from what you choose to share.
Can we review your security documentation?
Yes. Your account team shares detailed documentation under NDA. Request it through the contact form.
Bring your security team.
We'll walk them through isolation, keys, audit and deployment, and share our security documentation under NDA.