LONG GATE · TRUST REPORT

Privacy processing, made visible.

This report contains no source row values. It shows what Long Gate did, what was blocked, what could leave the trusted zone, and why.

Gate status

BLOCKED · Synthetic data failed the privacy gate.

Rows

Columns

Backend

demo

Network send

Blocked

Processing path

1 · Source

Local file · SHA-256 recorded

→

2 · Inspect

Schema + sensitivity · local

→

3 · Synthesize

No deterministic identity mapping

→

4 · Audit

Copy/linkage checks · local

→

5 · Gate

Default deny · safe payload only

Who can see what

Data	Local worker	Local model	Network AI
Raw rows	YES	OPTIONAL	NO
Real identifiers	YES	OPTIONAL	NO
Pseudonym mapping	LOCAL ONLY	NO	NO
Audited synthetic rows	YES	YES	NO
Aggregate results	YES	YES	ELIGIBLE

Privacy audit

Exact row overlap

Identifier overlap

Quasi-combo overlap

Near-copy rate

0.00%

Selected backend is marked demonstration-only and cannot pass the egress gate.

These are v0.1 engineering checks, not a formal guarantee of anonymity or differential privacy. A backend marked demonstration-only can never pass the egress gate.

Column treatment

Identifiers regenerate; quasi-identifiers, sensitive values, and general values use synthetic generation. Source row values are not shown in this report.

Run timeline

localRun startedTrusted local pipeline initialized.

localPrivacy audit completedBLOCKED because the demo backend is intentionally non-egress.

Provenance

Policy	`deny-by-default / v0.1`
Long Gate version	`0.1.0`