What This BetAlice Page Does Not Collect
Open a page here, read it, close the tab. Almost nothing follows you out the door.
That is plumbing, not a promise. betalicecanadacasino.com is a stack of static pages about one casino brand, and static pages have very little to collect with. Below is the short inventory of what does happen anyway, because “we gather nothing” is almost never true.
Why This BetAlice Site Shows You No Cookie Banner
You have dismissed a hundred consent walls this month. There is none here, for a dull reason: nothing on these pages writes a non-essential cookie. Absent from every one of them:
- Analytics of any kind — no Google Analytics, no Plausible, no session recorder
- Advertising tags — no Meta pixel, no TikTok pixel, no conversion tag
- Any login or member area, so no session cookie is ever issued
- Comment boxes, newsletters and forms that store what you type
The only JavaScript sits at the document's foot: it prints the year and opens the menu and question panels. It reads nothing about you.
A banner exists to gather meaningful consent for tracking, which Quebec's Law 25 polices hardest. No tracking, no banner.
What a Web Server Records When a BetAlice Page Loads
Here is where data genuinely lands. Every web server writes a line for each request it answers, and ours is no exception:
| Recorded | Purpose |
|---|---|
| IP address | Blocking abusive traffic |
| Date and time | Putting an incident in order |
| Page or file asked for | Finding dead links |
| Referring page, when sent | Spotting sudden traffic floods |
| User-agent string | Browser or crawler |
| Status code and bytes | Errors and runaway bandwidth |
Those lines sit in a short rolling window — days, not years — then the host rotates them away. Never archived, never fed to an analytics tool, never sold. The hosting company and the delivery network in front of it see what any site's host sees.
Under PIPEDA an IP address can be personal information once combined with other details. So it is combined with nothing here.
Google Fonts: The One Third Party a BetAlice Page Reaches
Plenty of sites claim zero outside connections. This one has one.
The stylesheet pulls two typefaces, Playfair Display and Source Sans 3, from Google's font servers, so your browser asks fonts.googleapis.com for them as a page renders. That request carries your IP address and user-agent to Google, and Google's own terms govern what follows.
No cookie comes back, and no font request here is tied to a reader we could name. Block it with an extension and pages render in your system typeface, reading fine.
What Happens the Moment You Click Through to BetAlice
The button in the top bar, and the one pinned to the foot of a phone screen, lead off this site. Follow either and you become BetAlice's visitor rather than ours: their privacy notice and their cookies govern from that second. We cannot see your account or your deposits.
The commercial half, plainly. An outbound click may be tagged so BetAlice can credit this site if you register. What comes back is arithmetic, not identity. A click happened. Some accounts opened. Which reader, which city, which evening — not reported, and not wanted.
Nothing you do inside a BetAlice account travels back to betalicecanadacasino.com.
PIPEDA, Law 25 and Your Rights as a BetAlice Reader in Canada
The Personal Information Protection and Electronic Documents Act lets you ask what personal information an organisation holds on you, have an error corrected, and complain to the Office of the Privacy Commissioner of Canada. Those rights apply here, and any request gets an answer.
Expect a thin one. With no accounts, no mailing list and no analytics store, an access request reaches a rotating server log at most — possibly nothing, if the window has turned over.
Where you live may add a statute: Quebec's Law 25, or the Personal Information Protection Act in British Columbia and in Alberta. Where a provincial rule runs stricter, treat it as the one governing your request.
Age, Contact and Revisions to This BetAlice Notice
Everything published here is written for adults who have already decided to gamble. No page addresses children or uses youth imagery. The legal minimum is 19 in most provinces and 18 in Alberta, Manitoba and Quebec; BetAlice's own footer says it accepts customers over 18, below the floor most Canadians live under.
Privacy questions and access requests go to [email protected], and the about page names who publishes this site. Say what you want to know rather than which statute you are citing.
This notice is rewritten whenever the site's technical behaviour changes: a new embedded element, a different host, a form where none existed.
BetAlice Privacy Questions Canadians Ask About This Site
No. No login to keep alive, no saved preference, no tracker. Your cookie list stays untouched by this domain.
A banner collects consent for tracking, and there is none to consent to. Showing one anyway would be pure theatre.
None — no analytics script, no tag manager, no heatmap recorder, no ad-network pixel. Pageviews here go uncounted.
Your IP address, the time, the page requested, the referrer, the user-agent and the status code, on a short rotation.
Its font servers get a request for two typefaces when a page renders, carrying your IP address and browser string.
That a click happened, and possibly that a registration followed. Not who you are, where you live, or what you deposited.
Yes. The realistic outcome is written confirmation that nothing stood to delete beyond an expiring log line.
Write to us first. If the answer disappoints, the Office of the Privacy Commissioner of Canada accepts PIPEDA complaints.