1 · Our core principle: metadata only
Org Warden is designed to never ingest your customer data. Our platform operates entirely on metadata: field definitions, object structures, permission configurations, and aggregate counts. Your actual customer records never leave Salesforce.
When we scan your Salesforce org for PII we see that you have a field called SSN__c. We never see the values stored in that field.
2 · Information we collect
We act in two roles. As controller, Org Warden Ltd decides how the information from this website and from people who write to us is used. As processor for our customers, we hold what the Console stores for a customer (its people’s work emails, sign-in records, the audit log and the packs it uploads) on that customer’s instructions, under our agreement with it; the customer is the controller.
Marketing site (orgwarden.co.uk) · we are the controller
- Contact information (name, work email, company) when you request a scan or reply to us.
- We do not run analytics on this site, and we do not fingerprint or profile.
- Essential cookies for site functionality.
Console (app.orgwarden.co.uk) · we process it for our customer
The Console is where you bring the Evidence Packs your Salesforce org produces. It never connects to your org; nothing reaches it except a file a person in your company uploads. What it then holds:
- Account information: the work email address of each person given access — added by us, or by an administrator at your organisation, who supplies a colleague’s address on your behalf — and whether they are an administrator or a member; the sign-in codes we send to it (stored hashed), the sessions that result, and an audit log of sign-in events and changes to who has access. When someone is added we email them once to say so. No passwords are held.
- Evidence Packs, as uploaded: your org’s identifier, name and domain, the Salesforce User Id of the person who generated the pack, object and field API names and labels, field counts, findings (which rule matched which field, and how many times), rule identifiers, coverage figures and content hashes. Where an access review ran, a pack also carries your org’s sharing and permission set-up as configuration and counts: each object’s org-wide sharing defaults, how many active users hold View All Data, Modify All Data, or read access to an object or field (split by user type, guest and external users included), which profiles, permission sets and permission set groups hold each kind of access (by their names and labels, with how many active users hold each), and whether a field is encrypted. Never a record value, a record Id used as data, a person’s name or email, or a file’s contents. Because a pack maps where personal data sits and who can reach it, treat it as confidential. A pack is kept byte-for-byte as it arrived so that it can be re-verified later.
- What you author in the Console: org labels, packs you set aside, scan definitions you compose, and the redaction work-list — each recorded against the signed-in address and the date.
A pack contains no customer record and no field value — not a sample, not an excerpt, not a partial value. It does contain the names of your objects and fields and what our rules found about them, which is information about your organisation and is treated as confidential.
What we never collect
- Customer record data from your Salesforce orgs.
- Field values (names, SSNs, emails, addresses, and so on).
- File contents from ContentDocuments or Attachments.
- Salesforce user credentials or session tokens.
3 · How we use it
To provide, operate, and improve the service; to send administrative and security communications; to respond to your requests; and to meet legal obligations. We do not sell personal data. We do not use your Salesforce metadata for any purpose other than delivering the service to you.
4 · Retention
- Evidence Packs and what you author: kept until you delete them or your agreement ends. A pack is evidence, so we do not expire it while your account is active; you can ask us to erase any pack, or everything, at any time and we do it within 30 days. Erasure removes the stored bytes and every derived record, and the fact of the erasure is itself recorded. Packs and their index are kept for 30 days after the agreement ends so you can download them, then erased; erasure is recorded in the audit log.
- Backups: An erasure removes every stored copy of the pack bytes at once; anything else we delete is removed from live storage at once, and from backups within 30 days, and deleted database rows, erased ones included, leave the database's point-in-time history within the same 30 days.
- Sign-in records: codes expire after ten minutes and sessions after twelve hours; both are deleted after a day.
- Audit logs (sign-ins, erasures, mail delivery events): retained for 2 years, then deleted. An address typed at sign-in that matches no account is recorded by its domain only.
- Marketing contacts: retained until you unsubscribe or ask us to delete them.
5 · Security
- TLS in transit everywhere; server-side encryption at rest on every stored pack and database.
- Sign-in by one-time email code, bound to the browser that requested it; no passwords to leak. Single sign-on (SSO) is on the roadmap for customers who require it.
- Every customer’s data is isolated by row-level security in the database, enforced by the database on every query, not by application code; and in storage by a per-customer prefix that the server writes into every file’s key from the signed-in session and checks again on every read.
- The Console holds no credential for, and no connection to, any Salesforce org.
- Nothing is logged that a pack contains: no field names, no findings, no sign-in codes.
- No analytics or session-recording service runs inside the Console, and no separate error-tracking service. Errors and request logs (the route, the request id and any stack trace, with no pack content) are kept by Vercel, our host in London.
The architectural detail is on the Security page.
6 · Sharing
- Sub-processors — the three companies that host the Console, listed by name, role and region in section 7 and on our sub-processor page, each under written data-processing terms.
- Legal process where required by law or valid legal process.
- Business transfers in the event of a merger or acquisition, with notice.
- Your consent, when you explicitly authorise it.
We do not share, sell, or rent your Salesforce metadata for anyone else's marketing purposes.
7 · Where your data is, and who holds it
Everything the Console stores is in London. The application runs on Vercel’s London region; the database is Neon (running on AWS, eu-west-2); stored packs are in an AWS S3 bucket in eu-west-2; sign-in codes are sent through AWS SES in eu-west-2. There are no other sub-processors, and we will give you 30 days’ notice before adding one.
- Vercel Inc. — runs the application and keeps its error and request logs; packs pass through it in transit and are not stored there. London (lhr1).
- Neon Inc. — the database: the pack index, what you author, and account records. AWS eu-west-2, London.
- Amazon Web Services — stored pack bytes (S3) and sign-in and access-notice email (SES). eu-west-2, London.
Jurisdiction. Residency in London answers where the data sits. It does not by itself answer whose law can reach it: Vercel and AWS are US companies, and US law (the CLOUD Act) can in principle compel a US provider to produce data it holds, wherever it is stored. Our position is the one nearly every UK software vendor is in, and we state it rather than obscure it: we choose UK/EU regions and providers with published transparency reporting and a policy of challenging over-broad requests; the material at stake is metadata about your Salesforce configuration, never customer records; and every pack can be erased on request. If your policy requires a UK-owned storage chain, tell us before you upload — that is a conversation we would rather have first.
8 · Your rights (GDPR / UK GDPR / CCPA)
- Access, rectification, erasure.
- Data portability.
- Objection to and restriction of processing.
- Withdrawal of consent where processing is consent-based.
Where we are the controller, email privacy@orgwarden.co.uk to exercise any of these rights. We respond within 30 days.
Where we process data for a customer (anything the Console holds, including the User Id in a pack), that customer is the controller: please make your request to your organisation, and we will help it answer. If you write to us instead, we pass the request to them.
9 · International transfers
We operate from the United Kingdom and store Console data only in the UK (see section 7). Our sub-processors are US-headquartered companies operating UK regions; the processing terms with each include the UK International Data Transfer Addendum or an equivalent lawful mechanism for any support access from outside the UK.
10 · Contact
- Privacy contact: privacy@orgwarden.co.uk
- General: hello@orgwarden.co.uk
Org Warden Ltd, United Kingdom. Salesforce is a trademark of Salesforce, Inc. Org Warden is not affiliated with, sponsored, or endorsed by Salesforce, Inc.