Romy Lind sits with her parents Elena and Vincent on the sofa and shows them a private moment on her phone

Freedom and private communication

Private messages are not raw material

Under the label chat control, the EU is debating rules for inspecting private communication. KBeam does not inspect private messages, automatically or manually. Their content is encrypted on the device before it reaches the transport path. Each user remains responsible for the content they send. A phone number, real name and email address are not collected as account data and are therefore not mapped to a wallet address or cryptographic contact: the app knows only the cryptographic identity, not the person behind it, and does not disclose such a personal identity link.

Reviewed on July 13, 2026

Romy decides which private moment she shares with her parents, Elena and Vincent.

None

automatic or manual inspection of private messages by KBeam

Before

encryption on the device before transport

None

mapping from wallet or contact to phone number, name or email address

01

What chat control means

Chat control is not a single technical product. The term covers political and legal proposals under which providers might automatically inspect private communication for certain content. A particularly sensitive question is whether scanning would happen on the device before, or despite, end-to-end encryption.

The legal process continues to change. On July 9, 2026, the European Parliament adopted amendments to a temporary ePrivacy derogation. Parliament's position would exclude communications protected by end-to-end encryption; the text now returns to the Council. This page therefore records a dated status, not a final legal outcome.

02

KBeam's product property

KBeam does not inspect private messages, automatically or manually. Their content is encrypted on the device before it reaches Fast Push, brokers, push services or other transport paths. Each user remains responsible for the content they send.

For registration and ordinary private messaging, KBeam does not collect or use a phone number, real name or email address as account data. KBeam therefore creates no mapping from those identifiers to a wallet address or cryptographic contact. For technical routing, KBeam knows only the cryptographic identity, not the person behind it; it can neither analyze nor disclose a personal identity link it never collected.

Technical metadata used for delivery, reliability and abuse prevention is separate from this statement. Public blockchain data may independently be linked to people through external sources; KBeam does not provide that attribution. KBeam also does not claim control over a compromised device, the operating system or every conceivable attacker.

How Fast Push, Kaspa Chain and V2 work

03

Optional features remain a conscious decision

Features that use external processing, such as a deliberately triggered external translation, must be explained and activated separately. In that case, the selected content leaves the ordinary private path for the specific purpose chosen by the user.

Privacy is not created by a slogan. It comes from understandable data paths, clear boundaries and the ability to leave optional features disabled.

FAQ

Questions about chat control and KBeam

Does KBeam automatically scan private messages?

No. KBeam does not inspect private messages, automatically or manually. Their content is encrypted on the device before it reaches the transport path. Each user remains responsible for the content they send. Only content explicitly submitted to an optional feature is processed separately for the chosen purpose.

Does KBeam link my wallet address to a phone number, name or email address?

No. KBeam does not collect those identifiers as account data for registration or ordinary private messaging and therefore creates no such mapping. For technical routing, the app knows only the cryptographic contact, not the person behind it. KBeam can neither analyze nor disclose an identity link it never collected.

Does encryption make every form of monitoring impossible?

Encryption protects content in transit, but it is not magic protection against compromised devices, visible screens, insecure backups or external processing that a user deliberately enables. Security must always be evaluated against a specific threat model.

Is this page legal advice?

No. It describes KBeam's product design and links to the current official EU procedure. Legal conclusions require qualified advice.

Private communication starts with a deliberate architecture

See how KBeam separates encryption, transport, metadata and optional functions.

Understand encryption