Last written 5 September 2026
01The stance
A situation is shown to us so we can hold it long enough to name a problem. That is a position of trust. We do not treat the unofficial path, the contested picture, or the cost of a wrong turn as material for a case study, a model, or a marketing page.
We do not claim certifications we do not hold. Your regulatory obligations remain yours. This page describes how Constrange behaves; it is not a substitute for your own security or privacy programme.
02Confidentiality
Working material stays inside the engagement unless you ask otherwise. We do not publish identifiable accounts of your systems, and we do not use a live situation as “anonymised colour” in public writing without a separate, explicit agreement.
If we need an example in a public note, it is invented or so general that it could belong to many organisations. The test is simple: you should not be able to recognise yourselves.
03Named access
Only the people on the work see the situation in detail. There is no internal “anyone can browse the files” culture. Access is named, time-bounded, and tied to the engagement.
04Your systems, your data
We do not take a copy of a production system unless the work requires it and you have authorised that copy. We do not train public models on what you share. We do not use advisory material to train or improve software unless a signed letter says otherwise.
If a file must move, we prefer a channel you already control. We do not ask for more access than the reading needs.
05Clear artefacts
Recommendations are written so they can be inspected, challenged, and handed on. A point of view that cannot survive contact with operations is not finished. Artefacts are yours to use inside the organisation that paid for them, as the letter describes.
Drafts and working notes are not the deliverable. When the work ends, drafts are treated as working material: kept only as long as required, then deleted or returned.
06Proportionate retention
Notes are kept only as long as the work requires. We do not retain unofficial maps as a library of other people’s operations. If you ask for deletion after an engagement, we will do so except where a legal duty or the letter requires a short, named hold.
07If something goes wrong
If working material is exposed in a way it should not have been, we will tell the people named on the engagement as soon as we understand what happened, what was involved, and what we are doing. We will not wait for a tidy narrative.
08The public site
The contact page uses Cal.com to book first conversations. What you share there is used to schedule and prepare that conversation. See the Privacy policy for what the site and Cal collect. Live work is a different channel, opened on purpose.
09What you can ask
You can ask who has seen the situation, what we still hold, and when it will be removed. You can ask us not to use a particular tool on the work. Put it in the letter if it needs to bind; say it in the conversation if it needs to start immediately.
Related: Terms of service · Privacy policy.