Privacy Policy
Effective date: 16 October 2026
Last updated: 16 October 2026
GamblingMaps is a regulatory-intelligence service about gambling law. The public site at gamblingmaps.org needs no account. An account (free during the BETA) adds a dashboard, regulation alerts, report PDFs and an API preview. This page says what we collect, why, on what legal basis, who else sees it and how long we keep it. We keep collection to what the service needs.
1.Who is responsible
GamblingMaps ("we", "us") is operated by BENREY OÜ (registry code 16790263), Ahtri 6a, Tallinn 10151, Estonia. BENREY OÜ is the data controller for personal data collected through gamblingmaps.org and the GamblingMaps accounts. For anything in this policy, including your rights, write to [email protected], or use the contact form on the About / Contact page.
2.What we do not do
We do not:
- Set any analytics cookie unless you opt in (see Cookies below): visit counting with Google Analytics starts only after you choose "Accept analytics"
- Set advertising cookies or pixels (Meta Pixel, Google Ads, TikTok pixel, etc.)
- Track you for advertising or build advertising profiles: Google Signals and ad personalisation are switched off
- Sell or rent personal data
- Use fingerprinting, device tracking, or session replay
- Send your personal data to an AI model (see AI summaries below)
Data goes to the service providers listed in section 6, only for the purposes below.
3.If you only read the site
Server-side request logs
Like every web server, ours records basic request information for each visit: the URL requested, the requesting IP address, the user agent string (browser type), and the timestamp. We use the logs for debugging and abuse detection, not for analytics, advertising, or profiling. Legal basis: our legitimate interest in running and securing the site (GDPR Art. 6(1)(f)). The server's system log, which holds these records, is rotated by size and not by age, so entries can currently stay for up to about 11 weeks; we are changing this to a fixed 30 days.
Google Search Console
We verify the Site with Google Search Console so we can see aggregate, anonymised search performance data (impressions, click volume, ranking queries) provided by Google. This data is aggregated, not tied to individuals, and is held by Google under its own terms. Search Console itself places no tracking script on the Site.
Cookieless visit counting (Cloudflare Web Analytics)
Since 11 November 2026 we also count page visits with Cloudflare Web Analytics. It sets no cookies, stores nothing on your device, does not fingerprint and does not follow you across sites: it records that a page loaded, how fast, and the visitor's country and browser type, as aggregate counts. Cloudflare already handles every request to the Site (section 7). Legal basis: our legitimate interest in knowing how many people use the Site (GDPR Art. 6(1)(f)); you can object (section 11).
Visit statistics (Google Analytics, only with your consent)
If you click "Accept analytics" on the consent banner, we use Google Analytics 4 to count visits: which pages are viewed, roughly where visitors come from, and which browser and device type they use. If you click "Reject" or ignore the banner, analytics cookies are not set and the Site works exactly the same. Google acts as our processor for this data (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland); the legal basis is your consent (GDPR Art. 6(1)(a)), which you can withdraw at any time. Google may process this data outside the EEA (section 7).
Contact form submissions
If you submit the contact form on the About / Contact page, the name, email, topic, and message you provide are saved to a database on our server so we can respond. A hash of the requesting IP address and user agent is stored alongside the message for abuse prevention; the raw values are not retained. A hash is not anonymous: someone with the right means could test guesses against it, so we treat it as personal data. We use this information to handle your enquiry (legitimate interest, Art. 6(1)(f), or taking steps at your request, Art. 6(1)(b)). We keep a contact message for at most 12 months from the enquiry, unless the law requires us to keep it longer, and then delete or anonymise it. If you are signed in, the message also opens a support ticket on your account (see Support below). We do not add submitted email addresses to a mailing list unless you tick the "email me when a new map launches" checkbox.
Newsletter signups (optional)
If you tick the newsletter checkbox on the contact form, the email address you submitted is saved to a separate newsletter table along with the date of signup, a randomly generated unsubscribe token, and the same hashed IP. We only use this list to announce new map releases. Every announcement will include a one-click unsubscribe link that calls our /api/newsletter/unsubscribe endpoint with your token and removes your row from the database. You can also write to us to request removal at any time. Legal basis: your consent (Art. 6(1)(a)).
4.If you have an account
Accounts are for people aged 18 or over who use the service for work or another professional purpose. We do not knowingly open accounts for anyone under 18; if we learn of one, we delete it. An account is optional. Everything in this section applies only if you open one.
The account itself
What: your email address; a hash of your password, if you set one (we never see or keep the password itself; an account opened through Google may have none); your name, company and role (player, operator, supplier, adviser, press or other) if you give them; your plan; the markets you follow; when you accepted these terms and this policy; whether you want product news, and when you said so; when your address was confirmed; your access level (see below); and, for each device you are signed in on, a session id and its expiry. Failed sign-in attempts are counted so the account can lock for 15 minutes after five wrong passwords.
Confirmation and reset links and codes: we email a link and a six-digit code to confirm an address. The link works for 7 days, a password-reset link for one hour and once, and a link to confirm a new email address for 24 hours. The six-digit code is calculated from the link rather than stored, and five wrong tries void it. The link tokens are kept until they are used or replaced.
Sign-in code by email: you can also ask us to email you a six-digit sign-in code instead of using your password. We store only a one-way hash of the code, for 10 minutes, and delete it once it is used; we count wrong tries so a code stops working after five. The code is sent through the same email provider as our other account emails.
Password check: when you choose a password we check it against known breaches through HaveIBeenPwned's range service. Only the first five characters of a hash of it leave our server, never the password.
Why and on what basis: to open and run the account, sign you in and keep it secure: performance of the contract with you (Art. 6(1)(b)), and our legitimate interest in preventing abuse and break-ins (Art. 6(1)(f)). Service emails (confirmation, password reset, security notices, team invitations, replies to your messages, alert and report delivery) are part of the service, not marketing.
Kept: until you delete the account (see "Deleting your account"). An account whose address is never confirmed is deleted after 7 days.
Signing in with Google
You can sign in with your Google account instead of a password. Google is then a sign-in provider for us: when you choose "Continue with Google", Google asks you to confirm, and then tells us your name, your email address, that Google has verified that address, and the id Google uses for your Google account. We do not receive your Google password, your contacts or anything else from your Google account.
We store the Google account id, the email address Google gave us when you connected it, and when you connected and last used it, next to your GamblingMaps account, so that the same Google account signs you in next time. If you open your account through Google, we also store your name from Google (you can change it in your settings), and we treat your address as confirmed because Google has verified it.
Google learns that you signed in to GamblingMaps, and when, as it does for any site you sign in to with Google. Google's own privacy policy covers what Google does with that.
You can disconnect Google in your security settings at any time once you have another way to sign in (a password or a passkey); we then delete the stored Google account id and address. Deleting your account deletes them too. Basis: contract (Art. 6(1)(b)), as for the rest of the account.
Access level and requests for more
During the BETA a new account starts on a waiting list and we grant access by hand. We record the level we gave you, who granted it and when, any limit we raised for you, and each change. If you use "Request more" (more report PDFs, alerts for more markets, API access), we store what you asked for, why, your name, company and a masked form of your address, and our decision. Basis: contract (running the account and the BETA limits) and legitimate interest (managing a limited BETA). Deleted with the account.
Sign-in security and history
If you turn on two-factor authentication we store an encrypted secret for your authenticator app and ten recovery codes as hashes. If you add a passkey we store its public key, a counter, its name, device type and when you last used it; the private key and any biometric stay on your device. We keep a list of your recent sign-ins (up to the newest 20): the time, the browser and system in words (for example "Chrome on macOS"), the country Cloudflare derives from your IP address, how you signed in (password, code, recovery code, passkey, reset link, Google, a code by email) and the session id. We do not keep the IP address or the user agent in that list. We email you when two-factor authentication is turned on or off, when a passkey is added and when your email changes. Basis: contract and legitimate interest (security, Art. 6(1)(f)). Deleted with the account; older entries beyond the newest 20 are deleted as new ones arrive.
Teams
Every account belongs to a team, even a team of one. A team has a name, a plan, optional billing details (legal name, VAT or tax number, address, billing email, purchase-order reference) and optional team markets. Owners and admins can invite people by email; we store the invited address, the role offered, who invited, a hash of the invitation token, its expiry and whether it was accepted or cancelled. Invitations work for 7 days. Team members see the team's report requests, and owners and admins see the team's activity log: who invited, removed or changed the role of whom, and when, with names and masked addresses. If you join a team, its owners and admins can see your name, masked address, role and whether two-factor authentication is on. Basis: contract, and legitimate interest in the team's own accountability. When a team is deleted, its markets, billing details, invitations and log are deleted. If you delete your own account, the log lines that name you stay in the team's log with your name and masked address as long as the team exists, but for no longer than 12 months after you delete your account; after that your name and masked address are removed from them.
Regulation alerts
If you set up alerts we store the channel and where to send them: your email address; or the Telegram chat id of the chat you connect; or the Slack incoming-webhook address, channel and workspace name that Slack gives us when you add our app. We also store the markets you picked, how often you want messages, your plan, the dates you signed up and confirmed, a random token for your manage and unsubscribe link, a hash of your IP address, and for each message which updates it carried, when it was sent and whether delivery worked. A Slack or Telegram address works like a password for that channel, so we do not log it and show it only in masked form (such as ro***@b***.io). Telegram and Slack handle the messages under their own terms. We connect to them only if you choose to.
Basis: contract (alerts are a feature of your account). Alerts you set up before there were accounts, by email only, rest on your consent (Art. 6(1)(a)). Every message has a link to change or stop your alerts; in Telegram, /stop works too. When you stop, we erase the address and keep a masked form and the delivery log for 90 days. A sign-up that is never confirmed is deleted after 7 days.
Our alert emails contain no tracking links or pixels that identify you.
Report PDFs, and the watermark
When you request a jurisdiction's research report, we store the request: your account, name, role, company if you gave one, the market, the time, whether it was sent, and the number and time of your downloads (not your IP address). We also keep a hash of your IP address and user agent, as for the contact form.
Each PDF is watermarked to you. We make a copy for your account: your email address and the date are printed in the footer, and a copy id is hidden in the file in several ways. We keep that copy and a record, outside the website's database, of which copy went to which address, with the edition and the time. We do this so that a copy passed on in breach of our terms can be traced back to its source. The legal basis is our legitimate interest in protecting our research (Art. 6(1)(f)); the watermark and the record are used for nothing else. The report is a personal copy: see the Terms.
Deleting your account deletes your requests from our database. The stamped copies and the record of who received which copy are handled differently: the stamped copies are deleted when the account is deleted, and we keep the record of who received which copy for 3 years, so that a leak can still be traced, and then delete it. Write to us if you want to object (section 11).
API keys
If you make an API key (an unfinished preview), we store its name, its first characters, a hash of the whole key (never the key itself), what it may read, when it was made, when it expires, when it was last used, a hash of the last caller's IP address, and a count of requests per day. We email you when a key is made, revoked or about to expire. Basis: contract and legitimate interest (security and fair use). Revoked and expired keys stay in your list. Everything is deleted with the account.
Your dashboard
To show you what is new since you last looked, we store when you last visited the dashboard. We also store which markets you follow, your per-market press-news switches, and whether you dismissed the "Get started" checklist. Basis: contract. Deleted with the account.
Complaints about a casino
What we do, and what we do not: we only connect people. We show you the official route for a complaint: the casino first, then the regulator or a free dispute-resolution body, and a law firm only if you choose to be put in touch with one. This is information, not legal advice; we do not represent you and we do not handle your case. Once you accept a law firm, you deal with that firm directly, not with us.
What we store: what you enter for a case (the casino's name and website, your country, the amount in dispute, the category, the reason the casino gave in your words, where you are now and whether you escalated), the licence you confirmed, the dates you record, the replies we write to you, and who on our team opened the case and when. We never ask for an ID, a passport, a bank statement or a source-of-funds document, and text that looks like an ID, card or bank number is refused. If you choose to let vetted law firms see your case, they see only the market, the category, an amount band and the stage; when a firm offers to help we show you its name, country, website and bar or registration number, and a firm sees your case and your contact details only if you accept it.
Why and on what basis: your own request (contract, Art. 6(1)(b)); sharing with a firm only with your explicit consent for that firm (Art. 6(1)(a)). No marketing use, and nothing from a case is used to train AI.
Kept: a case's content is deleted 6 months after the case closes, or after 6 months with no activity (we remind you in your Inbox a month before), or at any time you delete the case. If you agreed to be put in touch with a law firm, we keep only a record of that referral (which firm, and when you consented), with no complaint text, for 3 years, so we can show who you agreed to be introduced to. Deleting your account deletes your cases at once; the referral record stays until its 3 years end and is then deleted. You can download your own case at any time.
Your role and set-up answers
We store the role you picked (player, operator, supplier, affiliate, law firm or other), when you picked it, a Player's home country, any request for business access, and your answers to the set-up questions (for example the markets you are licensed in, what you supply, your advertising channels, the brands you promote). We use them to arrange your dashboard. If you are a law firm and ask to be listed for marketplace requests, we keep your firm's name, country, website, bar or registration number and our vetting notes. Basis: contract. Deleted with the account.
Market news feedback and interest
If you mark a Market news item "Not relevant to me", we store that, with your role, the market, the checklist question it was tied to and the reason we showed, to hide the item for you and to review how we route news. Deleted with the account. If you press "I'd use this", we record only your role, the market and the time, not who you are.
Support
If you message us from the Help panel, or send the contact form while signed in, we store the conversation: your account id, address, name, plan, team, the subject, the market and the page you wrote from, your messages and our replies. We reply by email. Each new message also sends a short notice to our private team chat on Telegram: your masked address, plan, subject and the first 300 characters. Basis: contract and our legitimate interest in answering you (Art. 6(1)(b), (f)). Kept until 24 months after the conversation is closed, or until you delete the account if that comes first.
Private messages
When both sides of a help request or an affiliate introduction have accepted, a private thread opens between the two accounts; there is no other way to message another member. We store the thread: the two account ids, what it came from (the request or introduction), your messages and when they were sent, whether either of you closed it, blocked the other or reported it, and when we last emailed you about it. Only the two of you can read it. Our team reads a thread only if one of you reports it, and then only that thread. A new message reaches the other side's inbox, and at most one email per thread an hour with no message text (you can turn these emails off in Settings). Basis: contract and our legitimate interest in a safe service (Art. 6(1)(b), (f)). Kept until 24 months after the thread is closed or its last message. If you delete your account, your messages are erased (they read "Message deleted", from "Deleted account") and the thread closes; the other side keeps their own messages.
AI summaries
Some updates have a short "Analyze" summary. When there is no write-up of our own, we make one by sending the update's title, the jurisdiction and up to the first 14,000 characters of the official document's text to an AI model through OpenRouter (currently a model from Anthropic). That is all that is sent: no account data, no address, no Telegram chat id, nothing you wrote. Pressing "Analyze" in Telegram can start this for an update that has no summary yet; the result is stored once per update and shown to everyone, not tied to you. The summary says it is a summary of the official text and not legal advice. Because the input is a public document and not data about you, this does not process your personal data.
Comments, votes and your public profile
What we collect: when you use the discussions in your dashboard we store: the text of each comment and reply you post, when you posted, edited or deleted it, the update it belongs to, whether you posted it under your name or anonymously, the name, company or role label shown with it, and the account that posted it (always, also for anonymous comments); your votes; reports you make (the reason and any note) and reports about your comments; your username; the mentions of you; the random handle each of your anonymous comments carries in its discussion; and your notification choices. If you add them, we store your profile photo, job title, About text, LinkedIn link and whether to show the markets you follow. When you upload a photo we convert it to a small square image and remove the information cameras and phones store in the file, including its location, before we keep it. We also keep counts of your activity (comments, votes received, replies and mentions received, active days).
Why and on what basis: to provide the discussions you choose to take part in and to show your profile to other members (performance of our contract with you, Art. 6(1)(b)); to send you notifications about replies and mentions, which you can switch off in Settings (performance of our contract, and our legitimate interest in keeping members informed); to moderate, prevent abuse and enforce our Terms, including by knowing who posted an anonymous comment (our legitimate interest in a safe and lawful service, Art. 6(1)(f)); to rank Top contributors and keep activity counts for community features and possible future rewards (our legitimate interest); and to comply with the law (Art. 6(1)(c)).
Who can see it: other members who have access to the dashboard can see the comments you post under your name together with your name and company as shown, your username, your photo, and, if they open your profile, your job title, About text, LinkedIn link, the number and score of your comments posted under your name, the month you joined, and the markets you follow only if you switched that on (it is off by default, because the markets you follow can reveal which markets your company is interested in). For a comment you post anonymously, other members see only "Anonymous member", any role label you chose and a random handle for that one discussion (different in every discussion, so your anonymous comments in different discussions cannot be linked to each other or to you); they do not see your name, company, email address, photo or username, and we do not show anonymous comments in your profile, its counts or any ranking. Our team can see who posted every comment, including anonymous ones, and your activity counts. Members who are not signed in, and accounts that do not yet have access, cannot see comments, profiles or photos. We may disclose who posted a comment where the law requires us to, or to establish, exercise or defend legal claims.
Kept: we keep your comments, votes and profile while your account exists, unless you delete them or we remove them. A comment you delete is removed; if others have replied to it, we keep an empty "[deleted]" entry without its text or your identity. When we hide a comment we keep it, with the reason, so that you can see it and we can restore it. Reports are kept with the comment they concern. A replaced or removed photo is deleted at once. Activity counts are calculated from the stored comments and votes and disappear with them.
Your choices: your profile is optional. You can add, change or remove your photo, job title, About text, LinkedIn link and username, and switch showing your markets on or off, at any time in Settings, Profile. You can switch off notifications about replies and the emails about mentions in the same place.
Product news (optional)
We send occasional product news only if you tick the box, which is separate from accepting the terms and is off until you choose. You can untick it in your settings at any time. Basis: your consent (Art. 6(1)(a)). We record when you gave it.
Deleting your account
You can delete your account yourself in Settings, Security, with your password. It deletes the account record, your sign-in history, passkeys, connected Google sign-in, alert subscriptions and their delivery log, report requests, API keys and usage, dashboard and checklist records, support conversations, and your access log and requests for more. It also deletes your profile and photo, your votes, your reports and the text and identity of your comments (a comment others replied to stays as "[deleted]" without your name or text). If you are the last owner of a team with other people, you must hand it over first; a team of one is deleted with you. What stays: a count of deleted accounts with the month and role and nothing that identifies you; the PDF record and stamped copies described above; your lines in a team log (above); and backups, which are overwritten within 30 days.
5.Legal bases
- Contract (GDPR Art. 6(1)(b)): running your account, sign-in, teams, alerts you set up, report delivery, support, service emails, the discussions and your member profile.
- Legitimate interests (Art. 6(1)(f)). Our interests are: keeping the site and accounts secure and preventing abuse (request logs, hashed IP addresses, the sign-in history, rate limits); protecting our research from being passed on in breach of the Terms (the PDF watermark and record); answering your enquiries; managing a limited BETA (access levels and limits); and moderating the discussions, enforcing the Terms (including knowing who posted an anonymous comment) and ranking Top contributors. We weigh these against your rights, and you can object (section 11).
- Consent (Art. 6(1)(a)): Google Analytics, product news, the newsletter, and email-only alerts made before accounts. You can withdraw it at any time, which does not affect what was done before.
- Legal obligation (Art. 6(1)(c)): records we must keep by law, such as accounting records if paid plans start, and answers to lawful requests from authorities.
You do not have to give us any of this, but without an email address and password we cannot open an account.
6.Who has access to your data
Only authorised GamblingMaps staff who need it to run the service can see your personal data. We use these providers as processors, under data processing agreements, and give each only what it needs:
- Hetzner (Germany): hosts the site and its databases.
- Cloudflare: sits in front of the site as a CDN and firewall (it sees requests, including IP addresses, and tells us the visitor's country), counts page visits without cookies (Web Analytics), and stores off-server backups of our databases in its R2 storage.
- Proton (Switzerland): sends our email (confirmations, alerts, reports, replies).
- Telegram and Slack: only if you connect them for alerts. They receive the alert messages and are controllers of their own accounts under their own terms. Telegram also receives our internal support notices described above.
- OpenRouter and the AI model provider behind it: only the public document text described under AI summaries, never personal data.
- Google (Analytics and Search Console), as described above.
- Google (Google Ireland Limited / Google LLC) as a sign-in provider: only if you choose "Continue with Google". It confirms who you are to us and learns that you signed in to GamblingMaps, under its own privacy policy (see "Signing in with Google" above).
- HaveIBeenPwned: the five-character hash prefix described above.
We disclose personal data to others only where the law requires it, for example to a court or authority, or to a buyer of the business if it is ever sold, under the same rules as this policy. We do not sell personal data.
7.International data transfers
Our servers are in the EEA (Germany). Some of our providers (Google, Cloudflare, Slack, Telegram, OpenRouter) may process data outside the European Economic Area, including in the United States. Where they do, the transfer rests on an adequacy decision of the European Commission or on Standard Contractual Clauses. Proton is in Switzerland, which the EU treats as adequate. You can ask us for a copy of the safeguards (section 11).
8.Data security
The site is served over HTTPS only. Passwords and API keys are stored as hashes, never in readable form. Two-factor authentication secrets are encrypted, recovery codes are hashed, and passkeys keep their private key on your device. Sign-in is rate-limited and an account locks after repeated wrong passwords. Our databases are readable only by the server's service account, and customer accounts cannot reach the administration area. Backups are kept off the server with Cloudflare R2, which encrypts stored data. No system is perfectly secure; if a breach affects your personal data we will tell you and the authority as the law requires.
9.Cookies and local storage
The Site sets these strictly necessary cookies without asking, because it cannot work without them:
NEXT_LOCALE: remembers the language version you are reading. 1 year.gm-account-token: keeps you signed in to your account. Only if you sign in. Up to 7 days, removed when you sign out, sent only over HTTPS, unreadable by scripts, not sent from other sites.payload-token: the same, for the Site's own editors signing in to its administration area. An account signed in before 16 October 2026 may still hold it until its next page view, which moves the session togm-account-tokenand removes it.gm-signup: lets the browser that opened an account be signed in when you confirm the address, instead of signing in again. Only at sign-up. 30 minutes, used once, sent only to our account endpoints, unreadable by scripts.gm-oauth,gm-oauth-newandgm-mfa: carry a "Continue with Google" or sign-in-code sign-in from one step to the next (protection against forgery, the new account's pending details, the two-factor step). Only while you sign in that way. 10, 15 and 5 minutes, sealed, sent only over HTTPS, unreadable by scripts.gm_alerts_slack_state: protects the "Add to Slack" connection against forgery. Only if you connect Slack. 1 hour.
The only other cookies we set are Google Analytics cookies, and only after you opt in with "Accept analytics" on the consent banner:
_gaand_ga_<id>: used to distinguish visitors and sessions for visit counting. They expire after up to 2 years.
Only the analytics storage signal is ever granted. Advertising storage, advertising user data and ad personalisation are permanently denied, Google Signals is off, and we set no advertising cookies.
Local and session storage in your browser, never sent to us: your consent choice (gm-consent); the theme and layout you picked (theme, rd-theme, rd-accent, rd-layout); in the account area, whether the side rail is collapsed, which sections are folded and which market columns show (dx-rail:<id>, dx-fold:<id>, dx-markets-cols:<id>); and, for the duration of the visit, a counter that stops the Reports page refreshing itself endlessly (gm-reports-refresh) and one that stops an error page reloading in a loop (gm-error-reload-at). These are convenience settings for your browser and need no consent. Clearing your browser's site data removes them.
Withdrawing consent. Use the "Cookie settings" link in the footer of any page to bring the banner back and change your choice. Choosing "Reject" stops further measurement and removes the Google Analytics cookies this Site can reach.
Some hosting and infrastructure providers (for example CDN edge networks) may set strictly necessary cookies to operate the underlying service; we do not place or read any cookies for marketing.
10.Third-party content
The Site links to external regulator websites, legislation portals, and operator pages. When you click an external link, the destination site will be subject to its own privacy policy and cookie practices, over which we have no control.
11.Your rights
Under the GDPR, and similar laws where you live, you have the right to:
- access the personal data we hold about you and get a copy;
- have inaccurate data corrected (rectification);
- have your data deleted (erasure);
- restrict how we use it;
- receive the data you provided in a machine-readable form, or have it sent to another service (portability);
- object to uses based on our legitimate interests;
- withdraw consent at any time, where we rely on it.
How: much of this you can do yourself. Change your details and product-news choice in Settings, and delete the account there. For anything else, write to [email protected]. We may need to confirm it is you, usually by replying from the account's address. We respond within one month under the GDPR, subject to permitted extensions. Other laws, such as the California Consumer Privacy Act, give similar rights; write to us the same way.
You can complain to the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, https://www.aki.ee/) or to the supervisory authority where you live or work.
12.Changes to this policy
We may update this Privacy Policy from time to time. The "Last updated" date at the top of the page reflects the most recent revision. If a change matters to account holders, we email them before it takes effect. Other material changes will be flagged in the page header for at least 30 days after the change is published.
13.Contact
BENREY OÜ (registry code 16790263)
Ahtri 6a, Tallinn 10151, Estonia
[email protected]
https://gamblingmaps.org
You can also use the contact form on the About / Contact page.