Security · Trust
Self-hosted by design. Governance data stays in infrastructure you control.
Olivares processes prompts and output in governed sessions. Its I/O recorder hashes frame content with SHA-256 and folds the digest and length into a chain anchored to the audit ledger; it does not store the frame content.
Data handling
What we touch, and what stays with you
Sessions process prompts and output; recording keeps digest evidence, not their content. Governance data stays in your infrastructure by default. Provider tools keep their own transcripts in their configuration home on your host; releasing a session does not purge them. Hosted providers receive what the session sends. Communication-channel messages are stored with the channel’s configured content protection.
Runs in your infrastructure
Self-hosting gives you control of the server and its storage. Hosted model calls, connected sources and configured exports can still cross your network boundary.
Session recording evidence
Recording keeps SHA-256 digests and frame lengths in a tamper-evident chain anchored to the audit ledger, not prompt or output bytes. It is automatic for critical launches and can also be requested by policy or the operator.
Secret redaction
Configured vault-secret values are redacted before session output reaches the recorder. Personal data can still appear in prompts, output, provider-tool transcripts and stored communication messages. The provider tool writes its own transcripts outside that redaction path.
Discovery and agent actions
Passive discovery reads configured sources. Operated agents can perform actions through their tools; review their permissions, policies and credentials before launch.
Network destinations
For example, Business activation and license refresh contact the licensing service; hosted providers and configured integrations use network connections. Self-hosting does not make those operations offline.
Retention boundaries
Recording and audit-ledger evidence is append-only: a retention setting does not purge it. Provider-tool transcripts on your host follow that tool’s own retention. Olivares retention does not set an external service’s retention policy.
Vulnerability disclosure
Report a security issue
We welcome coordinated disclosure and act in good faith with researchers who do the same. Findings in the security model itself are explicitly welcome.
Report privately to
security@olivares.aiPlease don’t open a public issue, pull request or discussion for a suspected vulnerability. PGP is available on request before you send details.
What to expect
- Acknowledgement within 3 business days
- Initial assessment within 10 business days
- Coordinated disclosure up to 90 days, sooner if a fix ships
Please don’t send
No real secrets, credentials or tokens (redact them), no customer or third-party personal data or production dumps, and no live exploitation of systems you don’t own. Describe sensitive impact rather than attaching it — we’ll arrange a secure channel.
The supported line is the latest tagged release; security fixes land on main and ship in the next tagged release.
Subprocessors
Who else processes data
This website uses no analytics, advertising or tracking subprocessors. It is a static site with self-hosted fonts, a strict same-origin Content-Security-Policy, and no cookies. It is served over a content delivery network, which handles only the connection metadata needed to deliver the page — we collect no personal data when you browse.
Olivares is self-hosted software. You choose the model providers and output or telemetry destinations used by your deployment. The services used for our website, licensing and communications are listed separately in the Trust Center.
Trust CenterData processing
Data Processing Agreement (GDPR Art. 28)
A Data Processing Agreement is available on request for enterprise procurement. Because Olivares AI is self-hosted, in most deployments you remain the controller and processor of your own data within your own infrastructure; a DPA can still be executed to formalize responsibilities for a commercial relationship.
Compliance posture
Honest about where we are
Olivares AI is not certified under SOC 2, ISO/IEC 27001, the EU AI Act or any other framework, and no audit is in progress. We design the product to map to the controls those frameworks examine — audit logging, access control, integrity, encryption and change management — so that it is ready to be audited when the time comes. Formal certification (for example SOC 2 Type 2) is a later step the architecture is built to enable; it does not gate the first release.
Frameworks we design toward
-
SOC 2 / ISO 27001
Control objectives we design toward — not certified, on the roadmap.
-
EU AI Act
Designed to support its control and documentation expectations.
-
CSA MAESTRO
A threat-modelling methodology we map against — not a certifiable standard.
-
OWASP agentic threats
Mapped against the agentic threat and mitigation list.
-
CISA / NIST guidance
Guidance, not a certifiable standard — design-toward, no conformance claim.
Where we describe alignment with external frameworks, this is a technical mapping, not a certification — and for standards that are not yet final it is a design-toward signal with no conformance claim.
Build integrity
- Releases are cryptographically signed, ship with a software bill of materials, and carry build provenance.
- A single, memory-safe static binary in minimal, hardened container images.
- Minimal, pinned dependencies — no install scripts that run unverified code.
- Dependency and secret scanning gate every change in CI.
These guarantees hold for every tagged release.
Remediation targets
- Critical 7 days
- High 14 days
- Medium 30 days
- Low next scheduled release
Our committed remediation cadence, in effect from the first tagged release. Actively-exploited vulnerabilities are treated as critical.
Business: runtime security and your own keys
Community includes guardrails, egress DLP and the deny-closed checks. Business adds a content firewall, server-tool egress and computer-use checks, a circuit breaker, MCP tool pinning, threat intelligence and keys in your own key service.
Trust questions
Where does my data go?
Sessions process prompts and output; recording keeps digest evidence, not their content. Governance data stays in your infrastructure by default. Provider tools keep their own transcripts in their configuration home on your host; releasing a session does not purge them. Hosted providers receive what the session sends. Communication-channel messages are stored with the channel’s configured content protection.
Are you SOC 2 or ISO 27001 certified?
Not yet. The product is designed to map to SOC 2 and ISO 27001 control objectives so it is ready to be audited, but formal certification is on the roadmap and has not been obtained. We will not claim a certification we do not hold.
How do I report a security vulnerability?
Email security@olivares.ai privately — please don’t open a public issue. Our full policy, including response timelines, is on this page and referenced from /.well-known/security.txt (RFC 9116). We acknowledge within three business days.
Do you offer a DPA?
Yes, a GDPR Article 28 Data Processing Agreement is available on request for enterprise procurement. Contact enterprise@olivares.ai.
Questions from your security or procurement team?
Report a vulnerability to our security contact, or reach out for procurement, a DPA or a security review.