Current as of 1 Oct 2025
Cookie Policy
Your privacy is important to us at Hellomatik. We respect your privacy regarding any information we may collect from you across our website.
Controller: HELLOMATIK, S.L. (CIF B22803126)
Contact: contact@hellomatik.com
Effective date: 1 October 2025 — Last updated: 1 October 2025
1) What are cookies and similar technologies?
We use cookies and similar technologies (e.g., local storage, SDKs, pixels, and device fingerprinting) to operate the site, remember your preferences, secure our services, and measure usage. In Spain, use of these technologies is governed by Article 22.2 LSSI and in the EU by Article 5(3) ePrivacy; when consent is required, it must meet GDPR standards and the AEPD Cookie Guide.
2) Types of cookies we may use
By purpose
Strictly necessary (technical/security) required for core functions (login, security, load-balancing, fraud/bot mitigation). Consent is not required.
Preferences remember settings such as language or interface; consent is required unless you actively choose the setting (e.g., pick a language).
Analytics/measurement understand visits and engagement; consent required (in Spain, "Accept" and "Reject" must be equally prominent in the first layer).
Advertising/targeting (if used) interest-based ads/remarketing; consent required.
By duration: session (deleted on close) / persistent (e.g., 24 h, 30 d, 400 d; subject to browser limits).
By party: first-party (set on hellomatik.com) / third-party (set by external providers).
3) Legal basis and consent
We do not set non-essential cookies/technologies without prior consent. Our banner's first layer presents Accept, Reject, and Settings with equal prominence; doing nothing is not consent. You can change your choices any time via the persistent "Cookie Settings" link.
4) Managing cookies
Cookie Settings: Use the footer link to accept, reject, or select purposes/vendors at any time.
Browser controls: You can also block/delete cookies in your browser (Chrome, Firefox, Safari, Edge, Opera). Blocking strictly-necessary cookies may break functions.
5) Third-party providers and international transfers
Some vendors (e.g., Google for analytics, Cloudflare for bot mitigation) may process data outside the EEA/UK. Transfers rely on a valid mechanism (e.g., EU-U.S. Data Privacy Framework for certified U.S. organizations, or Standard Contractual Clauses). You can verify DPF status in the official public list. The Cookie Settings panel shows vendor-specific details.
6) Children
Where consent is required, Spanish law sets the digital age of consent at 14; below that age, consent must be provided by a holder of parental responsibility.
7) Cookie walls
We do not condition access to our site on accepting non-essential cookies. Any future alternative models (e.g., paid alternative) will follow EU guidance on freely-given consent.
8) The current list of cookies and technologies
The live list (name, provider, purpose, duration, first/third-party, and transfer info) is always available in Cookie Settings and updates dynamically via our Consent Management Platform (CMP).
Illustrative examples
(actual items depend on your current setup — see Cookie Settings for the authoritative list)
Strictly necessary: cookies_enabled — first-party — stores cookie consent preference — 1 year.
Strictly necessary: cookie_essential, cookie_analytics, cookie_marketing — first-party — store individual cookie type preferences — 1 year.
Analytics (GA4): _ga, _ga_<container-id> — first-party (provider: Google) — distinguish users/sessions — up to ~400 days in Chrome (shorter in Safari due to browser limits). We block GA4 until analytics consent is granted and send Consent Mode v2 signals.
Marketing (Calendly): Calendly widgets may set cookies for scheduling functionality — third-party (provider: Calendly) — loaded only after marketing consent is granted — session/persistent per Calendly's policy.
9) Google Consent Mode (v2)
For Google tags we implement Consent Mode v2. Before consent, analytics and ads storage are denied; after consent, tags adjust behavior accordingly. If we enable advertising features in the future, we will also set ad_user_data and ad_personalization signals.
10) Changes to this policy
We will update this page and seek new consent when introducing new purposes or vendors that require it.