PRIVACY & COOKIE POLICY

How account, transaction and device information may be handled

Understand the main information categories, service purposes, cookies, security safeguards, retention and available support choices.

Account information Transaction records Security data Cookie choices

Last updated: 30 August 2026

This Privacy & Cookie Policy explains the main categories of information that may be processed when you visit GDBET, create or use an account, access the wallet, play a game, claim a promotion, join the referral programme or contact support. The information actually handled depends on the features you use and the records needed to provide, secure and review those services.

1. Information you provide

Information supplied directly may include a username, name, mobile number and other registration details; messages sent to support; survey or feedback responses; promotion or referral information; and screenshots or documents submitted to explain an account, transaction, security or payment issue.

If verification is required, GDBET may ask for information that helps compare the account holder with the registration or payment record. Do not send a password, one-time verification code or unnecessary full financial information through chat.

2. Account, wallet and game records

Service records may include login history, wallet balances, deposits, withdrawals, order references, claim activity, turnover progress, promotion participation, referral relationships, game sessions and provider transaction identifiers. These records can be needed to display account activity, calculate an applicable rule, investigate a missing transaction or compare the GDBET record with a provider or payment record.

3. Device and technical information

Technical information may include IP address, browser type, operating system, device identifiers, screen or language settings, referring page, access time, error information, security events and cookie or similar identifiers. This information may be used to maintain sessions, adapt the display, diagnose errors and identify activity that appears unauthorised or inconsistent.

4. How information may be used

Information may be used to:

  • create, authenticate and operate an account;
  • provide wallet, game, promotion and referral functions;
  • process deposits and withdrawals and confirm payment ownership;
  • calculate rollover, promotion or commission status;
  • respond to support requests, complaints and correction reports;
  • detect duplicate accounts, suspicious access, payment abuse or prohibited conduct;
  • maintain platform performance, security and service records; and
  • send operational notices or permitted promotion communications.

GDBET should use information that is reasonably connected to the stated service, security or record-review purpose.

5. Where information may come from

Information may come from the member, the device or browser used to access GDBET, platform logs, payment services, game providers, communication channels, referral records or another person who submits a genuine security or transaction report. Information received from another source may be compared with retained account records before it is relied upon.

6. Service providers and necessary disclosure

Relevant information may be made available to payment services, game providers, hosting and security services, communication providers, technical contractors, professional advisers or other parties needed to operate and protect the platform. Only information reasonably needed for that function should be shared.

Information may also be preserved or disclosed when reasonably necessary to respond to a valid legal request, protect a person or account, investigate fraud or misuse, enforce platform rules or resolve a dispute. This policy does not mean that every listed provider receives every category of member information.

7. Processing in different locations

Online services and their providers may operate infrastructure or support functions in different locations. As a result, information can be processed or stored outside the member's current location. The safeguards, access routes and storage practices of a provider can differ. Contact support if you have a specific question about the handling of information for a feature you use.

8. Security and member responsibility

Reasonable technical and operational safeguards may be used to reduce unauthorised access, loss, alteration or misuse. No online service or transmission method can guarantee absolute security. Members should:

  • use a unique password and keep it away from other people;
  • protect the registered phone, device and one-time codes;
  • access GDBET through an address listed on Official Domains & Security;
  • sign out on a shared device and avoid unknown browser extensions; and
  • report an unfamiliar login, payment instruction or account change promptly.

9. Retention

Information may be retained for as long as reasonably needed to provide the service, maintain account and transaction records, protect platform security, investigate abuse, resolve complaints and meet operational or legal requirements. Different records may be kept for different periods. A deletion request may therefore not result in immediate removal of information that is still needed for one of these purposes.

When information is no longer reasonably required, it may be deleted, anonymised or placed beyond ordinary use according to the applicable process.

10. Cookies and similar technologies

Cookies and similar technologies can store or read small identifiers through a browser or device. Depending on the feature, GDBET may use:

  • Essential technologies for login, account security, navigation and wallet functions;
  • Preference technologies for language, display or remembered choices;
  • Performance technologies for errors, loading times and service reliability;
  • Analytics technologies for aggregated page and feature usage;
  • Marketing technologies for measuring or presenting permitted campaigns; and
  • Notification technologies where a member enables a browser or device notification.

Browser or device controls can block or remove cookies. Disabling an essential technology may prevent login, saved preferences or another account function from working correctly. Removing a cookie does not necessarily remove a related transaction or security record already stored by the service.

11. Service and promotion communications

Operational messages may relate to account access, security, transactions, platform maintenance or a support request. Promotion messages may relate to available GDBET campaigns. Available unsubscribe or preference controls should be used for optional marketing messages; however, a member may still receive necessary service or security notices while the account remains active.

12. Access, correction and deletion requests

You may contact support to ask what request options are available, correct inaccurate account information or raise a concern about the use of information. Provide the username or masked account reference, the information concerned and the requested correction. Identity verification may be needed before account information is disclosed or changed.

Access, deletion or restriction may be limited where records are still needed for transaction reconciliation, account security, fraud prevention, dispute handling or an applicable legal requirement. Support should explain the available outcome for the particular request rather than promise that every record can be removed.

13. Adult use and another person's information

GDBET is intended only for adults who meet the applicable age and legal requirements. Do not create an account for a minor or submit another person's identity, payment or contact information as your own. If you believe another person has used your information without permission, preserve the relevant message or transaction details and report the issue through an official support route.

14. Policy updates and contact

This policy may be updated when services, technologies, risks or information practices change. The latest version displayed on GDBET applies from the stated update date. A material question should be asked before continuing to use the affected feature.

For a privacy question, inaccurate record or security concern, use the Help & Contact Centre or Report a Problem. Include only the information needed to locate and understand the issue.