See it in action.
Seven real screens from the product — what privacy operations look like when AI drafts the routine work, your team signs off, and every step lands in an append-only audit trail with cryptographic receipts a regulator can re-verify.
The whole privacy program, on one screen.
Open the app and immediately see what needs attention: open DSARs ticking down to their deadline, escalations waiting for review, vendor reviews coming due, and the month's Q&A volume.
- Color-coded DSAR tile turns red when something is ≤ 7 days from deadline.
- Latest three escalations preview right on the home screen.
- Trial banner + onboarding checklist for fresh workspaces.
Latest escalations
Grounded answers, with receipts.
Type a privacy question. The assistant retrieves the relevant paragraphs from your uploaded policies and approved-vendor inventory, drafts an answer, and shows you exactly which sources it leaned on.
- Composite confidence (retrieval × LLM self-confidence × citation validity).
- Low-confidence or out-of-policy questions escalate to your privacy team automatically.
- Built-in prompt-injection and conflicting-intent detection.
Drew on: 4 chunks from your documents · 3 cited
Yes, with the existing DPA on file. Acme Analytics is listed as an approved processor for product-usage telemetry under your Vendor Privacy Policy (last reviewed Jan 2026).
- Data residency: EU only. Confirm your Acme tenant is in the eu-central-1 region.
- Retention: 13 months, per your retention schedule.
- Special categories: not permitted.
Review, edit, approve — one click.
When the AI isn’t confident or detects a conflicting intent, the question lands in your inbox with a draft answer pre-written. Review the source citations, edit if needed, and approve.
- Intent chips flag prompt-injection, conflicting requests, hard-blocks.
- Independent judge model verifies every draft — its note appears below.
- Markdown-rendered draft so structured AI output reads cleanly.
AI draft answer
You have two conflicting requirements here — the right of erasure (GDPR Art. 17) and a statutory retention obligation (typically 6–7 years for tax records). Both can co-exist:
- Erase personal identifiers (name, email, address) from the customer record.
- Retain the order history with the personal identifiers redacted (a pseudonymous customer ID is fine).
- Document the legal basis for retention in your Records of Processing under "tax compliance".
Article 35 in ten minutes, not ten hours.
Describe a new processing activity in plain language. The AI drafts an Article 35-defensible DPIA with screening, scored risks, and mitigations. You review and approve.
- 3×3 likelihood × severity heatmap with numbered chips that jump to the matching risk row.
- Inline editing on every field.
- Approved DPIAs sync into your RoPA (Records of Processing) automatically.
Customer support AI assistant — DPIA
DPIA required: Yes · Residual risk: Medium · Status: Approved
Risk heatmap
| # | Risk | L | S | Status |
|---|---|---|---|---|
| 1 | Stored chat logs include incidental PII | Low | Low | Mitigated |
| 2 | LLM provider data residency outside EU | Med | Med | Owner |
| 5 | Prompt injection extracts other tenants' data | High | High | Active |
From inbound email to closed request, with the regulatory deadline enforced.
The AI classifies an inbound email as a deletion / access / portability / opt-out request and starts the verification flow. Once you verify the requester’s identity, every department that holds their data gets a tokenized link to confirm what they hold and take action.
- Five-step lifecycle stepper across every DSAR.
- Per-DSAR fan-out to your configured department contacts.
- Aggregate completion email back to the requester when every team has responded.
Deletion request — Sarah Kim
Department fan-out · 2 of 5 responded
The AI surfaces the tension. You sign it off.
When a DSAR has cross-jurisdictional friction — a deletion request meeting a litigation hold, a portability request running against an IRS retention rule — the AI drafts a flag: the relevant statutory texts, the customer-authored facts, and a verbatim line that the obligations interact and resolution is the human’s. It cites only from a corpus reviewed by external counsel, scoped to your jurisdiction.
- Schema-level guarantee: no signed-off determination can land without an authenticated user id and a non-empty citations array.
- Closed citation menu — the AI cannot invent a statute reference; the validator rejects any id not in the corpus.
- Gated per-jurisdiction on an external UPL review; reviewed list is at
/api/upl/reviews. - Audit chain records the signing user, the draft it came from, and the prompt+hash that produced it.
Cross-jurisdictional conflict flag
Controlling texts
- GDPR Art. 17(3)(e) names a carve-out from the deletion right for legal claims.
- FRCP 37(e) creates preservation duties once litigation is reasonably anticipated.
Observed facts
- A litigation-hold marker is set on this subject (set 2026-04-12).
- Your retention policy cites IRS §6001 for related business records.
One click. A regulator can verify it without an account.
Every closed DSAR can produce a signed evidence packet: a JSON bundle of every audit event, verification trace, and completion proof, Ed25519-signed under a domain-separated prefix. The same data renders as a printable HTML the customer’s privacy lead saves to PDF for the regulator.
- Public verifier at
/api/audit/evidence-packets/verify— no authentication required, regulator pastes the JSON, gets a yes/no with the signing-key fingerprint. - Byte-stable: re-issuing the packet on the same DSAR produces the same bytes (deterministic canonicalisation, no timestamp jitter).
- Signing key is itself published at
/api/audit/transparency-keyso a reviewer can pin it. - Backed by the same daily Merkle-root + Bitcoin + Sigstore Rekor anchoring chain as Invariant 3 on the trust page.
Signed evidence packet
Ed25519Regulator-facing bundle of audit events, verification trace, and completion proof for this DSAR. Signed under the workspace’s transparency key; verifiable without an account.
POST /api/audit/evidence-packets/verifyResponse: { signature_valid: true } + signing-key fingerprint + canonical SHA-256.
"schema": "https://privacyautomated.ai/schemas/evidence-packet/v1",
"dsar_id": "5fe…",
"controller": "Acme Ltd.",
"audit_events": […],
"signature": {
"algorithm": "ed25519",
"domain_prefix": "PA-EVIDENCE-PACKET-V1\n",
See it on your own data.
Sign up free, upload one privacy policy, ask the AI a question about your actual workflow. Takes about three minutes.
Start free 14-day trialNo credit card required · Drops to Free after, your data stays