For the DPO, compliance lead and Salesforce admin at a UK regulated firm

Find your PII. Prove your controls. Never move your data.

Org Warden finds the personal data in each of your Salesforce orgs, in fields, free text and documents, without a single value leaving the org. Every scan gives you an Evidence Pack you can verify by its hash: what was found, by which rule and check, and what was not read. The rules include UK identifiers checked the way their issuers publish, and each finding names the UK GDPR obligation it is evidence toward.

No value, record or file leaves your org.

What you get

Evidence you can hand to an auditor. Not a dashboard.

Every finding names the rule that produced it and the check it passed, inside an Evidence Pack whose hash anyone can re-verify. The pack also names what the scan did not read. In the Console, one rule opens onto every org and field where your packs say it matched, each line citing its pack, beside the orgs where it found nothing and the orgs where it never ran.

fig. 01illustrative · a made-up Estate of six orgs · no values, ever
The rule · the same in every Console
NHS number
What it matches
Ten digits, usually written 3-3-4, identifying a patient in England, Wales and the Isle of Man. Health data under UK GDPR Article 9.
The check
The last digit is a modulus 11 check, as the NHS Data Dictionary publishes it. A number whose check comes out as 10 was never issued and is refused. The first three digits must fall in an allocated range.
What a finding may claim
Validated. A passed check confirms the arithmetic. It does not show the number was issued to a person, or that it belongs to the record it sits in.
UK GDPR obligations it is evidence toward
  • Article 9: a condition for special category data
  • Article 30: records of processing
  • Article 35: data protection impact assessment
where it matched in your Estate
Your Estate · what your Evidence Packs state
3 fields found in values in 3 orgs
  • Scotland SalesMedical_Disclosure__c · Health_Number__cfound in values · Sensitive13 recordsPack of 1 Nov 2026
  • Scotland HRMedical_Disclosure__c · Health_Number__cfound in values · Sensitive16 recordsPack of 2 Nov 2026
  • Broker PortalMedical_Disclosure__c · Health_Number__cfound in values · Sensitive25 recordsPack of 5 Nov 2026
Checked, nothing found · 1 org

Claims — read 1 field with this rule and matched none, in a scan its pack says was complete. Pack of 4 Nov 2026

Not checked · 2 orgs

Group Finance, Group Risk — no pack from them ran this rule, so it is unknown there.

Every line cites the Evidence Pack that states it, and every pack is checked against its hash file. No value appears, because none left the org.
Where teams use it

Three moments when you need the answer in writing.

Audit and regulator requests

When an auditor asks where personal data sits, hand over the Evidence Pack for each org. Every finding names the rule, the check it passed and the UK GDPR obligation it is evidence toward, and the hash shows the pack has not changed since the scan.

Acquisitions and consolidation

Before an acquired org is merged into yours, install Org Warden in it and scan it in place, with no data taken out. Read it beside your own orgs in the Console: one rule opens onto every org where it matched, where it found nothing and where it never ran.

Data no map lists

Personal data turns up where no data map looks: case descriptions, emails, Chatter posts and attached files. The scan reads those as well as fields, and the pack names what it did not read, so a gap is stated rather than assumed away.

Purpose

Three questions your estate can't answer today.

These three questions land on the desk of whoever is responsible for Salesforce data. Today they take spreadsheets, custom Apex or a consultant. Org Warden answers them from its Evidence Packs.

fig. 02your estate · metadata plane · what we answer
Your Salesforce estate4 orgs
Production
email · NI number · phone · XLSX · case PII
Sandbox 1 · Dev
email · NI number · DOCX
Sandbox 2 · UAT
email · phone · JSON
Full Copy · Perf
email · NI number · phone · XLSX · case PII
metadata
counts · classes · telemetry
Org Warden · observer
counts · classes · snapshot hash
no values · no files · no records
Where
PII, cross-org, fields + files
Who
FLS breadth · sharing model
What
drift between two dated packs

Where is PII in our estate?

Before: Spreadsheets pieced together per org, per quarter, always stale.With Org Warden: A dated Evidence Pack per scan, from every org you scan, production or sandbox. Fields, free text, files and attachments, and a named list of what was not read.

Who can read it?

Before: Nobody. Access mapping happens in a different tool, or in nobody's tool.With Org Warden: Each field's FLS breadth across profiles and permission sets, and each object's org-wide default with an upper bound on its share table. Sharing rules and the role hierarchy are not read, and every pack says so.

What has changed?

Before: Diff two spreadsheets from different quarters. Best of luck.With Org Warden: Compare two dated, hash-verified packs of one org in the Console. What moved between the two scans, over the scope both covered, shows up as a row.
Why we built it this way

Every category default asks you to move your data first. Org Warden does not.

fig. 03ahow it's normally done
Your Salesforce org
records · files · fields
ingestrecords · values · filesboundary
Vendor cloud
your data · copied
  • Data leaves the org. Add another processor to your DPA.
  • Copies age. Findings drift from the source of truth.
  • Security review is about the vendor's environment, not yours.
  • Priced and deployed as an enterprise programme.
fig. 03bhow Org Warden does it
Your Salesforce org
records · files · fields
metadatacounts · classes · telemetryboundary held
Org Warden
metadata ledger
  • Values never leave. The package alone adds no processor; the Console holds pack metadata and your team's sign-in details, as our privacy notice sets out.
  • Findings are written in the org, per scan. Each pack is a dated, point-in-time record.
  • Security review is about absence, not architecture.
  • Priced per org, predictably, no seat maths.
From finding to control

You cannot encrypt what you cannot enumerate. A finding is the first time a control has something to bite on.

Security teams are rarely short of controls. Salesforce already ships encryption at rest, field audit history, field-level security, and event monitoring. What is missing is the list to point them at. Encrypting everything is unaffordable and breaks filtering and sorting; encrypting a guess is a control you cannot defend in a review. Once PII is enumerated per field, per file type, per org, with the rule and check that found it and a snapshot hash behind it, the mandate becomes writable: these fields, these orgs, this quarter.

01 · you can now
Mandate encryption at rest
Point Shield Platform Encryption at the exact fields that hold PII rather than a subset someone chose three years ago. The rule that fired, the check digit it passed and the snapshot hash give the scope a defensible provenance when procurement asks why these fields and not those.
02 · you can now
Tighten who can read it
The access map states each field's FLS breadth, each object's sharing model and the share table's upper bound, and names the sharing mechanisms it could not read. Restrict FLS or split a permission set with the actual breadth in front of you instead of an admin's recollection of it.
03 · you can now
Monitor where it earns its cost
Field Audit History and event monitoring are priced and performance-costed per field. Enable them on the fields that carry regulated data, and leave the rest alone.
04 · you can now
Scope a subject request
Deletion and access requests can only be honoured against data you know exists. A pack names the fields, objects and file types that hold personal data, including text inside documents that structured scanners never see, and states what it could not read: PDFs reach only Salesforce's search index, and file counts are lower bounds. It does not find one person's records for you.
To be clearOrg Warden does not apply these controls. It gives you the scope they apply to, and the next scan shows when that scope moves.
How Org Warden compares with Salesforce's own tools, Varonis, AppOmni and Blackthorn

No value leaves your org, the package for your production org has no code that can change your records, redaction runs only in sandboxes, and each customer's Console data is kept apart. How each one is checked →

See it working

Book a demo.

In a demo we take you through the Console on a demonstration estate whose data is all made up: a rule opened onto every org where it matched, and an Evidence Pack checked by its hash.

Work email · or write to hello@orgwarden.co.uk · we reply within 1 business day
Next argument · 2
How it works.
Choose what to scan in the Console, run it in your org, and bring the Evidence Pack back to read.