Cookies and local storage
What GatPilot keeps in your browser, why and for how long.
Last updated: 9 October 2026 · Version 3
In short
Your browser, in six lines
The summary helps you find what matters; the full text below is the one that applies.
No advertising or tracking cookies.
We collect visit statistics without cookies.
On an ordinary visit: no cookie on gatpilot.md, a single one on gatpilot.com, for the currency of the prices.
The chat button remembers its colour and, once you open it, the conversation.
The dashboard remembers your sign-in, so that you do not have to type your password on every visit.
You can delete them at any time, in your browser settings.
01 · About
Who we are and what the policy covers
The GatPilot websites, dashboard and chat widget.
GatPilot is a service operated by TOPFED WEB S.R.L., a limited liability company registered in the Republic of Moldova under IDNO 1026023125543. The company's registered office is in Chișinău, Republic of Moldova.
The policy shows what gatpilot.md, gatpilot.com, the GatPilot dashboard and the chat widget that businesses put on their websites keep in your browser.
Cookies are small text files that a website saves in the browser and receives back with every request. Local storage and IndexedDB, a small database in the browser, also keep data in the browser, but do not send it on their own.
Below we call them “keys” for short and show each one, with its place, role and duration.
02 · Keys
What we keep in the browser
Every cookie and every key, with its place, role and duration.
| Name | Where | What for | How long | Type |
|---|---|---|---|---|
gp_currency | Cookie, only on gatpilot.com, set by the website's pages. | The currency you see prices in: EUR, USD or GBP. On your first visit we choose it from your country, and you can change it with the currency switch. | 12 months. | Preference. |
| The sign-in session | IndexedDB (firebaseLocalStorageDb), in the dashboard and on the sign-in pages of gatpilot.com. If the browser has no IndexedDB, local storage. | Keeps you signed in, so that you do not have to type your password on every visit. | Until you sign out. | Strictly necessary. |
firebase-heartbeat-database | IndexedDB, in the dashboard and on the sign-in pages. | The Firebase library records, once a day, the date and its own version, and sends them to Google with the sign-in requests. It contains no data about you. | Until you delete it. | Technical, Firebase's own. |
gatpilot:plan-intent | Local storage, on the account creation page of gatpilot.com. | Remembers the plan chosen on the Pricing page until there is an account to put it on. It is written only if you arrived with a plan chosen. | Until your first sign-in to the dashboard, when we delete it. | Strictly necessary. |
gp-sidebar | Local storage, in the dashboard, on a computer. | Remembers whether you collapsed the side menu. It is written only when you press the menu button. | Until you delete it. | Preference chosen by you. |
gatpilot:accent: followed by the assistant's key | Local storage, on any website with the GatPilot widget, including gatpilot.md and gatpilot.com. | The colour of the chat button, so that it appears straight away in the company's colour. It is written when the widget loads, with no data about you. | Until you delete it. | Functional. |
gatpilot:visitor | Local storage, on any website with the GatPilot widget, including gatpilot.md and gatpilot.com. | A random identifier, so that the conversation continues when you come back. It is written only after you open the chat. | Until you clear the browser's data. | Strictly necessary. |
gatpilot:account-deleted | Session storage, in the dashboard. | Written only when the Owner deletes the account from the dashboard, so that the goodbye page knows the deletion came from there. | Until the goodbye page opens, which deletes it. | Strictly necessary. |
| Cloudflare's security cookie | Cookie, on gatpilot.md and gatpilot.com. | Cloudflare may set it only when it needs to check that the visitor is not an automated program. | Under Cloudflare's rules. | Strictly necessary. |
On an ordinary visit to gatpilot.md we set no cookie. The chat button loads on your first action on the page or after 3 seconds; that is when we store its colour.
The dashboard does not use cookies for sign-in: every request carries an access token, in its header.
On Safari and on phones, Firebase loads, in the dashboard and on the sign-in pages, a hidden page from gatpilot-45e09.firebaseapp.com, its own domain. What that page keeps in the browser is decided by Google.
The GatPilot mobile app does not use cookies. On the phone it keeps the session, the app's language, the language chosen at sign-up for the first assistant, the notification token and whether you have seen the intro screens. It also remembers whether it has already asked for your consent to notifications.
03 · Statistics
How we count visits without cookies
Aggregate statistics, with Plausible, only on the website's pages.
We count visits with Plausible Analytics. The script loads from analytics.buum.md on the gatpilot.md and gatpilot.com pages, but not in the dashboard.
The script sets no cookies and writes nothing in the browser. It only reads the plausible_ignore key, which a person sets themselves if they do not want their own visits counted.
For each page it sends its address, the referring website and the domain. The browser, the operating system, the device type and the country are inferred from the request.
It also measures how far you scroll a page and how long you stay on it, clicks on links to other websites and file downloads.
We also count a few actions, only as categories, never what you write:
- a click to create an account, free or Pro;
- a contact form sent;
- a subscription to GatPilot news;
- opening the demo assistant;
- a click on the email address or the phone number;
- a click on “Log in”;
- a page that does not exist, with its address.
We see only aggregate statistics, on the basis of our legitimate interest in knowing which pages are read.
04 · Widget
For businesses that put the widget on their website
Two keys, in your website's local storage.
The GatPilot widget, that is, the chat button and window, keeps two keys in your website's local storage: the button's colour and the visitor's identifier.
The colour is written when the widget loads, and the identifier only after the visitor opens the chat. The chat window opens in a separate frame, from the GatPilot domain, and sets no cookies.
Mention these keys in your own cookie policy. If your website asks for consent before any storage, load the widget's script only after consent.
05 · Emails
The emails we send you
No tracking pixels added by us.
Our emails go out through Brevo: invitations, codes, password change links, alerts when a customer is waiting and the installation code. GatPilot news also goes out through Brevo, if you subscribe.
In the emails the product sends, we put no images, pixels or tracking links.
Brevo records the delivery of each email. We do not use data about opens or clicks for profiling or advertising.
06 · Control
How you control them
From your browser settings, at any time.
You can delete or block cookies and local storage in your browser settings. What changes then:
- without
gp_currency, on the next page we choose the currency from your country again; - without the widget's keys, the next conversation starts from scratch;
- if you block storage, the dashboard no longer keeps you signed in from one visit to the next;
- without
gp-sidebar, the dashboard's menu opens again; - without
gatpilot:plan-intent, the chosen plan is lost if you have not created your account yet.
The statistics use no cookies, so there is nothing to delete for them. You can stop them with a script blocker.
07 · Changes
If something changes
We update the policy first.
We add a new key to the table above first.
Questions about this policy: info@gatpilot.com.
- : links to the mobile app section of the new Privacy Policy and explains the `gatpilot:account-deleted` key, written when the account is deleted from the dashboard.
- : policy rewritten, with the table of all the keys.
- : statistics described correctly, from analytics.buum.md.
- : policy rewritten for the new website.
Documents
All GatPilot legal documents
The same company and the same rules on gatpilot.md and gatpilot.com.
Legal notice
Who operates GatPilot, how to contact us and where to turn.
Terms of service
The contract for GatPilot: account, plans and payment, your AI key, your content, liability and the applicable law.
Acceptable Use Policy
What is not allowed with GatPilot assistants and what we do when someone breaks the rules.
Privacy Policy
What data we process, why, for how long and what rights you have.
Data Processing Agreement
How we process your customers' and employees' data on your behalf.
Sub-processors
The providers that help us run GatPilot and the data each one receives.
Cookies and local storage
What GatPilot keeps in your browser, why and for how long.
AI transparency
What a GatPilot assistant is and what it means when you write to one.
GatPilotBot
What our crawler reads and how to stop it.
Have a question about this document? Write to us at info@gatpilot.com.