Security and sovereignty
Nothing to trust. Everything to check.
Every claim on this page is a mechanism in the product or a certification of the company behind it. The security model is documented in full and goes to your security team for review before a single document is sent anywhere.
Certifications and proof
ISO 9001
Company certification behind Cogeto. Quality management, audited.
ISO 27001
Company certification behind Cogeto. Information security management, audited.
The security design in six mechanisms
One instance per customer
No shared database, no tenant column, no cross tenant query path. Isolation is a deployment boundary, not a filter.
Offline means offline
Models, embeddings, page recognition, and search run inside the instance. One egress seam, enforced in CI. No telemetry.
Redaction fails closed
Sensitive entities are pseudonymized locally before any external model call. If redaction cannot run, the call does not happen.
Deletion you can prove
Deletion runs as a saga across all three stores and ends in a signed, hash chained receipt, re-verified nightly.
An audit log that cannot be edited
Append only, enforced by a database trigger, written in the same transaction as the action, covering reads as well as writes.
Leaving is supported
The Memory Passport exports everything, signed, in an open documented format that verifies outside Cogeto.
Controls, in questionnaire form
Verb led, so your reviewer can paste them straight into the vendor form.
Isolation and access
- Runs one deployment per customer; no multi tenant mode exists
- Enforces access inside the query, in both stores, never on fetched results
- Assigns scope deterministically; never infers permissions from content
- Encrypts originals at rest under tenant scoped keys; serves them only through short lived signed URLs
Spaces, walls inside the instance
- Separates work that must not mix: one client per space, one department per space, one household per space
- No retrieval, comparison, linking, or reporting ever crosses a space
- Two spaces relate to each other exactly like two separate instances
- Carries a receipt chain and a Memory Passport per space, not per instance
Model traffic and sovereignty
- Routes every model call through a single gateway seam, enforced in CI
- Ships with no model provider preselected; the operator chooses one, and fully local models are supported
- Pseudonymizes names, organizations, and amounts before any external call, embeddings included
- Uses no customer content for training, ever
Proof and integrity
- Signs deletion receipts and hash chains them to their predecessors
- Sweeps nightly for orphans and tampering; reports and never repairs
- Records every state change in an append only audit log
- Publishes measured accuracy per release, per language, per model configuration
The security model is documented, in full
How access is gated, how deletion is proved, how provenance is enforced, how redaction fails closed, and how the instance and its supply chain are hardened: each one written up, and each one answered for your security review before anything is installed. That is the standard this page holds itself to: no claim without an artifact.
The company behind it
Cogeto is built by MCTO Advisory d.o.o., a company operating from Croatia in the European Union. The company processes behind Cogeto are ISO 9001 and ISO 27001 certified, so the product's quality and information security management stand on audited processes, not only on code.
Take the artifacts with you
Start in a minute, or bring your security team.
Create an instance and the same architecture is running for you today. Data residency requirements, air gaps, and security reviews are normal conversations here, not exceptions.