Security & trustNothing leaks when something .
How RedactWall is built, what it holds of yours, and how to report a vulnerability. For where every certification and attestation stands today, read the disclosures.
How we protect what you trust us with
The answers your security team will ask for during diligence.
We do not keep it
Prompts, files, customer and member records, and credentials do not go into our logs, our analytics, our error reports or the evidence record. The record says what kind of sensitive data was found, never the data itself.
Your data is separated from every other customer’s
Separation is enforced by the storage layer itself rather than by application code remembering to ask. If the system cannot establish whose data it is looking at, it returns nothing.
An outage does not become a leak
If the system cannot record a decision, it refuses the request rather than allowing it through unrecorded. An outage costs you availability; it does not cost you a silent gap in the record.
Every part can do only its own job
Each component runs with the narrowest access it needs, and the system checks its own permissions before it will start serving. Too much access is treated as a defect, not a convenience.
Secrets never end up somewhere readable
Passwords and keys are never placed anywhere they could be picked up from a process list, a shell history or a log file. The system refuses to accept them that way at all.
It cannot be quietly edited
Entries can be added and never altered or removed, and your own team can confirm the record is intact on your own systems. How you check it →
Reporting a vulnerability
Send reports to support@redactwall.com with SECURITY in the subject line. Please do not send exploit details to any other address. The machine-readable policy is published at /.well-known/security.txt.
Our commitments
- Acknowledgement within three business days, including whether we have reproduced the issue.
- A written outcome. A fix and its ship date, an accepted risk and its rationale, or a reasoned disagreement. Always an answer.
- Safe harbour for good-faith research. We will not pursue legal action for testing conducted against your own tenant or an installation you control.
- Coordinated disclosure. We request an embargo proportional to severity and will confirm when the fix ships. No indefinite embargo, and no NDA is required to submit a report.
- Credit at your discretion. Tell us the name to use, or ask to remain anonymous.
Testing boundaries
- Test only against your own tenant or an installation you control.
- No denial-of-service testing.
- Do not access, modify, or retain any record that is not yours.