Cookie Policy
Last updated: 31 October 2026 Version: 1.2
This Cookie Policy explains how VELOX ("we", "us", "our") uses cookies and similar technologies on the public website at https://velox.fitness (the "Website") — for example the home page, about, FAQ, contact, legal pages, and invite links.
It describes what these technologies are, what we actually use today, and how you can control them. For how we process personal data more broadly (including in the VELOX mobile app), see our Privacy Policy.
This Policy is provided for transparency under applicable data protection and e-privacy rules. It is not legal advice and does not form part of a contract.
What this Policy covers
This Policy applies to the public Website only. The VELOX mobile app may use SDKs (for example Firebase Analytics or Crashlytics) that are not cookies; those practices are described in the Privacy Policy, not in this Cookie Policy.
Key terms
- Cookies — small text files stored on your device by a website. They may be session cookies (deleted when you close the browser) or persistent cookies (kept until they expire or you delete them). They may be first-party (set by velox.fitness) or third-party (set by another domain).
- Similar technologies — storage that can work like cookies for many legal purposes, including local storage and session storage.
- Strictly necessary — technologies required to provide a service you request (for example submitting the contact form) or needed for security and basic operation of the page.
General information about cookies: allaboutcookies.org.
What we use on the public Website
On public marketing pages (home, about, guides, FAQ, contact, legal pages, invite links, and similar), we use online advertising and measurement tools so we can run Google Ads and Meta (Facebook / Instagram) campaigns, understand whether ads lead to visits or app installs, and improve marketing. These tools are loaded via tags such as the Google tag (gtag.js) and/or Google Tag Manager, and the Meta Pixel.
The signed-in web Panel (/panel) and
password-reset flows load the Flutter application and Firebase;
they are covered by the App / Firebase sections of our
Privacy Policy, not by the advertising
cookies below.
Where required by law (for example in the UK, EEA, and similar jurisdictions), we ask for your consent before loading non-essential advertising and measurement cookies. If we show a consent banner or preference centre on the Website, your choice may be stored in a first-party cookie or local storage so we can honour it on later visits.
Technologies on the public Website
| Technology | Purpose | Category | Duration |
|---|---|---|---|
| Google tag / Google Ads (Google) |
Conversion measurement, remarketing, and campaign analytics
for Google Ads. May set cookies such as _ga,
_ga_*, and Google Ads identifiers (for example
_gcl_*).
|
Advertising / analytics (non-essential where consent applies) | Varies; see Google’s cookie documentation |
| Meta Pixel (Meta) |
Measurement and optimisation of Meta ads, including
conversion events and audiences. May set cookies such as
_fbp and _fbc.
|
Advertising (non-essential where consent applies) | Varies; see Meta’s cookie documentation |
| Consent / preference storage (Velox) | Remembers your cookie or marketing consent choices where we display a banner or preference centre. | Strictly necessary for the consent service you use | Typically up to 12 months unless you clear site data |
| Contact form (HTTPS POST) | Sends name, email, subject, and message to our Google Cloud Function endpoint; messages are forwarded by email via Postmark. This is a network request, not an advertising cookie. | Strictly necessary for the form you submit | No cookie set by the form itself |
| Firebase Hosting access logs (Google) | Server logs (IP address, user agent, requested URL) for security and reliability. | Strictly necessary / legitimate interests | Short operational retention on Google’s systems |
| URL parameters (e.g. invite links) |
Invite pages may read query parameters such as
utm_campaign or n in the
browser to show invite copy. Advertising tags may also
read campaign parameters from the URL.
|
Functional / advertising measurement | URL: while the page is open; ad cookies: per provider |
Other tools we do not use on the public Website
We do not use Mixpanel, AppsFlyer, or similar mobile attribution SDKs on these static marketing pages. In-app analytics are described in the Privacy Policy.
Legal bases
Where personal data is processed in connection with the public Website (for example when you submit the contact form):
- Article 6(1)(b) GDPR — where needed to provide a service you request (for example handling your contact message).
- Article 6(1)(f) GDPR — where needed for security, fraud prevention (including spam filtering on the contact form), and reliable operation of the Website (legitimate interests balanced against your rights).
Under UK PECR / ePrivacy rules, strictly necessary storage for a service you request typically does not require prior consent. Non-essential analytics or advertising cookies would require consent before they are set.
Your choices and controls
Choices below apply to the public Website. In-app analytics and notifications are described under Your choices and controls in the Privacy Policy.
Advertising & measurement (Google Ads, Meta Pixel)
Google Ads and Meta measurement tags on marketing pages are used only with your consent where the law requires it—for example via our cookie banner or preference centre. You can withdraw consent through that banner (where available) or by clearing cookies and site data for velox.fitness in your browser. Declining advertising cookies does not block access to Website content or to the Velox App.
You can also use provider controls, including Google Ads Settings and Meta ad preferences in your Meta account, to limit personalised advertising and matched or lookalike audiences.
Browser controls
Most browsers let you block or delete cookies and site data (often under Privacy, Cookies, or Site settings). Blocking all cookies may affect how some pages work.
Velox App (Firebase analytics)
Optional Firebase Analytics in the mobile App is separate from Website ad cookies. It stays off until you opt in and can be disabled under Settings → Share Usage Data. Crash diagnostics and Performance Monitoring are described in the Privacy Policy.
Third parties
Advertising and measurement providers act as separate controllers or processors under their own terms:
- Google — Google Ads, Google tag, and related measurement (Google Privacy Policy, How Google uses cookies)
- Meta — Meta Pixel and Meta Business Tools (Meta Privacy Policy)
When you submit the contact form, your message is sent to our backend hosted on Google Cloud and forwarded to us by email through Postmark so we can receive and reply to it. We do not sell personal data. We may share online identifiers and event data with Google and Meta for advertising and measurement as described above and in our Privacy Policy.
Changes
We may update this Cookie Policy when our Website technologies change. The "Last updated" date at the top will change when we do. Continued use of the Website after an update means you should review the revised Policy.
Contact
Questions about cookies or this Policy: support@velox.fitness or Contact.
Read the Privacy Policy →