Privacy on Our Lussurio Guide
Our guide collects as little as an information site can: the messages readers send through the contact form, the reply address attached to them, and the standard analytics that count page visits without naming the visitor. Consent choices sit in the same basket, stored so a repeat visit skips the question.
The guiding rule behind the list is simple: anything a reader shares with the casino itself never passes through our hands, because our pages hold no accounts and take no payments. That line keeps the collection list short and the retention table honest.
What we may collect
- Contact messages: the text a reader writes to our team and the email address used for the reply.
- Analytics: aggregated page-view counts, referral pages and session durations, stripped of direct identifiers.
- Preference data: consent choices on cookies, stored, so a repeat visit does not ask again.
- Nothing else: no logins to the casino, no payment details, no identity documents ever belong in a message to us.
How policy changes reach readers
The dated policy line
When collection practices change, the update lands in the date line at the foot of the policy, so a reader can compare the current date against the last visit.
Notes on material changes
A change that alters what is collected or how long it is kept gets a plain-language note near the top of the policy until the next full revision, so the reader sees the difference without rereading every line.
How long information is kept
| Data type | Retention | Why |
|---|---|---|
| Contact messages | Up to 12 months after resolution | To keep a correction thread auditable |
| Analytics records | Up to 14 months | Standard analytics retention windows |
| Consent choices | Until withdrawn or 12 months idle | To honour a cookie preference |
| Correction threads | Duration of the correction plus 3 months | To verify the fix stayed fixed |
Reader rights over the data
- A reader can ask what their message thread holds and request a copy of it.
- A reader can ask for a correction thread to be deleted once it is resolved, and for analytics entries tied to their visits to be removed where the records allow it.
- A reader can withdraw a cookie consent choice at any time through the consent banner and the browser’s cookie controls.
- Every request runs through the contact form, with no fee and no identity documents required.
How the data is used
Contact messages are used to answer the reader, to verify a correction against the research behind the guide and to keep a short audit trail of what changed and when. Analytics are used to see which guides earn their length and which need pruning, never to profile a single reader. Consent choices are used to honour what a visitor decided about cookies. Nothing collected here is sold, rented or merged with advertising profiles. Last updated: 2026-11-09