Metadata-only, drawn.
The answers a security review asks for first.
- What leaves the orgCounts and classifications, never a value. The two lists.
- Where the Console's data is heldThe services we use and where they run: subprocessors.
- What we keep, and for how longPrivacy notice.
- Reporting a vulnerabilityHow to report one, and how security updates reach you.
- Your questionnaireSend it to hello@orgwarden.co.uk, and we answer it.
If you stop using Org Warden, nothing in your org depends on us. Your scans are records in your own org and can be run again from its Scans tab, and your Evidence Packs are files you already hold. The packages uninstall from Salesforce Setup.
Everything an Evidence Pack may carry, and what has no way out.
Eight promises. Each one has its own tests, and if a test fails the release does not ship.
A security reviewer can find each one in the code and its tests.
One package reads. A separate package writes, and only in a sandbox.
Org Warden Redact replaces personal data in a sandbox copy of your org, so testers and developers work without real customer data. It is a second package. Org Warden Core, the package in your production org, does not contain it and has no direct reference to it: the two meet only through a list of jobs that an administrator can read in Setup.
| Job | Package | Reads or writes | Runs in |
|---|---|---|---|
| Schema: what objects and fields exist | Core | reads | production and sandbox |
| Detection: which values match a rule | Core | reads | production and sandbox |
| Access: who can read | Core | reads | production and sandbox |
| Files: what documents contain | Core | reads | production and sandbox |
| Redaction | Redact | writes | sandbox only |
From a sandbox refresh to a redaction, in five steps.
Redaction plans are kept in production as plain records, so no write code is needed to hold them, and a refresh copies them into the sandbox. Nothing runs on refresh by itself: an administrator starts the redaction.
- Step 1planPlans copiedA refresh copies production into the sandbox. The redaction plans arrive. The Redact package does not.
- Step 2requestedA redaction requestedAn administrator asks for a redaction from a plan, in the org or by importing one composed in the Console.
- Step 3waitingWaiting, not failedWith no Redact package in the org, the job waits. Nothing that changes a record is attempted.
- Step 4installRedact installedAn administrator installs Org Warden Redact in the sandbox. The waiting job can now run.
- Step 5readyDry run, then the gateA dry run shows what would change. Only then does the five-check write gate open.
If you think you have found a security vulnerability in an Org Warden package, the Console or this site, email security@orgwarden.co.uk with what you found and how to reproduce it. Please give us time to correct it before you make it public, and test only against a Salesforce org and data that are yours.
The Console and this site check their dependencies against published security advisories on every change and again every morning. A security update to the Console is deployed by us and needs nothing from you. A security update to a Salesforce package reaches your org only as a new package version, which your administrator installs.
We do not publish a statistic we cannot back, show a wall of badges, or imply a certification we do not hold.
To reproduce anything on this page yourself, email security@orgwarden.co.uk and we will walk you through it in the code.
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.