HelloMeThis page covers the web version of HelloMe, used in a browser. It sets out every piece of information placed on your device, what it is for and how long it stays.
1.The short version
HelloMe uses no advertising cookies, no analytics cookies and no third-party trackers. We place nothing to follow you from one site to another, and no ad network reaches your browser through us.
What we do place is limited to what the service strictly needs to work: one cookie to remember your language, and a few items kept by your browser to keep you signed in and to hold your preferences.
Since none of these items serve advertising or analytics, the law does not require a consent banner: they are essential to the service you asked for. You still stay in control, as explained below.
3.What your browser keeps
The items below stay in your browser's local storage, on your device. Unlike a cookie, they are not sent automatically with every request.
| Name | Role |
|---|---|
| hellome.token | Your sign-in token: it is what saves you from typing your password every time you open the app. |
| hellome.user | A copy of your profile, so the app can appear immediately without waiting for the network. |
| hellome.deviceId | A device identifier, to recognise this session in the list of your devices. |
| hellome.theme | Your choice of light, dark or automatic theme. |
| hellome.phoneCountry | The last country chosen for your number, so it can be offered by default. |
| hellome.chatPrefs.v1 | Your per-conversation preferences: wallpaper, translation, media loading. |
| hellome.chatLock.v1 | The chat lock set up on this device. |
| hellome.emoji.recent | The emoji you have just used. |
| hellome.channels.hidden | The channels you have hidden from the list. |
| hellome.assistant.history | Your current conversation with the assistant. |
| hellome.permissions.asked | Remembers that the permission prompt has already been shown to you, so it is not repeated. |
Two items last only as long as the tab and disappear when it closes: "hellome.chatLock.unlocked", which remembers that a locked conversation was opened during this session, and "hellome.plannedCallAlerts", which avoids showing you the same scheduled-call reminder twice.
4.The admin console
The console reserved for our team keeps the administrator's session token, email address, theme choice and menu state in their browser. It is not open to the public and places nothing on the devices of the people who use the service.
5.The chat window on a company's website
When a company installs the HelloMe live chat on its own site, the window keeps one thing in your browser: a token that lets you find your conversation again if you reload the page or come back later. It is kept by the company's site, not by us, and serves nothing else.
| What is kept | Where | What for | How long |
|---|---|---|---|
| hellome.livechat | Local storage of the company's site | Finding your conversation when you come back | Until you clear the site's data |
That token is neither an advertising cookie nor an identifier that follows you from site to site: it is worth something only with the company you are chatting to. Another company using HelloMe can neither read it nor recognise you through it.
Clearing the site's data, or chatting in a private window, starts you on a fresh conversation: neither the company nor we can then connect you to what you wrote before.
6.Items placed by third parties
Some features call on outside services which may, at the moment you use them, place their own technical information: carrying an audio or video call, showing a preview image for a link you share, or searching for an animation.
These items serve the feature you asked for. We make no advertising use of them, and we deliberately embed no social network button that could track you on our pages.
7.What you can do
- Your browser lets you view and delete cookies and site data, site by site. Deleting them signs you out of HelloMe and erases your local preferences.
- You can browse in private mode: everything is erased when the window closes.
- In the app, "My devices" lets you sign a session out: the matching token then stops working, even if it remains in the browser concerned.
- Refusing local storage stops the web version from working: without a stored token, the session cannot be kept from one page to the next.
A question about this page: support@gracelab.io.
These documents are written and checked in French and in English. The French version is the reference for readers in French-speaking countries; the English version applies everywhere else. Whatever language HelloMe is displayed in, only these two versions are binding.