Confidential software development.
Your website or application belongs to you. BRÈCHE never uses client projects as references, publicly or privately. Confidentiality also shapes access, delivery and handover.
Your work stays yours.
Say what needs to stay private.
Client identity, a commercial relationship, an unreleased product and application data are different kinds of information. We start by naming what must remain private and who may access it during the work.
You can use a name or alias in the initial brief. Send a useful outline first, with sensitive material shared through an agreed channel once access and confidentiality requirements are clear.
No portfolio. No client case studies.
We never publish or share client names, project links, screenshots, credits, testimonials or results from past work. Removing a name does not make a project available for an anonymised case study. This rule also applies to sales conversations and private reference requests.
You decide what your own product publishes. A public launch, an open repository or a branded website does not become a BRÈCHE reference. The release materials we prepare follow your agreed publication requirements.
Review the proposed work.
You can assess the brief, architecture decisions, acceptance checks and source handover before agreeing a build. Our guides use explicitly fictional scenarios to make that process concrete.
For your project, agree what each review must demonstrate: an editing flow for a website, access rules for a portal or recovery from an integration failure. Payment milestones and review points belong in the proposal. No past client's work is needed for that discussion.
Review the public surface.
We can review visible content, files, metadata and deployment choices to reduce unwanted links to a client's identity. The review follows a defined list of information and the parts of the delivery we control.
Public content and private configuration need separate treatment. The build should not expose credentials or private environment values. An image, downloadable document or social preview may also contain information that needs review.
Keep the limits explicit.
Confidential delivery is not a guarantee of anonymity, zero traceability or control over third-party records. Hosting, domain and payment providers have their own requirements and systems.
We record what is covered, what depends on external services and what you need to maintain after handover. Standard projects delivered openly under your brand are equally welcome.
A few things to know.
Will you put my project in your portfolio?
No. BRÈCHE never uses client projects as references. We do not publish names, links, screenshots, credits or results from client work.
Do you share anonymised case studies or private references?
No. We do not turn past projects into case studies, even without names, or share them privately with prospects. Public examples are fictional and labelled as such.
Can my identity stay off the public website?
That can be part of the requirements. We review content, metadata and deployment choices within the agreed scope. It does not remove external provider requirements or guarantee anonymity.
Does paying in crypto make the project anonymous?
No. Payment method and confidentiality are separate decisions. The asset, network, providers and operational setup have their own disclosure properties.
From first spec to production.