Naobet Privacy Policy – Personal Data, Cookies and GDPR

Naobet Privacy: Personal Data, Cookies and Your Rights concerns the data that may be processed in connection with an account, the possible purposes of that processing and the rights of data subjects.

This page describes general privacy mechanisms and does not make unconfirmed statements about the practices of Naobet Casino. For specific data categories, retention periods and contact options, a player can consult the applicable privacy statement and account information.

How Naobet handles your privacy

Personal data are data that can directly or indirectly refer to a person. A privacy statement should explain which data are used, for which purposes and on what legal basis. The player can also check which parties receive data and how privacy rights can be exercised.

Controller of your data

The data controller determines the purposes and means of processing. The identity of that organisation has not been established here. A player can check the applicable privacy statement for the name, contact details and any details of a data protection officer.

Data you provide yourself

When using an account or making contact, data may be provided directly by a player. Which fields are mandatory and why should be stated in the relevant form or privacy statement. Not every request for information means that all possible data are necessary.

Registration details

Registration details may include, for example, a name, date of birth and contact details. Such data may be necessary to manage an account and enable contact. The player can check which data are requested and how changes can be submitted.

Identity documents

An identity document may be requested to verify identity or age and to comply with applicable obligations. The player can check which document is required, how it can be submitted securely and whether certain details may be hidden without preventing the verification.

Communication with customer support

A question or complaint may contain contact details, correspondence and information about the issue. These data may be used to handle the request and retrieve previous communication. It is sensible to share only information that is relevant to handling the matter.

Data collected automatically

When using a digital service, technical data may be generated without a player entering each item separately. The applicable statement should describe which data are collected, for which purposes and whether cookies or similar technologies are used.

IP address and location

An IP address can provide information about an internet connection and may sometimes indicate an approximate location. It may be used for security or access control. A derived location is not necessarily accurate and differs from an exact location shared through a device.

Device and browser

Technical data may include browser type, operating system and device characteristics. Such information may help with troubleshooting or identifying unusual access. The player can check the privacy and cookie statement to see which technologies are actually used.

Gambling and transaction history

Account activity and transactions may form a history that is needed for administration, checks or player protection. The exact content and retention period depend on the processing and applicable rules. An access request can clarify which data are linked to a person.

Purposes of data processing

Processing must have a clear purpose and an appropriate legal basis. Possible legal bases include performance of a contract, a legal obligation, consent and legitimate interest. Which legal basis applies must be assessed for each purpose; consent is not required for every processing activity.

Managing your account

Data may be necessary to manage an account, apply settings and handle requests concerning the service. When processing is necessary for a contract, that contract may form the legal basis. The statement should clarify which data are necessary for this purpose.

Legal checks

Applicable legislation may require checks or the retention of certain data. In that case, a legal obligation may form the legal basis. Which obligations actually apply depends on the responsible organisation, the service and the applicable regulations.

Security and fraud prevention

Security data may be used to investigate unusual access or possible fraud. Legitimate interest may form a legal basis if the interests and rights of data subjects have been carefully balanced. A player may object to processing based on this ground.

Player protection

Data about account activity or configured restrictions may be relevant to measures intended to protect players. The applicable statement should explain which data are used for this purpose and on what legal basis. Protection should not serve as a general reason to collect unlimited amounts of data.

Naobet cookie policy

Cookies are small data files that a service can place or read through a browser. Similar technologies may also store or recognise information. The player can consult the available cookie information to check purposes, involved parties and available choices.

Necessary cookies

Necessary cookies may support functions that are essential for a requested service, such as remembering a session. Whether a cookie is genuinely necessary depends on its function. The applicable information should clearly describe that function.

Preference cookies

Preference cookies may remember settings, for example a selected language. Depending on their operation and applicable rules, consent may be required. A player can check which preferences are stored and what happens when these cookies are refused.

Statistical cookies

Statistical cookies may provide insight into the use of a service, for example which sections are visited. The privacy implications depend, among other things, on the collected data and any third parties involved. Where consent is required, a choice should be available.

Marketing cookies

Marketing cookies may be used to measure advertising or track behaviour across services. Such technologies often require consent. The player can check which parties are involved and withdraw previously given consent through the available settings.

Refusing or deleting cookies

A cookie preference menu may offer options to refuse non-essential cookies or change consent. Browser settings can also delete existing cookies or limit future storage. Deleting cookies through the browser does not always replace withdrawing consent from the relevant service.

Sharing data with partners

Data may be shared with other organisations for specific purposes. The privacy statement should describe categories of recipients, purposes and any transfers outside the European Economic Area. For such a transfer, applicable safeguards must be assessed; specific partners have not been established here.

Payment providers

A payment service provider may receive data necessary to process or verify a payment. The role of that party may differ depending on the processing. The player can check which data are shared and which privacy information the payment service provider provides.

Verification services

An external verification service may be used to verify identity or age. It should be clear which data are provided, for what purpose and which party is responsible. A player can ask how documents are protected and when they are deleted.

Game providers

A game software provider may need technical or account-related data to make a service function. Which data are involved and whether the provider is independently responsible depend on the arrangements and the actual processing. The privacy statement may provide clarification.

How long data are retained

Retention periods may differ by data category and purpose. An organisation should not retain data longer than necessary unless an applicable obligation or another valid reason requires further retention. Specific periods have not been established here; the player can consult the statement or ask for an explanation.

Technical security of data

Appropriate security may include access restrictions, encryption and system monitoring. Which measures are actually applied has not been established here. Security reduces risks but does not completely eliminate incidents; in the event of a relevant data breach, legal notification and information obligations may apply.

In addition to measures taken by the controller, a player can also reduce risks themselves. The actions below do not replace an organisation’s security obligations, but help with careful handling of access, documents and personal preferences.

Exercising your privacy rights

The General Data Protection Regulation gives data subjects various rights depending on the circumstances and legal basis. A request may be addressed to the data controller. The controller may ask for additional information to confirm identity where there is reasonable doubt.

The following rights can help a player exercise control over personal data. Applicability differs by request and legal basis; the controller should clearly explain a decision and any legal exceptions.

Right of access

Access can clarify whether personal data are being processed and which information about that processing is available. A data subject may also request a copy of the personal data. The rights of others and legal exceptions may affect the content of the response.

Right to rectification

Incorrect personal data can be corrected and incomplete data can, depending on the purpose, be completed. A clear description of the error and the correct information helps with handling the request. Some changes may require an additional check.

Right to erasure

Erasure may be requested under certain conditions, for example when data are no longer necessary. The right is not unlimited: a legal retention obligation or another applicable exception may mean that certain data must be retained.

Right to object

An objection may be made, among other things, to processing based on legitimate interest. The controller must assess the objection according to the applicable rules. A data subject may object to processing for direct marketing, after which that processing for that purpose must stop.

Right to data portability

Data portability may apply to data that a data subject has provided and that are processed automatically on the basis of consent or a contract. Under the applicable conditions, the data are then provided in a structured, commonly used and machine-readable format.

Closing an account and data

Closing an account and deleting personal data are separate actions. A player can clearly formulate both requests and ask which data are retained afterwards and why. Closing an account does not automatically remove an applicable legal retention obligation.

Protection of minors

Age verification may help prevent access by minors. If data relating to a minor have been processed incorrectly, a parent or legal representative can make contact and explain the situation. The controller may ask for proof of identity and representation.

Changes to this policy

A privacy statement may change when processing activities, services or legal requirements change. The player can check the date and content of the applicable statement and see how important changes are communicated. A change does not remove existing rights.

Asking privacy questions

For questions, a player can check the contact options in the applicable privacy statement or account environment. If an answer is insufficient, a complaint can be submitted to the Dutch Data Protection Authority. A data subject may also contact another competent supervisory authority.

A privacy request to Naobet Casino can be prepared and submitted step by step. The data subject can check the applicable contact information, specify the right they wish to exercise and keep relevant correspondence for any follow-up question or complaint.

  1. 1. Choose the request — First, the data subject determines which right fits the question, for example access, rectification or erasure. Account closure and data erasure are not the same; when both are desired, both can be mentioned separately.
  2. 2. Make contact — The player then looks in the applicable privacy statement or account environment for a contact option for privacy questions or customer support. The request can be submitted there, stating that it concerns a privacy right.
  3. 3. Confirm identity — If there is reasonable doubt about identity, the controller may request additional information. The data subject can check why that information is needed, which details are sufficient and how any documents can be submitted securely.
  4. 4. Describe the request precisely — The player can then indicate which data, period or processing activity the request concerns and which result is requested. A clear description helps with handling the request without requiring unnecessary sensitive information to be sent.
  5. 5. Follow up or submit a complaint — Finally, the data subject can keep a copy of the request and ask for an explanation if the response is delayed or unclear. A response should follow within the legally required period; if dissatisfied, a complaint can be submitted to the Dutch Data Protection Authority.