disdroc
Before you join disdroc.
Choosing a place for your conversations takes trust. Here is who runs disdroc, what you can check for yourself, and how the service handles your data.
Public code on GitHub, under AGPL-3.0.
Check availability on the status page.
Dated release notes for features and fixes.
A named person runs the service.
disdroc is built and operated by nadirisim, an independent developer. The hosted service runs on hardware the operator owns. You use it at disdroc.com; you do not need to set up a server. It is an independent project and is not affiliated with Discord.
Who can access your messages?
End-to-end encryption is optional for each private chat: one-to-one DMs and group DMs start unencrypted. After a member enables encryption and every member has a registered encryption device, new message content and attachments are encrypted on participating devices. Encryption cannot be turned off for that chat. Community channels and history sent before encryption was enabled remain readable by the service.
Encryption does not hide who talks to whom, chat membership, device public keys, message times, ciphertext sizes, IP addresses, reactions, pins or read/delivery activity from the operator. Participants can copy, record, forward or report content they can read. Support submissions and reports are not end-to-end encrypted.
Reporting an encrypted message deliberately shares its per-message decryption key with the service so it can verify the sender-device signature and your snapshot. This reveals the entire reported payload, including any quoted text, poll, attachment details and attachment keys; the service can therefore decrypt that message’s attached files. Admin review displays only the retained text/poll snapshot and report details, not surrounding messages, attachments or later edits. The snapshot can remain after the message is deleted or the report is resolved, until the report itself is deleted.
Keep your recovery key outside your devices. If you lose every device with the required keys and the matching recovery key, encrypted history cannot be recovered by the operator; resetting your account password does not restore it. A backup can recover only the message keys it contains. Anyone with the recovery key and access to the matching backup can read that history. Revoking a device prevents future delivery but cannot erase copies it already received.
In encrypted chats, server search, link previews, bots, server-side profanity/media scanning and mention notifications are unavailable. Reactions, pins and unread counts still use visible metadata. Push notifications for encrypted messages use generic “New message” text without message previews. Calls keep their existing WebRTC encryption; enabling chat encryption does not change call security.
What is stored, and what can you control?
- Account details, messages and uploads are stored to operate the app. IP addresses, device information and session records are used for account security.
- Uploads do not automatically expire after 24 hours. Delete a message to remove it and its attachments from the conversation.
- Settings includes account deletion, two-factor authentication and session management. For questions about retained data or help with deletion, use Support.
The service records security and usage information. Referral links measure visits and signups using cookies and device information. Email and notification delivery use outside providers. Unencrypted-message notifications can include previews; encrypted-message push notifications use generic text. See the privacy policy for retention and deletion limits.
Where do outside services come in?
Cloudflare delivers the website and processes connection data. Public pages load fonts from Google Fonts. Optional features such as GIF search, embedded video, music and push notifications involve other providers. Those providers may receive requests, search terms or connection information when you use the relevant feature.
Disdroc AI runs on the operator's hardware rather than an external AI API. Its conversations are still messages stored by the service. Owning the hardware does not mean that the website has no external connections.
What does the public source prove?
You can inspect the published client source and its requests. The server implementation is not public, and reading the client does not independently verify the live service. This page and the source link are not a security certification.
The operator serves the web client and can change the code your device runs. The current desktop and Android apps also load this web client; installing a wrapper does not remove that trust requirement. Encryption does not protect against a compromised device or malicious client update. Compare chat safety numbers with other members through a trusted channel. This implementation has no independent security audit and does not provide a forward-secrecy ratchet.
Can you rely on it?
disdroc is a small, independently operated service. Outages can happen, and there is no uptime guarantee. Check the status page when something is unavailable and keep your own copy of important files. Release notes show the work being shipped over time.
Start with one conversation.
Try a voice call or a small server with a friend before moving a whole community. If something feels unclear or goes wrong, tell us through Support. For a security issue, avoid posting private details in a public issue or community thread.
Updated