Privacy: Reader Data on Our Aqua Spins Guide
Our guide collects as little as a functioning website allows, and what it collects serves the reader rather than the other way around. The pages work without an account, without a login and without any player data, because we are an information site and run no player accounts of our own.
This policy explains the categories of information our site can hold, the purposes behind each, and the rights a reader keeps over all of it. It covers our own operations only; the casino’s handling of its players’ data is a matter between players and the operator under its own privacy notice.
How We Use the Information We Hold
Contact messages are used to answer the reader and, where the message reports an error, to correct the page. Analytics data is used in aggregate to see which guides are read and which need work, never to profile a single reader. Commercial links, where present, may earn us a commission if a reader chooses to use them, and that flow carries no reader data from us beyond an ordinary click. Security logs exist to keep the site available and are not used for anything else.
Categories of Information in Our Care
What a reader sends us
A message through our form brings what the reader puts in it: usually an email address, the page the message concerns and the text itself. We use it for the reply and keep nothing beyond what the exchange needs.
What the site measures
Analytics counts page views, referral sources and reading duration in aggregated form. The data carries no names and no player information, because none ever passes through our site.
How Changes to This Policy Are Announced
Material changes to this policy are published on the page itself with a new date line, so the current text always sits where the old one did. Where a change touches how existing data is used, we treat that as material by default and date it clearly rather than quiet-editing the wording.
Minor edits and wording fixes
Wording fixes and clarified sentences can land without a separate announcement; the date line still moves so readers can see how current the text is.
Reader questions about a change
A reader unsure how a change affects their earlier messages can raise it through the contact form and get a direct answer about their own data.
Cookies and Analytics in Brief
- Essential cookies keep the site readable and the form working; no consent is needed for them.
- Analytics cookies measure aggregate traffic so we know which guides to maintain.
- Affiliate or commercial links can set their own third-party cookies under their operators’ policies.
- The cookie policy page lists the types in detail and how a reader manages them.
- Blocking analytics cookies in the browser costs nothing in site function.
Reader Rights Over Their Data
A reader can ask what their messages and addresses hold in our care, ask for a correction, or ask for deletion of an exchange once it has served its purpose. Each request runs through the contact form, and we answer about the requester’s own data only. Retention follows purpose: an answered exchange is deleted when it no longer has a use, and analytics aggregates carry no personal data to delete.
Security around what we hold
Access to message archives is limited to the editorial work, transmissions run encrypted, and no reader data is sold or shared for advertising.
The line between us and the casino
Player account data lives in the operator’s systems under its own privacy notice, and requests about it go to the casino’s support, where the account and its data actually sit.
Last updated: 11 November 2026