Legal
Cookie Policy — What warebee.com Stores and Why | WareBee
Every cookie and browser storage key warebee.com uses, what it does, how long it lasts, and how to change or withdraw your consent at any time.
This Cookie Policy explains how WareBee Ltd uses cookies and similar browser storage on warebee.com. It sits alongside our Privacy Policy, which is the controlling document for personal data at WareBee, and our Website Terms of Service.
This document covers this marketing website only. If you use the WareBee application, the platform privacy policy published at app.warebee.com/legal governs your account and the operational data you send us.
1. How consent works here
Nothing but strictly necessary storage is set when you first arrive.
Every analytics and marketing script on this site is embedded inert — as an unexecutable placeholder — and is only promoted to a running script after you give consent. If you reject, or simply never answer the banner, those scripts never execute and their cookies are never set.
You can change your mind at any time through the Cookie preferences link in the site footer.
2. Strictly necessary
These are required for the site to function and to stay protected. They cannot be switched off.
| Name | Set by | Purpose | Duration |
|---|---|---|---|
__cf_bm |
Cloudflare | Bot management — distinguishes human visitors from automated traffic | 30 minutes |
cf_clearance |
Cloudflare | Records that you passed a security challenge, so you are not challenged repeatedly. Set only if a challenge was shown to you | Up to 1 year |
consent (localStorage) |
WareBee | Stores your cookie choices and the version of this policy they were given against, so we do not ask again | Until you clear it or the policy version changes |
Form abuse protection (no cookie). When you submit a form we compute a one-way HMAC of your IP address and hold it server-side for one hour to rate-limit submissions. The IP itself is not stored, and this uses no cookie or browser storage.
3. Analytics — consent required
Set only after you allow the Analytics category. These help us understand which pages people visit and which content is useful.
First-party measurement
We run our own collector on warebee.com. Page-view events are sent to an endpoint on this domain and forwarded server-side to Google Analytics 4. Because the measurement runs server-side, the standard Google _ga cookies are not set in your browser — only the two first-party cookies below.
| Name | Set by | Purpose | Duration |
|---|---|---|---|
_cid |
WareBee (first party) | Randomly generated client identifier, so repeat visits can be counted as one visitor | 2 years |
_sid |
WareBee (first party) | Rolling session identifier, refreshed on activity | 30 minutes |
Third-party analytics and marketing
These vendors load their own scripts after consent and set their own cookies. Names and durations are set by each provider and can change without notice.
| Provider | Typical cookies | Purpose |
|---|---|---|
| Cloudflare Web Analytics | None — cookieless | Aggregate, privacy-preserving traffic and performance measurement |
| Segment | ajs_anonymous_id, ajs_user_id (≈1 year) |
Routes analytics events to our downstream tools under one anonymous identifier |
| HubSpot | hubspotutk, __hstc (≈6 months), __hssc (30 minutes), __hssrc (session) |
Associates form submissions and page views with a contact record in our CRM |
| Woopra | wooTracker (≈2 years) |
Journey and behavioural analytics across the site |
| Leadfeeder | _lfa (≈2 years) |
Identifies the company a visit came from (via IP lookup) for B2B interest reporting |
| Leadsy (vtag.ai) | Provider-set identifiers | Visitor intent and company-level identification |
| Microsoft Clarity | _clck (≈1 year), _clsk (1 day), CLID and related provider-set identifiers |
Heatmaps and session replay, so we can see where pages confuse people and fix them |
Each of these is an independent controller or processor for the data it collects. Their own privacy notices govern what they do with it; see section 7 of our Privacy Policy for how we share data with service providers.
4. Functional — consent required
Set only after you allow the Functional category.
| Name | Set by | Purpose | Duration |
|---|---|---|---|
| Form draft keys (localStorage) | WareBee | Save-and-resume for long forms, such as job applications, so a part-completed form survives a page reload | Until submitted or cleared |
If you decline this category, forms still work — you simply need to complete them in one sitting.
5. Changing or withdrawing consent
- On this site — open Cookie preferences in the footer, adjust the toggles, and save. Withdrawing consent stops the affected scripts from loading on your next page view.
- In your browser — you can block or delete cookies through your browser settings. Blocking strictly necessary cookies may stop parts of the site working, including form submission.
- Clearing site data also clears your stored consent record, so the banner will appear again.
6. Changes to this policy
We publish a version of this policy with each material change. When the policy version changes, previously stored consent is treated as expired and you will be asked again.
7. Contact
- Data protection: [email protected]
- Legal: [email protected]
WareBee Ltd, Unit 1, Cambridge House, Camboro Business Park, Oakington Road, Girton, Cambridge, Cambridgeshire, CB3 0QH, United Kingdom.