Privacy Policy

This policy covers only veergameclub.com — the pages, cookies and any contact form on this guide site. It does not apply to VeerGame's own app, website or customer-service channels. Those products are run by a different organisation, under a different set of rules.

If you have a VeerGame account, that operator holds its own data under its own privacy policy. Look for that policy on the official VeerGame site or in the app. This page does not invent a URL for it, because the operator's document lives on the operator's own properties and can move without notice.

Two kinds of information may be collected here, and only these two. The first is ordinary web analytics: pages viewed, approximate location at country level, device or browser type, and referral source, usually via cookies. That is the same class of data most informational sites collect to see which articles are read.

The second is information you type into the Contact form, if and when that form is connected to a real inbox — for example a name, email address and the text of your message. Until an inbox is listed on the Contact page, those fields do not submit, so there is nothing for this site to store from them.

• Standard analytics — pages viewed, approximate country, device or browser type, and referral source.
• Information you type into the Contact form, only if that form is later connected to an inbox.

We do not ask for VeerGame passwords, OTPs, bank details or wallet addresses, and you should not send them to this site. Anything of that kind belongs only in the operator's own in-app support chat.

Cookies on this site, if enabled, would be used for analytics (understanding which guides are read) and for remembering preferences such as a dismissed banner. They are not used to serve you personalised betting offers, and they cannot be joined to a VeerGame account because this site cannot see those accounts.

This policy does not name a specific analytics vendor. When a vendor is chosen, this section will be updated with its name, what it stores, and how to opt out. Until that update, treat any cookie banner or vendor list you might see as unconfirmed rather than as a finished inventory.

Analytics, if collected, are used to improve the site — which guides need a clearer explanation, which searches fail, which pages are outdated. That is an editorial use, not a marketing use against a gambling account.

Contact-form messages, once an inbox exists, would be used only to respond to the inquiry you sent: a correction, a content suggestion, a business question, or a question about the Telegram channel.

We do not use this site to serve you personalised betting offers, and we do not combine anything collected here with a VeerGame account, because we cannot see those accounts.

This site may load analytics from a third-party provider once one is confirmed, and it links out to the official VeerGame site and app. Those destinations have their own privacy practices. Following a link does not bring their data back under this policy.

Following a link to VeerGame means you are leaving veergameclub.com. What that platform collects after you arrive is governed by the operator, not by this policy. The same is true of any other third-party site you open from a page here.

Analytics records, if kept, should be retained only as long as they are useful for improving the site, then deleted or aggregated. Contact messages should be kept only as long as needed to answer them and to have a record of the conversation.

We take ordinary care with whatever this site does store — HTTPS in transit, restricted access to any inbox, no VeerGame credentials on our servers because we never collect them. This is a general statement, not a security audit, and it is not a promise that no incident can occur.

Depending on where you live, you may have the right to ask what data this site holds about you, to correct it, or to ask for it to be deleted. Those rights apply to data this guide site actually has — analytics identifiers and contact-form messages — not to a VeerGame account we cannot see.

To make that request, use the Contact page. This policy does not invent an email address; if the form on that page does not send, there is no public inbox listed yet. Account, deposit or withdrawal requests still have to go to the operator.

If this policy changes, the updated text will replace this page. Material changes — a new analytics vendor, a live contact inbox, a new use of data — should be reflected here before they go into effect, not after.

The last-updated date on this page is the date to trust for the wording currently published. Older copies of this policy, if you saved them, are historical only.