Privacy & Compliance

Redact PII
before it ever leaves.

Your raw records never leave your environment. SentraZero runs redaction and preprocessing locally — the control plane provably never sees the content.

Zero client data in the control plane.
The proof

Sovereignty you can verify, not just claim

Compliance teams ask for evidence. Here it is — the control plane holds only metadata, so your raw data has nowhere to leak.

0 rows

Client data in the database

Verified in production: vector_store, step_outputs, and plugin_execution_history contain zero rows of your content. The control plane stores metadata only.

Ed25519

Signed, sandboxed plugins

Every redaction plugin is cryptographically signed and executes in a sandbox. Unsigned code cannot run.

RLS

Per-org isolation

Organizations are separated by Row-Level Security. One tenant can never read another tenant's records.

Problems

Why current redaction fails compliance

Third-party redaction trades one risk for another: you solve PII exposure in your system by creating a copy of it somewhere you don't control.

Egress risk

Sending records to a redaction API moves the exact data you're trying to protect across a boundary.

No verifiable proof

"Redaction ran" isn't evidence. Auditors want to know what ran, which version, on which data.

Drift between environments

Dev, staging, and prod run different script versions — so the redaction you tested isn't the one in production.

Unenforced policy

A redaction policy written in a doc isn't the same as a control enforced on every single run.

Solution

Redaction that runs where the data lives

The redaction plugin executes inside your environment on CSVs, images, video, and documents. Every run emits a signed, immutable audit record. One engine. Every data type.

Local execution

Raw PII is read and redacted in place. No record transits to SentraZero.

Signed, identical logic

Ed25519-signed plugins guarantee the same redaction in every environment.

Audit-ready record

Timestamped, immutable log of what ran, on what data, by which version.

Stop on failure

If redaction fails validation, the pipeline halts before any data flows downstream.

Run the pipeline. Keep the data.

The control plane is proof, not a liability

Because the control plane stores only metadata, there is nothing to exfiltrate, subpoena, or accidentally log. Your compliance story becomes simple: the platform that orchestrates your redaction cannot contain the data it protects. That is the difference between “we promise” and “we can show you.”

vector_store
0 rows
step_outputs
0 rows
plugin_execution_history
0 rows

Bring the redaction to the data

Tell us where your sensitive records live and what you need to redact. We'll show you SentraZero running on your infrastructure — with the control plane empty of your data, by design.