1. About this policy
flo.space is a product of FLO SPACE LLC ("Company," "we," "us," or "our"). This policy explains the cookies and similar technologies used on the flo.space website, and — just as importantly — the ones we do not use. It sits alongside our Privacy Policy, which describes how we handle personal data more broadly. Where this policy uses the word "cookies" it also covers similar client-side technologies such as browser local storage, session storage, pixels, and device fingerprinting.
2. What cookies and similar technologies are
A cookie is a small text file that a website asks your browser to store, so it can be read back on later requests. Related technologies — local storage and session storage — store data in your browser in a similar way. Pixels (tiny images or scripts) and fingerprinting techniques can identify or profile a device without storing anything at all, often just from the network request a page makes to load an external resource. All of these are "tracking technologies," and most privacy laws treat them the same way regardless of the label.
3. Our honest position
We have kept this site intentionally lean. As of the effective date above:
- We set no first-party cookies of our own.
- We do not use browser local storage or session storage to track you.
- We run no web analytics — there is no Google Analytics, no Tag Manager container, and no tool that measures how you move around the site.
- We run no social or third-party ad pixels — there is no Meta/Facebook, TikTok, or LinkedIn tracking. We do use Google Ads conversion measurement, so we can tell which advertisements lead to signups. It loads only if you accept the consent banner, and it is listed in the table below.
- We use no session recording (such as Hotjar or FullStory) and no chat widget.
This website transfers data to third parties in three ways, all listed in the table below: an advertising tag that records whether a visit became a signup and a webfont load, both blocked until you accept, and the Cal.com booking page, which loads only when you open it. In each case the third party can see your IP address. None is essential to reading the site, and we do not ourselves build a profile of you.
4. Technologies and third parties we use
| Name | Provider | Type | Purpose | Data it can receive | Consent required? |
|---|---|---|---|---|---|
| Consent preference | flo.space (first party) | Strictly necessary | Stores your choice from the consent banner (accept or reject) so we can honour it and not ask again on every page. | Your consent choice only. Stored locally in your browser; not sent to us as a cookie for tracking. | No — required to record your own choice. |
| Live demo settings | flo.space (first party) | First-party / on request | Remembers how you left the live demo at flo.space/preview, such as its layout and recent searches. | Your demo settings only. Stored locally in your browser; never sent to us. | Not through the banner. Written only when you open the demo. |
Google Ads conversion tracking (gtag.js, _gcl_*) | Google LLC | Third-party / advertising (non-essential) | Records that a visit turned into a signup, so we can tell which advertisements are worth paying for. | Your IP address, browser user-agent, the pages you view on this Site, and any Google advertising identifiers already in your browser. Google sets its own _gcl_* cookies. We do not send Google your name, email address, or phone number. | Yes. The script is not requested at all until you accept, and it starts with every Google Consent Mode signal set to denied. Declining blocks it entirely; the site is unaffected. |
| Google Fonts | Google LLC | Third-party / functional (non-essential) | Loads the site's typefaces from fonts.googleapis.com and fonts.gstatic.com for consistent typography. | Your IP address and browser user-agent, transmitted to Google when the font files are requested. | Yes. Blocked until you consent; the site falls back to standard system fonts if you decline. |
| Cal.com booking page | Cal.com, Inc. | Third-party / on request | Lets you book a call with us. | Your IP address, browser user-agent and the address of the page you are on when the booking page loads, and what you type into it. Cal.com may set its own cookies inside the booking page. | Not through the banner. It loads only when you open Book a call or the Custom plan window, or press "Load the booking page (Cal.com)" on flo.space/meet. |
A non-essential load ("functional / third-party") is one the site can work without. A consent tool controls whether these non-essential third-party resources are loaded at all — see the next sections. The Cal.com booking page is the exception: it loads only when you open it.
5. Legal basis and consent
In the EU and UK, the ePrivacy rules and the GDPR require your prior consent before non-essential technologies are used or before content is loaded from a third party that can receive your data. The consent-preference storage in the table above is strictly necessary — it exists only to remember your choice — and does not require consent. The two Google items, Google Ads conversion tracking and Google Fonts, are non-essential, so we ask for your consent before either runs. The Cal.com booking page loads only when you open it.
We take this seriously in part because loading Google Fonts from Google's servers without consent transmits the visitor's IP address to Google, and courts in Germany have found that doing so without a lawful basis breaches the GDPR. Our default is therefore to hold these loads back until you decide.
When you first visit, a consent banner offers two clear choices:
- Accept — allow the non-essential third-party load described above.
- Reject non-essential — block it. The site continues to work: it uses your device's built-in system fonts instead of Google Fonts.
Until you make a choice, non-essential loads stay blocked. Rejecting has no cost to you beyond the cosmetic fallbacks noted above.
6. Managing and withdrawing your consent
Your choice is not permanent. You can reopen the consent preferences at any time from the link in the site footer to change or withdraw it, and the change takes effect immediately for future page loads. Withdrawing consent does not undo transfers that already happened while consent was in place, but it stops any further non-essential loads.
You can also control these technologies in your browser. Most browsers let you block or delete cookies and site data, block third-party requests, or use private/incognito windows. Because we set no tracking cookies of our own, browser controls mainly affect the third-party services listed above. Blocking those third parties in the browser has the same practical effect as rejecting them in our banner.
7. Do Not Track and Global Privacy Control
Some browsers can send a "Do Not Track" (DNT) or Global Privacy Control (GPC) signal. There is no universal standard for how a first-party site must respond to DNT, so we do not rely on it. We do not sell personal data. Google Ads conversion measurement, which may count as "sharing" under some US state privacy laws, runs only after you accept the consent banner. Your banner choice remains the most direct way to control the non-essential loads on this site.
8. Changes to this policy
If we add or remove a technology — for example, if we ever introduce analytics — we will update this policy, the table above, and the consent banner before that change takes effect, and we will revise the "last updated" date. Material changes will be made prominent on the site.
9. Contact
Questions about this policy or your choices can be sent to hello@flo.space. For more on how we handle personal data generally, see our Privacy Policy.
Related: Privacy Policy · Terms of Service · Cookie Policy · Early Access Terms · Accessibility Statement