Naobet Casino Responsible Gambling – Limits and Self-Exclusion

Naobet Casino Privacy Policy – Personal Data, Cookies and Rights describes which privacy topics may be important for a player. This page provides general explanations; without available brand information, the actual procedures and the identity of the controller cannot be confirmed.

Personal data may be required for account management, checks and communication. The player can review the applicable privacy policy to determine which data is actually processed, on which legal basis this takes place and how a request can be submitted.

Privacy at Naobet at a glance

The table shows categories that may be relevant to an online gambling service. It does not confirm that Naobet Casino collects every listed category or uses it for every stated purpose. The applicable privacy policy should clearly explain which data is actually processed and which parties are involved.

Under the General Data Protection Regulation, the GDPR, an organisation must, among other things, explain why processing is necessary and which rights data subjects have. A player can compare this information with their own account settings and request clarification if anything is unclear.

Which data Naobet collects

With an account, identification data, contact details and data about use of the service may be processed. Messages to support and technical data may also be generated when someone contacts the service or logs in. Which fields are mandatory and which data is collected automatically should be clear from the information provided with the relevant action.

An identity check may require additional documents or information. It is important that the organisation explains why the check is necessary, how the document can be submitted securely and which data is required. A player does not have to assume without explanation that every requested document is necessary for every purpose.

What your data is used for

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. The applicable legal basis may differ by data category and purpose; the privacy policy should make that connection clear.

Your account and your gambling

Account data may be used to provide access, save settings and administer transactions. To the extent that processing is necessary for the contract, performance of that contract may provide the legal basis. Not every processing activity related to an account is automatically necessary; additional purposes require their own assessment and explanation.

Legal obligations and anti-money laundering checks

Depending on the applicable rules, checks on identity, transactions and possible money laundering risks may be required. A legal obligation may then provide the basis for the necessary processing. Which checks actually apply and which data is required for them should be explained by the controller.

Fraud prevention and responsible gambling

Data about access and transactions may be relevant for detecting misuse or unusual activity. Information about gambling behaviour and configured restrictions may also play a role in protection against gambling-related harm. Depending on the purpose, a legal obligation or legitimate interest may be relevant; in the latter case, the interests involved should be balanced.

Cookies at Naobet

Cookies are small files that a service can place on or read from a device. Similar technologies may store or collect information. Some applications are necessary for a requested function, while others may, for example, measure usage or support communication preferences.

Prior consent may be required for non-essential cookies. The player can review the cookie information to see which technologies are used, what they are used for and how choices can be changed. Browser settings can provide additional control but do not always replace the consent choice within the service.

Sharing with third parties

An organisation may share personal data when this is necessary for service provision, checks or a legal obligation. The privacy policy should explain the recipients or categories of recipients, the purposes and any transfers outside the European Economic Area. Without brand information, it cannot be established which parties Naobet Casino actually uses.

Payment partners

A payment service provider may receive data needed to process, verify or investigate a payment. Depending on its role, such a party may independently be responsible for certain processing or act on behalf of another organisation. The player can check which data is shared and which privacy information is provided by the payment service provider involved.

Verification services

An external verification service may be used to check identity or age. Document data or a verification result may be processed in this context. The controller should explain which party is involved, which data is shared and how the check relates to the purpose for which it is carried out.

Retention periods and security

Personal data should not be retained longer than necessary for the purpose unless an applicable obligation or another valid reason requires further retention. Retention periods may differ for account data, transactions and correspondence. Specific retention periods for Naobet Casino are not available here; the player can review the privacy policy or ask for the applicable period and reason.

Appropriate security may include access restrictions, encryption and checks for unusual access. Which measures are actually applied has not been confirmed without brand information. A player can also reduce risks by carefully managing account details and not trusting suspicious messages.

In addition to security measures taken by the controller, careful account use can reduce exposure of personal data. The measures below are general precautions and do not confirm which security features are available at Naobet Casino.

Your rights under the GDPR

The GDPR gives data subjects various rights, including access, rectification and, in certain circumstances, deletion. Restriction, data portability, objection and withdrawal of consent may also be relevant. Applicability depends on the legal basis, purpose and any legal exceptions; a request therefore does not always lead to the desired outcome.

If a request is rejected, the data subject can ask for an explanation. An organisation may request additional information where necessary to confirm the identity of the requester but should not ask for more data than necessary. A complaint can be submitted to the Dutch Data Protection Authority if the data subject believes that privacy rules are not being followed.

The following rights provide practical ways to exercise control over personal data. Not every right applies in every situation; the legal basis, purpose and legal exceptions also determine what the controller must do.

Contact about privacy

The identity and contact details of the controller for Naobet Casino are not available in the provided information. The player can review the applicable privacy policy and available contact options to determine where a privacy request should be submitted. If a data protection officer has been appointed, their contact option should also be included in the privacy information.

A clear request states which right is being exercised and which data or processing it concerns. The organisation should respond within the period prescribed by applicable law. If the response is unsatisfactory, the data subject can ask for clarification or submit a complaint to the Dutch Data Protection Authority.

A privacy request can be handled more effectively when the data subject clearly describes the desired right and the relevant data. The following sequence provides a practical approach without assuming a specific contact person or response period for Naobet Casino.

  1. 1. Choose the correct request — First determine whether the request concerns access, rectification, deletion, restriction, data portability, objection or withdrawal of consent. For account closure and data deletion, it is advisable to mention both requests separately because they may have different consequences.
  2. 2. Make contact — Look in the applicable privacy policy for the controller and the available privacy or support contact option. Use that contact method for the request and keep a copy of the message so the content can be reviewed later.
  3. 3. Confirm your identity — If the controller has reasonable doubt about the identity of the requester, additional confirmation may be required. The requester can ask which information is necessary and how it should be provided securely without sharing more personal data than required for the check.
  4. 4. Describe the request precisely — State which right is being exercised and which data, period or processing the request concerns. A clear description helps the controller assess the request; for deletion, the requester can also ask which data may still need to be retained.
  5. 5. Follow up or submit a complaint — Keep the response and ask for clarification if the decision or explanation is unclear. The controller should respond within the period prescribed by applicable law; if the handling is unsatisfactory, a complaint can be submitted to the Dutch Data Protection Authority.