Skip to main content

The last check before a file leaves. With a record of what it carried.

A privacy office signs off what leaves the organisation, and is asked about it months later.

The free check reads a Word, Excel, PowerPoint or PDF file in the browser and lists what the page does not show, such as a comment with its author's name, a tracked change, the author field or a hidden sheet. The file is not uploaded, nothing is removed and no record is kept.

The paid workspace makes a processed copy with the removable items taken out, checks that copy again, and shows what was removed, what was kept and what still needs a person to look. When something is still in the file, the evidence PDF says "Review required" and lists it. The record holds the SHA-256 digests of the original and the copy. What to disclose stays the team's decision.

It does not search mailboxes, read the visible text for personal data or redact. The workspace is USD 999 a month plus VAT where applicable, for one organisation and up to 20 seats, by application, with a 14-day walkthrough and no card.

Representative scenario

Snapshot dated 8 October 2026.

No files are processed in this preview.

Access request SAR-0142, subject ref A-104

Response in DPO review

6daysleft to the recorded deadline, 14 October 2026
GDPR Art. 12(3)

response-letter.pdf

Metadata review pending

account-export.xlsx

Metadata review pending

Disclosure review

With Katrin Albers, DPO

What it is

ScrubMetadata is a workspace for the privacy office of one organisation in the EU, built around a check of each file before it is released. The free check is the first step and stands alone.

Six records a privacy office may be asked to show

  1. What left

    Process files

    Before a supported file leaves, the team processes it in the browser. The file itself is not uploaded. The workspace makes a processed copy and sorts everything the check found into three groups. Removed means gone from the processed copy. Kept means still in it, for example the file's own structure or content a reader can see. Needs review means still in it and left for a person to look at, for example white text in a Word file.

    In a Word file a comment is taken out, and a tracked change is taken out by accepting it, so text that was inserted stays as ordinary text and text that was deleted is gone.

    For one Word (.docx) or Excel (.xlsx) file at a time, the reviewer first says what the file is for, then chooses Keep or Remove for the author, last modified by, company and manager fields. You decide what the requester should receive. Your choice and reason are saved with the record. A kept field needs a reason, such as "The requester's own data", and stays in the processed copy. Comments, tracked changes and custom properties can still only be removed, and PowerPoint, PDF, image files and batches have no decision step.

    Some of what is taken out can be the requester's own personal data. A comment that gives an opinion about the requester is one example (EDPB Guidelines 01/2022, para. 96). Where it is, the processed copy is not the whole answer, and how the requester receives that data is for the team to decide.

    A second check then runs on the processed copy, and if it fails the result says so. The record keeps the names of the items that were removed (for example "Creator") without their values, and the SHA-256 digests of the original and the processed copy. The evidence PDF shows the four counts of the result: inspected, removed, kept and needs review. A digest is a fingerprint of the exact bytes, so a matching digest shows the same file. It does not show that the disclosure was right. The record does not list which files were sent on a case.

    In an Excel file a hidden worksheet is taken out of the processed copy without a decision. Hidden rows and hidden columns are listed as still in the file. The result on screen names the sheet, the columns and the rows; the evidence PDF and the record name the kind of item only.

  2. When it arrived, and when the reply is due

    Subject requests

    The request record holds the receipt date the team enters and the date one month later. Art. 12(3) GDPR asks for a reply "without undue delay and in any event within one month of receipt of the request".

    The workspace counts from the receipt date. It does not work out a later start or a pause, for example while the team waits for proof of identity or, in the UK, for clarification under Art. 12A(5) of the UK GDPR.

    The record does not search for the data or judge an exemption. A completed case does not show that the reply was delivered or that it was lawful.

    A subject request is not a two-person step. One person can take it from receipt to completion.

  3. The advice, and the decision

    Impact assessments

    The assessment keeps its version history and the DPO's advice.

    The full text of the assessment is held in the browser that created it. The workspace cannot rebuild it if that copy is lost, so the team should keep its own copy. The record does not assess the risk.

    The person who wrote or submitted an assessment cannot approve it. Approval needs a second member with the DPO role.

  4. What is processed

    Processing records

    The register holds each processing activity under nine field groups that cover the points in Art. 30(1) GDPR, from the controller's name to the security measures, and exports the recorded rows for the selected organisation. It does not find processing that nobody declared. An export shows what was recorded. Whether the register is complete is for the team to judge.

    Activating a record is not a two-person step. The person who created it can activate it.

  5. What was decided, and when

    Breaches

    The breach record holds the time the team became aware, as the team enters it. That time can be earlier than the time the record was opened. The record shows the point 72 hours later and keeps the notification assessment, with an export.

    Art. 33(1) GDPR asks for notification "where feasible, not later than 72 hours after having become aware of it", unless the breach is unlikely to result in a risk to people's rights and freedoms. Art. 33(5) says the controller "shall document any personal data breaches", and the EDPB reads that as all of them, notified or not (Guidelines 9/2022, para. 121). Whether to notify is the team's decision.

  6. What is still open

    Tasks and approvals

    A task can be created, started and completed. A request raised from incident response is listed in Approvals, and the person who raised it cannot decide it. An administrator at ScrubMetadata decides that request, not the team. Tasks have no approval step and no export.

    The record does not hold a stand-in for an approver who is away, or the reason for an exception.

What it does not do

  • It does not search mailboxes or collect documents.
  • It does not read the visible text for personal data, and it does not redact. Keep the tools your team uses for that.
  • It does not accept email files (.eml, .msg) or the older Office formats (.doc, .xls, .ppt). An office whose disclosures are mostly email should wait.
  • It does not decide what you disclose, whether a breach is reportable or whether you comply. A person decides.

Where your files and data go

  1. 1The file. A supported file is read and processed in the browser tab and is not uploaded. The free check sends nothing about it. In the workspace these are sent: the few leading bytes that identify the file's format, the record in the next line, and usage figures such as the file's size and the time processing took.
  2. 2The record. The workspace receives the record of each check and whatever the team enters on a case. The record includes the file type and size, a generated identifier in place of the file name, the two SHA-256 digests, the counts, and the name, category and risk level of each item found, without its value. What the team enters on a case includes personal data, such as a requester's name and email address.
  3. 3Where it is held. The application runs in Frankfurt (Vercel, region fra1). The database and the cache are in Frankfurt too (Neon and Upstash, AWS eu-central-1).
  4. 4What is outside the EU. This is not an EU-only service. Resend sends email from Ireland and stores its records of those emails in the United States. Audit checkpoint files are in a Vercel store in the United States. The contact mailbox is at Zoho in India. Vercel's network serves pages worldwide, and Paddle, Sentry and Cloudflare have their own locations. The operator is in Nepal. No transfer mechanism for a customer's account is presented as complete. The provider register says what is established for each provider and what is not.

Who operates it

ScrubMetadata is operated by Anju Kumari Dhital, an individual, from Biratnagar, Nepal. No company is registered. Paddle is the merchant of record for payments.

The Data Processing Agreement is published as a draft. It names the operator as the processor. Once it is approved, it is accepted at checkout.

There is no SOC 2 report and no ISO 27001 certificate, and no independent penetration test has been carried out. There is no paying customer yet. No EU or UK representative has been appointed. The operator intends to appoint an EU representative before the first paid agreement starts.

USD 999 a month, or USD 9,990 a year paid in advance, plus VAT where applicable, for one organisation and up to 20 seats. The workspace is by application and admin approval. The 14-day walkthrough needs no card. Whether it is worth that to your team is something to test during the walkthrough.

Show it a year later.

EU privacy workflows and metadata removal · ScrubMetadata