Tiki Taka Casino Privacy Policy – Data Protection and Cookies describes which privacy topics may be relevant to players. Because no specific policy information from the operator is available, this page provides general explanations and points to check.
Personal data may be required for account management, identity verification and legal obligations. Which data Tiki Taka actually processes, with whom it is shared and how long it is retained should be explained in the applicable privacy policy and account information.
Privacy at Tiki Taka at a glance
The GDPR requires personal data to be processed for clear purposes and on an appropriate legal basis. Depending on the situation, this may be the performance of a contract, a legal obligation, consent or a legitimate interest. The applicable legal basis should be assessed for each processing activity.
A player can check the privacy policy to determine who is responsible for processing, which contact options are available and whether data is transferred outside the European Economic Area. This page does not confirm any specific practices of Tiki Taka.
What data Tiki Taka collects
The type of data depends on the service being used and the checks that apply. The categories below are examples; the actual collection should be checked in the privacy policy or during the relevant process.
Data collected during registration
When creating an account, identification and contact details may be requested, such as a name, date of birth and email address. Account settings may also contain personal data. The registration form and privacy policy should clearly explain which fields are required and why.
Data collected during verification
An identity check may require an identity document or additional information. A player can check in advance which data is needed, how documents can be submitted securely and whether certain parts may be hidden without preventing the verification process.
Data related to payments and gambling
Transaction data may include amounts, timestamps and payment status. Account activity and information about configured gambling restrictions may also be relevant. The exact data flows and recipients should be checked with the operator.
How your data is used
A purpose must be sufficiently specific and the chosen legal basis must be appropriate. Consent is not required for every processing activity; where a legal obligation applies, withdrawing consent cannot remove that obligation.
Account management and services
Data may be used to manage an account, answer questions and process transactions. For activities necessary to perform a contract, performance of that contract may provide a legal basis. Not every additional processing activity automatically falls under that basis.
Legal obligations and anti-money laundering checks
Where applicable law requires it, identification, transaction monitoring and retention of certain data may be necessary. The privacy policy should explain which obligations are relevant. This general description does not confirm which specific obligations apply to Tiki Taka.
Fraud prevention and responsible gambling
Monitoring suspicious activity and measures intended to protect players may involve processing account and usage data. Depending on the circumstances, a legal obligation or legitimate interest may be relevant. Where legitimate interest is relied upon, the interests and rights of data subjects must be taken into account.
Cookies at Tiki Taka
Cookies and similar technologies can store or access information on a device. Some are necessary for a requested function; others may be used for analytics or marketing. For non-essential technologies, prior consent is required in many cases.
Adjusting cookie preferences
A player can review the available cookie settings and check which categories can be refused or changed later. Browser settings may provide additional control, but deleting cookies can remove saved preferences. The cookie policy should describe the technologies used and their purposes.
Sharing data with third parties
Personal data may be shared with external parties when necessary for a service, a verification process or a legal obligation. Sharing does not automatically mean selling. Without specific policy information, it cannot be established which parties Tiki Taka uses or whether data is sold.
Payment providers
A payment service may receive data needed to process or verify a transaction. A player can check which party is involved, which data is exchanged and whether that party acts as an independent controller for part of the processing.
Verification and fraud prevention services
External services may be used for identity verification or fraud detection. Identification data or verification results may be exchanged in this process. The privacy policy should explain the categories of recipients, purposes and any transfers outside the European Economic Area.
Game providers and technical partners
Technical partners may process data to operate or secure parts of a service. Which data they receive and in which role they act varies depending on the setup. A player can request further information from the responsible operator.
Data retention periods
Personal data should not be retained longer than necessary for its purpose unless an applicable obligation or another valid reason justifies continued retention. Different categories may therefore have different retention periods. Specific retention periods for Tiki Taka are not available here.
After an account is closed, certain information may still be required for administration, legal obligations or dispute handling. A player can ask which categories remain, why this is necessary and when deletion or reassessment takes place.
Security of your data
The GDPR requires appropriate technical and organisational measures based on the risks involved. Without information from the operator, it cannot be confirmed which specific security measures Tiki Taka applies. Players can also take steps themselves to reduce the risk of unauthorised access.
In addition to measures taken by an operator, a player can handle access credentials, documents and preferences carefully. The following actions reduce certain risks but do not provide a complete guarantee against misuse or security incidents.
- Unique password — A long, unique password for the account reduces the risk that a data breach at another service could provide access. A reliable password manager can help store different passwords securely.
- Additional login security — If additional verification is available, a player can check how it is enabled and which recovery options exist. Recovery codes should be stored securely and separately from the account password.
- Be careful with messages — Unexpected messages requesting login details, payment information or identity documents deserve extra scrutiny. A player can independently find the known contact method instead of following instructions from a suspicious message.
- Share documents carefully — Before sending an identity document, a player can check why it is required, which information must remain visible and which secure submission method is available. Unnecessary copies should not be stored without protection.
- Protect the device and session — Regular updates, a screen lock and logging out on shared devices reduce risks. If unauthorised access is suspected, the player can change the password and notify the operator through the available contact method.
- Review preferences — Cookie and marketing settings can be reviewed periodically, especially after changes to the service. A player can withdraw unnecessary consent and verify that the chosen preferences have been saved correctly.
Encrypted connection
An encrypted connection can protect data during transmission from being read by third parties. A player can check connection information in the browser and be cautious about unexpected requests for documents or login details. Encryption alone does not prevent every form of misuse.
Access management and internal controls
Restricted access rights, access monitoring and clear internal procedures are examples of organisational safeguards. The operator can be asked how access to sensitive data is restricted and how a suspected security incident can be reported.
Your rights under the GDPR
Depending on the circumstances, a data subject may request access, correction, deletion, restriction or portability and may object to processing. Consent can be withdrawn where processing is based on consent. These rights are not unlimited; the controller must justify any refusal.
A request may concern the data itself, the purposes, recipients and retention periods. If there is doubt about identity, the controller may request additional information insofar as necessary to identify the requester.
The GDPR provides several ways to exercise control over personal data. Which rights apply in a specific situation depends on the processing and any applicable exceptions; a clear request helps with the assessment.
- Access — With an access request, a data subject can ask which personal data is being processed, for which purposes and to which recipients data has been disclosed. A copy of the data may form part of the response.
- Correction — Incorrect personal data can be identified with a request for correction. Where information is incomplete, an additional statement may be appropriate; supporting information can help clarify the requested correction.
- Deletion — A deletion request may concern data that is no longer necessary or where another GDPR basis applies. Legal retention obligations and other exceptions may limit complete deletion.
- Restriction — Where accuracy is disputed or in other applicable situations, restriction of processing may be requested. The data generally remains stored while further use is limited under certain conditions.
- Data portability — For certain data processed automatically on the basis of consent or a contract, a data subject may request a structured, commonly used and machine-readable copy or request transfer to another controller.
- Objection — Processing based on legitimate interest may be objected to with an explanation of the personal situation. Processing for direct marketing may also be objected to; specific rules apply in that case.
- Withdraw consent — Where consent is the legal basis, it can be withdrawn through available preferences or by submitting a request to the controller. Earlier processing does not automatically become unlawful as a result, and other legal bases may remain relevant.
Closing an account and requesting data deletion
Account closure and data deletion are separate actions. A closed account does not automatically mean that all data disappears immediately. A separate deletion request makes clear which data the data subject wants removed and what confirmation is requested.
If retention remains necessary, the player can request an explanation for each data category and ask for restriction of further processing where applicable. The operator must handle the request within the period prescribed by applicable law.
A privacy request generally follows a recognisable sequence of steps. A player can check the available contact information, define the scope of the request and keep correspondence in order to follow the handling process and any subsequent steps.
- 1. Choose the request — First determine whether the request concerns access, correction, deletion, restriction, portability, objection or withdrawal of consent. Account closure can be requested separately because closure does not automatically mean that all personal data is deleted.
- 2. Make contact — Look in the privacy policy or account information for the available support or privacy contact method. State that the request concerns GDPR rights and keep a copy of the message so that it is clear later what was requested.
- 3. Confirm identity — Where reasonable doubt about identity exists, additional verification may be required. Ask which information is necessary and how it can be provided securely; do not send additional sensitive documents unless needed.
- 4. Describe the request precisely — Specify which data, period or processing activity the request concerns and what result is expected. For deletion, for example, it can be asked which data may need to remain and on what legal basis.
- 5. Follow up or submit a complaint — Keep the response and ask for clarification if parts are missing or a refusal has not been sufficiently explained. The request should be handled within the period prescribed by applicable law; if necessary, a complaint can be submitted to the Dutch Data Protection Authority.
Minors and age verification
Age verification may be necessary to prevent minors from accessing services intended for adults. The operator should not request more data than necessary for the check and should clearly explain how supporting documents are handled.
If data relating to a minor may have been processed incorrectly, a parent or legal representative can make contact and request an investigation. The controller may verify whether the requester is authorised to act on behalf of the child.
Changes and contact
A privacy policy may change when purposes, legal obligations or service providers change. A player can review the available version and any information about changes and check how important updates are communicated.
For questions or requests, a player can use the support or privacy contact method listed in the account information or privacy policy. If no response is received or the response is insufficient, a complaint can be submitted to the Dutch Data Protection Authority.