Privacy Policy
About this site
FridayFriday Australia Guide is a static editorial website. It does not create casino accounts, accept bets, hold player balances, process deposits or withdrawals, or ask visitors to submit identity documents. This policy describes the data practices of the editorial site only, not those of FridayFriday Casino or any external destination.
Last reviewed: 9 September 2026.
Information collected directly
The current site has no contact form, account area, newsletter form, comments, analytics script, advertising tracker, affiliate tracker or embedded third-party widget. It therefore does not intentionally ask visitors for names, email addresses, phone numbers, payment details, identity information or gambling-account credentials.
Do not send casino login details, payment information or verification documents to this editorial site. Any account request should be checked inside the genuine operator account or through a support route reached from it.
Hosting and server logs
The hosting provider may process ordinary technical request information needed to deliver and protect the website. Depending on the hosting configuration, this can include an IP address, request time, requested page, response status, browser or device information and security events. Server logs are controlled by the hosting environment rather than by an HTML form on this site.
The publisher should review the hosting provider’s settings, retention period, access controls and security practices before launch. Logs should be retained only as long as needed for delivery, troubleshooting, abuse prevention and security, subject to the publisher’s actual legal obligations.
External links
Some articles link to FridayFriday or official public sources such as ACMA. When a visitor follows an external link, the destination receives the request and applies its own privacy, cookie and security practices. This site does not control how an external website processes information.
Check the destination address before entering personal data. A link from an editorial article should never be treated as a request to send casino credentials or identity documents to the publisher of this guide.
Cookies and browser storage
The current editorial pages do not set cookies or use local storage through site scripts. The separate Cookie Policy explains the current zero-cookie state in more detail. A browser, network service, security product or external destination can still have its own storage and logging behaviour outside this site’s control.
Data sharing and sale
Because the site does not intentionally collect visitor-submitted personal information, it does not maintain a visitor database to sell or share for advertising. Technical request data handled by the hosting provider should be limited to website delivery, security and troubleshooting under the provider’s applicable terms.
Security and reader choices
No website can promise absolute security. Visitors can reduce exposure by keeping their browser updated, checking addresses before following links, avoiding shared devices for casino account activity and not entering sensitive information on an editorial page.
Browser privacy settings can limit cookies and clear stored website data. Network-level privacy tools can affect how request information is exposed, but they may also change site behaviour. Review the tool’s instructions before changing security settings.
Children and intended audience
This site concerns gambling products and is intended for adults. It is not designed to collect information from children. Anyone below the applicable gambling age should not use casino services.
Policy changes
If analytics, advertising, forms, affiliate tracking, consent tools, embeds or other services are added, this policy must be updated before those tools go live. The revised policy should identify what is collected, why it is processed, which providers receive it, how long it is kept and what choices are available.
The review date at the top of this policy should change whenever the site’s actual data practices change. No contact identity is published here because none has been verified; one should be added only when the publisher can provide a real, monitored privacy contact.