How Privacy Automated handles privacy & security.

Privacy Automated uses Privacy Automated to operate its privacy program. This page is generated automatically from the live workspace and reflects the current state of the sub-processor inventory, policies, and platform-level security controls.

Operates under: US-FL

Sub-processors

Third parties Privacy Automated authorises to process personal data on their customers' behalf. List is generated live from Privacy Automated's approved-vendor inventory.

Sub-processor	Purpose	Location	Role
Anthropic, PBC	Large-language-model inference and verification (Claude) for AI features — Q&A drafting, DPIA / PIA generation, DSAR classification, vendor	US (United States)	processor
Backblaze, Inc.	Off-site, encrypted, geographically separated backup storage for the application database.	US (US-East)	processor
Clerk, Inc.	Identity, authentication, and organization management (sign-in, SSO, MFA, workspace membership).	US (United States)	processor
Cohere Inc.	Reranking of search results for relevance	Canada	processor
Hetzner Online GmbH	Application and database hosting (compute, storage, networking, physical security) for the Privacy Automated platform.	EU (Falkenstein, Germany)	processor
Monkey See Monkey Do, s.r.o. (Healthchecks.io)	Dead-man's-switch monitoring of scheduled jobs (backup pipeline, daily expiry tasks). Alerts on failure.	EU	processor
Postmark (ActiveCampaign LLC)	Transactional email delivery (escalation notifications, DSAR routing emails, customer ack messages) and inbound email parsing for the privac	US	processor
Sentry (Functional Software, Inc.)	Application error monitoring — captures stack traces and request context when the API or web app encounters an unhandled error.	EU (Frankfurt, Germany — Sentry EU region)	processor
Slack Technologies, LLC	Engaged only when a workspace installs the Slack integration. Routes inbound privacy questions and DSAR receipts from the customer’s Slack w	US	processor
Stripe, Inc.	Billing, subscription management, payment processing (Managed Payments).	US (United States)	processor
Voyage AI (a MongoDB company)	Text embeddings for semantic search / retrieval-augmented generation	United States	processor

Platform security

Controls maintained by Privacy Automated (the underlying platform) that apply to every workspace, including this one.

TLS 1.2+ for all customer-facing traffic, HSTS enabled.
AES-256 encryption at rest for the application database.
Row-level security (PostgreSQL RLS) enforces workspace isolation at the database engine.
Daily off-site encrypted backups (Backblaze B2), 35-day retention, restore drilled.
Identity provided by Clerk (SOC 2 Type II). MFA available to all administrators.
Payment processing by Stripe (PCI DSS Level 1). No card data stored by Privacy Automated.
Application error monitoring with PII scrubbing (Sentry).
Audit log of every significant action — visible to the workspace administrator.

Continuously-verified controls

Commitments Privacy Automated re-verifies automatically every day. Each verdict is computed deterministically and committed to Privacy Automated’s daily public transparency root (anchored to Bitcoin). Only currently-passing commitments are shown.

DSAR deadlines metVerified Jul 21, 2026
Lawful basis declaredVerified Jul 21, 2026
Periodic reviews on scheduleVerified Jul 21, 2026
Policy matches processingVerified Jul 21, 2026
Required DPIAs completedVerified Jul 21, 2026
Retention periods declaredVerified Jul 21, 2026
Special-category condition recordedVerified Jul 21, 2026
Vendor certifications currentVerified Jul 21, 2026
Vendor DPAs in placeVerified Jul 21, 2026

Privacy policy

Privacy Automated keeps its published policy in sync with what it actually does. Each version below is signed and anchored to Privacy Automated’s public transparency log, so you can confirm the policy was current as of the date shown.

Vendor Management Policyv1signed

Current as of July 20, 2026.

manifest 7cf10434fdbd347b…

Customer Privacy Noticev8signed

Current as of July 20, 2026.

manifest 928f7a5448a246f6…

Verify independently: fetch the Ed25519 key at /api/keys/signing and confirm the publication event in the daily transparency roots.

Public verifier · no account required

Verify a sealed packet from Privacy Automated

If Privacy Automated has shared a signed evidence packet with you — a sealed DSAR, an approved DPIA — paste its JSON below. The verifier re-checks the Ed25519 signature against the transparency key published at /api/audit/transparency-key — no account, no API key, no contact with Privacy Automated or PrivacyAutomated required.

Don’t have a sample to verify? Ask Privacy Automated for one — sealed packets are a one-click download from any closed DSAR or approved DPIA in their workspace, and the bytes are byte-stable so the same record produces the same packet every time.

Paste the evidence-packet JSON

Three ways to convince yourself, in order of setup cost

1Read the verdict

Zero setup

The verifier above re-canonicalizes the packet you pasted (sorted keys, compact separators), prepends the domain prefix PA-EVIDENCE-PACKET-V1\n, and Ed25519-verifies the embedded signature against the public key at /api/audit/transparency-key. If the result above says authentic, the packet’s bytes haven’t changed since the customer sealed it.

2Check our side offline

One terminal, no network round-trip

Download the public Ed25519 verification key once, then verify any packet bytes locally — without ever talking to our servers afterwards:

# Once: fetch the public key
curl -o pa-transparency.pem \
  /api/audit/transparency-key

# Per packet: pull the sig, zero that field, prepend domain, canonicalize, verify
python3 -c "import json, base64; \
  d = json.load(open('packet.json')); \
  sig = base64.b64decode(d['verification']['signature_base64']); \
  d['verification']['signature_base64'] = ''; \
  body = b'PA-EVIDENCE-PACKET-V1\n' + \
    json.dumps(d, sort_keys=True, separators=(',',':')).encode(); \
  open('/tmp/sig', 'wb').write(sig); \
  open('/tmp/body', 'wb').write(body)"
openssl pkeyutl -verify -pubin -inkey pa-transparency.pem \
  -rawin -in /tmp/body -sigfile /tmp/sig

Signature Verified Successfully = same answer as the verdict above, no trust in our server required after the initial key fetch.

3Verify against Bitcoin without trusting us

Requires a Bitcoin node (yours or a public RPC)

The packet’s seal references the daily audit-event Merkle root, which is itself anchored to Bitcoin via OpenTimestamps. The full verification chain — packet → audit chain → daily Merkle root → Bitcoin block height → block in YOUR Bitcoin — is documented step-by-step at privacyautomated.ai/trust-architecture.html (Invariant 3). Most regulators don’t need to go this deep, but the option exists, and it’s the answer to “but how do I know you didn’t just sign a fake timestamp?”

What the seal proves

The packet bytes are unaltered since sealing.
The sealing happened on the embedded date.
The named human signed off.
Any AI inference that touched the record was running the named system prompt at the named SHA-256 hash.
The audit-event chain is intact from the start of the record to the seal.

What the seal does not prove

Legal correctness. The seal proves the DSAR closed in 21 days; it does not prove 21 days satisfied the regulatory obligation. That’s a separate claim involving deadline math + legal judgment.
Truth of the inputs. The seal proves nothing was altered after sealing. It does not prove the privacy team did the underlying work correctly. Garbage in, signed garbage out.
What a court would conclude about the underlying records. That’s for your counsel.

The full engineering substrate behind these claims is documented at privacyautomated.ai/trust-architecture.html.

Have a question?

Skip the questionnaire. Ask Privacy Automated’s privacy team directly — about sub-processors, data residency, certifications, DPAs, anything. They’ll reply to you by email, and may point you at one of the proof packs above.