Last updated: 13 November 2026
This Cookie Policy explains what cookies and similar technologies Fortis Communications Inc (“Fortis”) uses on veloconnect.me, why we use them, and how you can control them. It is a companion to our Privacy Policy, which describes how we handle personal information generally.
The short version
veloconnect.me sets analytics and advertising cookies — Google Analytics and the Meta Pixel — only if you accept them in the banner shown on your first visit. Until you do, no Meta code runs and Google’s tag runs without cookies. You can change your mind at any time with Cookie settings at the foot of every page.
Everything else the site stores is strictly necessary — the site cannot do the job you asked it to without it — or remembers a choice you made, so under the ePrivacy Directive and the GDPR it does not require consent. Cloudflare Web Analytics, which counts visits and measures page speed for everyone, sets no cookie and stores nothing in your browser. Every item is listed below.
What cookies are
A cookie is a small text file that a website asks your browser to store on your device. Cookies let a site recognize your browser between page loads or visits — for example, to keep you signed in, remember your consent choices, or count how many distinct visitors a page received. Some cookies are set by the site you are visiting (first-party); others are set by services embedded on the site (third-party). Beyond cookies, sites can use similar technologies such as localStorage, sessionStorage, and pixels — we treat these the same way as cookies in this policy.
How we categorize cookies
Following the categories used under the EU ePrivacy Directive, the GDPR, and PIPEDA, we group every cookie into one of four types:
- Functional — strictly necessary for the site to work, including security and remembering your cookie choice. Loaded without consent.
- Preferences — remember a choice you made, here only light or dark display. Set only when you make that choice.
- Statistics — usage data so we can understand which pages are useful: Google Analytics. Only with your consent. Cloudflare Web Analytics works without any cookie (see below).
- Marketing — used to measure and target advertising: the Meta Pixel. Only with your consent.
Functional cookies and storage
- Cloudflare security cookies (
__cf_bm,cf_clearance) — Cloudflare sits in front of veloconnect.me. It sets__cf_bmwhen its bot protection is switched on for the site, andcf_clearancewhen you complete one of its security challenges; both are used to tell legitimate browsers from automated traffic. Duration:__cf_bmexpires after 30 minutes of inactivity;cf_clearancelasts for the challenge-passage period set on our Cloudflare account, 30 minutes by default. - Your cookie choice (
vc_consent) — set when you choose Accept or Decline in the cookie banner, so the site honours that choice and does not ask again. It holdsgrantedordeniedand nothing else. Duration: 180 days, after which the banner asks again. - The Meta Pixel’s hold (
wc_facebook_signals_state) — set by the Meta Pixel plugin once you have accepted, or declined after accepting, to record whether its measurements may be sent. It holdsactiveorheldand nothing else. Duration: one year. - WordPress sign-in cookies (
wordpress_*,wp-settings-*) — set only on the sign-in page of the site’s administrative area and for signed-in administrators. Duration: session, or up to one year for admin preferences. - Security plugin cookies (
wfwaf-authcookie-*,wf_loginalerted_*,wfls-remembered-*) — set by Wordfence, the security plugin on our server, only for administrators who sign in: they let its firewall recognise a signed-in administrator, notice a sign-in from a new device, and remember a device for two-factor sign-in. Never set for visitors. - Pricing page session storage (
vc-geo-gated) — on the pricing page, records for the current browser tab whether a local-currency price view applies to the country your connection comes from, so the page does not have to ask our server again. It holds a single 1 or 0 and nothing else. Duration: removed when you close the tab.
We do not set a cookie to remember that you submitted a form, and we do not use local storage or fingerprinting for tracking.
Preferences
- Light or dark (
vc-theme, local storage) — stored only when you press the light-mode switch in the header, so the next page opens the way you chose. It holdslightordarkand is never sent anywhere. Duration: until you clear your browser’s site data.
Statistics and marketing — only if you accept
These run only after you choose Accept. Until then the Meta Pixel’s code is not run and nothing is fetched from Meta, and Google’s tag runs in Google’s consent mode, which sets and reads no cookies and sends Google only cookieless measurements of the visit, with no identifier linking one visit to another.
- Google Analytics (
_ga,_ga_*) — set by Google’s tag, loaded fromwww.googletagmanager.com, to tell one visitor from another and keep a visit together, so Google can give us statistics on visits, pages and where visitors come from. Duration: two years. If our Google tag is linked to Google Ads, Google may also set_gcl_au(90 days) to measure ad conversions. - Meta Pixel (
_fbp,_fbc) — set by Meta’s script, loaded fromconnect.facebook.net, to measure and improve our advertising on Facebook and Instagram._fbpidentifies your browser to Meta;_fbcis set only when you arrive from one of our ads, and records that click. Duration: 90 days each. If your browser allows third-party cookies, Meta may also read or set its own cookies onfacebook.com. The Pixel’s code also keeps a list of the events it has sent in session storage (fbpix_seen_event_ids), removed when you close the tab, and our server reports the same page views to Meta directly (Meta’s Conversions API) with your IP address and browser user-agent. - Meta Pixel relay (
PHPSESSID) — once the Pixel runs, it also sends its events to Meta through our own server, and the Meta Pixel plugin starts a server session for that, which keeps a random identifier attached to your events. Duration: 90 days. It is readable only by our server, so withdrawing consent stops the Pixel from using it but cannot delete it; clearing this site’s cookies in your browser does.
Third-party cookies and embedded services
Beyond Cloudflare, Google Analytics and the Meta Pixel — the last two only with your consent — veloconnect.me does not embed third-party services that set cookies. We load no other tag-management scripts, social media widgets, customer-data platforms or session-replay tools, and the site’s videos are served from veloconnect.me itself.
Cloudflare Web Analytics
Cloudflare adds its Web Analytics script to our pages as they pass through its network — it is a setting on our Cloudflare account, not part of the site’s own code. Your browser fetches the script from static.cloudflareinsights.com, and it reports page-load timing measurements to Cloudflare at /cdn-cgi/rum on this site. We see aggregate figures: visits, page views, load times and Core Web Vitals, which can be broken down by country, page, referring site, browser, operating system and device type.
According to Cloudflare’s documentation, Web Analytics does not use cookies, localStorage or any other client-side state, and does not fingerprint visitors by IP address, user agent or any other data. It sets nothing on your device for this policy to list. If you would rather it did not run, block scripts from static.cloudflareinsights.com in your browser or with a content blocker; nothing on this site depends on it.
What we log without cookies
Our server records ordinary web-server log entries for every request — IP address, user-agent, the page requested, the referring page and the time. This happens without any cookie, is necessary to operate and secure the site, and the logs are kept for up to 90 days. The site’s firewall separately records requests it blocks and sign-in attempts — IP address, user-agent and the address requested — on our server, for up to 30 days.
When you submit a form we store a one-way hash of your IP address rather than the address itself. See the Privacy Policy.
Consent
On your first visit a banner offers two choices of equal weight, Accept and Decline. Google Analytics’ cookies and the Meta Pixel wait until you choose Accept — before that, Google’s tag runs only in the cookieless mode described above — and leaving the banner unanswered is the same as declining. Your choice is kept for 180 days.
To change it, use Cookie settings at the foot of every page. Withdrawing takes effect at once: Google’s tag returns to its cookieless mode, the Meta Pixel is held, and the Google Analytics and Meta cookies already on this site are deleted from your browser (all but PHPSESSID, above). What Google and Meta received before you withdrew is kept under their own policies. The functional cookies above need no consent.
Browser controls
You can control cookies at the browser level. Every major browser lets you block all cookies, block third-party cookies, prompt before each cookie, or clear cookies on exit. Blocking Cloudflare’s cookies may mean a security challenge cannot complete, and our forms then refuse the submission — they fail closed by design, so a failed challenge is a rejection rather than a free pass. If that leaves you unable to reach us, the contact form shows an email address that needs no JavaScript and no cookies.
Statistics and marketing cookies are set only if you accept them, and Cookie settings withdraws that at any time. To stop Cloudflare Web Analytics, block scripts from static.cloudflareinsights.com, as described above.
Updates to this policy
We may update this Cookie Policy if we add, remove, or change a cookie. When we do, we revise the “Last updated” date at the top of this page.
Questions about cookies
For any question about cookies on this site, write to [email protected]. For broader privacy questions, see our Privacy Policy.