Skip to content
ThetaLayer

Security & trust

Raw data stays in your network. Only minimized evidence leaves.

ThetaLayer is designed around the security review: a read-only collector that runs in your environment, sensitive values hashed or dropped before export, and an EU-hosted control plane that stores evidence append-only.

Book a DemoHow it works
Collector preview
erp.change_log · 1 record
Raw · stays in your network
OBJECT
LFA1 · vendor V100234
NAME1
Muster Logistik GmbH
FIELD
IBAN
VALUE_OLD
DE89 3704 0044 0532 0130 00
VALUE_NEW
DE02 1203 0000 0000 2020 51
USERNAME
SVC_VENDOR_AGENT
CHANGED
14.10.2026 09:42:17 (Berlin)
minimize · validate · DLP scan
Exported · leaves your network
tool_id
erp.vendor_updated
object.ref
V100234
actor
agent:vendor-master
field
bank_account
old_value_hash
iban_4be0c2a1d9f3
new_value_hash
iban_9a1f07c3e2b8
occurred_at
2026-10-14T07:42:17.000Z
NAME1 · droppedVALUE_OLD · hashedVALUE_NEW · hashed
Illustrative · sample values, not customer data

At a glance

The short version for your security review

Customer-side collector

Runs in your environment and reads native exports and audit logs. Raw records are processed there and never sent.

Read-only, least privilege

Read access to the exports and audit logs each adapter needs — nothing more, and no write access to any system.

Credentials stay with you

Source credentials, the hash salt and the identity map live in your network. ThetaLayer never holds them.

Minimized by default

IBANs, invoice numbers and message IDs are hashed; subjects, bodies, cell values and tool payloads are dropped.

Schema-validated ingestion

Collector and control plane validate every event against the same JSON Schema. Unknown fields are rejected.

Tenant isolation

Every event is tenant-scoped and checked against the identity of the authenticated collector that sent it.

Append-only evidence

Evidence is never edited in place. Human decisions and mandate changes are written to an audit log.

Encrypted in transit and at rest

TLS for all traffic between collector, control plane and browser; provider-managed encryption at rest.

Data minimization

Hashed, dropped or kept — decided before export

Minimization happens in the collector, not after the fact. Every event passes four gates on its way out, and the most important drops are fixed guarantees that configuration can't switch off.

  1. Gate 01
    Adapter minimization

    Only the facts needed for reconciliation are derived from each raw record.

  2. Gate 02
    Attribute allow-list

    Anything not on the list is dropped, and the drop is recorded.

  3. Gate 03
    Schema validation

    additionalProperties: false at every level of the event.

  4. Gate 04
    Outbound DLP scan

    An email address or IBAN pattern anywhere in an event blocks it from being sent.

Kept
Facts needed to reconcile and measure
  • Amounts, parsed to two decimals
  • ERP document and vendor references
  • Tool IDs, operations and results
  • Model names and token counts
  • Timestamps, converted to UTC
  • Identities as canonical principals
Hashed or masked
Keyed HMAC-SHA256; the key stays with you
  • Supplier invoice numbers → invoice_key
  • IBANs and bank accounts → iban_…
  • Internet message IDs → msg_…
  • Recipient addresses → domain only
  • Unmapped email identities → h_…
Dropped
Removed before an event is queued
  • Email subjects and bodies
  • Spreadsheet cell values
  • Approval comments
  • Prompts, tool arguments and tool results
  • ERP item texts, vendor names, VAT IDs
  • Client IP addresses and mailbox owners
Fixed guarantees. Dropping tool arguments and results, email subjects, cell values and approval comments — and enforcing the attribute allow-list — can't be disabled in configuration. Switching off a hash removes the derived key; it never exports the raw value instead.

Hosting

EU-hosted by default

The control plane runs in Frankfurt by default. Other regions are available on request.

Region
EU (Frankfurt) by default; other regions on request
In transit
TLS between collector, control plane and browser
At rest
Provider-managed encryption
Isolation
Tenant-scoped evidence; authenticated collectors; idempotent batches
Retention
Configurable, and agreed with you in the contract

Subprocessors

Subprocessors used to run the ThetaLayer control plane
SubprocessorPurposeLocation
VercelApplication hostingEU (Frankfurt)
NeonManaged Postgres databaseEU (Frankfurt)
Email providerNotification emailsListed in our DPA

Subprocessors only ever handle minimized, schema-validated events and the data needed to run the service. The current list is maintained in our DPA, available on request.

What reaches the control plane

Canonical events only — references, amounts, hashed keys, identities as canonical principals, costs and outcomes. No raw records, no free text, no credentials.

Integrity

Evidence you can trace. Decisions you can attribute.

  • Append-only evidence keyed by deterministic event IDs: re-sending is idempotent and nothing is overwritten.
  • Every event carries its collector, adapter version and a SHA-256 digest of the raw record, so it can be matched to its source inside your network.
  • Runs, links and mandate checks are rebuilt from evidence on every pass — never edited by hand.
  • Review decisions and mandate versions are durable, and written to an audit log with who made them and when.
provenance · evt_4771…37fbIllustrative
collector_id
col-nordwind-fra-01
adapter
erp_change_log
adapter_version
0.1.0
raw_digest
sha256:1830200e7e21f08e…
Audit log
  • 21 Oct 09:14k.bauerreview.confirmed duplicate_posting
  • 21 Oct 10:02a.okaformandate.activated ap-intake-de v2
  • 21 Oct 10:02systemreconcile.completed history re-checked

Compliance

Where we stand today

We're a young company, and we'd rather be precise than impressive. This is our current posture.

GDPR and UK GDPR

Processing aligned with GDPR and UK GDPR, built on data minimization and purpose limitation from the collector onward.

Data processing agreement

A DPA is available on request, including our current list of subprocessors.

Certifications

SOC 2 and ISO 27001 are on our roadmap. We don't claim either today.

Security documentation

Architecture, data-flow and data-handling documentation is available on request for your review.

Your obligations

How ThetaLayer supports your regulatory evidence

ThetaLayer supports these obligations with evidence. It doesn't make an organization compliant on its own — that depends on your wider controls, processes and legal assessment.

EU AI Act — Regulation (EU) 2024/1689. DORA — Regulation (EU) 2022/2554.

EU AI Act

Human-oversight and logging duties for high-risk uses apply from 2 December 2027.

ThetaLayer supports with: Reconstructed run records with their evidence, a log of human review decisions, and mandate history showing what each agent was permitted to do, and when.

DORA

Already applies to financial entities.

ThetaLayer supports with: Evidence of what each agent — including vendor-provided agents — did in financial systems, and end-to-end reconstruction when something goes wrong.

Internal audit and controls

Approval and segregation-of-duties controls now involve non-human actors.

ThetaLayer supports with: Approval controls evidenced from the systems of record, with the agent, the person and the credential behind every change.

Responsible disclosure

Found a vulnerability? Tell us.

If you believe you've found a security issue in ThetaLayer, please report it through our contact page and mark your message as a security report.

Report via contact page
We ask that you
  • Include the steps to reproduce and the potential impact
  • Give us reasonable time to investigate and fix the issue before any public disclosure
  • Don't access, modify or delete data that isn't yours
  • Don't degrade the service or run automated scans that affect other users

We'll keep you updated while we investigate, and we appreciate reports made in good faith.

FAQ

Security questions

Does ThetaLayer need write access to any of our systems?
No. The collector uses read-only access to exports and audit logs. ThetaLayer doesn't write to your agents or your systems of record. If you later choose enforcement at a specific tool boundary, that's scoped separately with you.
Can ThetaLayer see email contents, documents or prompts?
No. Subjects, bodies, cell values, approval comments, prompts and raw tool arguments and results are dropped inside your network before export. The event schema has no fields that could carry them, and an outbound scan blocks any event that contains an email address or IBAN pattern.
Can you reverse the hashed values?
No. Hashes are keyed with HMAC-SHA256 using a salt that stays in your network. The control plane can see that two records share an invoice key or bank-account hash — that's how duplicate postings and reused IBANs are caught — but it can't recover the underlying value.
Where is our data hosted, and for how long is it kept?
The control plane is EU-hosted in Frankfurt by default, with other regions on request. Retention is configurable and agreed with you in the contract.
Do you have SOC 2 or ISO 27001?
Not yet. SOC 2 and ISO 27001 are on our roadmap. Security documentation and our DPA are available on request, and we'll work through your security questionnaire with you.
Can our security team see exactly what will leave the network?
Yes. The collector has a preview mode that shows a raw record, which stays in your network, next to the exported event, which leaves it — source by source. Every exported event also lists the redactions applied to it.

Book a Demo

Bring your security team to the demo.

We'll walk through the trust boundary, the redactions applied to each source and exactly what reaches the control plane — then scope a six-week, read-only pilot.

Book a DemoSee the pilot