How our BetWest Australia guide handles reader data
Why we hold information
Contact messages
Our pages carry a contact form, and a message sent through it holds what the reader puts in it: an e-mail address for the reply, the page the message concerns, and the correction or question itself. We use that information to answer the message and, where the message points at a wrong figure, to check and update the page it names.
Aggregate analytics
Analytics run in aggregate, which tells us which guides are read and which questions keep coming back. The aggregate numbers never identify a reader, and the purpose list stays this short: answering messages and reading our own traffic are the whole of it.
Commercial links in the same frame
Some links on our pages may be commercial links, and following one takes the reader to another site with its own data practices. What a reader does on the operator’s site is governed by the operator’s own policy, and the split is worth remembering before any account is opened from a link on a guide.
When this policy changes
Changes to the policy appear in the text itself, and the date line at the end of the page moves with each revision. A change that affects how contact messages are used is written into the purpose list above rather than into a footnote, so the current text is always the whole policy. Readers who have written to us and want to know whether a change touches their message can ask through the same form.
The control you keep
Asking about a message
A reader can ask what we hold from their contact messages, ask for a correction to it, or ask for the thread to be deleted once the question is settled. The route is the same contact form: name the e-mail the message was sent from and the page it concerned, and the request is handled from the thread itself.
Cookies and analytics choices
Analytics run through cookies, and a reader controls those in the browser: blocking third-party cookies leaves the pages working, and our cookies page explains which types the site sets and what each does. Clearing cookies does not affect a reader’s access to the guides. A rights request and a cookie choice are independent of each other, and both are handled without any operator involvement, because the guide holds nothing that belongs to an account.
What we may hold, and why
| Information | Purpose | Lifetime |
|---|---|---|
| Contact form e-mail address | replying to the message | while the thread is open |
| Message text and page reference | checking the correction against the published rule | while the thread is open |
| Aggregate analytics | seeing which guides are read and which questions recur | aggregate, not personal |
| Cookie preferences | keeping the site working as the reader set it | until cleared in the browser |
Last updated: 5 November 2026