ANONYMITY FORORDINARY PEOPLE.

ALEPH DROR is being built as one-click privacy software with VPN-like simplicity. When enabled, it masks and regularly renews the digital identity exposed across protected internet traffic so large-scale observers see a changing public profile instead of one permanent fingerprint.

ALEPH CHAT uses the same identity, encryption, routing and user-held key layers. The privacy software and encrypted communication app are therefore two interfaces to one system designed for maximum anonymity.

The present website communicates the architecture and development direction. The public software release scheduled for 2 February 2027 is intended to put a usable identity-masking prototype and encrypted chat into the hands of ordinary people and begin the public development cycle.

• One on/off privacy system instead of a VPN, messenger and identity layer working separately.
• Designed for everyday users, not only security specialists.
• A public prototype first; continuous hardening and improvement after launch.

A VPN can change the location from which traffic appears to arrive, and end-to-end encryption can protect message content. Neither protection automatically removes the wider pattern made from device signals, timing, contact graphs, account records and the way a person uses a device.

Over time, many small signals can be correlated into a durable behavioural profile. Changing a phone, account or IP address does not necessarily make that pattern disappear. ALEPH DROR is designed to reduce linkability across the wider signal set instead of treating location or message content as the whole privacy problem.

• Content privacy does not automatically provide identity privacy.
• Metadata and behavioural signals can remain identifying.
• Centralized observation creates a point of surveillance, compulsion and failure.

The first public release is planned for 2 February 2027. It is intended to be usable by ordinary people, not presented only as a laboratory demonstration. Users should be able to experience the first working form of the anonymity layer and communication application in normal use.

This launch begins public development; it does not declare the system finished. The prototype will continue to improve through measured releases, user feedback, adversarial testing, remediation and independent technical review.

The one-click ALEPH DROR client brings identity masking, behavioural camouflage, user-held keys, minimal required data and distributed paths into one protected internet connection. Public identifiers and network-visible identity signals are designed to renew regularly rather than follow a person indefinitely.

ALEPH CHAT runs on the same encryption and identity layer. It combines encrypted content with a changing public identity so privacy does not stop at the message body.

• Local key custody rather than a universal operator recovery key.
• Reduced collection of identity, metadata and behavioural signals.
• Distributed paths intended to reduce centralized visibility.
• Private continuity for trusted contacts while public identity changes.

The project has a one-click identity-masking system under active private development. The public whitepaper does not expose the detailed encryption composition, key exchange, routing logic, identity-renewal method, anti-correlation techniques or adversarial procedures used to test it.

Those details require staged handling: expert review under controlled access, remediation of discovered weaknesses, safe documentation and later public evidence. Disclosure timing must protect the people building the system and the people expected to use it.

ALEPH DROR targets maximum anonymity by minimizing stable links between a person and activity carried through its protected connection. The software is designed to mask and renew the network-visible identity while the shared encryption layer protects ALEPH CHAT and the system around it.

A compromised endpoint can still expose data already available on that device, and an existing external account can retain its own history. Those boundaries do not change the product goal: make activity inside the protected connection as difficult to link to one lasting digital identity as possible.

• Maximum anonymity applies to traffic carried through the ALEPH DROR protection layer.
• Every version must state which traffic and identity signals it protects.
• Limitations belong in the product, not only in legal text.

Telegram, Signal, WhatsApp and commercial VPNs are practical benchmarks because people already understand what they do. ALEPH DROR aims to go further on required identity, metadata minimization, key custody, behavioural linkability and centralized points of observation.

The public prototype is intended to make that difference visible in ordinary use. One click should activate a wider change in what the observing network can connect to the same person, while ALEPH CHAT carries conversations through the same protected identity layer.

From the public prototype launch on 2 February 2027, the project plans a 24-month development window. The prototype will remain usable while privacy protections, stability, usability, scaling and the communication layer are strengthened in successive releases.

The target for the most fully developed version currently planned is 2 February 2029. That milestone marks the mature state of this development cycle, not the end of maintenance, security research or future improvement.

• 2027: public prototype, real-world feedback and rapid hardening.
• 2027–2028: threat-model testing, usability work and staged expert review.
• 2028–2029: scaling, mature capabilities, extended security testing and broader technical disclosure.
• By 02 February 2029: full-scale version target for the current development cycle.

$DROR is intended as the native unit of the network: for in-application value transfer, network services and rewarding infrastructure other participants rely on. Presale contributions are intended to finance the engineering, testing and release path described in this document.

Token ownership is not proof that the product will be delivered, does not provide ownership of the project and does not promise a financial return. Economic figures are read from the same configuration used by the presale interface and remain provisional until the final token documentation is published.

• Utility described here is intended functionality until released.
• No return is promised and none should be inferred.
• Product claims and token figures must remain separately verifiable.