Privacy policy
Last updated:
This page explains what data Dialova uses, why it is necessary, and how you can control your information. It describes the current operation of the service.
For any requests concerning your data, contact the Dialova team.
1. Data used
Your account includes your email address, nickname, authentication information, email address validation, and acceptance of the terms of service. Passwords are stored as secure hashes, not in plain text.
Your profile may include a date of birth, gender, country or location, a bio, photos, and other information you choose to share. Required fields are indicated in the forms; optional information can be left blank.
The service also processes messages, read status, preferences, blocks, reports, moderation actions, credit movements, and data necessary for the games used. Connections produce technical information such as IP address, connection dates, and incident logs.
2. Why this data is processed
Creating and managing your account, authentication, profiles, messages, games, and requested features serve to provide the service as described in the terms of service: these processes are based on the execution of the contractual relationship.
Preventing abuse, protecting accounts, security checks, moderation, and incident diagnosis respond to the legitimate interest of protecting the service and its users. Requests imposed by law or a competent authority are subject to applicable legal obligations.
Authorized administrators and moderators also have a view of recent WebIRC connections: nickname, IP address, entry site, times, browser and system announced, screen and window dimensions, language, timezone, touch availability, and application mode. This view is used for moderation and troubleshooting; it does not contain your conversations. Limited to 500 connections and a maximum of 24 hours, it is stored only in memory until the server restarts. Language and timezone are not a geolocation.
To understand chat interruptions, technical diagnostics may record page background activity, browser-reported network status, reloads, and connection openings or closures. These events are linked to the chat session and can be correlated with connection information in the secure moderation view. They do not contain conversation text or visited URLs. They are not used for advertising.
When an optional processing requires your consent, it must be requested separately and can be withdrawn for the future. Camera or microphone authorization is also managed in your browser. Accepting the Terms of Service does not constitute a general consent to any use of your data.
3. What other members can see
Your nickname, your presence, the information displayed on your profile, your shared photos, and certain personalization elements are visible depending on the features used. Your age depends on the setting on your profile; your full date of birth and login email are not displayed on your profile.
The directory and profiles are reserved for connected members. They are not published in the sitemap for search engines. Messages in a room are visible to participants, including those who can access its history available.
Photos published in a room are stored and accessible to authorized accounts present in that room. They are not private photos between two people. A member can copy content or take a screenshot. Avoid publishing personal addresses, identity documents, financial data, or any information you do not want to share.
4. Notifications from the installed application
If you enable them, Dialova can alert you to new private messages when the installed application is in the background. A technical subscription and the necessary keys for delivery are associated with your session. Your browser's notification services, provided by Apple, Google, or Mozilla depending on the device, deliver an encrypted notification that does not contain the text of your conversations.
Activation and deactivation are done in Settings → Chat on each device. Corresponding sound preferences are linked to your account; the global silence delay is memorized on the device. An expired or revoked session will no longer receive new notifications. Invalid subscriptions are removed, and account deletion removes subscriptions and preferences.
5. Private messages and history
Private messages between Dialova accounts are stored to retrieve exchanges, unread messages, and messages received offline. Participants can view this history. Photos and voice messages sent in a Dialova private message are also stored and accessible only to the two participants from that conversation. Closing a tab or clearing its display does not delete stored messages.
These chats aren't end-to-end encrypted: the servers process them to ensure their transmission and storage. They aren't intended for other members; authorized processing may be necessary for reporting, safety, or a legal obligation.
The interface doesn't currently offer individual deletion of an entire private message history. You can submit a request regarding your data via Contact. Discussions with external network identities don't necessarily follow the same retention rules.
6. Webcam and Microphone
The camera and microphone are used when you voluntarily activate their broadcast and grant browser permissions. A public broadcast is intended for authorized viewers of the service; a private broadcast requires the permissions specified in the application.
Dialova doesn't offer a function to record webcam streams. Technical session data is needed to manage access and connections. The service can't completely prevent a viewer from making a capture on their own device.
Check the camera's field of view before broadcasting and stop the broadcast when you no longer want to share. Refusing the camera doesn't prevent you from using the text chat.
7. Optional Audience Measurement
With your consent, Dialova also uses Google Analytics to measure the viewing of public pages and general chat sections, the member list, and your own profile. Google Tag Manager is also used to manage measurement tags, with the same prior consent. This Google service involves communication from your browser to Google and optional cookies. No conversation content, email, nickname, or member profile is sent to Google Analytics by Dialova. You can refuse or withdraw your consent on the Cookies page without limiting your access to the site.
8. Internal service statistics
Dialova also measures the activity of its members and the events necessary to track the service: login days or visible usage, Web/PWA mode, mobile/computer categories, messages sent, and game sessions. Private exchange statistics only use their metadata, without copying their content.
These indicators are used to improve exchanges and monitor community safety. Only authorized administrators have access to the aggregated dashboard. Events and activity days are retained for a maximum of 180 days and are deleted when the account is purged. They are not used to establish an advertising profile.
9. Who can receive the data
Data is accessible to authorized team members when their tasks require it and to technical service providers involved in hosting, backups, or email routing. Backups use Backblaze and are encrypted before transfer.
Other members only receive the information necessary for interactions and the content you share with them. A competent authority may receive information when a legally founded request requires it.
Third-party services may process data outside the European Economic Area according to their organization. Their privacy policies describe the conditions applicable to their own services.
10. External Networks and Optional Services
When you use an external chat network, your nickname, the presentation information transmitted by the client, and the messages sent are communicated to that network. A direct connection may also reveal your IP address. Their own rules and recipients apply; blocking or deleting on Dialova doesn't automatically erase their data.
You can disable external networks in Settings → Chat. A global deactivation or moderation restriction can also prevent their use.
If a connection via an identity provider is offered and you choose it, the information necessary for authentication is exchanged with that provider. The Contact form may use Cloudflare Turnstile when this anti-abuse protection is enabled.
11. Retention for the Lifetime of the Account
Account information, the profile, photos, and private messages are retained to ensure the corresponding functions as long as the account exists, subject to an applicable deletion request. No automatic general deletion after a period of inactivity is currently implemented.
The recent history of Dialova rooms is limited to three days and server capacity; it may disappear sooner, especially after a restart. This timeframe doesn't apply to private messages saved between accounts.
Recorded connection IP addresses in account history are purged after 90 days. Application technical logs have a retention period of 14 days. These timeframes don't describe all possible logs from a provider or external network.
Reports, exchanges addressed to support, and tracking items are retained to process requests, examine incidents, and follow up on any potential disputes.
12. Account Deletion and Backups
The deletion request from Settings → My account immediately revokes access to the account. The deletion of data attached in the production database is performed by the deletion process, after confirmation of the stop and cleaning of associated services. The receipt indicates the progress or any potential problem.
Once this deletion is finalized, the information attached to the account is erased from the production database, including associated private messages, the profile, and related tracking items. This doesn't remove a copy made independently by another member or an external service.
Previous backups may still contain this information during their 14-day archival cycle. They are encrypted, access-restricted, and intended for disaster recovery; they are not used to maintain an active profile. Deleting in production does not retroactively modify each archive.
Restoring an old backup can reintroduce the state recorded at that date. If you experience any issues related to a deletion, please contact the team for review of your request.
13. Information Security
Exchanges with the site use HTTPS, and chat connections are protected by encrypted transport. Session cookies are protected against access by scripts and are reserved for secure connections. Access is controlled by roles, and sensitive actions are monitored.
Two-factor authentication can be enabled in Settings → Security. It is required to access moderation spaces. Keep your recovery codes in a safe place and use a unique password.
These measures reduce risks without constituting an absolute guarantee against any incident. Report any suspected access or vulnerability via Contact, without transmitting any secrets.
14. Your Rights and How to Exercise Them
According to the treatments and conditions provided by GDPR, you can request access to your data, rectification, erasure, restriction of processing, object to processing based on legitimate interest, and request data portability. When processing is based on your consent, you can withdraw it.
Address your request via Contact, indicating the account concerned and the right you wish to exercise. A proportionate identity verification may be necessary; do not spontaneously provide an ID, password, or login code.
The response time is, in principle, one month from receipt of the request, with a possible extension under the conditions provided by GDPR and notification within the first month. You can also file a complaint with the CNIL.
15. Cookies and Evolution of This Policy
The cookies and local storage used by the service are described on the dedicated page. This policy will evolve with the features and providers actually used. The update date appears at the top of the page.