Security you can inspect, not a page that asks for trust.

Below is what is built and running, and further down, what we do not claim yet. Both matter when your risk team fills in a questionnaire.

Data

  • Tenant isolationEach customer runs on an isolated deployment. Knowledge, memory and records are scoped to that tenant and the scope rules are tested adversarially, not assumed.
  • Personal data detected on the way inTurkish and international identifiers are recognised during ingestion, so sensitive content is classified before anything reads it.
  • Retention with an ownerEvery source carries a sensitivity level and a retention window agreed with you, not a default nobody chose.

Access

  • Secrets by referenceCredentials are registered as references and resolved at use. The governance store has no column that could hold a secret value.
  • Rotation on a scheduleDue credentials raise an approval request automatically, and channel tokens refresh on their own timer with an atomic write back.
  • Closed surfaceInternal services listen on loopback only. The operator dashboard sits behind mutual TLS and authentication.

Integrity

  • Prompt injection scanningIngested content is scanned and quarantined before retrieval, with the pattern recorded and the payload withheld.
  • Request guards on researchAttempts to reach internal or metadata addresses are blocked, and the block is visible in the trace instead of silently returning nothing.
  • Append only auditUpdates and deletes on audit rows are blocked at the database level, so the record survives the application.

Data subject requests resolve to an operation, not an email thread.

KVKK and GDPR obligations only work if someone can actually execute them on the day they are asked.

Register

Every source of personal data is registered with its lawful basis, its sensitivity and its retention window before it is connected.

Locate

A request resolves across memory, knowledge, records and artifacts, because they all share the same spine rather than living in separate tools.

Export or purge

Per source export, or a two phase purge where the removal is staged, confirmed and then recorded as having happened.

What we claim, and what we do not.

A vendor who overstates this at the sales stage costs you more later than one who is precise now.

We do claim

  • Single tenant deployments with tested scope isolation
  • An append only audit trail enforced by the database
  • Risk classification and human approval on every send path in scope
  • Credential handling by reference, with scheduled rotation
  • Approval authority held apart from every agent, so no agent can approve its own work
  • Operational logs leave your deployment only with your explicit consent, with phone numbers, email addresses, national ID, IBAN and card numbers masked
  • A signed processing agreement and retention terms before the first channel goes live

We do not claim

  • An ISO 27001 or SOC 2 certificate. Neither audit has been completed.
  • A published uptime percentage. Support windows are agreed in your contract instead of advertised here.
  • A multi tenant SaaS. That architecture is deliberately not sold yet.
  • Penetration testing by a third party. Internal adversarial testing is documented and can be shared.

If a certificate is a hard requirement for your procurement process, say so on the first call and we will tell you honestly whether to wait.

How change is handled after go live.

staged flags

Nothing flips in one move

Enforcement and new capabilities advance one reversible flag at a time, verified live at each stage before the next one is considered.

rollback

A way back is prepared first

Each deployment parks a rollback snapshot of the previous state, including the database, before the change is applied.

adversarial checks

Tested against its own claims

Acceptance runs probe the guarantees directly: can an audit row be updated, can a quarantined document be retrieved, can a request reach an internal address.

visibility

No demonstration data

The operator dashboard shows real state or an honest empty state. A surface that invents numbers to look healthy is worse than no surface.

Send us your security questionnaire.

We will answer it as written, including the questions where the answer is not yet.