Your Privacy on This Richard Casino Website

Every page here was written once, saved as a file and handed to a web server. When your browser asks for one, the server writes a log line: your IP address, the user agent your browser announces, the referring address if any, the path, the response code and a UTC timestamp.

An IP can count as personal information in Australia, so it is treated that way. Those lines get read to check pages load as fast from Perth as from Sydney, and to spot a crawler hammering the server. Not in them: what you typed, what you clicked, how far you scrolled. That needs JavaScript reporting home; the only script here sets the footer year and opens the menu.

Every gold button points at a /go/ address here, which attaches an affiliate parameter and forwards you to richardcasino12.com.

The moment it fires, you have left: you are on infrastructure run by Metlait SRL in Costa Rica under Tobique e-gaming licence No. 0000064, and the operator's privacy policy governs from there, not this one. Register, and the casino takes your email, date of birth, address and eventually a KYC pack — photo ID, proof of address, proof of payment. None of it reaches me. I cannot see your balance or whether a payout cleared, which is why the withdrawals page and the sign-in page point account problems at the operator's support.

A cookie is a scrap of text your browser keeps and hands back later. The one that matters here does a single job: it marks that a click on a Richard Casino link came from this domain, so a later sign-up is credited here rather than to nobody. It holds an affiliate identifier and a timestamp — no name, no email, nothing about which pokies you opened. Its lifespan belongs to the operator's platform; cookies of this type usually run 30 to 90 days, occasionally a year.

Blocking it costs you nothing as a player. The package, codes and wagering terms on the Richard Casino bonus page are identical either way — blocking just means this site earns nothing, and the disclaimer explains how the lights stay on.

Promises are cheap, so here is the checkable version:

• No advertising network. Nothing on this domain is bought or sold through an ad exchange.
• No analytics ID shared with other sites. Traffic understanding comes from the host's own logs, never joined to a property watching somebody else's site.
• No mailing list, no push notifications. No newsletter box, no bonus alerts, no browser prompt begging to nag you.
• Nothing aimed at children, no profiling of them. Adult reading at 18+, and no mechanism here could profile anyone.

Australian privacy law runs on the Privacy Act 1988 and the thirteen Australian Privacy Principles beneath it. The regulator is the Office of the Australian Information Commissioner. Raise a problem here first; if nothing moves, the OAIC at oaic.gov.au takes complaints from any Australian.

Here is the bit that usually gets one vague line and a shrug. Richard Casino sits outside that framework. Metlait SRL runs from Costa Rica under a Tobique licence, with no Australian one, so the Act does not reach it in practice and the OAIC cannot order it to delete your KYC scans. A complaint there travels through the operator's support, then its licensing body. The paperwork is laid out on the Richard Casino review page. Not a scare, just worth knowing which door you knock on.

Access logs rotate out at 90 days, overwritten in ordinary housekeeping. Want a line gone sooner? Ask through the contact route on the page explaining who writes this site, quoting when you visited, to the hour, in local Australian time, along with the IP you were on. A log line carries no identity, so matching is best-effort and a shared mobile IP may cover several readers.

This policy carries a date at the top and another in the footer. Both move when something of substance changes: a new cookie, a new tool, a different retention window. A tidied sentence does not. Give the money side the same clear head: the player support page covers deposit limits and where help lives in Australia.