Privacy Policy

1. Who we are

This Privacy Policy explains how personal information is handled when you use the Bonnie Blue platform at bonnieblue.bet, sign in, participate in leaderboards and challenges, or submit a VIP transfer request.

2. Collection and storage of information

Sign-in and linked accounts. When you choose to sign in with Google, Kick or Discord, or link another account, we receive an account identifier and, where provided by the service, your display name, email address and profile picture. We store this information to recognise your account and the sign-in methods linked to it. We do not receive the password you use with these providers.

For Google sign-in, we request the openid, profile and email permissions. These provide basic identity information; they do not give us access to your Gmail messages, Google Drive files or contacts.

BetBolt information. We collect the BetBolt nickname you provide during registration. We use it to check your referral eligibility and associate your platform account with relevant BetBolt statistics. We receive information such as leaderboard position, wagered amounts, points and VIP rank, where available. For challenges, we receive the relevant game statistics and the time a qualifying target was reached. Leaderboard and challenge information may also concern BetBolt participants who have not registered an account on our website.

VIP transfer requests. If you submit this form, we process the casino name, bet-slip link, Telegram username and supporting file you provide, together with a request identifier and submission time. Supporting files may contain additional account or betting information that you choose to include. Submit only information needed to review your request.

Technical and security information. Our website and infrastructure providers process connection and request information needed to deliver and protect the service. This can include your IP address, browser or device information, request times, security-verification results and operational logs. We also use cookies and related authentication information to maintain sign-in and protect account access.

Communications. If you contact us, we process the information you include in that correspondence to respond to your request.

3. Cookies and security checks

Cookies keep you signed in, help complete registration and protect the account-linking process. Cloudflare also processes technical signals to distinguish people from automated traffic. Its Turnstile Privacy Addendum describes that processing: https://www.cloudflare.com/turnstile-privacy-policy/.

Your browser lets you manage or remove cookies. Restricting them may prevent sign-in and other account features from working. Signing out, removing a cookie or withdrawing a provider's access does not by itself erase stored account information or competition records.

4. Purposes of processing

We use information to create and maintain accounts, authenticate users, manage linked sign-in methods, check referral eligibility, display leaderboard positions and challenge results, review VIP transfer requests, communicate about submitted requests, and protect the platform against abuse and unauthorised access.

5. Public results and disclosure

Leaderboards, past leaderboard results and challenge results are available publicly. They can include BetBolt nicknames, rankings, relevant game statistics and prize information. Some views mask part of a nickname; this does not make the underlying information anonymous.

Your Google, Kick or Discord email address and provider account identifiers are not displayed as public leaderboard information by our platform. Authorised staff can access account information needed to operate and support the service.

VIP transfer requests are shared with the team responsible for reviewing them through a Telegram group or topic intended for that purpose. Your request and attachment are visible to the people with access to that destination. They are not posted as a public request on our website.

We use external services to operate the platform:

Google, Kick and Discord authenticate you when you choose those sign-in methods. These services also process information under their own privacy policies.

BetBolt receives the nickname and relevant period or game parameters needed for our referral and statistics requests, and supplies the associated results. Our current integration does not send your Google, Kick or Discord profile or email address to BetBolt as part of those requests.

Cloudflare provides network protection and Turnstile security checks. Turnstile processes technical signals, including IP address and browser or connection information, to detect automated traffic. Cloudflare explains its processing in its Turnstile Privacy Addendum: https://www.cloudflare.com/turnstile-privacy-policy/.

Telegram processes VIP request messages and supporting attachments sent to our review team. Telegram's own privacy policy also applies to its operation of that service.

Hosting and infrastructure providers process information needed to store data and run the website on our behalf.

We may disclose information when required by applicable law or where necessary to establish, exercise or defend legal claims, subject to the requirements that apply to us.

These providers may operate in countries other than yours. Their own privacy notices explain their handling of information. Links to casinos, social platforms and other websites also lead to separately operated services.

6. Google API information

Google provides the identifier and basic profile information described above after you choose Google sign-in. We use that information to associate the correct account with your sign-in and make account features available. Linking another provider does not give us access to your Google messages or files.

Google profile information is stored with your account. Authorised staff may access account information when needed to provide support, administer accounts or investigate security issues. Our current referral-statistics and VIP-form integrations do not automatically forward that Google profile to BetBolt or attach it to Telegram requests.

We handle information obtained through Google APIs in accordance with the Google API Services User Data Policy: https://developers.google.com/terms/api-services-user-data-policy. Any additional Google requirements apply where relevant to the permissions used.

You may withdraw the application's access in your Google Account settings. Withdrawing Google authorisation does not by itself delete information already stored by the platform.

7. How long information is kept

We determine retention according to the purpose of the information, whether the account or request remains active, the need to maintain accurate competition records, security and dispute-resolution needs, and applicable legal requirements.

Account information supports continued use of your account. Leaderboard and challenge records support historical results and the review of competition outcomes. VIP requests and their attachments support the review of the request and related follow-up. Operational records and backups support security, troubleshooting and recovery.

Retention also concerns copies held by the review team, including in Telegram, and backup copies. The expiry of a cache entry or sign-in session is not a promise that all associated information has been deleted.

8. Your choices and requests

You can choose which supported service to use for sign-in and manage available linked-account options through your profile. You can also revoke our application's access through the relevant provider's account settings.

Disconnecting a sign-in provider does not automatically remove other account information, public competition records or copies of a previously submitted VIP request.

Depending on the law that applies, you may also have rights to receive a copy of your information, restrict or object to certain processing, withdraw consent where processing relies on it, or complain to a relevant supervisory authority. We will consider requests in accordance with the applicable requirements.

9. Security

We use measures intended to protect information, including HTTPS, access controls, restricted administrative access and separation of internal services. No online service can guarantee absolute security. Access to account and application information is restricted according to operational responsibilities.

10. Policy updates

We may update this policy as the platform or its data practices change. The effective date will identify the version in force. Where required, we will provide additional notice or obtain permission before using information for a new purpose.