Legal
Halingo cookie policy
Version 1.0. In force from 27 September 2026.
This is a shortened English version of the Dutch cookie policy, with the same substance. The Dutch text is the full and prevailing version. What is stored on your device is the same whichever version you read.
This policy belongs with section 9 of our privacy statement and covers our website, the help centre and the web application at app.halingo.be.
1. Why you see no consent banner
We use no analytics cookies, no marketing cookies and no third-party advertising trackers. We do not measure our visitor statistics with a third party. We do not follow you across other websites and we build no profile of you.
That leaves very little: a handful of technical items needed to make the page and the forms work, plus the language you read in. For that kind of storage the law expressly allows us not to ask consent. Article 129 of the Act of 13 June 2005 on electronic communications, which transposes Article 5(3) of Directive 2002/58/EC, sets out two exceptions: storage strictly necessary to deliver a service you expressly asked for, and storage whose only purpose is to carry a communication.
A banner asking your consent for something we do not do is not protection. It is a click. So we show none.
2. Cookies and browser storage
A cookie is a small text file a website keeps in your browser and reads back on a later visit. Browser storage (sessionStorage and localStorage) is the same idea, except the file is not sent back to the server with every request. The law treats both the same way, which is why they sit in one table below.
3. What we store or read
| Name | Kind | What it does | Retention | Party |
|---|---|---|---|---|
session_id | Cookie | Keeps your session and protects our forms against misuse of that session. The cookie is HttpOnly, Secure and SameSite=Lax, so a script cannot read it and another website cannot send it along | 7 days | First party |
frontend_lang | Cookie | Remembers the language you read our pages in, so you do not have to choose again on every visit | 12 months | First party |
tz | Cookie | Passes your browser time zone to the server so a time can be shown in your own time. Set by the platform our pages run on | Until you close your browser | First party |
hs_last | Browser storage (sessionStorage) | Remembers the last help article you read, so the ticket form can mention it and we can answer in context. Your browser clears it when you close it | Until you close your browser | First party |
presence.focus | Browser storage (localStorage) | Used by the platform to know whether the tab is active | Until you clear your browser data | First party |
_GRECAPTCHA | Third-party cookie | Google’s reCAPTCHA spam protection on our contact form and our ticket form. See section 4 | Up to 6 months | Third party, Google |
4. How the reCAPTCHA spam protection works
Our two public forms, the contact form and the ticket form, are protected by Google reCAPTCHA. Without it they fill with automated messages within days.
reCAPTCHA does not load when you open a page. It loads at the moment you touch a field of the form. If you read a help article or a page of our website without filling a form in, nothing goes to Google.
From that moment Google does receive data, in particular your IP address and signals about how you interact with the page, and it sets the _GRECAPTCHA cookie. Google also uses that data for its own purposes, among them improving its security service. Google is not our processor there but an independent controller. What Google does with the data is set out in its privacy policy and its terms of service.
We do not ask consent for this, because it protects the form you opened yourself and because nothing loads until you use that form. If you would rather reach us without Google involved, write directly to support@halingo.be or info@halingo.be.
5. Two items we are having removed
We would rather be honest than fully reassuring.
tz and presence.focus are set by the platform our pages run on, not because our pages need them. A help article does not need your time zone, and an informational page does not need to know whether your tab is active. They hold no identifier and we do not use them to recognise or follow you, but they do not fall under the exceptions in section 1.
We are not asking your consent for them. We are having them removed. Once that is done, both rows disappear from the table in section 3.
6. What you can do
You can refuse, block or delete cookies in your browser settings, and you can clear browser storage along with your browsing data. The exact route differs per browser and is described in your browser’s own help pages.
If you refuse session_id, our ticket form and our contact form do not work and you cannot sign in to app.halingo.be. If you refuse frontend_lang, you have to choose your language again on every visit.
7. Changes
We adapt this policy whenever we change something on our pages that affects what is stored on your device. The current version is always on this page, with a version number and a date.
8. Questions
Write to us at support@halingo.be.
Autopilot Pte. Ltd., 160 Robinson Road, #14-04 Singapore Business Federation Centre, Singapore 068914, Singapore
UEN 202011848W
You may also lodge a complaint with the Gegevensbeschermingsautoriteit, Drukpersstraat 35, 1000 Brussels, contact@apd-gba.be.
Related documents. Terms and conditions · Privacy statement · Data processing agreement