What this policy covers
Disdroc is an independent chat service operated by the individual developer known publicly as nadirisim. This policy covers the hosted website and its desktop and Android clients. Disdroc is not affiliated with Discord Inc. For data questions or requests, use Support; an account is not required.
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.
Data we receive and why
Account data includes your username, email, salted password hash, self-reported date of birth, profile details and settings. We use it for registration, sign-in, recovery, profiles and age-related content controls. If enabled, two-factor authentication also requires verification secrets and recovery-code records.
The service stores ordinary message content, AI conversations and uploads to provide chat and media features. For encrypted private chats it stores ciphertext, opaque encrypted history-key backups and device public keys instead of ordinary message content. Friendships, memberships, reactions and activity in chats and calls remain visible metadata. Reports and support requests include disclosed content, contact details and relevant account or connection information.
Security and operational records include IP addresses, browser/device details, device identifiers, sessions, login history, approximate country, risk events, moderation actions and call-usage statistics. Country information helps choose a language and assess unusual sign-ins; it is also stored in security records. Rate limits and automated safety checks can restrict actions; contact Support to request review.
Data comes from your submissions, your device and connection, other participants who mention or report you, and services you choose to link. We use it to provide requested features, protect accounts, investigate abuse, answer support requests and maintain the service. We do not sell personal data or use it to build advertising profiles.
Referral links measure visits and resulting signups using a referral cookie lasting up to 30 days, IP addresses, browser details and a device fingerprint. Referral records can link a signup to a campaign and help detect duplicate referrals. There is no automatic expiry for all referral records. Security tools also compare account, device and IP information to identify potentially related accounts for abuse prevention.
Who can access content
Platform admin status does not grant access to other people’s private conversations. Admins who participate in a conversation have the same access as other participants. Admin moderation tools show reported snapshots, without opening the surrounding conversation or later edits. Automated image/video classifiers process ordinary uploads, but cannot scan encrypted attachments.
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, within the evidence retention window described below.
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.
Installed bots may receive messages and events made available to them. Their developers may operate separate services with their own data practices. Disdroc AI runs on operator-managed hardware; its prompts and replies are stored as ordinary chat messages. Do not send secrets to a bot or assume its conversations are confidential from the operator.
Calls and encryption
HTTPS protects transport to the website; it alone does not hide content from the service or its HTTPS delivery provider. Opt-in chat encryption adds encryption on participating devices for new private-chat content and attachments. Calls use WebRTC DTLS-SRTP between connected peers. Disdroc handles signaling and connection metadata; calls may use STUN/TURN infrastructure, and peers may learn network addresses. Chat safety numbers do not verify call keys.
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.
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.
Disdroc does not provide service-side recording of voice, video or screen sharing. Participants can still record using their own tools. Password hashing, session controls and optional two-factor authentication reduce risk but do not guarantee security.
Outside services
Cloudflare delivers and protects the website and processes requests and connection data. Google Fonts receives requests when pages load its fonts. Resend provides outgoing email delivery; it and your email provider process addresses and email contents, including verification codes and security alerts containing IP or device information.
If you enable notifications, browser push services or Google Firebase Cloud Messaging handle delivery identifiers and notification traffic. Unencrypted-message notifications can include sender names and message previews, including on your lock screen. Encrypted-message push payloads use generic “New message” text without plaintext previews; delivery metadata is still visible to providers.
GIF searches and media features use outside providers, including Tenor, GIPHY, YouTube/Google, Spotify and Twitch. Searches, thumbnails, embeds or shared activities may contact providers when loaded, before you press play. They can receive connection information and feature-specific requests and may use their own cookies. Linked YouTube Music accounts require credentials or tokens stored by Disdroc so it can act on your requests; unlinking removes the active link but does not erase the provider’s records.
Advertising: the website and the web app can show ads served by Google AdSense, and the Activities panel in calls can show ads (including a short ad before a call activity starts). Google and its partners use cookies and similar technologies to serve ads based on your prior visits to this and other websites. You can opt out of personalized advertising at Google Ads Settings (adssettings.google.com) or opt out of third-party vendors’ cookies at www.aboutads.info. Ads we serve ourselves are counted (views and clicks per ad) without tracking cookies.
Outside providers may process data in other countries under their own policies. Operator-managed storage does not mean all processing stays in Türkiye. We may also disclose relevant information where legally required or to address abuse. This page does not assert that every international transfer has been independently assessed or certified.
Spotify linking stores access and refresh tokens to retrieve your listening status. YouTube Music linking stores browser-session credentials or OAuth credentials and uses them to retrieve music, playlists and account-specific results. AI replies can use recent conversation history and your configured persona as context.
Retention and deletion
Messages remain until removed through an available deletion action. Some actions hide messages before all stored content is cleared. Explicit message deletion clears the message body and attempts to remove its attachments. Deleted-message cleanup also runs periodically. Uploads do not automatically expire after 24 hours.
History keeps identity and moderation observations for up to 365 days; sensitive field values and security events for up to 90 days. Report evidence expires at the earlier of 365 days after submission or 180 days after resolution. Login history and abuse-action records have a 90-day cleanup window, as do risk events, call-usage records and upload counters. Sessions are removed after 60 idle days, or 35 idle days when revoked; trusted devices after 90 idle days. Retention does not reconstruct states before collection or recover removed values. Cleanup and subject-erasure rules apply to the active database; operational backups have separate lifecycles.
Account deletion removes the account and records covered by database deletion rules, including its E2EE device registrations and encrypted history-key backups in the active database. It does not guarantee removal from every operational backup, uploaded file or support record. Retained report snapshots and copies held by participants or providers may remain. Not every category has an automatic expiry. Contact Support for a specific retention or deletion request.
Cookies and device storage
Sign-in uses httpOnly access and refresh cookies. Browser storage also holds device identifiers, preferences and message drafts. Clearing site data removes local settings and can sign you out; it does not delete server records. You can revoke sessions and notification permission and unlink optional accounts. Third-party media can use separate cookies or storage.
Your requests and rights
You can edit your profile, delete your own messages where the app permits, manage sessions and delete your account in Settings. For access, a copy, correction or deletion of personal data, contact Support and specify the account and request. We may need proportionate identity verification; never send your password, authentication codes or recovery codes. Requests are reviewed manually, not through an automatic data-export tool.
Depending on applicable law, you may also have rights to information about processing and recipients, objection, restriction, portability, withdrawal of consent where processing relies on consent, and a complaint to the competent data-protection authority. Rights and exceptions depend on the request and law. See Türkiye’s personal data protection law and, where applicable, EU data-subject rights. This policy is a description of service practices, not a certification of legal compliance.
Age and content safety
The service is not intended for children under 13 or below a higher minimum age required locally. Birthdates are self-reported, not verified identity evidence. Content filters and age checks can make mistakes; some older accounts have no recorded birthdate. Do not rely on Disdroc to guarantee that minors cannot encounter explicit content. Report an underage account or unsafe content through Support.
Policy updates
We publish revisions here with an updated date. Material changes to data handling may require additional notice or consent under applicable law; merely publishing this page does not replace those requirements. See the Terms of use for service rules.