On-site preferences
OptionalLocale choices, dismissed banners, and similar settings kept in cookies or local storage.
Kept for: Wiped when you clear site data in your browser — see our cookie notice for detail.
Casino Sites
Casinos by Software
Casinos by Payments
Sportsbook Sites
Bet By Sport
About & Editorial
Policies & Trust
Privacy
Last updated September 3, 2026
Exact entitlements depend on country. These steps describe how to reach us when a right applies to data we control.
Start on our about page contact routes. Share enough to verify identity — not your entire life story.
Grouped by how data arrives — not by vendor brand names.
Locale choices, dismissed banners, and similar settings kept in cookies or local storage.
Kept for: Wiped when you clear site data in your browser — see our cookie notice for detail.
Short referral parameters on partner links so we know which article sent traffic — not what you did after landing.
Kept for: We never receive operator login credentials through these URLs.
Each visit creates a brief technical entry used to deliver pages, block abuse, and debug outages.
Kept for: Rotated on a rolling window — weeks, not multi-year archives.
Email or form text kept so we can reply, fix errors, or handle a privacy request.
Kept for: Deleted or archived once the thread is closed unless law requires longer retention.
No website is perfectly safe; these controls reduce everyday risk.
Pages travel over HTTPS between your browser and our infrastructure.
Look for the padlock in the address bar before you submit a form.
Production tools are limited to staff who require them for publishing or security work.
Sensitive admin actions leave an audit trail.
We do not trade identifiable browsing profiles to gambling operators or list brokers.
Contractors sign terms that restrict how they reuse information.
Four processing reasons, each with the legal basis we cite under EU/UK-style privacy rules.
We watch for bots, abusive traffic spikes, and error patterns so a single bad actor cannot take every reader offline.
Aggregated analytics show where people abandon a hub or hit layout bugs on small screens — usually without naming individuals.
Emails and form posts are stored long enough to answer corrections, partnership questions, or accessibility reports.
Outbound links may carry short tags so we know which article sent traffic — not what you did after landing on a casino.
Principles we apply whenever information leaves our direct control.
Hosting and security vendors may see technical logs — only what is needed to run or protect the site.
Analytics tools get aggregated traffic shapes, not a resale-ready list of named individuals.
Valid legal orders may require us to hand over limited records we actually possess.
We do not sell your email to casinos for cold marketing without a separate consent you gave them.
When a vendor contract ends, we delete or anonymise data they processed on our behalf where practical.
Vendor stacks evolve. Material changes show in the “Last updated” date above.
The headline version before you read the sections above.
VectorBets.com is an editorial website. We do not process deposits, settle wagers, or store casino account passwords.
Typical records cover pages opened, browser type, and approximate region from network routing — not your balance at a partner site.
Where local law grants access, correction, or erasure, contact us using the routes on our about page.
No. Hubs and reviews are open. Extra detail appears only if you email us, join a newsletter, or save on-site preferences.
No. Wallet history, KYC files, and wager logs stay with the operator you signed up with.
Cookies explain browser storage line by line. This page covers server logs, emails, legal bases, and regional rights.
Technical logs roll off after a short window — typically a few weeks. We do not build decade-long personal browse histories.