How Our Qzino Guide Handles Reader Data

Our site is an independent guide to Qzino, and it collects only the little data a reading site needs: what a reader chooses to send through the contact form and basic usage figures. No gambling account exists here, so payment details and passwords are never requested.

This policy explains each kind of data, the purpose behind it and the choices readers have. Some links on our pages may be commercial (affiliate) links, and opening one can pass the visit to a partner whose own rules then apply.

What we collect

Data	Collected through	Purpose
Name and e-mail address	Contact form	To answer the message
Message text	Contact form	To correct a page or follow up on feedback
Page views, referrer and device type	Analytics	To see which topics are read and where pages fail
Click on an affiliate link	Analytics	To understand which pages lead readers onward

Only the details a reader types into the form are stored as contact data. Account numbers and similar items are unnecessary and best left out of a message.

Cookies and analytics

Cookies on our site are kept few and are described in full on the cookie policy page. In brief:

Essential cookies keep pages displaying correctly.
Analytics cookies show aggregate patterns, not individual identities.
Affiliate cookies record that a visit came from our pages when a partner link is opened.
Browser settings let any reader refuse or delete them at any moment.

Reader rights

Readers can control the data tied to them, and the route is always the contact form on our site:

A copy of the contact data held can be requested.
A correction can be requested when a detail is wrong.
Deletion of a message and the address attached to it can be requested.
Consent to analytics can be withdrawn by clearing cookies in the browser.
A reply to any of these requests comes back through the same form route.

How data is used

Answering messages

Contact details serve one purpose: replying to the person who wrote. They are not added to mailing lists and are not shared for promotion, and a conversation closes once the question has been answered.

Improving the guide

Usage figures help the team see which sections answer real questions and which need more work. Results are read in aggregate form, so no single reader is singled out, and a page that loses readers early is the first to get attention.

Protecting the site

Technical logs help spot abuse such as automated spam. Security measures keep stored messages away from public access, and records are kept only as long as the purpose requires. Changes to this policy appear in this text together with a new date.

Last updated: 27 October 2026