Privacy policy

This is the privacy policy for didibet-australia.com. It describes what happens to data when you read this website, and nothing beyond that. It is not the privacy policy of Didibet, of any casino operator, or of any payment provider, and it does not cover what happens once you leave here. Last updated: September 2026.

The policy is short because the site is simple. We publish articles about an offshore gambling brand for an Australian audience, most thoroughly in the Didibet review, and a publishing site needs very little data to run. There is no account to open here, no registration form and no cashier. What follows sets out the little that is collected, the reason for it, and how to have it removed.

What this site collects

There are three categories, and the list below is complete.

Server logs

Like every web server, ours records a line each time a page is requested. That line holds your IP address, the date and time, the URL you asked for, the referring URL if your browser sent one, your user-agent string (browser, version, operating system, device class) and the response code. Logs of this kind are what keep a site running and secure — diagnosing errors, finding broken links, blocking abusive traffic. They are not used to build a profile of you, and they are never sold or shared for marketing purposes.

Analytics

We look at aggregate traffic data to see which articles get read and which need rewriting. That covers page views, entry and exit pages, approximate location at country or state level, device type and referral source, all of it as totals and trends — not individual records. Where the tool supports it, IP addresses are truncated before storage. None of this identifies you by name, since your name is never collected in the first place.

Cookies and similar storage

A small number of cookies and local storage entries may be set: strictly necessary ones that keep the site working, preference cookies that remember a setting you chose, and analytics cookies for the aggregate counting described above. Control over all of them sits with your browser — every major browser can block them, delete them, or discard them at the end of a private session. The site remains fully readable with cookies switched off.

What this site does not collect

For most readers this is the more relevant list:

  • No payment data. No card numbers, bank details, crypto wallet addresses or PayID. There is nothing to buy here and no cashier on this domain.
  • No identity documents. We never ask for a driver’s licence, passport, Medicare card, utility bill or selfie. Any page claiming to be us and asking you to upload ID for account verification is not this site.
  • No gambling account data. No usernames, passwords, balances, bet histories or transaction records for Didibet or any operator. We have no access to them and could not retrieve them on request.
  • No registration or newsletter database. There is no sign-up on this site, so there is no mailing list.
  • No sensitive information as the Privacy Act defines it — health, racial or ethnic origin, political opinions, religious beliefs, sexual orientation, criminal record or biometric data.

The only personal information held deliberately is whatever you type into an email to us, and that only happens if you choose to write one.

The legal framework

This site is operated for an Australian audience and handles personal information in line with the Privacy Act 1988 (Cth) and the thirteen Australian Privacy Principles (APPs). The APPs cover transparent handling of information, collecting only what is reasonably necessary, using it only for the purpose it was collected for, keeping it secure, and giving people access to and correction of what is held about them.

Where a site collects almost no data, most of the APPs have very little to operate on. We collect the minimum a web server needs and use it for site operation and content decisions. None of it is disclosed for marketing, and none of it is sold — to anyone, gambling operators included.

Why we hold the little we hold

  • To deliver and secure the site. Server logs are how an unreachable page, a broken redirect or a credential-stuffing attempt gets found and fixed.
  • To improve what we publish. Aggregate analytics show which guides get read to the end and which get abandoned halfway.
  • To answer you. If you email us, we use your address to reply, and for nothing else.
  • To meet legal obligations. Where a lawful request from an Australian authority requires disclosure of records we hold, we comply.

When you click through to Didibet

This section deserves close attention. Once you leave this site for Didibet’s own domain, you are on a different company’s property and a different set of terms applies. Everything you do there, from creating an account and uploading ID through to depositing, betting and contacting support, is governed by Didibet’s privacy policy, not this one. We have no visibility into what is held there and no ability to have it changed or removed.

The distinction carries more weight with an offshore operator. Didibet holds no Australian licence, so its data handling is not supervised by Australian regulators, and the enforcement mechanisms in the Privacy Act do not reach it the way they reach a domestic business. Before handing identity documents to any offshore site, read its own privacy terms and form a clear view of where that data will be stored and who can access it. The same caution applies to the third-party gaming and sportsbook platforms that Didibet routes some products through, since each is a separate company operating under its own policy.

Third parties that touch data here

The site runs on commercial web hosting, and the host processes server logs to deliver pages. An analytics provider handles the aggregate usage data described above. A content delivery network may sit in front of the site to speed it up and filter malicious traffic, inspecting request metadata including IP addresses as part of that job. Some providers operate servers outside Australia, so limited technical data may be processed overseas — standard for modern web infrastructure, and covered by the reasonable-steps obligation in APP 8.

Reader data is not shared with gambling operators. There is no data brokerage, no list rental, and no arrangement under which your information is passed on as a product.

How long data is kept

Server logs are kept only as long as they are useful for security and troubleshooting — weeks to a few months — then rotated and deleted. Aggregate analytics are retained in summary form, because the whole point of them is comparing one quarter against the next. Emails are kept while a conversation is live and deleted afterwards. Nothing is warehoused indefinitely on the chance that it might become useful later.

Your rights, and how to use them

Under the Australian Privacy Principles you may ask what personal information we hold about you, have it corrected if it is wrong, and have it deleted. Unless you have emailed us, the answer to the first question is usually that we hold nothing which identifies you. The right still stands, and any request gets a proper answer.

Write to [email protected] with enough detail for us to locate the relevant records. We aim to respond within 30 days, which is the timeframe the Privacy Act works to. There is no charge for making a request.

If you are unhappy with how a request is handled, raise it with us first so that it can be put right. Should that lead nowhere, the complaint can be escalated to the Office of the Australian Information Commissioner (OAIC) at oaic.gov.au. The OAIC handles privacy complaints against Australian entities and investigates them independently.

Security

The site is served over HTTPS, so traffic between your browser and our server is encrypted in transit. Administrative access is limited to the people who maintain the site and protected by strong authentication, and software is kept patched. The most effective control of all is simply that there is very little personal data here to lose.

No system is perfectly secure, and we would not claim otherwise. If a breach occurred that was likely to result in serious harm, affected people and the OAIC would be notified, as the Notifiable Data Breaches scheme requires.

Children

This site covers gambling and is intended solely for adults aged 18 and over. It is not directed at children, we do not knowingly collect information from anyone under 18, and nothing here should be served to a minor. If you believe a minor has sent us personal information, email us and it will be deleted.

Changes to this policy

This page is updated whenever the site changes in a way that affects data: a new analytics tool, a different host, an adjustment to what gets logged. The date at the top reflects the current version. Material changes are summarised here rather than made quietly, and continued use of the site after an update means the current version applies.

Contact

Questions about this policy, an access or deletion request, or anything else concerning how this site handles data can go to [email protected]. We cannot help with account, deposit, withdrawal or verification issues at Didibet, because we are not the operator and have no access to its systems. Those enquiries belong with Didibet’s own support.

About the desk. Nathan Whitlock has covered offshore casino and sportsbook brands for Australian punters since 2018. Every page here is written after opening the operator’s live site, walking the sign-up and cashier flows, and recording what the brand actually publishes — including the gaps. Where Didibet does not publish a number, this site says so instead of inventing one.

Corrections and reader reports go to the editor; the contact address is in the site footer.