Privacy Policy

This privacy policy covers this independent information website. The external gambling platform at betandyou.com has separate data practices and its own privacy notice, which you should read before registering on that platform.

Data this site collects

This guide does not provide a registration form, a payment form or a document upload facility. It does not ask you to enter a password, card number or identity document. No user account exists on this site. The site code does not set first-party tracking or advertising cookies and does not include a third-party analytics script that collects identifiable visitor data.

Server and infrastructure logs

When your browser loads a page, it sends technical data to the hosting infrastructure. This typically includes the IP address of the connection, the request time, the path requested, the HTTP status returned, the response size and the browser's user-agent string. Log retention and data handling are governed by the hosting provider's own policies. This site does not use that data to build individual visitor profiles.

Referral links and the external platform

Access buttons on this site contain referral tracking parameters. When you follow a link, the request is sent to the external platform with those parameters included. The external platform can process the technical data in that request, set its own cookies and apply its own privacy terms. Your use of the external platform is governed by that platform's privacy notice, not this one.

AMP pages

The AMP version of this site loads the AMP JavaScript runtime from Google's delivery network. That request is subject to Google's data handling practices. No additional third-party scripts are loaded on AMP pages beyond the AMP runtime itself.

Email contact

Email links open your own email application. Any message you send goes to the recipient and through your email provider. Do not send passwords, one-time codes, card numbers or identity documents through email or any unverified channel. The published brand contact email is [email protected].

Your rights

Under applicable data protection law you may have rights to access, correct or erase personal data held about you. Because this site does not collect personal data through its own forms or accounts, most of these rights apply to data held by the hosting infrastructure or the external platform. For platform account data, contact the operator directly. For hosting-level inquiries, contact the relevant infrastructure provider.

Changes to this policy

This policy may be updated to reflect changes in site technology or applicable law. Continued use of the site after a revision constitutes acceptance of the updated policy.

Follow the information through each service

A single browsing session can involve this guide, a referral destination, the operator and your email provider. Each service receives information through the interaction it handles. Loading an article is different from creating an account or sending a message. Identify which organisation received the information before asking about it. This guide cannot retrieve account records held by the gambling platform or remove messages from your email provider. Keeping those boundaries clear helps direct a privacy question to the service that can actually respond to it.

Share only what a request needs

An account support request may need a transaction reference or a description of an error, but it should not include unrelated documents or a complete view of your device. Before sending a screenshot, check for visible names, balances, addresses and notification previews. Crop or obscure information that is not required. If the operator requests a document, ask which official upload channel to use and why the item is necessary. Sending the same material to several unverified channels increases exposure without necessarily helping resolve the original issue.

Understand browser controls and their limits

Your browser may let you delete cookies, limit stored history and control site permissions. These settings affect information stored or permitted on your device. They do not automatically erase records already received by a hosting service or an external platform. Private browsing similarly does not make network requests anonymous to every service involved. Review permissions separately for each destination, especially requests to access notifications, location or files. Grant a permission only when you understand what it enables and why it is relevant to the action you chose.

Treat referral parameters as part of the destination request

A referral URL can contain campaign and source identifiers used to attribute a visit. These parameters describe the route by which a visitor reached the destination; their presence should not be confused with an account password. Nevertheless, a complete URL can reveal contextual information about a session or campaign. Avoid sharing full account or recovery URLs publicly. Once the destination loads, its own notice explains any further processing. The information website cannot determine how every external service combines referral information with other records it holds.

Frame a data inquiry precisely

When raising a privacy question, identify the service, the approximate date and the kind of interaction involved. Explain whether you loaded an article, followed a button, sent an email or registered on the platform. Ask what information is held and which process applies to your request. Do not include a password as proof of identity. A service may need to verify that a request concerns your own records, but that verification should use an appropriate official channel. Keep a copy of the request and any response for your reference.

Review privacy when the browsing context changes

The relevant privacy notice can change when you move from reading to registering, paying or installing an application. An app may request device permissions that a simple article never needed. A payment provider may have its own account and transaction records. Read the notices at those points instead of assuming this guide's description covers the entire journey. If a new permission or request seems unrelated to the action, pause and seek an explanation. The decision to continue should be based on the actual service and information being requested.