Last updated: 17 Mar 2026
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., with registered office at Calle Lago de Sanabria 60, 28981 Parla, Madrid, Spain, registered in the Mercantile Registry of Madrid (CIF B22803126)
Contact: contact@hellomatik.com
Effective date: 1 October 2025. Last updated: 17 March 2026
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 the UK, "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).
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.
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.
Some vendors (e.g., Google for analytics and tag management via GA4 and GTM, 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.
Where consent is required, UK law sets the digital age of consent at 13; below that age, consent must be provided by a holder of parental responsibility (subject to any stricter sector-specific laws).
The live list (name, provider, purpose, duration, first/third-party, and transfer info) is always available in Cookie Settings and is updated when we add or remove technologies.
(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.
For Google tags (GA4, GTM), we use a script-blocking approach: analytics scripts are not loaded at all until you grant analytics consent. Before consent, no data is sent to Google. After consent is granted, GA4 and GTM scripts are loaded and begin collecting data. If we enable advertising features in the future, we will implement Google Consent Mode v2 with appropriate deny-by-default signals.
We will update this page and seek new consent when introducing new purposes or vendors that require it.