Skip to content

Security and sovereignty

Nothing to trust. Everything to check.

Every claim on this page is a mechanism in the open source release or a certification of the company behind it. The architecture is public, the audit is published, and the code can be read before a single document is sent anywhere.

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

Model traffic and sovereignty

  • Routes every model call through a single gateway seam, enforced in CI
  • Defaults to a European provider; supports fully local models
  • 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

Audited, and the audit is public

The 2.0 security audit is closed out across five remediation waves: every finding fixed or consciously accepted with a written rationale. Both the audit and its independent verification are published in the repository, readable in full. That is the standard this page holds itself to: no claim without an artifact.

The company behind it

Cogeto is built by MVT Solutions Group d.o.o. and MCTO Advisory d.o.o., two companies operating from Croatia in the European Union, founded and led by Ivan Golubic. MVT Solutions Group is ISO 9001 and ISO 27001 certified, so the product's quality and information security management stand on audited company processes, not only on code.

Bring your security team to the pilot.

Data residency requirements, air gaps, and security reviews are normal conversations here, not exceptions.