Cookie Policy | Hiveality

1. What this Policy covers

This Policy applies to the Hiveality marketing site, admin platform, and customer-facing experiences we host. Some cookies or tracking tools are set by Hiveality directly, and others are enabled by a website owner using Hiveality.

2. What we mean by cookies and similar technologies

When we say "cookies" in this Policy, we also mean similar technologies such as local storage, session storage, analytics scripts, tracking pixels, SDKs, tags, and browser-based identifiers.

3. Categories of cookies and similar technologies we use

Strictly necessary technologies used for authentication, security, fraud prevention, session continuity, cross-subdomain login support, checkout flows, and basic site operations.
Preference technologies used to remember settings such as selected workspaces, dismissed prompts, editor state, cart state, saved UI preferences, and similar product settings.
Analytics technologies used to understand visits, performance, attribution, page usage, and product engagement.
Marketing and advertising technologies used to measure campaign performance, attribute conversions, and support remarketing or similar activities where enabled.
Media and embedded-content technologies used when a page loads third-party video, fonts, images, or other external assets.

4. Examples of technologies used on Hiveality properties

Supabase authentication cookies to keep users signed in and support authenticated admin and member sessions.
Local storage and session storage for preferences, attribution context, carts, popup frequency, editor helpers, and similar product behavior.
Vercel Speed Insights on Hiveality-operated properties to measure performance and reliability.
Managed analytics scripts on Hiveality-powered websites to record visits and lightweight traffic analytics.
Google Analytics 4 and Meta Pixel where a website owner configures those tools for a particular site.
Google Fonts, Loom embeds, Uploadcare, Mux, and similar third-party services when a page loads those resources.

5. Why we use them

To authenticate users and protect accounts.
To keep the platform functioning across pages, sessions, and supported subdomains.
To remember preferences and improve usability.
To measure traffic, campaign attribution, performance, conversions, and product engagement.
To support embedded media, integrations, and customer-configured analytics or advertising tools.

6. Customer-controlled tracking on Hiveality-powered websites

Website owners using Hiveality can enable analytics and marketing tools on the sites they operate, including Google Analytics 4, Meta Pixel, managed analytics scripts, and customer-configured webhooks or conversion flows. Those settings are controlled by the website owner and may vary from site to site.

If you are visiting a customer's Hiveality-powered site, you should also review that website owner's own cookie and privacy notices.

7. Your choices

You can change browser settings to block or delete cookies.
You can clear local storage or session storage from your browser settings.
If the site you are visiting offers cookie controls or consent tools, you can use those controls there.
You can use vendor opt-out tools made available by companies such as Google or Meta where applicable.
If you block strictly necessary technologies, parts of Hiveality may stop working correctly.

8. Regional consent

Where law requires consent before non-essential cookies or similar technologies are used, the operator of the relevant site is responsible for configuring and honoring those requirements. Any consent controls, banners, or preference tools may vary by site, feature, jurisdiction, and configuration.

9. More information

For questions about cookies or tracking technologies used by Hiveality, contact support@hiveality.com.

If you need help with a cookie, analytics, or advertising-related preference on a Hiveality-operated property, contact support@hiveality.com.