Evidence DeskIndependent Australian consumer reference
Privacy on this static publication
The recovery site serves public HTML, CSS and JavaScript. It has no account system, contact form, comments, newsletter, payment flow or operator integration that asks readers to submit personal information.
Research checkpoint:
| Activity | Present on this site | Privacy consequence |
|---|---|---|
| Public page request | Yes | Hosting infrastructure can process technical delivery data |
| Publisher account or form | No | No voluntary profile or message fields are collected here |
| Advertising or affiliate tracking | No | No operator conversion event is created by this edition |
| External evidence link | Yes | The destination applies its own privacy practices |
Evidence step 01
Information the site does not request
Readers do not create a profile or enter a name, email address, phone number, gambling account identifier or payment detail on these pages. The publisher does not ask for identity documents, verification selfies, passwords or financial records. There is no browser storage used to build a reader profile and no embedded operator widget through which account information is transmitted.
Because no editorial contact endpoint is published in this edition, the site does not receive correction submissions through the website. If a channel is added in a later version, its collection purpose, required fields and handling terms should be disclosed before the form is used. This policy describes the present static output and does not invent practices for a service that is not available.
Evidence step 02
Routine delivery records
A request for a public page necessarily reaches the hosting and network infrastructure that delivers it. Those systems can process technical details such as an IP address, request time, requested path, browser or device information, referral data and security signals. Such records may be used for delivery, reliability, abuse prevention and troubleshooting according to the infrastructure provider's operation and retention settings.
The static files do not expose a publisher dashboard that lets a reader inspect those network logs, and this policy does not claim that no infrastructure record exists. It distinguishes server delivery data from voluntary account data. Readers seeking details about a network provider's processing should consult that provider's current documentation and understand that routing can involve more than the visible page file.
Evidence step 03
Third-party destinations
Substantive external links in the recovery edition lead to Australian legislation, regulator information and support resources. Following one leaves this site and gives the destination its own request data. That organisation controls its separate privacy notice, security settings and retention. The publisher does not receive a Rainbet account event merely because a reader follows an official evidence link.
There are no Rainbet operator links, affiliate tracking destinations, advertising pixels, social-media embeds or payment components in this edition. Local presentation assets are served with the publication instead of requesting them from a marketing network. A future material change to embeds, measurement tools or submission features would require this notice to be reviewed before deployment.
Evidence step 04
Privacy choices during research
A reader can inspect browser developer tools, clear local browser data, limit referral information and use browser privacy controls. Those actions do not erase logs already held by a network provider. Shared-device users should consider local history and downloaded copies, particularly when researching gambling harm, disputes or identity exposure. Private browsing mainly changes storage on the device and does not make network activity invisible.
Do not paste private evidence into the address bar, a search box or an unverified service while researching a claim. Store case files separately and redact working copies. If a published page appears to expose personal information, preserve the page address and the minimum proof needed for a future verified publisher security channel, while avoiding further distribution of the affected material.
Questions
Questions for this evidence task
Does this site ask readers to create an account?
No. The static recovery edition has no registration, profile, newsletter, comment or payment feature.
Can the hosting network process technical request data?
Yes. Page delivery can involve an IP address, request time, path, device information and security signals at infrastructure level.
Does this policy cover an official site reached through an external link?
No. The destination has its own controller, systems and privacy terms once a reader leaves this publication.