Security

Your data stays in your workspace. Here is how you check that.

Most vendors answer this question with a badge. We answer it with three things you can run yourself: the privacy check script, the public verification page, and this document. No certificate is implied — we do not have ISO 27001 or SOC 2, and we say so below.

Stored in
One SQLite file on your host
data/traceseal.db
Sent to third parties
Nothing at runtime
no analytics, no telemetry, no AI API calls
Personal data in logs
Masked before storage
email, phone, IBAN, national ID, card

What is stored, field by field

FieldContent
Who actedThe user or service identity that triggered the event
Event typeinference, approval_request, approval_decision, human_review, data_access, model_change, error
Model and versionProvider, model name, version as reported at the time
Masked summaryUp to 320 characters of input and output, with personal data replaced by a label
Data categoriesLabels such as email, phone, iban, health — not the values
TimestampsWhen it happened (UTC) and when it was received
Hash chainPrevious hash and this record's hash
Approval recordApprover, time, decision, note, signature

What is never stored

  • ×Raw prompts or completions beyond the masked summary
  • ×Passwords of the people in your logs
  • ×Customer documents or uploaded files (we do not accept them)
  • ×Payment card data (the payment provider handles it)
  • ×Behavioural analytics, session recordings or advertising identifiers

How the masking works

Before a record is written, the payload passes through a masker that replaces email addresses, phone numbers, IBANs, 13-digit national IDs and card numbers with a label, and records which categories were present. The same masker runs over the raw payload copy, so a search of the database for an address finds nothing but the label. The categories are kept because the Act asks which data was processed — not what the value was.

input:  "Rank these applicants. Contact ana@example.com or +381 60 123 4567"
stored: "Rank these applicants. Contact [email] or [phone]"
categories: ["email", "phone", "employment"]

Verify it yourself

These commands run against your own copy. They do not phone home.

1. Privacy check
npm run privacy-check

Scans every event, payload and approval for raw personal data, checks that no code calls an external host, and lists what is not covered.

2. Verify a pack without an account
GET /verify?h=<pack hash>

Recomputes the hash and checks the Ed25519 signature. Works from any browser, for anyone holding the PDF.

3. Read the schema
src/lib/db.ts

The whole data model is one SQL block in one file. There are no hidden tables and no external store.

What this page does not claim

Encryption at rest

Depends on the disk. Turn on full-disk or volume encryption at the host; we do not encrypt individual fields.

Key custody

The workspace signing key is stored in the database. Before production, move it to a KMS or HSM; the code is one function away.

Certifications

No ISO 27001, no SOC 2, no eIDAS seal. If a buyer requires one, we say no rather than invent a badge.

Backups

The operator's responsibility. Keep a copy of the database and the packs directory, and test a restore.

Subprocessors

Hosting only. No analytics, no email marketing tool, no AI provider is called when you use the product.

Access and retention

  • ✓ Access is per workspace, with a session cookie; no shared links to the application.
  • ✓ API keys are stored as SHA-256 hashes and shown once.
  • ✓ Logs are kept at least six months (Art. 19 / 26(6)); the retention rule is yours to set.
  • ✓ Deleting a workspace means deleting one file — there is nothing to chase in a third-party system.
  • ✓ Evidence packs stay verifiable after the underlying data is deleted: the hash chain is enough.
Need a DPA or a security questionnaire?

Write to hello@traceseal.eu. We answer with this page, the source, and a signed DPA — not with a badge.

Start with the free risk check

Last reviewed 2026-11-16. This page describes the software as shipped in this repository; a deployment can differ (for example if the operator adds encryption or a managed database). Ask the operator for their configuration before relying on any statement here.