Cookie Policy
This policy explains what fg-platform.com stores in your browser, and what the FG assistant stores when you meet it on one of our customers’ websites. The short version: one cookie, and it exists to keep you signed in.
1. Cookies we set
One, and only when you sign in.
| Name | Purpose | Lifetime | Type |
|---|---|---|---|
fg_session |
Keeps you signed in to your account and console. It holds a random token and nothing else — no name, no email, nothing readable. The token is matched against a session record on our server. | 30 days, or until you sign out | Strictly necessary |
It is set HttpOnly (JavaScript on the page cannot read it), SameSite=Lax (it is not sent along with requests started by other sites) and Secure (it travels only over HTTPS). Signing out deletes it on both ends: the cookie in your browser and the session row in our database.
2. Cookies we do not set
- No advertising or cross-site tracking cookies. We do not run ad networks, retargeting pixels or social buttons.
- No analytics cookies. There is no analytics script on this site.
- No third-party cookies. Our pages load no scripts, fonts, styles or media from anyone else’s domain — everything, including the 3D library and the speech-detection model, is served from fg-platform.com. A domain that is never contacted cannot set a cookie.
Because the only cookie we set is strictly necessary for a service you asked for by signing in, no consent banner is required for it under the ePrivacy Directive or the GDPR. If we ever add anything that is not strictly necessary, we will ask first.
3. Browser storage, which is not a cookie
Some things are kept in your browser’s localStorage and sessionStorage instead. They are never sent to us automatically the way a cookie is: our code reads them on your device and sends only what a feature needs. sessionStorage is erased when you close the tab.
| Key | What it holds | Where | Lifetime |
|---|---|---|---|
fgVisitorId | A random identifier so repeat conversations with the same assistant read as one visitor in the business’s dialogue log. Random — not derived from you or your device. | Assistant | Until you clear site data |
fgWidgetSid | A random identifier for the current conversation, so the assistant keeps the thread. | Assistant | The tab |
fgWidgetMsgs, fgChatMsgs | The last twenty turns of the conversation, so reloading the page does not lose what you were saying. | Assistant, /chat | The tab |
fgWidgetPos, fgWidgetSize, fgWidgetTpl:… | Where you dragged the assistant, what size you gave it, and which design the business chose. | Assistant | Until you clear site data |
fgWidgetLead | A flag that you already left your contact details, so you are not asked twice in one visit. | Assistant | The tab |
fg_agent_quiz_v3 | Your answers while building an agent, so closing the tab mid-way does not start you over. | Setup flow | Until you clear site data |
fgHeroSeen, fgCvSeen, fgSpeed, fg.desktop-agent.downloaded | Small display preferences: whether the opening animation has already played in this tab, when you last read the dialogue log, the speaking speed you set in the playground, and whether you have downloaded the desktop app. | Site, console | The tab, or until you clear site data |
4. When you meet the assistant on another company’s website
The assistant is embedded by that company, and the conversation belongs to them: they are the controller of it, and we process it on their behalf under our Data Processing Addendum. The assistant sets no cookies on their site. It uses the browser-storage keys in the table above, scoped to that site, and it does not follow you from one website to another — the identifiers are per-site and cannot be read across domains.
5. Controlling what is stored
- Every browser can block or delete cookies and site data, usually under Privacy settings. Deleting
fg_sessionsigns you out; deleting the storage keys resets the assistant to how it looks on a first visit. - Private/incognito windows discard all of it when the window closes.
- Blocking the strictly-necessary cookie means you can browse the public site normally, but cannot stay signed in to the console.
6. Consent
We do not show a cookie banner, because there is nothing to consent to: a single strictly-necessary cookie and local storage used to deliver features you have asked for. This is a position we will revisit if the storage above ever grows a purpose that is not strictly necessary.
7. Changes and contact
If what we store changes, this page changes with it and the date below is updated. Questions: privacy@fg-platform.com.