Cookie Policy
Hububb Technologies Ltd
Last updated: 19 November 2026
Version 1.0
1. About this policy
This policy explains how hububb.com and the Hububb app (together, the "Platform") use cookies and similar technologies, why we use them, and how you stay in control.
The Platform is run by Hububb Technologies Ltd, a company registered in England and Wales (company number 16729682), whose registered office is at 27 Old Gloucester Street, London WC1N 3AX, United Kingdom. In this policy, "Hububb", "we", "us" and "our" mean Hububb Technologies Ltd.
We use some of these technologies to make the Platform work. We only use the others if you say yes. You can say yes or no for each type, and you can change your mind at any time using "Cookie settings" at the bottom of every page.
Where a cookie involves personal data, our Privacy Policy also applies. It explains what we do with your data, why, and your rights.
2. The technologies we use
Cookies are small text files that a website saves on your device. Some last until you close your browser (session cookies). Others stay for a set time (persistent cookies). Cookies set by us are first-party cookies. Cookies set by another company are third-party cookies.
Local storage and similar browser storage work like cookies. They let a website keep small pieces of information in your browser. When we say "cookies" in this policy, we include these too.
Pixels and tags are small pieces of code that send information to another company, for example to tell an advertising company that a page was viewed.
Server-to-server connections pass information from our servers straight to another company, without going through your browser. We use one of these for advertising measurement (see section 5).
Server logs. Like most websites, our servers automatically record technical details of each visit, such as your IP address, the date and time, the pages requested, and your browser and device type. We use these to keep the Platform secure and running well. They are not used for advertising.
3. Our four categories
We group what we use into four categories. Apart from Strictly necessary, everything is off until you choose to turn it on.
3.1 Strictly necessary (always on)
These make the Platform work and keep it secure. For example, they remember that you are logged in, protect payments from fraud, stop automated abuse of our forms, and remember your cookie choices. You cannot switch these off in our settings, because the Platform would not work without them. You can block them in your browser, but parts of the Platform will then stop working.
| Name | Set by | What it does | How long |
|---|---|---|---|
hububb_consent | Hububb | Remembers your cookie choices and the version of this policy you saw | 6 months |
hububb_consent_notice (browser session storage) | Hububb | Shows you a confirmation after the page reloads when you have switched a cookie category off | Removed as soon as the confirmation is shown |
firebaseLocalStorageDb, firebase-heartbeat-database (browser storage, IndexedDB) | Hububb, using Google Firebase | Keeps you signed in to your account | Until you sign out or the session expires Google documentation |
__session (set only after you sign in) | Hububb, using Google Firebase | Keeps you signed in to your account | 14 days, or until you sign out Google documentation |
__stripe_mid, __stripe_sid (only on pages that load Stripe) | Stripe | Helps Stripe detect and prevent fraud when you pay | __stripe_mid 1 year; __stripe_sid 30 minutes (per Stripe documentation) Stripe documentation |
| Cloudflare Turnstile (sign-up form only, after you start the form) | Cloudflare | Checks that a form is being completed by a person and not a bot | No cookie by default. Turnstile saves one item, cf.turnstile.u, in your browser storage, set by Cloudflare on challenges.cloudflare.com. It has no expiry and stays until Cloudflare replaces it or you clear your browser data Cloudflare documentation |
__cf_bm (set on cal.com by the Cal.com booking calendar, only when you ask to book a call) | Cal.com | Lets you pick a time for a call with us | About 30 minutes Cal.com documentation |
3.2 Performance (off until you opt in)
These help us understand how people use the Platform, so we can fix problems and make it better. They may measure which pages you visit, how you move around, and where something goes wrong. Some can record how you use a page (see "Session recordings" below).
| Name | Set by | What it does | How long |
|---|---|---|---|
ph_phc_bliD6KvYRvHBLnG7abY6Vo3sBdObQ2XuHQLYdCiLwJp_posthog (cookie), plus storage entries with the same name in your browser | PostHog (EU cloud, hosted in Frankfurt), on our behalf | Gives your browser a random ID and remembers your visit, so we can see how pages and journeys are used | 365 days PostHog documentation |
Session recordings. If you opt in to Performance, PostHog may record how you use pages, such as where you click and scroll, so we can find what confuses people. We mask all text typed into forms, including email and phone fields, so that what you type is not visible to us in the recording. Payment card details are never recorded.
3.3 Functional (off until you opt in)
These remember choices and switch on extra features that make the Platform easier or more pleasant to use. If you say no, the Platform still works, but some things may be slower or less convenient.
| Name | Set by | What it does | How long |
|---|---|---|---|
hububb.guest-shell (browser storage) | Hububb | If you are a signed-in guest, remembers the first letter of your first name, whether you host and your unread message count, so the header appears instantly on your next visit | 30 days, or until you sign out |
hububb.displayCurrency, hububb.fxRates.v2 (browser storage) | Hububb | Remembers the currency you chose to see prices in, and keeps the day’s exchange rates so they are not fetched again. The rates come from Frankfurter (api.frankfurter.dev), and are only requested when you open the currency picker or have chosen a currency other than pounds | Your currency choice: until you change it or clear your browser storage. Exchange rates: replaced each day Hububb documentation |
hostie:agents (browser storage) | Hububb | Remembers which assistants you switched on in the Hostie help widget | Until you change it or clear your browser storage |
| Google Maps (only where a map or place search is shown) | Shows maps and place suggestions | Set by Google under its own policy, not by us. In our checks no cookies were set when the map loaded. We set nothing for it on hububb.com Google documentation | |
| Calendly booking calendar (only when you book an onboarding call) | Calendly | Lets you pick a time for a call with us | Set by Calendly under its own policy, not by us. Calendly does not publish a full list. In our checks its booking calendar set Cloudflare security cookies, a OneTrust consent cookie, a Google reCAPTCHA cookie and a Stripe fraud prevention cookie, lasting from one visit up to about 13 months. We set nothing for it on hububb.com Calendly documentation |
3.4 Targeting (off until you opt in)
These help us measure and improve our advertising, and show Hububb adverts to people who may be interested in our services. They work with advertising companies, who may link what they learn from our Platform to what they already know about you.
| Name | Set by | What it does | How long |
|---|---|---|---|
_fbp | Meta (Facebook and Instagram), via the Meta Pixel | Identifies your browser so Meta can measure and optimise our adverts | 90 days Meta documentation |
_fbc | Meta, via the Meta Pixel | Records that you arrived after clicking a Meta advert | 90 days Meta documentation |
lastExternalReferrer, lastExternalReferrerTime (browser storage) | Meta, via the Meta Pixel | Notes which site sent you to us | Until you turn Targeting off or clear your browser storage Meta documentation |
hububb_utm | Hububb | Remembers which advert or campaign brought you to us (the campaign tags and any advert click ID in the link you clicked), so we can see which adverts work | 90 days |
hububb_attr_first, hububb_attr_last (browser storage) | Hububb | Same purpose as hububb_utm; records the first and the most recent campaign | 90 days |
hububb_lead_event_id, hububb_schedule_event_id, hububb_event_id:<event> (browser session storage) | Hububb | Gives a form you send one reference number, so the Meta Pixel and the Meta Conversions API count it once and not twice | Until you close the tab |
| Meta Pixel (ID 1105328470979971) | Meta (Facebook and Instagram) | Code in your browser that tells Meta which pages you view and what you do on them, such as sending a form | Sets the Meta cookies and storage entries listed above Meta documentation |
| Meta Conversions API (server-side, no cookie) | Hububb, to Meta | A connection from our servers to Meta. When you send us a form, we send Meta a record that this happened (see section 5) | No cookie. Information already sent is held by Meta under its own policies Meta documentation |
We do not currently use Google Analytics.
4. Why we use these technologies
- To let you use the Platform, sign in, pay safely and keep your account secure (Strictly necessary).
- To understand how people use the Platform, find faults and improve it (Performance).
- To remember your choices and provide helpful features (Functional).
- To measure our advertising and show our adverts to people who may be interested (Targeting).
- To keep a record of your cookie choices, so we respect them and can show we did.
5. Meta Pixel and Meta Conversions API
If you turn on Targeting, we use two tools from Meta Platforms Ireland Limited (and its group companies) to measure our advertising.
- The Meta Pixel (ID 1105328470979971) is code in your browser. It tells Meta which pages you view and what you do on them, such as sending a form.
- The Conversions API is a connection from our servers to Meta. When you send us a form, for example to book a call or to tell us about your property, we send Meta a record that this happened. The record may include your email address, phone number and name (each scrambled by a process called hashing before sending), your IP address, your browser and device type, the page address, and the cookie values
_fbpand_fbc.
Meta uses this to match the form to an advert, to measure how well our adverts work, and to improve advert delivery. Hashing makes the details harder to read, but they can still identify you, so we treat them as personal data.
If you do not turn on Targeting, we do not load the Meta Pixel, we do not set the Meta cookies, and we do not send anything about you to Meta, including when you send us a form. If you turn Targeting on and later turn it off, we stop at once and delete the Targeting cookies from your browser. We will not send anything further to Meta, though information already sent is held by Meta under its own policies.
Meta acts as an independent company, and in some respects we and Meta make joint decisions about this data. Under Meta's Business Tools Terms, we and Meta are joint controllers for collecting this information through the Meta Pixel and the Conversions API and sending it to Meta, for purposes such as targeting and delivering adverts. After Meta receives it, Meta uses it as an independent company under its own policies. You can ask us or Meta to exercise your rights over this information, and we will pass on requests that Meta needs to handle. See Meta's own Cookies Policy and Privacy Policy. Some of this data is transferred outside the UK. We explain the safeguards in our Privacy Policy.
6. Who else is involved
Companies that may set cookies or receive information through the Platform, depending on your choices, include:
- Meta Platforms Ireland Limited (Meta Pixel and Conversions API) (Targeting)
- PostHog (analytics and session recordings, EU cloud) (Performance)
- Stripe (payments and fraud prevention) (Strictly necessary)
- Google (Firebase sign-in; and Google Maps) (Strictly necessary; Functional)
- Cloudflare (bot protection) (Strictly necessary)
- Cal.com (booking calendar, loaded only when you ask to book a call) (Strictly necessary)
- Calendly (booking calendar) (Functional)
We choose these partners carefully. Each uses the information under its own privacy policy as well as our instructions. Our Privacy Policy lists what each one receives and where it is processed.
7. Your choices
On our Platform. When you first visit, we ask you to choose. You can accept all, keep only the necessary cookies, or manage your preferences by category. All three options are equally easy. If you choose "Only necessary", you can still use the whole Platform.
Changing your mind. Select "Cookie settings" at the bottom of any page at any time to change your choices. Withdrawing consent is as easy as giving it. When you withdraw, we stop using those technologies, tell our partners where we need to, and remove the cookies we can from your browser.
How long we remember your choice. We ask again after 6 months, or sooner if we add new tools or change how we use cookies.
Your browser. You can also block or delete cookies in your browser settings. Blocking Strictly necessary cookies may stop parts of the Platform working. Your browser's help pages explain how.
Advertising choices. You can manage how Meta uses information to show you adverts in your Facebook or Instagram ad settings. You can also use Your Online Choices to opt out of interest-based advertising from taking part companies. These tools are run by others, and we do not control them.
8. Changes to this policy
We may update this policy, for example if we add a new tool. We will change the "Last updated" date at the top. If a change affects the cookies we ask your permission for, we will ask you to choose again.
9. Contact and complaints
If you have a question about cookies or how we use your data, email us at support@hububb.com, or write to Hububb Technologies Ltd, 27 Old Gloucester Street, London WC1N 3AX, United Kingdom.
To make a data protection complaint to us, email support@hububb.com with "Data protection complaint" in the subject line. We will acknowledge it within 30 days (we aim for much sooner), look into it, and tell you the outcome. You also have the right to complain to the Information Commissioner's Office at ico.org.uk or on 0303 123 1113.