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.
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.
- 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
- 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
Claims — read 1 field with this rule and matched none, in a scan its pack says was complete. Pack of 4 Nov 2026
Group Finance, Group Risk — no pack from them ran this rule, so it is unknown there.
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.
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.
counts · classes · telemetry
Where is PII in our estate?
Who can read it?
What has changed?
Every category default asks you to move your data first. Org Warden does not.
- 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.
- 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.
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.
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 →
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.