What this site stores in your browser.
A cookie or a browser-storage entry is a small piece of data a site keeps on your device. Here, category by category, is what this site uses, why and for how long. Last updated: September 28, 2026.
Terms we use
Cookie: a small file a site stores in the browser and that is sent with every request. localStorage: browser storage that is not sent to the server (this is how we store your cookie decision). Third-party storage: cookies or data another domain (for example cal.com) stores when you use its service. Technical logs: per-request data processed by the server (IP, browser), storing nothing on your device.
How we decide what loads
Nothing non-essential loads without your permission. On your first visit, analytics and marketing are off. Your decision is stored in this browser (record “cc_consent”, never sent to third parties) for 180 days; if we change the categories or providers, we ask again.
Analytics or marketing providers are currently configured; that is why you see the cookie notice.
Necessary
Always active: without them the site cannot provide the function you request.
| Provider | Purpose | Cookies / storage | Duration | When it loads | Status |
|---|---|---|---|---|---|
| Ciancoders (primera parte) | Remember your cookie decision so we don’t ask again on every page. | localStorage “cc_consent” (version, timestamp and accepted categories) | 180 days | When you decide in the cookie notice. | Active on this site |
| Cloudflare | Site hosting and delivery network (Workers, static assets). | No cookies in our current configuration. Technical request logs (IP, browser) for security. | Per Cloudflare’s retention policy | Always (it is the server). | Active on this site |
| Cal.com | Call scheduling. It is the function you request when you click “Book”. | Cal.com’s own cookies and storage inside its scheduling window (third party). | Per Cal.com | Only when you interact with a booking button (pointerover, focus or touchstart on the button); never eagerly. | Active on this site |
| Web3Forms | Email delivery of the site’s forms (Software Readiness Assessment). | No cookies. Receives the form data when you submit it. | Not applicable | When you submit the form. | Active on this site |
| hCaptcha (vía Web3Forms) | Anti-spam protection for the Software Readiness Assessment: verifies the submission comes from a person. Web3Forms validates the response server-side. | hCaptcha’s own storage inside its widget (third party), governed by its policy | Per hCaptcha | Only when reaching the final step of the assessment (contact details); never on initial load or other pages. | Active on this site |
Analytics
Only with your permission.
| Provider | Purpose | Cookies / storage | Duration | When it loads | Status |
|---|---|---|---|---|---|
| Google Analytics 4 | Measure how the site is used (pages, events such as booking or completing the assessment), with IP anonymization and Consent Mode. | Cookies “_ga” and “_ga_<ID>” (first-party, written by Google’s SDK) | According to the active Google Analytics property configuration, within Google’s platform limits (exact setting pending admin validation) | Only after accepting “Analytics”. Consent Mode v2: everything denied by default; only analytics_storage becomes granted with Analytics. | Active on this site |
| Microsoft Clarity | Qualitative behavioral analytics: session recordings, heatmaps, click and scroll behavior, to improve the site experience. | First-party cookies “_clck” (user id) and “_clsk” (session) written by the script; Microsoft cookies on its own domains (for example “CLID”, “MUID”, “ANONCHK”, “MR”, “SM”) | Per Microsoft Clarity documentation: “_clck” up to 1 year, “_clsk” 1 day; Microsoft-domain cookies per Microsoft. Recording and heatmap retention per the Clarity project configuration (exact setting pending admin validation). | Only after accepting “Analytics”, once per page. Masking: the Software Readiness Assessment, the booking form and the calendar carry data-clarity-mask (content hidden in recordings); form fields are additionally masked by the project configuration. | Active on this site |
Marketing
Only with your permission.
| Provider | Purpose | Cookies / storage | Duration | When it loads | Status |
|---|---|---|---|---|---|
| Meta Pixel | Measure Meta campaign conversions and build audiences. | Cookies “_fbp” and “_fbc” | Up to 90 days (per Meta’s documentation) | Only after accepting “Marketing”: fbq(consent, grant) → init → PageView. Never initialized with Analytics alone. | Not currently active |
| Apollo.io (website visitor tracking) | Identify companies visiting the site for the sales team. | Apollo’s own cookies and identifiers (not documented in detail by the vendor) | Per Apollo | Only after accepting “Marketing”. Categorized as marketing because its purpose is sales prospecting, not site measurement. | Not currently active |
Changing your decision
You can accept or withdraw each category at any time. When you withdraw consent, we stop loading those providers on subsequent pages, disable the ones already loaded on the current page and delete the first-party cookies they write (for example “_ga”, “_clck”, “_fbp”). Cookies a third party has stored on its own domain can only be removed from your browser or from that provider.
What happens when you withdraw consent, by provider
- Google Analytics 4
- Consent Mode set to denied and “_ga”, “_ga_*”, “_gid” and “_gat” cleared where possible.
- Microsoft Clarity
- clarity(consent, false) and “_clck”/“_clsk” cleared; not loaded again on subsequent pages. Cookies on Microsoft domains cannot be deleted from this site.
- Meta Pixel
- fbq(consent, revoke) and “_fbp”/“_fbc” cleared where possible. Cookies on the facebook.com domain cannot be deleted from this site.
- Apollo.io (website visitor tracking)
- Not loaded again on subsequent pages. Apollo offers no documented opt-out API: an already-loaded SDK remains until navigation or reload.
Contact
Questions about this policy: ventas@ciancoders.com.