Privacy policy

What is recorded when you read a page

What is recorded depends on your answer to the site's banner. Before you answer, or if you decline: the site's own server-side code records the address of the page, the page you came from, your country, your browser's language and user-agent string and, if you arrived from an advertising campaign, the campaign identifiers in the address (utm parameters and similar). That record carries neither your IP address, nor your city or region, nor any visitor identifier or ad click identifier (the ad click identifier is kept in a session cookie, described below, so that a later partner click can be attributed to the campaign); the record carries a random identifier generated for that one request and stored nowhere. If you accept: the record additionally carries your IP address, your region and city as derived by the network provider, the ad click identifiers (gclid, msclkid, fbclid and similar) and a random visitor identifier stored in a first-party cookie, which joins your page views to your partner clicks. Nothing is read from your device beyond what a browser sends with every request. The record goes to a measurement backend we run ourselves; it is not sold, not shared with advertising networks, and not joined to data about you from anywhere else.

What is recorded when you open a partner link

Casino links go through monteclar.com/go/. Opening one always records a click identifier, the brand, the kind of page and the button position, your country, your user-agent and — if you arrived from an advertisement — the campaign and ad click identifiers, and forwards you to the operator. The visitor identifier, your IP address and your city and region are added only if you accepted the banner. The operator receives the click identifier together with the brand, edition, country, page-kind and button labels — never your name, e-mail or anything else, because we hold none of it. When the operator reports a registration or a deposit it sends the click identifier, an event type and an amount to our measurement system; that is how a payment to us is matched to a page. If the measurement backend is unreachable, the record is written to a queue at the edge and replayed by later requests; after twenty failed delivery attempts (about two weeks of retries) it stops being retried; it is kept so we can look at it and is deleted automatically thirty days after it was created, or sooner if we clear the queue by hand.

What the Telegram bot keeps (@monteclar_bot)

The bot is optional and separate from the site: nothing about you is recorded unless you open @monteclar_bot in Telegram and press Start. It then keeps one record per chat: the Telegram chat id, the language and site edition it answers in, the country you choose, where you came from — the edition and kind of the page and the button, never the page address — and the times you started, confirmed you are 18 or older, turned alerts on or off, last wrote to it and last received an alert from it. It does not keep your name, @username, phone number, profile photo or the text of your messages, and Telegram gives it no IP address. To hold back floods it also counts how many messages you sent it in the last minute. For each alert prepared for you it also keeps a delivery row: the chat id, which alert it is, when it is due and when it was sent, how many times sending was tried and the last sending error, if any.

It uses the record to answer your commands — the list of partners that accept the country you chose, with the bonus where there is one and the MONTECLAR code where the casino takes it — and, only if you turn alerts on (they are off until you do, and the bot offers them only for the countries Monteclar has opened to alerts), to message you when a new partner or a new code appears for that country, at most once a day. The links it sends go to monteclar.com/go/ and carry the bot's own label, the site edition and the country, never anything that identifies you or your chat: a click from the bot is counted as a click from the bot, not from a person. An alert's links also carry a label of that alert only when it goes to ten chats or more, so a click on an alert is counted per alert, never per person.

Telegram carries the messages and processes them under its own policy; Cloudflare hosts the database. Answering a command you send is why we process the record; alerts rest on your consent, which /alerts withdraws at any time. The Cloudflare count described below also counts the bot's commands — which command, the edition, the kind of page and button, the country — never the chat id. Send /stop and the record is deleted at once — it is the last message the bot sends; blocking the bot deletes it as well.

Writing to the team (/contact): after you send /contact, the bot forwards your next text message, up to 1,000 characters, to the Monteclar team's own chat with the bot, adding your language, the site edition, the country you chose and a short random reference, never your name, @username, phone number or chat id. The team's answer, if there is one, comes back to your chat as a message from the bot. The site does not store the text of either message: both stay in the two Telegram chats, yours and the team's, under Telegram's policy, until they are deleted there. On its way, the text passes through the bot's code on Cloudflare, which writes it nowhere. To route the answer and to limit how many messages the bot forwards from one chat, the database keeps for each forwarded message only its message number in the team's chat, your chat id, the reference and the time, and, while the bot waits for your message, the time you sent /contact. Answering your request is why we process this; /stop or blocking the bot deletes these entries at once, together with your record.

What is stored in your browser

Cookies set by the site. Always: mc_consent, your answer to the banner, one year; mc_attr, the campaign and ad-click identifiers from the address you arrived on (utm parameters, gclid, msclkid, fbclid and similar), if you arrived from an advertisement — until you close the browser while you have not accepted, and for 90 days once you accept. Only if you accept: mc_vid, the random visitor identifier, two years; and, only if you arrived from a Meta advertisement, mc_fbp and mc_fbc, identifiers in the format Meta's advertising uses, 90 days. If you decline or withdraw consent, mc_vid is removed on the next request. Local storage, which never leaves your device: your light-or-dark theme, your reader-language choice and your answer to the banner. Clearing the site's data in your browser removes all of it.

Counters in your browser: two on every visit, two only with your consent

Besides the server-side record, two third-party counters run on every visit, whatever you answer to the banner. Yandex Metrica counts page views, how far each page is read and which links are clicked; it is Yandex's product and sets its own cookies under Yandex's policy. Cloudflare Web Analytics, which our host, Cloudflare, adds to every page, measures how long the page takes to load and counts the view; it sets no cookies.

Google Analytics 4 and Microsoft Clarity load only after you accept the banner, and never if you decline. Google Analytics counts page views and clicks on partner links; Microsoft Clarity records how the page is used — clicks, scrolling and cursor movement — to build heatmaps and session recordings. Each is its company's product and sets its own cookies under that company's policy.

What the hosting records

The site is served through Cloudflare. Like any network provider it processes the technical minimum needed to deliver a page and to protect itself from abuse: IP address, user agent, requested URL and timestamp. That processing is the provider's, in its role as a processor, and is governed by its own policy.

Besides those records, the site's own code keeps a count of the same events in Cloudflare's analytics service (Workers Analytics Engine), so that the figures in our measurement system can be checked against an independent tally. For each page you read it notes the page address, your country and where you came from: one of our own pages, a search engine, an AI assistant or another site, with that site's host name, or a direct visit. For each partner link it notes the brand, the page and the kind of page, the button position, your country, the country you chose on the list of operators if you chose one, how many operators that list offered and where the request came from (one of our own pages, or another site's host name and type). For each registration or deposit an operator reports it notes the operator and the event type. And for each of them it notes whether the record reached our measurement system. The count never holds an IP address, a user-agent string, a visitor identifier or a click identifier. Cloudflare deletes it after three months.

Links to other sites

Guides link to sources — regulators, game providers and testing laboratories — directly. Review and comparison pages link to casinos through the partner links described above. Each of those sites has its own policy, and what happens after you leave this one is governed by it.

How long we keep it

Visit and click records stay in the measurement backend for as long as the operator accounting described in how we are funded needs them; no automatic deletion is in place today. The edge queue for failed deliveries keeps a record until it is delivered, or until twenty attempts have failed; whatever is left in that queue is deleted thirty days after it was created, and we can clear it sooner by hand.

Telegram bot: the record is deleted at once when you send /stop or block the bot; a record with alerts off is deleted 13 months after your last message to the bot. A record with alerts on is kept until you turn them off, send /stop or block the bot; if, when an alert is sent, Telegram answers that the chat is blocked or gone, the record is deleted then. An alert's delivery rows are deleted with your record and, in any case, 30 days after the alert was prepared. Telegram update ids, kept so that Telegram's retries are ignored, are deleted after seven days. A deleted record also leaves the point-in-time recovery copy Cloudflare keeps of the database within 30 days.

Writing to the team: the link between a forwarded message and your chat is deleted 30 days after the message was sent, or at once by /stop or a block; the note that the bot is waiting for your message is deleted when the message goes, when you cancel, and in any case within a day. The text itself is never in the database. Deleted entries also leave the point-in-time recovery copy Cloudflare keeps of the database within 30 days.

Your rights

Data protection law — the GDPR for readers in the EU, PIPEDA and Quebec's Law 25 in Canada, the LGPD in Brazil, Law 21.719 in Chile — grants rights of access, rectification and erasure over personal data a controller holds about you. What we hold is pseudonymous: records keyed by the mc_vid cookie value if you accepted the banner and, for partner clicks, by a click identifier. To exercise a right, send the mc_vid value from your browser's cookies to contact@monteclar.com and we will return or erase every record tied to it. Declining the banner, or not answering, means no visitor identifier is assigned to you, your IP address and city are not recorded, and Google Analytics and Microsoft Clarity are not loaded (Yandex Metrica and Cloudflare Web Analytics run either way, as described above); you can change your mind by clearing the site's data, after which the banner asks again.

Telegram: send /stop and the bot deletes your record at once. To see what it holds, send /help — it shows your chat id — and write to contact@monteclar.com with that id. For readers in Canada: the bot sends commercial electronic messages only after you turn alerts on, each one identifies Monteclar, and /alerts or /stop ends them.

Changes

Any change is published on this page with its date. We do not change this policy retroactively.