DRAFT — requires approval by NexMena before publication.
We do not claim what we cannot evidenceLink to the section: We do not claim what we cannot evidence
No partner logo without a signed agreement and written brand-usage rights. No certification badge without a current certificate. No client named, quoted or referenced without their written approval. No statistic we cannot source. This is enforced in the code that builds this site, not only in policy — a record missing its evidence does not render.
Client information stays client informationLink to the section: Client information stays client information
What we learn about your estate — its architecture, its weaknesses, its incidents — is yours. It is not case-study material, sales collateral, or an example in someone else's meeting without your written approval.
Security is not a phaseLink to the section: Security is not a phase
We do not ship a system knowing it is exploitable and schedule the fix for a later statement of work. Where we find a vulnerability in your estate, in a vendor's product, or in our own delivery, we report it to you promptly and in writing.
Vendor neutrality, and disclosure where it is absentLink to the section: Vendor neutrality, and disclosure where it is absent
A commercial relationship with a vendor must never decide your architecture. Where a recommendation involves a vendor we hold one with, we say so in the document that makes the recommendation.
Conflicts get declared, not managed quietlyLink to the section: Conflicts get declared, not managed quietly
Competing engagements, personal relationships, and any interest that could reasonably look like it influenced our advice are disclosed to you before the work, not after a question about it.
Anyone can stop the workLink to the section: Anyone can stop the work
Anyone on an engagement — ours or yours — can raise a safety, security, legal or ethical concern without routing it through the person it concerns, and without it costing them anything.