Skip to content
MaskioEU

Security and trust center

We can’t leak what we never store.

Maskio is a stateless privacy airlock. Sensitive payloads and token dictionaries live in volatile RAM and expire. That is the property a DPO can verify, not a slogan about “enterprise grade”.

  • 0 bytes of token maps on disk
  • Compute in Germany
  • AES-256-GCM for credentials
  • No model training on payloads

Trace a request through memory.

Ephemeral vault

In memory. The pair token ↔ value lives in encrypted process RAM.

Protected. TTL from 15 minutes to 7 days, depending on plan.

Destroyed. No SSD, disk volume, or token table.

Draft a TOMs note for counsel.

Pick the data, the model, and the deployment. Copy the paragraph. It describes Maskio’s measures. It does not certify your whole stack.

TOMs summary

Processing mode: MCP reverse proxy.
Data category declared: Customer CRM PII.
Maskio processes payloads in volatile RAM in Germany. Token maps are not written to disk.
OpenAI API receives semantic tokens, not the original customer crm pii.
Audit records store timestamps, workspace IDs, latency, and entity counts. They do not store raw prompts or resolved values.
Upstream credentials use AES-256-GCM envelope encryption and are decrypted only for the active request.

Envelope encryption

CRM tokens, database strings, and provider keys are encrypted at rest with AES-256-GCM and an EU-hosted key service.

Just-in-time decryption

Secrets are opened in worker memory for the request being routed. The model sees the gateway URL, not the upstream credential.

Tenant namespaces

Each workspace has its own routing keys and token namespace. Agency clients do not share a dictionary.

What logs hold, and what they never hold.

DimensionMetadata we storeNever stored
RequestStatus, latency, byte sizeRaw prompts, completions, CRM JSON
EntitiesCategory and countNames, emails, IBANs, clinical text
Token mapTTL expiry timeA durable token-to-plaintext table
DocumentsPage count and OCR durationThe original PDF or extracted text

EU hosting

Production compute is in Germany. Cloudflare terminates DNS and the public edge for maskio.io, api.maskio.io, and mcp.maskio.io. See sub-processors before you tell a client “no US company is involved”.

No training

Customer prompts, documents, and proxy payloads are not used to train or fine-tune models.

Disclosure

Report vulnerabilities to security@maskio.io. The policy file is at /.well-known/security.txt.

Questions

Where does processing run?+

Application compute for the API and MCP gateway runs in Germany. Token maps are process memory, not a database of plaintext.

What is written to logs?+

Timestamp, workspace, gateway, latency, payload size, and entity counts such as “2 IBANs masked”. Raw prompts, CRM bodies, and resolved tokens are not logged.

Who are the sub-processors?+

The current list is published at /sub-processors and names the infrastructure providers that actually sit on the request path.

Need the DPA or a free gateway?

Read the Article 28 draft or open a workspace.