Platform documentation.

Pryvonis is an operational privacy management platform. It gives privacy, legal, and compliance teams a single place to handle data subject requests (DSRs), manage consent, and keep a tamper-evident audit record of every action taken.

It is designed around how privacy work actually happens — with multi-channel broker outreach, evidence collection, workflow state tracking, and operator verification — not just a ticketing system with a privacy label on it.

Cases — a single privacy request from a subject (erasure, access, portability). One case can span many brokers.

Workflows — the operational unit. One workflow = one outreach attempt to one broker on behalf of one case. Workflows progress through states: created → preparing → notice sent → awaiting response → response received → verifying → verified → closed.

Brokers — data controllers and processors in the registry. Each broker has a contact channel (email, portal, API), priority tier, and metadata.

Evidence — every material action produces an evidence envelope: a SHA-256 hash-chained record of what was sent, when, and what was received. Evidence cannot be altered after creation.

Audit log — append-only log of all operator and system actions, linked to the actor, resource, and timestamp.

Pryvonis is currently in private pilot. Access is invite-only.

To apply: go to pryvonis.com/pilot and submit your application. The team reviews applications within 2–3 business days. Approved applicants receive an email with a link to set their password and access the platform.

Once logged in, your account is pre-configured as a tenant admin. You can invite colleagues from Settings → Team Members.

• 1. Go to Cases → New Case.
• 2. Select or create a subject (name + email minimum; phone and address are optional).
• 3. Choose the request type: Erasure (right to be forgotten), Access (DSAR), or Portability.
• 4. Set the jurisdiction (EU/GDPR, UK GDPR, US/CCPA, etc.).
• 5. Save — the case is created with a unique case number and a 30-day statutory deadline calculated automatically.

  From the case detail view you can create one workflow per broker, or use the bulk-create flow to target multiple brokers at once.

|-------|---------|

Pryvonis supports three live channels:

Email notice — generates a GDPR/CCPA-compliant erasure notice from a template and sends it to the broker's DPO or privacy contact. Fully tracked for delivery, bounces, and responses.

Portal submission — operator submits a request via the broker's privacy portal (Typeform, OneTrust, custom form). Pryvonis records the submission as evidence with a SHA-256 request digest.

DSR API — automated submission to brokers that expose a standardised DSR API (e.g. OneTrust-powered portals). The full request and response are hashed and stored as evidence.

The routing is resolved automatically from broker metadata. You can also override the channel manually when creating a workflow.

When a broker responds (by email or otherwise):

1. Open the workflow in Workflows.

• 2. Expand the row and click Record Response.
• 3. Select the response type: Removal confirmed, Rejected, More info requested, Acknowledged, or Bounce/delivery problem.
• 4. Paste the response body or notes.
• 5. Save — the workflow transitions to response_received and a response_received evidence envelope is created.

  If the response confirms deletion, proceed to Verify Removal.

Verification is the final step before closing a workflow. It confirms that deletion actually happened.

1. Open the workflow → click Verify Removal.

• 2. Choose a verification method:

- Operator attestation — operator reviewed response and attests deletion

- Re-query check — operator re-queried the broker and confirmed the record is gone

- API response — automated API response confirmed deletion

- Subject self-report — subject confirmed they no longer appear in search results

• 3. Set confidence: High / Medium / Low.
• 4. Add notes (optional — required for audit purposes in regulated environments).
• 5. Save — workflow moves to verified with a deletion_verified evidence envelope.

Every workflow produces a hash-chained evidence record. The chain is:

1. notice_prepared — the notice payload (template + subject data merged) is SHA-256 hashed. Hash stored as requestDigest.

• 2. notice_sent — the delivery confirmation or submission result is hashed as responseDigest.
• 3. response_received — broker response envelope (if any).
• 4. deletion_verified — operator verification record with method, confidence, and notes.

  Each envelope links to the previous one's digest, creating a chain that detects any post-hoc tampering.

  View the chain at Evidence → filter by case or workflow.

The audit log records every material action:

• - Who did it (actor email or system)
• - What resource was affected (case ID, workflow ID, broker ID, etc.)
• - What action was taken
• - When (UTC timestamp)

  The audit log is append-only. No entry can be modified or deleted through the application. View it at Audit in the sidebar.

  For compliance purposes, you can filter by resource type, actor, or date range.

The broker registry contains 112 data brokers and data controllers, each with:

• - Category — data_broker, enrichment_provider, reverse_lookup, advertising_identity_graph, people_search_engine
• - Priority tier — Tier 1 (highest reach/risk), Tier 2, Tier 3
• - Channel capability — email, portal URL, DSR API, suppression list
• - Workflow path — how Pryvonis routes requests to this broker

  The Coverage view (sidebar) shows registry health: how many brokers have metadata, how many have been live-tested, and which Tier 1 targets are still untested.

Each broker in the registry can have extended metadata (broker_registry_meta):

- Target category — more specific than the base broker type

• - Workflow flags — direct_workflow_supported, suppression_supported, guide_only, manual_escalation_only
• - Portal URL — link to the broker's privacy/opt-out portal
• - DSR API config — for brokers with a machine-readable DSR endpoint (e.g. OneTrust)
• - Data types held — what categories of personal data this broker typically holds
• - Live tested — date and channel of the last verified live workflow run

  Metadata drives automatic routing: when you create a workflow, Pryvonis resolves the optimal channel from the broker's meta.

To invite a colleague:

1. Go to Settings → Team Members.

• 2. Enter their first name, last name, and work email.
• 3. Click Send invite.

  They will receive an email from Pryvonis with a link to set their password. The link expires after 24 hours. Once they complete setup, they appear in the member list with the role you assigned.

  New invitees are given Admin role by default. You can change this to Viewer from the member list.

|------|--------|

To prevent a user from accessing the platform:

1. Go to Settings → Team Members.

• 2. Find the user and click Disable.

  The user's session is invalidated and they cannot log in until re-enabled. Their audit history and any data they created is preserved. You can re-enable them at any time with the Enable button.

  Note: you cannot deactivate your own account.

Users can reset their own password from the login page by clicking Forgot password?.

They will receive a reset link by email valid for 15 minutes. If the email does not arrive, check the spam folder or ask your admin to resend the invite.

Admins cannot directly set a user's password. If a user has lost access and the reset email is not arriving, contact [email protected].