Legal
Client Confidentiality
Last updated: August 2026
Early access draft. This policy is written in plain English for Decifer's early access period. It is meant to be clear, not a substitute for legal advice. Final versions will be reviewed by counsel before commercial launch. Questions to [email protected].
Why client work is anonymised by default
Client work is anonymised on this site unless the client has asked, in writing, to be named. Some asked us not to name them. For the rest, we chose not to, because a business that would publish your name to win the next job would publish the next client's name to win the one after that. We would rather be believed for what we describe than trusted for who we can point at.
The exception runs the other way. A client who wants their name on their own project is entitled to it, and one has asked. Where you see a named case on this site, that name is there at the client's written request and nowhere else.
What we publish instead
Each piece of work is described by shape: the sector, the country, the problem, what we built, what changed, how it is measured, and where a person stays in charge. We keep sector descriptions general enough that the client cannot be guessed. If an honest description would identify someone, we cut the description rather than soften it.
What we publish only with permission
- Any number. A figure appears only with the before measurement and how it was taken, the after measurement taken the same way at least sixty days later, the period and sample size, the other things that could explain it, and the client's written permission. Until all five exist, we publish words and say why.
- Any quotation, attributed by role rather than by name, and only with written permission for that exact wording.
What we never publish
- Client names, brands, domains or logos, unless that client has given written permission to be named.
- Customer, patient, guest or end-user data of any kind.
- Prices, revenue, margins, supplier terms or contract values.
- Anything that was shared with us during an engagement, including documents, credentials, data exports and internal conversations.
What this means in practice
During an engagement we work inside your accounts, in your name, on systems you own. At handover the code, the data and the runbook are yours. Nothing we build for you is reused for someone else without your agreement. If you later want to be named, that is your call to make, in writing, at any time.
Questions about this statement can be sent to [email protected].