Source-code redaction is the removal of personal data from programs produced under an FRCP 26(c) protective order. Rule 26(c)(1)(G) lets a court set terms for a trade secret. That is why code goes to a standalone, non-networked review machine. anonym.plus prepares it locally.
When this applies
A code order limits the room, the machine, and the printed page count. What it cannot limit is what the files already hold: developer names in comments, addresses in commit trailers, and live keys sitting in config.
How anonym.plus handles it
- Load the program files into anonym.plus on your device.
- It scans comments, commit logs, and config values.
- The tool flags developer names, emails, and tokens.
- Confirm the flags; leave the program logic untouched.
- Replace or mask each confirmed value.
- Save the clean files on your device.
What you need to provide
- The program files (modules, config, or text logs).
- An allow-list to keep variable and function names.
- An operator; Replace keeps the file parseable.
PII entity types detected
| Category | anonym.plus entity type | Example |
|---|---|---|
| Names | PERSON | // author: J. Doe → [DEV] |
| Contact | EMAIL_ADDRESS | j.doe@corp.com → [EMAIL] |
| Identifiers | PERSON | commit user token → [USER] |
| Secrets | PERSON | hardcoded key → [SECRET] |
| Dates | DATE_TIME | commit date → [DATE] |
| Contact | PHONE_NUMBER | support phone → [PHONE] |
Compliance achieved
- FRCP 26(c)(1)(G) supports the standalone, non-networked review terms.
- Comments, commit trailers, and config values hold names and keys — those are cleared.
- An allow-list keeps identifiers the code needs, so the file still parses.
- Nothing is uploaded, so proprietary logic never reaches a hosted service.
Anonymize source code productions offline — see plans & start free →
Limitations & cautions
Code is sensitive to syntax. A swapped value must keep the file parseable, so use an allow-list for variable and function names. The tool clears named PII in comments and config, but a human must judge what counts as a trade secret versus a name.
Frequently asked questions
Why does code get its own protective order?
Rule 26(c)(1)(G) lets a court order that a trade secret be revealed only in a specified way. For code that usually means a standalone machine in a controlled room, no network access, and a cap on printed pages.
Will clearing names break the build?
Not if variable and function identifiers sit on the allow-list. The pass targets names in comments, commit trailers, and config values, which the compiler ignores.
Does it catch hardcoded credentials?
It flags many secret patterns, like keys and tokens, but treat that as a starting point and review the results.