Privacy Policy
Last updated: August 2026
monro.info has no sign-up, no member area and no newsletter form. The short version: we do not collect personal data from readers. Everything we do process is listed below in plain language. Data usage on this site amounts to anonymous visit statistics and an affiliate tag on outbound links.
What we record
Only anonymous navigation statistics: which pages were opened, how long they were read, which device and browser were used, and an approximate region derived from an aggregated IP address. Name, personal ID number, email and phone are never requested, never stored and technically cannot be tied to an individual by us.
Google Analytics 4
The only analytics tool on the site. Cookies and anonymous identifiers produce aggregate visit reports rather than individual profiles. They can be blocked in browser settings at any time without affecting how the pages work. If we ever change analytics providers, this cookie policy will be updated before the new tool goes live, not after.
The affiliate tag
Links to the Monro platform carry a source marker and no personal data whatsoever. The moment you register on the platform the operator’s own privacy policy takes over — worth reading before you fill in the first form, because it is the operator, not us, that receives your KYC documents.
Where the data goes
In exactly two directions: aggregate statistics to Google, and a click marker to the operator. Short technical logs live on the hosting side for security, with no individual profiles and automatic deletion on the provider’s cycle. There is no visitor database on our side.
Your rights under GDPR
Access, rectification, erasure, portability and objection to processing are in practice addressed to Google and to the operator, because there is nothing on our side to hold. If a question concerns this site itself, write to the domain contact address: we answer directly, without layered forms. Latvia is an EU member state, so GDPR applies in full and the supervisory authority is the Latvian Data State Inspectorate.
Age protection and retention
Statistics live exactly as long as the GA4 retention window allows and are then deleted automatically. The site is not aimed at anyone under 18 and collects data from nobody — the zero-collection policy applies to every reader without exception.
If the analytics stack changes
Adding or replacing a tool means this page is updated before the tool starts working. Consent requested after the fact is not consent.
Outbound links
The only functional external link on this site points to the Monro platform. There are no social widgets, no advertising pixels and no third-party trackers.
Privacy questions
Send them to the domain contact address. They are handled with the same priority as factual corrections: no forms, no ticket queue, no circular replies.
Revisions
Changes are published here with a date. Substantial revisions are additionally flagged at the top of the page.
Privacy and cookie policy: how your data is handled
A privacy policy explains which personal data a site collects — email address, device information, payment traces — and for what purpose. A cookie policy covers the small files stored in the browser: some hold a session, others measure which pages are read so the material can be improved.
Responsible data usage means collecting only what is necessary and deleting it once it is not. Cookie consent is configured through the banner or your browser settings, and refusing cookies does not close access to the informational pages of monro.info.
Personal data on the operator side: what is collected and how it is protected
Everything typed into the platform cashier — card number, document photograph, home address — travels to Monro over an encrypted channel: SSL encryption turns the contents into a string that is useless to anyone listening on the same public Wi-Fi. Connection encryption is the baseline standard for a licensed site, and the padlock beside the address bar is the fastest way to confirm data protection is active before a single field is filled in. What the operator actually stores is less than most people assume: identity and contact details for verification, transaction history because financial rules require it, and technical records of logins and devices so that access by somebody else becomes visible. The full list sits in the operator’s privacy policy, and reading it once is enough. To the blunt question of whether it is safe to play, an honest answer rests on the same foundations: an encrypted connection, a verifiable licence and tidy account habits.
Data flows in a few predictable directions: to payment providers moving the money, to document-checking services, and — on a formal request — to a regulator or a bank. All of that processing happens on the operator’s side rather than on this site, so a request for erasure or for a copy of your file goes to its support team. From the player’s side, the useful habits are dull and effective: a password used nowhere else, two-factor authentication switched on in account settings, and no logging in from other people’s phones or computers. If a session was left open on a device you no longer hold, changing the password ends it faster than hoping nobody looks. A copy of your data, or its deletion, is a GDPR right rather than a favour, and licensed operators describe the same procedure in their privacy policy even for players outside the European Union. A safe casino protects every connection with SSL encryption and explains data protection in its privacy policy rather than in a banner.