On this page
Five jobs, run in order by the owner
Each job feeds the next, and you run them in order.
Measure
Reads every connected system read-only and writes an inventory with counts only: per system, year, mailbox and channel; internal versus outside participants; and how many threads end in an outcome, such as a reply, a meeting or a deal. Measured volume per source replaces a quick estimate.
Sort
Applies green, amber and red rules. Out go data held for customers (client domains pulled from the CRM, client deliverables), HR, payroll, health, recordings with outsiders, live credentials and records licensed from vendors. Every drop is counted in an exclusion ledger, with no content.
Clean
Replaces people, contacts, client names and codenames with consistent placeholders: the same person is one token in email, chat and the CRM, so the workflow survives. The key that maps tokens back to real names is encrypted and stays with you. A QA pass then re-scans the output, a local model tries to re-identify a sample, and you review before and after pairs before signing off.
Fitting room
A buyer's scoring code runs on the clean copy with the network switched off. Only numbers come out, schema-checked and size-capped, and you see them before release. Everything the buyer brought is then wiped.
Receipts
A signed manifest (file fingerprints, counts, policy version and QA results), the data card and the provenance log, and a signed certificate called the Rightmark.
A hallmark for your data
A hallmark is the stamp an assay office puts on silver after testing it. The Clean Room is Rightmark's assay office in your own building, and the signed certificate, called the Rightmark, is the mark.
Code mode is available now
Repo Check already measures code on your own machine, and it becomes the Clean Room's code mode. One command reads a repository and its git history, and you share a file of counts and fixed labels, never code.
As code mode, it will also find secrets so they are rotated first, and rewrite author names and emails.
Early access for email, chat, CRM and ticket archives
For operational archives, the Clean Room is offered as early access only: there is nothing to run yet. To ask for it, send the contact form and name the systems your archive lives in.
Questions
Does my raw data ever leave my environment?
No. The Clean Room runs on your own machine or in your own cloud account, and Rightmark has no remote access by default. Raw data never leaves your environment and never touches Rightmark.
Who holds the key that turns placeholders back into names?
You do. The mapping from tokens to names is encrypted, kept on your side and held by you. Rightmark and buyers never get it.
Is the network on while my data is cleaned or scored?
No. The network is switched off while the Clean Room cleans your data and while a buyer's scoring code runs, so even a poisoned dependency has nowhere to send data. Dependencies are pinned and hash-checked.
Can the Clean Room change anything in my systems?
No. Every connector is read-only: it reads your systems and writes nothing back to them.
Can anything leave without my approval?
No. Nothing leaves without your click. The inventory, samples, scores and the delivery are each shown to you first.
How can my IT team check what happened?
Everything is logged and signed: an append-only local audit log, signed manifests, and signed container images with a parts list (SBOM) your IT team can check.
Can my IT team read the code?
Yes. Your IT team can read the code that measures and cleans your data.
Sources
- Rightmark: Repo Check