Local encryption
Messages are encrypted on your device before they reach the server.
Private communication without identity
Create temporary encrypted chat rooms without an account, email address, phone number, or permanent identity.
Why VOID exists
Private communication should not be treated as evidence of wrongdoing. Mass scanning of private messages threatens the confidentiality of digital communication. VOID is built around one principle: only the people inside a room should be able to read its contents.
No backdoors. No advertising profiles. No mass surveillance.
VOID opposes indiscriminate mass surveillance and EU Chat Control. Targeted investigations should be based on lawful individual suspicion, due process, and judicial oversight—not the routine scanning of everyone’s private conversations.
Privacy architecture
Concrete design choices instead of vague promises.
Messages are encrypted on your device before they reach the server.
VOID does not intentionally store IP addresses in application or analytics logs.
VOID does not create permanent login histories or personal activity timelines.
Temporary rooms work without email addresses, phone numbers, or permanent identities.
Encrypted room data is deleted after the selected expiration time.
The client and server code can be publicly inspected.
NO IP LOGS. NO TIME LOGS. NO TRACKING. NO ADS.
Encryption cannot protect a compromised device, screenshots, or messages copied by another participant. No-log claims must match the real production infrastructure and should be independently verified before launch.Optional identity
Users may optionally create a pseudonymous cryptographic identity without an email address, phone number, or conventional password. Temporary rooms still work without one.
If you lose it, the identity is permanently lost. VOID cannot recover it.
FAQ
No inflated security language. No fake guarantees.
The product is designed so messages are encrypted on participant devices before reaching the server. A production release still needs a documented protocol, secure key handling, independent review, and reproducible clients.
No. Temporary rooms can be created and joined with a room code and display name.
The intended architecture avoids persistent IP logging in the application and analytics stack. Reverse proxies, hosting providers, and security tooling must also be configured consistently before this claim is published.
VOID is designed not to create permanent personal activity timelines. Temporary in-memory connection data may still be processed while a room is active.
The server removes the encrypted room state after the configured expiration. This cannot erase screenshots or copies made by participants.
Yes. End-to-end encryption protects transport and storage, not the behavior or devices of people inside the room.
Without the code or invitation link, the room cannot be rejoined unless another participant shares it again.
The pseudonymous identity is permanently lost unless it remains unlocked on an authorized device. VOID has no recovery mechanism.
VOID opposes indiscriminate scanning of private communications. Investigations should target specific suspects under lawful oversight instead of treating every private conversation as potential evidence.
That is the intended release model. Do not advertise this until the actual client, protocol, and server repositories are public.
Potential paid features include larger rooms, longer room durations, encrypted file transfers, self-hosting, and organization plans. User data is never sold.
Start now
No account. No phone number. No permanent identity.
Your room. Your keys. Your decision.