Privacy Policy

Last updated: 29 June 2026

This policy explains how data associated with the use of Dhamet is collected, used, stored, and protected.

This policy applies to the official version of Dhamet published through official OuglSoft domains and to the features connected with it, including accounts, play against the computer, online play, spectating, chat, voice, leaderboard, and contact forms.

1. Controller

The entity responsible for operating the application and processing the related data is:

El Ougl Software SARL
www.ouglsoft.com
[email protected]
[email protected]

2. Practical summary

Dhamet processes the data needed to operate the game and its features. This includes sign-in, profile data, online play, match synchronization, invitations, chat, voice, statistics, ranking, analytics, and performance improvement.

We do not sell user data. We do not rent it. We do not give it to third parties for their own commercial or marketing purposes. Some data passes through technical services required to operate the application, such as Firebase, Google Analytics, Cloudflare, and browser services related to voice.

3. Data the application may process

3.1 Account and sign-in data

When a user creates an account or signs in, the application may process data needed to manage the account and authentication, such as:

• Email address.
• Technical user identifier.
• Sign-in method.
• Google sign-in data when this option is used.
• Nickname.
• Selected profile image or avatar.
• Account creation date or last activity when available.
• Session data needed to keep the user signed in or restore the sign-in state.

Passwords are not stored inside the application files. Authentication is handled through Firebase Authentication or the technical service used to manage sign-in.

3.2 Profile and statistics data

The application may process data connected with the player profile, such as:

• Nickname.
• Selected avatar or image.
• Number of wins.
• Number of losses.
• Number of draws.
• Points.
• Overall ranking.
• Activity indicators related to updates and statistics.

This data is used to display the player profile, leaderboard, and gameplay statistics.

3.3 Online gameplay data

When online play is used, the application processes operational data needed to create and synchronize the match, such as:

• Player presence status.
• Sent and received invitations.
• Room or match identifier.
• Player names or nicknames.
• Board state.
• Current turn.
• Moves.
• Match status.
• Synchronization data.
• Exit, disconnection, or reconnection data.
• Spectator data when a user joins as a spectator.

This data is necessary for online play and is not used to create a marketing profile about the user.

3.4 Text chat data

If the user uses text chat inside a match, the application may process:

• Message text.
• Sender identifier.
• Sender nickname.
• Sender role inside the room, such as player or spectator.
• Time of sending.
• Read indicators or last-read indicators when available.

Chat should not be used to send sensitive or private information. Messages may remain for a period connected to the life of the room or to technical cleanup processes.

3.5 Voice and microphone data

If the user enables voice conversation, the browser asks for microphone permission. The application cannot use the microphone without the browser permission.

Voice conversation is used in real time through WebRTC. The application may process technical data needed to establish and maintain the connection, such as:

• Voice participation status.
• Mute status.
• Technical signaling data.
• Data about participants in the voice room.
• Network data needed for direct or indirect communication between users.

The application does not store saved voice recordings in the service. The voice feature is not intended to record or archive conversations.

The user can stop the microphone from inside the application or revoke microphone permission from browser settings.

3.6 Spectator data

When a user joins a match as a spectator, the application may process data needed for spectating, such as:

• Spectator identifier.
• Presence status inside the room.
• Entry time or last activity.
• Read or chat data if the spectator participates in chat.

3.7 Data for improving play against the computer

The application may record some completed-match data or technical gameplay states for performance improvement and the development of play against the computer, such as:

• Move sequence.
• Board state.
• Match result.
• Match duration.
• Final or technical data related to the match.

The purpose of this data is technical improvement, training, and analysis, not building a personal identity profile about the user. The data may be used in aggregated or derived form to develop gameplay models or logic.

3.8 Local browser data

The application may store data on the user’s device inside the browser, such as:

• Selected language.
• Appearance or visual mode.
• Gameplay settings.
• Session data.
• Saved or resumed match data.
• Last room or active state.
• Interface preferences.

This data remains on the user’s device until the user deletes it, the browser clears it, or it is replaced by newer data.

3.9 Analytics data

The application may use Google Analytics or similar measurement tools to understand how the application is used and to improve performance and stability. Analytics data may include:

• Device and browser data.
• Pages or screens used.
• General usage events.
• Approximate performance data.
• Session-related data.
• IP addresses or connection data processed by the service provider according to its policies.

Analytics is not used to sell user data or create advertising targeting inside the application.

3.10 Contact data

When a message is sent through a contact page, the application or company website may process:

• Name.
• Email address.
• Message subject.
• Message text.
• Technical data needed to send the form and protect it from abuse.

This data is used to respond to the request, note, or report, and is not used to create an account in Dhamet or publish the message inside the application.

4. Purposes of processing

• Create accounts and sign users in.
• Operate the profile.
• Display statistics and leaderboard.
• Operate play against the computer.
• Operate online play.
• Manage invitations, rooms, and matches.
• Synchronize match state between players.
• Enable spectating when available.
• Operate text chat.
• Operate voice conversation when enabled.
• Save settings and resume play.
• Improve performance and stability.
• Develop logic for play against the computer.
• Protect the service from abuse.
• Receive contact and support requests.
• Comply with legal or security requirements when needed.

5. External services

5.1 Firebase Authentication

Used to manage sign-in and accounts, including email sign-in or Google sign-in when available.

5.2 Firebase Realtime Database

Used to synchronize data required for the application, such as accounts, profiles, online players, invitations, rooms, matches, chat, spectating, voice, statistics, and leaderboard.

5.3 Google Analytics

Used to measure usage and improve performance and user experience.

5.4 Cloudflare

Used to host or deliver the site, and Cloudflare functions may be used to process contact forms or some technical requests.

5.5 WebRTC and related network services

Used to operate real-time voice. This may involve exchanging technical data between browsers or through supporting servers depending on the connection state.

6. Data sharing

We do not share, sell, or rent user data. However, when data passes through the technical service providers needed to operate the application, such as hosting, authentication, databases, analytics, email, or voice services, those third-party providers process the data that passes through them according to their own policies.

7. Retention

• Account and profile data remains as long as the account exists or as long as it is needed to operate it.
• Statistics and ranking data remains as long as the account or related record exists.
• Room, match, chat, voice, and spectator data is operational by nature and is removed when the match ends, the room is left, or during periodic cleanup processes.
• Training and improvement data is retained for analysis and development, converted into aggregated or derived data, and then the original data is deleted.
• Contact data remains for the period needed to reply, follow up, and retain support records when necessary.
• Analytics data is subject to the settings and policies of the service used.
• Local browser data remains on the user’s device until the user deletes it or the browser clears it.

8. Account and data deletion

The user can delete the account through the tools available inside the application when available. When the account is deleted, the application works to delete the direct data linked to the account from the main paths it controls, such as profile, leaderboard, player status, and invitations.

Account deletion may not immediately remove every technical or historical trace, such as:

• Data in backups or temporary logs.
• Aggregated or derived data that does not directly identify the user.
• Messages or traces linked to rooms or matches that ended before deletion.
• Data kept by an external service provider under its own policies.
• Data that must be kept to protect the service or comply with law.

9. User choices

• Use a nickname that does not reveal the user’s real identity.
• Edit available profile data.
• Delete the account and its data from inside the application.
• Delete local browser data from browser settings.
• Revoke microphone permission from browser settings.
• Avoid using chat or voice.
• Avoid Google sign-in and enter as a guest.
• Contact us for privacy or support requests.

10. Chat, voice, and user-provided content

The user is responsible for what they write, send, or say in chat or voice. Sensitive data, passwords, financial information, personal data of others, or illegal, immoral, or rights-infringing content must not be shared.

We may review, restrict, delete content, or suspend access if needed to protect the application, users, or the company’s rights.

11. Children and minors

Dhamet is a general web game and is not directed specifically to children. If the user is a minor under the laws applicable in their country, the application should be used with the approval or supervision of a parent or guardian.

We do not intentionally ask children to provide sensitive data. If a parent or guardian believes that a child has provided personal data without appropriate approval, they may contact us to request review or deletion.

12. Security

We use reasonable technical and organizational measures to protect data, such as secure connections, access controls, authentication services, and database security rules. No internet service can guarantee complete or absolute security.

The user is responsible for protecting sign-in data, using a strong password, and not sharing the account with others.

13. External links

The application or site may contain links to external websites or services, such as the developer’s website OuglSoft, Google services, or others. These websites and services are governed by their own privacy policies and terms.

14. International transfer and processing

Data may be processed through cloud services operating in countries different from the user’s country. By using the application, the user acknowledges that data may be processed through international technical infrastructure according to the services used to operate the application.

15. Changes to this policy

We may update this policy when the application features, data-processing methods, external services, or legal requirements change. The updated version is published with a last-updated date. Continued use of the application after publication of an update means the user has reviewed the new version.

16. Contact

For privacy, support, or questions about this policy: [email protected] / [email protected]