Cookie policy

The principle

At Cloud y Olé we use technical cookies that are necessary for the operation and security of the website and, subject to consent, analytics cookies to understand how the site is used in aggregate. Analytics cookies are not loaded until you accept them.

Until you decide, no measurement tool is loaded. Pages with a form, the demo page and the pack pages, load the HubSpot form, which is what lets you send it. The banner has no highlighted option: accepting and rejecting carry the same visual weight and both take one click.

What cookies are

Cookies are small text files stored on your device when you visit a website. They let the site remember information about your visit, such as your preferred language or the pages you have viewed.

Technical cookies, no consent required

These are essential for the site to work and do not require your permission because they are not used to profile you or for advertising.

• cf-consent: stores your decision about analytics cookies so we do not ask you again. Expires after one year.
• locale: remembers the language you are browsing in. Expires after one year.
• __cf_bm: set by Cloudflare on HubSpot domains when the form loads, to tell people from bots. Technical, for security. Expires after 30 minutes.
• __cf_bm and _cfuvid (calendly.com): set by Cloudflare for Calendly when the booking calendar opens, for the security of the booking. The first expires after 30 minutes; the second when the browser session ends.

Analytics cookies, only if you accept

These help us understand which pages are useful and which are not. They are not loaded until you press «Accept» on the banner, and if you later reject them they are deleted.

• Google Analytics 4 (_ga and _ga_*), from Google, acting as processor: measurement of visits and navigation with a pseudonymous identifier: pages viewed, visit duration and device type. Google sets them for up to two years; current browsers cap them at 400 days. If you reject the notice, the Google Analytics script is never downloaded or executed.
• HubSpot (hubspotutk and similar): session attribution when a form is submitted. Only if HubSpot tracking is switched on, which it currently is not.

What exactly we measure

Besides the pages that get visited, we record four interactions so we can tell whether the site is useful and not just how many people arrive. None of them collects personal data or the content of what you type: only that the action happened, and from which page.

• Pressing a call-to-action button: which button, and which page you were on.
• The form on the demo page becoming visible.
• The form being submitted successfully, or the submission failing: the latter tells us the form is broken, which we would otherwise take weeks to notice.
• Switching language.

And what we do not measure

We use no advertising or profiling cookies, we do not share the data with social networks or advertisers. If you reject analytics cookies the site works exactly the same: nothing degrades and you are not asked again.

The demo form

The form on the demo page is served by HubSpot inside an iframe. It is a form you fill in deliberately, so it does not depend on cookie consent: what you send reaches us because you sent it. The basic data protection information is shown below each form.

The HubSpot forms on this site display the HubSpot branding. That branding loads in a HubSpot frame of its own (app-eu1.hubspot.com) that stores the following items in your browser's session storage (sessionStorage); they do not depend on your choice about analytics cookies and are deleted when you close the tab:

• __hmpl: device and session identifier that HubSpot uses to measure the use of the branding on its forms. HubSpot's, for its own measurement purposes.
• HUBLYTICS_EVENTS_*: queue of events for HubSpot's analytics. HubSpot's, for its own measurement purposes.
• rhumb_transition_history: HubSpot performance measurement, including the page address. HubSpot's, for its own measurement purposes.

When the booking calendar opens

If you choose a slot after requesting the demo, the calendar is served by Calendly in a pop-up window, and Calendly in turn loads Stripe's anti-fraud system, which stores identifiers (_ab, _mf, 1 and id) in your browser's session storage. Those cookies and that storage belong to Calendly and Stripe; see their privacy policies at calendly.com/privacy and stripe.com/privacy.

How to manage cookies

You can set your browser to accept or reject all cookies, or to warn you each time one is stored. Check your browser's settings and help for how to change these preferences. Note that if you disable technical cookies, some features of the site may not be available.

Your decision about analytics cookies is stored in your own browser. You can change it at any time from the «Cookie preferences» link in the footer: withdrawing consent is as easy as giving it.

Updates to this policy

Cloud y Olé may amend this Cookie Policy in response to new legislative or regulatory requirements, or to adapt it to the instructions issued by the Spanish Data Protection Agency. We recommend reviewing it periodically.

If you have any questions about our cookie policy, write to us at contacto@cloudfortress.es.