Cookie Policy
Version: 1.1. Effective Date: 26 September 2026
1. Introduction
This Cookie Policy explains how BettingView Ltd., a company incorporated in the Republic of Cyprus ("BettingView", "we", "us", or "our"), uses cookies and similar technologies when you access or use the BettingView website and related consumer-facing services (the "Platform").
This Cookie Policy should be read together with our Privacy Policy, which provides further information about how BettingView collects, uses, shares, stores and otherwise processes personal data.
For the purposes of this Cookie Policy, references to "cookies and similar technologies" include cookies, local storage, session storage, scripts, beacons, browser and device identifiers, analytics and measurement technologies, and other technologies that store or access information on your device or enable us to recognise, measure or understand interactions with the Platform.
BettingView uses Cookiebot by Usercentrics as its consent management platform ("CMP") to manage cookie preferences and, where required, obtain consent for the use of non-essential cookies and similar technologies.
This Cookie Policy applies to the consumer-facing BettingView Platform. BettingView PartnerHub may be subject to separate or additional cookie and tracking disclosures.
2. What Are Cookies and Similar Technologies?
Cookies are small text files that websites may place or access on your device when you visit or interact with them. They can perform various functions, such as maintaining authenticated sessions, remembering preferences, supporting security and measuring interactions with website features.
BettingView also uses technologies that perform similar or related functions without necessarily placing traditional cookies on your device. These include:
local storage, which allows information to be stored in your browser across browsing sessions;
session storage, which generally stores information for the duration of a browser tab or session;
scripts and software components used to provide authentication, support, payments and other Platform functionality;
beacons and measurement technologies used to measure interactions with listings, odds, referrals and other Platform features;
browser and device information used for security, fraud-prevention and anti-abuse purposes; and
other technical mechanisms used to operate, secure and improve the Platform.
The Platform currently uses browser storage for purposes including authentication, age acknowledgement, referral attribution, language settings, Platform preferences and certain user-interface functionality.
3. How We Use Cookies and Similar Technologies
BettingView may use cookies and similar technologies to:
operate and provide the Platform;
authenticate users and maintain user sessions;
maintain security and prevent fraud, abuse and unauthorised activity;
remember user settings and preferences;
record and manage cookie consent choices;
support age and jurisdiction-related functionality;
provide customer support functionality;
support payment and subscription functionality;
attribute referrals and measure qualifying referral activity;
measure interactions with bookmaker listings, odds and other Platform features;
understand how the Platform is used and improve its functionality and performance;
provide maps and location-related features where requested by the user; and
comply with applicable legal and regulatory requirements.
The particular technologies used and whether your consent is required before they are activated depend on their purpose and applicable law.
4. Categories of Cookies and Similar Technologies
Our CMP uses the categories Necessary, Preferences, Statistics and Marketing.
4.1 Necessary Technologies
Necessary technologies support the operation, security and essential functionality of the Platform. They may be required to provide a service or functionality requested by you and generally cannot be disabled through our cookie consent tool.
They may be used to maintain authenticated sessions, store your cookie choices, provide security and fraud-prevention functionality, support age or compliance controls, facilitate payment functionality requested by you and maintain other essential Platform functionality.
4.2 Preferences / Functional Technologies
Preferences or functional technologies enable enhanced or optional Platform functionality and help remember choices you make.
They may support customer support functionality, language or interface preferences, referral-related functionality, application preferences and other optional Platform features.
Where these technologies are not strictly necessary, they are used subject to your preferences and, where required, your consent.
4.3 Statistics / Analytics Technologies
Statistics and analytics technologies help us understand how the Platform and its features are used and measure interactions with content and services.
These technologies may measure interactions with bookmaker listings and placements, odds impressions, referral activity, clicks, qualifying sessions or actions and other Platform interactions.
The Platform uses first-party analytics and measurement functionality. In addition, certain events are transmitted from BettingView's servers to Google Analytics 4 through the Measurement Protocol, and — only where you have consented to Statistics — the Platform loads Google Analytics 4 in your browser (the gtag library) and Microsoft Clarity. Google Analytics measures pages viewed, features used, searches performed and subscription purchases. Microsoft Clarity additionally provides aggregated heatmaps and session replay, meaning a reconstruction of interactions such as clicks, scrolling and mouse movement; all text is masked before a recording is created.
Where you do not consent to Statistics, neither the Google Analytics browser tag nor Microsoft Clarity is loaded, and no session replay is created. Server-side measurement of bookmaker listings, odds impressions and placements continues, because BettingView is contractually required to record and report how often a commercial partner's content was displayed; those records identify a display, not a person.
4.4 Marketing Technologies
Marketing technologies may be used to track users for advertising purposes, measure advertising across websites or services, build advertising profiles, or support personalised or targeted advertising where permitted by applicable law.
The current Platform implementation does not use Meta Pixel, client-side advertising-network SDKs or similar cross-site advertising trackers. The Platform may display paid placements, promotions and other commercial content and measure interactions with such content using the first-party measurement technologies described under Statistics / Analytics above. The display of such commercial content does not itself involve the use of Marketing technologies.
If Marketing technologies are introduced in the future, they will be managed through the applicable consent controls and this Cookie Policy will be updated as appropriate.
5. Cookies and Similar Technologies We Use
The following table describes the main cookies and similar technologies identified in the current BettingView Platform implementation. Exact technologies may vary depending on the functionality you use, your device and browser, and third-party service configurations.
| Cookie / Technology | Provider | Category | General Description / Purpose | Duration / Retention |
|---|---|---|---|---|
| CookieConsent / Cookiebot consent technologies | Cookiebot / Usercentrics | Necessary | Records and manages your cookie consent choices. | Approx. 12 months |
| accessToken | BettingView | Necessary | Authentication cookie used to maintain an authenticated Platform session. | Access-token/JWT lifetime |
| refreshToken | BettingView | Necessary | Authentication cookie used to refresh an authenticated session. | Refresh-token/JWT lifetime |
| bv_accessToken / bv_refreshToken | BettingView | Necessary | Authentication tokens stored in local storage to maintain and refresh authenticated sessions. | Until logout, account deletion, failed refresh or applicable token expiry |
| bv_age_ack | BettingView | Necessary | Records completion of the applicable age acknowledgement or age gate. | Until browser storage is cleared or a higher age requirement applies |
| bv_attribution | BettingView | Statistics | Records first-touch referral information for referral attribution. | 30 days |
| Referral and qualifying-event storage (bv_qualifying_session_sent, bv_qualifying_action_sent, bv_click_beacon:<code>) | BettingView | Necessary | Records and deduplicates referral clicks, qualifying sessions/actions and related referral activity. | Generally browser/tab session; some related UI flags may persist for up to 7 days |
| Referral UI storage (bv_raf_welcome_seen, bv_raf_page_visited, bv_raf_banner_dismissed_until, bv_raf_banner_hidden_session) | BettingView | Statistics | Supports referral-related interface state and prevents repeated display of referral messages or banners. | Certain values persist for up to 7 days; session-specific values last for the browser session |
| Placement impression and click measurement | BettingView | Statistics | Measures impressions and clicks relating to operator placements and Platform content for measurement, verification and partner reporting. | Session/page identifiers; relevant event records may be retained server-side |
| Odds impression measurement | BettingView / Betadata | Statistics | Measures operator odds impressions for partner reporting and verification. | Server-side |
| Google Analytics 4 Measurement Protocol | Statistics | Receives selected measurement events from BettingView's servers for analytics and verification of clicks and placements. | According to configured Google Analytics retention settings | |
| Google Analytics 4 (gtag) — _ga, _ga_<container-id>, bv_ga4_internal, bv_ga4_purchase_<id> | Statistics | Distinguishes visitors and sessions in order to measure use of the Platform, including pages viewed, features used, searches performed and subscription purchases. Loaded only after consent to Statistics is given. | _ga: up to 2 years; _ga_<container-id>: up to 2 years | |
| Microsoft Clarity — _clck, _clsk, CLID, MUID, ANONCHK, SM, MR and related storage | Microsoft | Statistics | Provides aggregated heatmaps and session replay (a reconstruction of interactions such as clicks, scrolling and mouse movement) in order to identify usability problems. All text is masked before recording. Loaded only after consent to Statistics is given. | _clck: up to 1 year; _clsk: 1 day; Microsoft-controlled server-side retention |
| Zoho Desk ASAP (including crmcsr, zalb_<id>) | Zoho | Preferences | Provides help-centre and customer-support functionality. | Provider/configuration dependent |
| Zoho SalesIQ | Zoho | Preferences | Supports customer-support, chat and visitor functionality where enabled. | Provider/configuration dependent |
| Google Identity Services – Sign-In / OAuth | Necessary | Enables authentication and registration using a Google account when requested by the user. | Google-controlled | |
| Google Identity Services – One Tap | Preferences | Provides the optional Google One Tap sign-in experience where enabled and permitted by the user's cookie preferences. | Google-controlled | |
| Sign in with Apple | Apple | Necessary | Enables authentication and registration using an Apple account. | Apple-controlled |
| bv_oauth_terms | BettingView | Necessary | Temporarily stores information required to complete the authentication/registration flow. | 30 minutes |
| bv_oauth_marketing | BettingView | Preferences | Temporarily stores the user's marketing preference during the authentication/registration flow. | 30 minutes |
| Stripe.js / Stripe technologies (including __stripe_mid, __stripe_sid, m and m.stripe.network storage) | Stripe | Necessary | Supports subscription checkout, card tokenisation and related payment functionality. | Stripe-controlled |
| bv_stripe_setup | BettingView | Necessary | Temporarily supports completion of the Stripe subscription/payment setup flow. | Until the relevant setup flow is completed or storage is cleared |
| Revolut Merchant Web SDK / Revolut Checkout technologies | Revolut | Necessary | Supports subscription checkout and payment functionality, including card payments, Revolut Pay and other payment methods made available through Revolut Checkout. | Revolut-controlled |
| Cloudflare security technologies, including __cf_bm and __cflb where used | Cloudflare | Necessary | Provides security, bot-management and network-protection functionality. | Cloudflare/configuration dependent |
| Cloudflare Turnstile | Cloudflare | Necessary | Provides security and anti-abuse verification during login and registration. | Cloudflare/configuration dependent |
| bv_cmp_notice_dismissed | BettingView | Necessary | Records dismissal of a CMP-related notice during the current session. | Browser session |
| bv_lang | BettingView | Necessary | Stores the language explicitly selected by the user. | Until changed or browser storage is cleared |
| bv_color_mode, bv_color_scheme-light, bv_color_scheme-dark | BettingView | Necessary | Stores the appearance mode explicitly selected by the user (system, light or dark). | Until changed or browser storage is cleared |
| Odds UI preference storage (bv_odds_format, bv_odds_view_mode, bv_odds_operator_types) | BettingView | Necessary | Stores the user's selected odds format, display mode and operator-type preferences. | Until changed or browser storage is cleared |
| PWA preferences and installation storage (bv_pwa_visits, bv_pwa_install_dismissed_at, bv_pwa_installed) | BettingView | Preferences | Supports installation prompts, dismissal preferences, visit counts and PWA installation status. | Varies; certain preferences may persist until cleared and certain prompts may reset after 7 days |
| Application update storage (APP_VERSION, bv_update_banner_dismissed) | BettingView | Necessary | Supports application version management and update notifications. | Version dependent or browser/tab session |
| CARTO / map technologies | CARTO / map providers | Preferences | Loads map content when you use map-based Platform functionality. | Provider dependent |
| Browser geolocation | Browser / BettingView | Preferences | Allows you to provide your location when using location-based features such as nearby shops or price maps. | Used when the relevant functionality is requested |
| Device fingerprint | BettingView | Necessary | Generates a technical identifier based on certain browser and device characteristics to help detect abuse and prevent fraudulent or duplicate signups. | Generated during signup; not stored in your browser as a cookie |
Revolut checkout technologies are currently being integrated and may not yet be available on the Platform. Specific cookies or similar technologies introduced by the Revolut integration will be reviewed following deployment and reflected in this Cookie Policy and/or our cookie consent tool as appropriate.
The table reflects the cookies and similar technologies currently identified as being used by the Platform, as well as technologies currently being integrated as indicated above.
Exact third-party cookie names and lifetimes may be determined by the relevant third-party provider and may change independently of BettingView. Where available, current information may also be displayed through our cookie consent tool.
6. Local Storage, Session Storage and Other Similar Technologies
Not all technologies used by BettingView are traditional cookies.
The Platform uses local storage for purposes including authentication, referral attribution, age acknowledgement, checkout functionality, language and odds-display preferences, referral interface state and PWA-related preferences.
The Platform also uses session storage for limited-duration functionality, including OAuth-related records, referral and qualifying-event deduplication, CMP notice state, checkout-related records and application update preferences. Information in session storage will generally cease to be available when the relevant browser tab or session ends, except where a specific shorter or longer duration is stated in Section 5.
BettingView may also use in-memory identifiers and other technical mechanisms for measurement and Platform functionality.
7. Analytics and Measurement
BettingView uses first-party analytics and measurement mechanisms to understand interactions with the Platform and provide reporting and verification relating to certain Platform activities, including paid placements and other commercial content configured through BettingView's partner-facing systems.
These may include measurement of:
placement impressions and clicks;
odds impressions;
referral clicks;
qualifying referral sessions or actions; and
interactions with certain Platform features.
Certain measurement events may be processed through BettingView's own APIs and may be mirrored from BettingView's servers to Google Analytics 4 using the Measurement Protocol where configured. The current implementation identifies these events as non_personalized_ads: true.
In addition, and only where you have consented to Statistics, the Platform loads Google Analytics 4 in your browser through the gtag library, and Microsoft Clarity for aggregated heatmaps and session replay. Google Consent Mode is used, so before any consent is recorded analytics and advertising storage are set to denied and no such cookies are written. The Platform does not use Google Tag Manager.
Browser-side analytics identifiers (the Google Analytics client and session identifiers) may be attached to the server-side measurement events described above, so that a recorded display can be attributed to the visit in which it occurred. Where you have not consented, that attribution does not happen and the server-side record is kept without it.
8. Third-Party Technologies
Certain Platform features depend on services provided by third parties. Depending on the functionality you use, information may be transmitted to or accessed by those providers.
The current Platform implementation includes, or is being integrated with, technologies associated with:
Cookiebot / Usercentrics – cookie consent management;
Zoho – help-centre, customer-support and related functionality;
Google – Google authentication, optional Google One Tap functionality, and analytics measurement both server-side and, with your consent to Statistics, in your browser;
Microsoft – Clarity, providing aggregated heatmaps and session replay with your consent to Statistics;
Apple – Sign in with Apple;
Stripe – subscription and payment functionality;
Revolut – subscription, checkout and payment functionality;
Cloudflare – network security, bot-management and Turnstile verification; and
CARTO / map providers – map functionality.
Some third-party technologies are activated only when you use the relevant feature or provide the applicable consent. Other technologies may be necessary to provide functionality that you specifically request, such as authentication or payment processing.
Third-party providers may process information in accordance with their own privacy and cookie practices. Their technologies, cookie names and retention periods may change independently of BettingView.
9. Cookie Consent and Your Choices
When required by applicable law, we ask for your consent before using cookies or similar technologies that are not strictly necessary for providing the Platform or functionality you have requested.
Through our Cookiebot consent tool, you can choose which categories of optional technologies you wish to allow.
You may change or withdraw your choices at any time by selecting "Cookie Settings" on the Platform and updating your preferences.
Withdrawing consent does not affect the lawfulness of processing based on consent before it was withdrawn.
Disabling certain optional technologies may affect the availability or operation of corresponding Platform features. For example, customer-support functionality that relies on preference technologies may not be available if those technologies are disabled.
You may also be able to delete or block cookies and other browser storage through your browser or device settings. Please note that blocking or deleting strictly necessary technologies may affect the operation of the Platform, including authentication or other essential functionality.
10. How Long We Use Cookies and Similar Technologies
The duration for which cookies and similar technologies remain active depends on their purpose and technical configuration.
Some technologies operate only for a browser session or tab session, while others persist for a specified period or until they are deleted, replaced or cleared.
For example, our current implementation provides for approximately 12 months for Cookiebot consent information and 30 days for first-touch referral attribution. Certain interface preferences may persist for shorter or longer periods depending on their purpose.
Where a technology is provided by a third party, its retention period may be determined by that provider and its configuration.
We may periodically review and update retention periods to reflect changes to the Platform, our service providers or applicable legal requirements.
11. Changes to This Cookie Policy
We may update this Cookie Policy from time to time to reflect changes in the cookies and similar technologies we use, changes to the Platform, legal or regulatory requirements, or our privacy practices.
Where we make material changes, we may provide additional notice where appropriate or required by applicable law.
The date of the most recent update is shown at the top of this Cookie Policy.
12. Contact Us
If you have questions about this Cookie Policy or our use of cookies and similar technologies, you can contact us at:
BettingView Ltd.
Email: [email protected]