01
Credentials
Every connector asks for read-only access scoped to a prefix, a schema or a topic. Nothing is installed inside your database. If a connector needs write access to function, we treat that as a bug in the connector.
- Access
- Read-only
- Scope
- Prefix or schema
- Agent
- None installed
02
Encryption
AES-256-GCM at rest, TLS 1.3 in transit, with no downgrade path. Keys stay in your own KMS on Professional and Enterprise, so revoking our access is a change you make on your side and not a support ticket on ours.
- At rest
- AES-256-GCM
- In transit
- TLS 1.3
- Key custody
- Customer managed
03
Isolation
One tenant, one key, one logical store. Quarantined rows never leave the region they were ingested in. Self-hosted deployments run entirely inside your own network boundary, with no outbound call required to validate a row.
- Tenancy
- Logically isolated
- Data residency
- EU, US, or your VPC
- Egress
- None required
04
Access
Decryption passes through a broker, so there is one ordered access log in one clock and one format. Role changes, policy edits and every decrypt land in the same append-only ledger as validation results.
- Log
- Append only
- Retention
- Up to 7 years
- Export
- CSV, Parquet, JSON