Witnio.
Trust

What actually protects your data and evidence

No certifications, no badges — just the controls that are actually running, described exactly as they run.

How a request stays inside its own tenant

TENANTAPI KEY (scoped)EVIDENCE (signed)DEVICE (real)OTHER TENANTdeny by default
01

Tenant isolation

  • Deny-by-default access between tenants
  • Every query scoped to the authenticated tenant ID
02

Authentication

  • Multi-factor authentication: enroll, verify, challenge, reset
  • Session and refresh-token handling scoped per tenant
03

API keys

  • Scoped to the permissions they need, nothing more
  • Rotation supported without downtime
04

Rate limiting & domain verification

  • Per-tenant rate limits on every public and authenticated endpoint
  • Corporate domain verification before enterprise access
05

Auditing

  • Every tenant has its own audit trail of sensitive actions
  • Audit records are never editable after the fact
06

Masking

  • Sensitive content masked before it is persisted
  • Masked before it is ever sent to an AI provider
07

Retention

  • Screenshots: 90 days
  • Logs: 30-90 days depending on type
08

Network

TLS everywhere, delivered through a Cloudflare Tunnel. The device fleet is never directly exposed to the internet.

09

Kill switch

Every product has its own kill switch, independent of the others.

10

Containers

Every container runs as a non-root user with all Linux capabilities dropped — verified today across the running fleet.

11

Evidence signing

Every manifest is Ed25519-signed over its JCS-canonicalized form and independently verifiable through the public verifier or the public keys endpoint.

Verify an evidence file

Not a substitute for certification

Witnio produces evidence that can support your controls or your own audit. It does not replace legal advice or independent certification.