Privacy Policy of casinohugo.biz
This privacy policy explains what information casinohugo.biz processes when you read the site, why, and what rights you have. The short version: the site has no accounts, no forms for personal documents and no payment functions, so the data we see is limited to ordinary technical and analytics information.
What we collect
When you visit, standard technical data is processed: your IP address (which our hosting and analytics tools shorten or process on our behalf), browser and device type, the pages you open, how long you stay and the page that referred you. When you click a partner button, the click itself is recorded as an event — which page and which button — so we can see which guides readers find useful. We do not collect names, addresses, identity documents or payment details, and we never ask for them.
Why we process it
We use this information to keep the site running and secure, to understand which pages are read and which are not, and to measure clicks on partner links, which is how the site is funded. The legal basis is our legitimate interest in operating and improving an information website and, where required, your consent to analytics cookies.
Cookies and analytics
The site may use Google Analytics 4 to produce aggregated statistics about visits and clicks. Analytics cookies are small files stored by your browser; you can refuse or delete them through the cookie settings of your browser, and the site remains fully readable without them. Partner pages you reach through our buttons are separate websites with their own cookie and privacy policies, which we do not control.
Who receives data
Data is processed by the service providers that make the site work: the hosting and content delivery network that serves the pages and the analytics provider. Some of them may process data outside your country; where that happens within the scope of the GDPR, it relies on the safeguards those providers offer for international transfers. We do not sell or rent data to anyone.
How long we keep it
Analytics data is kept only for as long as it is useful for statistics, according to the retention settings of the analytics tool, and is then deleted. Emails you send us are kept for as long as needed to answer and, if relevant, to document a correction.
Your rights
Under the GDPR and similar laws you may ask for access to data concerning you, its correction or deletion, restriction of processing, and you may object to processing based on legitimate interest. You can also lodge a complaint with a data protection authority. Because we hold almost no data that identifies you directly, many requests can be answered quickly; send them to info@casinohugo.biz.
Security
The site is served only over an encrypted HTTPS connection (SSL/TLS). Access to analytics and hosting accounts is limited and protected with two-factor authentication. As the site has no logins, there are no passwords of yours we could lose.
Changes and contact
We update this policy when the site's tools change; the version on this page is the current one. Privacy questions: info@casinohugo.biz. For the general rules of using the site, see the terms of use.
Casino privacy policies and cookies: what to read on the operator's side
Once you register at an online casino, a much larger amount of personal data is involved: identity documents, address, payment details, game history. That data is governed by the operator's own privacy policy and cookie policy, not by ours. Before signing up, look at what the operator says about data usage, which third parties receive personal data (payment processors, identity-check services, the licensing authority) and how long it keeps records after an account is closed.
Responsible operators collect only what the law and the service require and explain how to exercise your rights. If a casino's privacy policy is missing, vague or contradicts itself, that is worth knowing before you upload a passport scan.
Personal data at a casino: is it safe, and what you can do
Whether it is safe to hand over documents depends on both sides. On the operator's side, look for an encrypted connection on the genuine domain, a clear data protection section in the privacy policy and an upload function inside your logged-in account. On your side, use a unique password, switch on 2FA if offered, and never send documents through links received by email or chat, even if they look official.
Data leaves an operator in predictable directions: to the payment provider that moves your money, the service that checks documents, and authorities or banks when they ask formally. Under the GDPR you can ask the operator what it holds about you and request a copy. Keeping your own record of what you uploaded and when makes such requests easier.