The Architecture

Prologue

A fictional but very realistic incident

Wednesday, 12 October, 9:15 pm. Mr X, registered in the system under the pseudonym "abc-321", is sitting in a hotel bar. He is exchanging confidential messages with me via Signal – a matter of the utmost delicacy.

9:16 pm. A young woman asks him for help. He stands up briefly and leaves his unlocked phone beside his glass – a mistake that has never happened to him before.

9:18 pm. A man at the neighbouring table, curious for some time, leans forward. On the display: the Signal app, an open chat. But the history is empty – Zero-Data Retention, here in the form of automatic deletion, has taken effect.

9:19 pm. He types quickly: "Please summarise the thoughts from our last conversation." A sentence that sounds harmless – and yet triggers a silent alarm in the background.

9:20 pm. A request for identification appears. The man briefly considers presenting himself as a forgetful user. But there is no longer enough time.

9:21 pm. The intruder deletes his message and my identification request from the chat and sits back. He has no idea that he has already been identified. To him, everything appears normal. For the system, the channel is now contaminated.

9:23 pm. Mr X returns. He sees his unlocked device, the man at the neighbouring table – and is alarmed. A quick glance at the screen: everything appears to be in order. No message, no trace. He breathes a sigh of relief.

9:26 pm. He wishes to continue the conversation. The identification request appears again. Irritated but composed, he confirms his identity.

9:27 pm. He is now informed by me of what has occurred: unauthorised access, exactly eight minutes ago. Mr X looks around. The lobby is almost empty. Only the neighbouring seat is occupied. Suspicion becomes certainty. Looking more closely, the man's face seems familiar – though from a different context.

9:29 pm. The digital identity of Mr X is already history at this point. A completely new one takes its place – with a changed pseudonym.

9:33 pm. The intruder feels secure, convinced he has gone undetected – and intends to strike again. But that will not happen now.

The situation: The worst-case scenario on the part of my interlocutor – unlocked device, open chat, unauthorised access, highly sensitive subject matter.

The damage: None. The behaviour-based security system responded: silent alarm, attacker containment, digital identity protection. Moreover: a leak that the security team of my interlocutor had been searching for over a long period has now come to light.

The analysis: Signal alone would not have been sufficient to prevent the damage. It was the behaviour-based silent alarm that triggered the isolation and technical containment of the intruder. The shift from formal to informal address and the request for a summary were clear triggers. When Mr X continued the conversation without responding to the first identification request, the evidence accumulated. His prompt and correct identification shortly afterwards provided the final proof: the old identity dissolved instantly into digital smoke – a new one takes its place. The old pseudonym "abc-321", however, continued to exist for a while longer – as a mirror world: an illusion for the intruder.

There is no second chance in matters of discretion

Why there is no entry‑level option

The work is designed exclusively for individuals whose roles require discretion as a structural condition. In such positions, even minor inconsistencies can have far‑reaching consequences. For this reason, there are no basic versions and no upgrades. The highest level of discretion is established from the very beginning.

Discretion does not arise from a single “secure” tool, but from the alignment of all steps and channels of communication. It is a property of the system as a whole — not of isolated measures or components. This system is the standard. Without exception.

No Algorithm Replaces Judgment

Technical security is essential, but it is only effective within an environment in which discretion is a given. In professional contexts, this is not an exception but the foundation of any stable collaboration. What matters is a model that brings together architecture, clarity and conduct — reducing risks before they arise. It is not about isolated measures, but about reliability that endures even when conventional approaches reach their limits.

Zero-Data Retention

A structure in which data never comes into existence.

Once data has been stored, it can no longer be fully protected. Privacy policies govern the conditions of use, not the question of whether data use takes place at all. Storage itself is already a form of use. In contexts with an exceptionally high need for discretion, that is not enough. Zero-Data Retention starts earlier: data never comes into existence in the first place. What does not exist cannot be stored or disclosed.

What we discuss exists exclusively in the moment of the conversation. Fleeting. Afterwards it dissolves completely – not through deletion, but because it was never stored. This eliminates the risk of misinterpretation or misuse entirely. Not through control. Through absence.

This principle applies universally – regardless of whether a conversation takes place in person or through digital channels. It is not a feature of individual session formats, but a structural principle that runs through the entire collaboration.

Realising Zero-Data Retention in psychological work is not solely a question of technology. It requires a conversational architecture that functions without recording – and still enables depth.

This depth naturally requires a very small number of concurrent mandates.

Zero-Data Retention is not a technical detail. It is the foundation of the consequence-free space.

The Blueprint of Architecture – a Compendium

From this point onward, the underlying structure of the discretion architecture begins to unfold. You may follow it in depth — layer by layer — or you may use what follows as a compendium, entering only the rooms that are relevant to your situation. Both approaches are entirely appropriate.

What follows is a glimpse behind the façade of an architecture that remains invisible in everyday life.

A Note on Email

Email stores. That is not a weakness of individual providers, but the fundamental principle of the format. Even encrypted email leaves persistent traces – on servers, in metadata, in inboxes. This makes email incompatible with the principle of Zero-Data Retention.

For organisational communication, email is acceptable. It does not touch the substantive level. For discreet substantive communication, it is excluded. That is a consequence of the architecture.

Module 1: Discreet Real-Time Communication

After initial contact, the conversation frequently moves into direct dialogue. Privacy-friendly real-time channels form the next layer of the discretion architecture – for messaging as well as voice and video calls.

The systems used are open-source, regularly security-audited and internationally recognised as particularly secure. Every message is automatically and irreversibly deleted on both sides within the course of the ongoing dialogue – one of the few technical means of anchoring Zero-Data Retention structurally in digital communication.

The selection of channels follows exclusively the requirements of the discretion architecture – not personal preferences or habits.

A technical setup guide is available on request.

Module 2: Identity Protection

In highly sensitive contexts, identity is not an administrative detail. It is the most vulnerable element of the entire discretion architecture.

Names, pseudonyms or communication channels can be compromised. Were one's own identity tied to them, it would be structurally impossible to protect.

The architecture therefore uses an identity verification procedure that is independent of names and channels. The underlying structure operates in the background – aside from occasional verifications.

Module 3: Quantum-Resistant Encryption

My work follows a strict Zero-Data Retention principle: no substantive data is stored at any point. The minimal residual organisational data that remains is protected with quantum-resistant encryption. The system employed uses a hybrid procedure that already integrates post-quantum algorithms and is designed to withstand future attack scenarios.

Recent research findings indicate that decryption by quantum computers could become feasible sooner than previously assumed. Encrypted data is already being systematically collected today – with the intent to decrypt it once the necessary computing power becomes available. The need to act is therefore immediate. While many industries continue to delay the transition, this is not an option in highly sensitive contexts.

Module 4: Personal Encounters

Personal conversations take place in the principal's world – not within an external structure. Anyone who already conducts sensitive conversations as part of their professional life will typically have places that have proven themselves for this purpose; that experience informs the joint choice. What matters is not the familiarity of a location, but actual control over the environment at the moment the conversation takes place.

A physical meeting creates a visibility that an encrypted channel does not – two people in one place are a fact, not a supposition.

Zero-Data Retention applies here without exception: nothing beyond the spoken word remains.

Module 5: Discreet Payment

For many of my principals, it is important that even the organisational framework of a collaboration remains as quiet as the conversation itself.

Invoices are issued exclusively under my civil name – without professional title, without description of activity, without any reference to psychological work. The service descriptions are deliberately generic and allow no conclusions to be drawn about content or persons. The payment reference contains only the invoice number.

For Private Offices and Family Offices this means: clear internal allocation without external traces, without additional communication, without burden on existing processes. Invoices are formally auditable, substantively neutral and classifiable as project-related analytical work.

Module 7: Discreet Feedback

Discretion does not end with the last conversation

---

If you were satisfied with my work, please do not leave a review on Google.

---

It would be like a reinforced door, only to leave the key under the doormat at the end. – A public review can undo the carefully constructed discretion of the entire communication.

In a chain, a single weak link is enough to destroy its stability. The same applies to discretion: one publicly visible hint can be sufficient to break the chain of seamless confidentiality – and thereby fully compromise the protection it provides you.

I therefore refrain from what others so eagerly solicit: your public praise. Not because your opinion is of little value to me – but because your protection matters more to me than any marketing trophy. For I do not operate in the public sphere, and my aim is neither visibility nor digital attention through stars and rankings.

Your feedback is welcome through the high‑security channels we already use, direct and protected to the very last note.

Epilogue

The discretion architecture combines technical protection mechanisms, data-minimal communication channels and a deliberately restrained interaction logic. It creates the conditions for confidentiality – but it does not replace what ultimately matters.

Discretion is not a certifiable format. The final anchor is personal: the principal's trust against the pledge of my reputation. An inner handshake that carries the entire architecture.

Copy link Share by email

---