The Dutch-language version of this Cookie Policy ("Cookiebeleid") is the authentic and governing version. This English translation is provided for convenience only; in case of any discrepancy, the Dutch text prevails. This policy goes together with the Privacy Policy.
1. Why HUB3 uses cookies and storage
HUB3 uses cookies and browser storage to make the app work correctly, to remember your session and settings, and to enable limited, privacy-friendly analytics. This policy explains which technologies we use, what they are for, who places them and how long they are retained. It goes together with our Privacy Policy.
2. What are cookies and similar technologies
Cookies are small files placed on your device. HUB3 also uses browser storage (localStorage and
sessionStorage), which stores data locally in your browser. In this policy, "cookies" refers to all
these similar technologies, unless stated otherwise.
sessionStorageis cleared as soon as you close the tab or browser session.localStoragepersists until it is removed (by you or by the app).
3. Categories we use
3.1 Strictly necessary cookies and storage
These are required for the platform to work and cannot be disabled without disrupting operation. No consent is required for these.
- Authentication and session management via Supabase (to keep you logged in and secure your session).
- Security and correct routing within the app (e.g. preventing abuse and checking whether your profile is complete).
- Remembering your cookie choice itself.
3.2 Functional cookies and storage
These remember your choices and ensure a consistent experience. They are generally necessary for a feature you use yourself.
- Language and locale settings.
- Theme preference (light/dark).
- Profile-completion, redirect and onboarding state within the app.
- Temporary storage for interface behaviour (e.g. page-transition direction) and cart status.
3.3 Analytics (only with your consent)
HUB3 uses limited, privacy-friendly analytics to understand platform usage and performance. These are only loaded after you give explicit consent via the cookie banner or preferences; without consent, none of the below is activated.
- Vercel Analytics for general, aggregated platform measurement. This runs cookieless and places no advertising or tracking cookies.
- Visit statistics for public studio profiles and pages. HUB3 counts visits and returning visits.
After consent, the web app places the HttpOnly visitor cookie
hub3_anon_visitor; counting itself happens server-side. A functionalsessionStoragekey and server-side session deduplication prevent double counting. The related data processing (such as IP address, pages visited and whether a visitor was logged in) is described in the Privacy Policy.
4. Overview of cookies and storage used
| Name / key | Type | Category | Purpose | Duration |
|---|---|---|---|---|
sb-…-auth-token (Supabase, including fragments and -code-verifier) |
cookie | Strictly necessary | Authentication and session management | Until logout or session expiry |
hub3_pc |
cookie | Strictly necessary | Remembers whether your profile is complete for correct routing | Max. 1 year |
hub3_cookie_consent_v1 |
localStorage | Strictly necessary | Stores your cookie choice (consent) | Until you clear or change it |
hub3_anon_visitor |
HttpOnly cookie | Analytics (opt-in) | Pseudonymous counting of unique public studio visitors | Max. 1 year |
hub3_survey_browser |
HttpOnly cookie | Functional | Limits duplicate survey submissions within this browser; no cross-site tracking | Max. 1 year |
hub3:surveys:*, hub3:*_platform_pulse:submitted_at:* |
localStorage / sessionStorage | Functional | Remembers survey participation and invitation cooldowns | Participation until cleared; cooldown 14 days; session keys until session ends |
hub3_locale, hub3_locale_source |
cookie / localStorage | Functional | Language and locale preference | Max. 1 year |
theme |
cookie / sessionStorage | Functional | Theme preference (light/dark) | Max. 1 year (cookie) / until session ends |
pendingStudio, pendingStudioPlan, pendingOAuthSignup, hub3_pending_onboarding_type |
localStorage | Functional | Remembers registration/onboarding steps during sign-up | Until flow completes or removed |
hub3_redirect_after_login, hub3_redirect_after_profile |
localStorage | Functional | Routes you to the right page after login/profile | Until flow completes or removed |
hub3_affiliate_referral_code |
localStorage | Functional | Remembers an affiliate/referral code during registration | Until flow completes or removed |
cart-updated |
localStorage | Functional | Syncs cart status across tabs | Until removed |
hub3_nav_dir, hub3_nav_ts, hubSwipeDir |
sessionStorage | Functional | Page-transition direction/timing | Until session ends |
hub3_public_profile_active_session_v1 |
sessionStorage | Analytics (support) | Prevents double counting of visits to public profiles | Until session ends |
| Vercel Analytics | cookieless | Analytics (opt-in) | General, aggregated platform measurement | No cookie placed |
Some functional keys may also be stored locally to remember UI state, such as dismissed hints, tours or surveys. Exact names may vary depending on configuration and updates.
5. Consent and management
5.1. On your first visit, HUB3 shows a cookie banner with three choices: Accept all (including analytics), Only necessary cookies (analytics refused) and Cookie settings (choose per category).
5.2. Strictly necessary and functional cookies/storage are needed for the platform to work and for features you use yourself. Analytics is only activated after your explicit consent.
5.3. Your choice is stored and remains valid until you change it. You can change or withdraw your consent at any time via the "Manage cookie preferences" button on the cookie policy page or the "Cookie preferences" link in the footer.
5.4. You can also manage or clear cookies and browser storage at any time via your browser settings. Disabling certain cookies/storage may affect how HUB3 works.
5.5. Certain analytics features can also be disabled centrally by an administrator.
6. Third parties
Some technologies are provided by third parties that may act as processors or independent controllers, including Supabase (authentication/infrastructure), Vercel (hosting and cookieless analytics), Stripe (payments; Stripe sets its own cookies on its domain during checkout) and Google Maps (map display of a location, may set Google cookies). Please review their respective privacy and cookie policies for more information. See also the Privacy Policy for the broader context of data processing and international transfers.
7. Changes
We may update this Cookie Policy from time to time to reflect changes in technology, law or our platform. After a material change, we may ask you to make your cookie choice again.
8. Contact
If you have questions about cookies or privacy on HUB3, contact us at info@hub3.be.
Last updated: 3 August 2026