Skip to main content

Solutions

Answer the DSAR. Do not leak the third parties.

For DPOs, privacy ops, and counsel who have to produce a subject access pack without drowning in page-by-page markup.

A DSAR mixes the requester with dozens of other people. Fast Track reviews by identity. Pseudonymize keeps the story readable. Binders turn 40 PDFs into a pack the subject can open. Verification blocks download if leftover personal data survives. Prompt Guard stops staff pasting the file into ChatGPT. Outbound Guard SoftBlocks unmatched CPR when the DPO replies from Outlook. Clocks and audit sit on the case.

30-day free trial · no card required

User stories

When this is already the job

Each When should make you nod. The ink cell is the module that sits in that moment. Then is the useful part: what it does, and what you stop doing in Word, Excel, Outlook, or a zip.

  1. When

    A subject access request lands with hundreds of pages from HR, CRM, and email.

    Northdocs

    Fast Track

    Accept the subject once across the set

    Then

    Dossiers group the requester and every third party. Accept the subject once. Everyone else stays protected without page-by-page markup in Adobe.

  2. When

    The 30-day GDPR clock started last Tuesday, and Legal still has not sent the file list.

    Northdocs

    DSAR clocks

    Pause, extend, and overdue heat

    Then

    Pause and extend with a recorded reason. The board shows overdue risk for the whole cell, not one person's calendar reminder.

  3. When

    The export mixes the requester with colleagues, customers, and a child.

    Northdocs

    Pseudonymize

    Person 1 stays readable, identity stays linked

    Then

    Reviewers keep the narrative. Identity stays linked as Person 1. Blackout when it must disappear. You are not choosing between an unreadable pack and a leak.

  4. When

    You need a pack the subject can actually open, not a dump of 40 PDFs in a zip.

    Northdocs

    Legal binders

    One TOC-ready export from the case

    Then

    Assemble a contents page on the verified files. Verification still blocks leftover personal data before that pack exists. The subject gets one document, not a folder.

  5. When

    A privacy analyst pastes the hardest page into ChatGPT to see if it is in scope.

    Northdocs

    Prompt Guard

    Clipboard wipe before ChatGPT

    Then

    CPR, emails, and phones leave the clipboard before paste. The question can still go. The file cannot become a prompt.

  6. When

    The DPO replies from Outlook, and last week's thread still has a CPR in the quoted mail.

    Northdocs

    Outbound Guard

    Send-time SoftBlock, body-free evidence

    Then

    Unmatched CPR stops at Send. You get counts and destination class for the accountability pack. No mail bodies stored.

  7. When

    The access request includes Teams chats and a recorded 1:1.

    Northdocs

    Conversation Redact

    Same identities on chats and audio

    Then

    Review speaker turns with the same Fast Track as documents. Names and IDs leave the transcript. Voices can beep, silence, or anonymize.

Activity map

What this team uses Northdocs for

Not a feature list. Grouped the way the work shows up.

Subject access production

  • Identity-first review

    Dossiers group name, email, ID, and phone so you do not hunt page by page.

    How the job works
  • Requester versus everyone else

    Release the subject's data. Redact or token third parties consistently across the set.

    How the job works
  • 30 calendar-day clock

    Pause and extend with a recorded reason. Deadline heat on the case board.

    How the job works
  • Withholdings and memo

    Art. 15(4) and related bases on the exemption schedule, then a response memo from those rows.

    How the job works
  • Fail-closed export

    Re-extract after apply. If a name or ID survives, download is refused.

    How the job works
  • Subject pack binders

    One TOC-ready export the subject can open, packed from the same case that ran Fast Track and verify.

    How the job works

Everyday leak paths

  • Prompt Guard

    Clipboard wipe before ChatGPT, Copilot, or an internal bot.

    How the job works
  • Outbound Guard

    SoftBlock unmatched CPR when privacy staff reply from Outlook.

    How the job works
  • Conversation Redact

    Chat exports and meeting audio that arrived as part of the access request.

    How the job works

What the DPO has to show

  • EU residency

    OVHcloud Frankfurt by default. Trust Center, DPA, and subprocessors published.

    How the job works
  • Audit export

    Who accepted which identity, on Firm and above.

    How the job works
  • AI off or EU AI

    Deterministic detectors first. Optional AI is OVHcloud AI Endpoints, not a US-only path.

    How the job works

Questions this team asks

Can we pseudonymize instead of blacking everything out?
Yes. Choose Redact or Pseudonymize per category so reviewers keep narrative context while identity stays protected.
What if AI misses something?
Structured IDs are caught by deterministic validators first. Unreviewed items can block export, and verification rejects surviving sensitive strings.
Is this only for public-sector DSARs?
No. Privacy ops in companies use the same DSAR path. Municipal FOI is a sibling workload with its own clocks and OFL bases.

Start with the pack you have to ship

Upload a real FOI, DSAR, or litigation file and download only after verification passes. Add Outbound Guard when mail is the next leak.