Overview
This Cookie Policy explains how Flona AI uses cookies and similar technologies when you visit flona.ai or use the Flona application. It sits alongside our Privacy Policy and uses the same defined terms.
Last updated: August 13, 2026.
What are cookies
Cookies are small text files that a website places on your device so it can remember things about you, such as that you are signed in or that you prefer a certain layout. We also use similar technologies such as local storage, session storage, and pixels. In this policy, we refer to all of them as "cookies".
Cookies are either first-party (set by Flona) or third-party (set by a vendor we use, such as our authentication provider).
Cookie categories we use
- Strictly necessary. Required for the Service to work. These include sign-in and session cookies and the cookie that stores your consent choices. You cannot turn these off; if you block them, parts of Flona will not work.
- Functional. Remember preferences that make Flona easier to use, such as whether your sidebar is collapsed. Some dashboard preferences are written when you use the relevant control. You can remove them through browser settings.
- Analytics. Help us measure how people use Flona so we can improve it. This can include cookieless traffic and performance measurement, product analytics, interaction measurement, attribution, and sampled session replay. In regions where prior consent is required, non-essential analytics are held until consent. Elsewhere they may run by default unless you reject or later withdraw analytics consent.
- Marketing. Help us measure and improve our advertising (for example conversion tracking from ad clicks to sign-ups). We only load marketing cookies if you explicitly accept the marketing category in the banner.
Cookies currently set by Flona
The table below lists the principal cookies and browser-storage identifiers used by the main Flona application. Authentication cookies can vary in their exact suffixes, and equivalent identifiers may change as the application is updated.
| Name | Category | Purpose | Duration |
|---|---|---|---|
| Authentication session cookies (names and suffixes may vary) | Strictly necessary | Keeps you signed in and protects your account against session hijacking. | Session or up to 1 year |
| sidebar_state | Functional | Remembers whether you left the dashboard sidebar open or collapsed. | 7 days |
| flona_country | Strictly necessary | Stores the country code supplied by our hosting edge so the application can apply region-appropriate analytics consent rules. | 180 days |
| flona_cc_cookie | Strictly necessary | Stores your cookie consent choices so we do not show the banner on every page load. | 6 months |
| Product analytics identifiers (names may vary) | Analytics | Distinguishes devices and sessions, attributes visits, measures product usage, and supports sampled session replay. | Session or up to 1 year |
| flona_pending_checkouts | Analytics | Correlates a return from payment checkout with the checkout attempt that started in this browser. | Until checkout correlation is completed or cleared |
| flona_referral_code and related referral keys | Functional | Remembers referral attribution through sign-in and prevents duplicate referral notices. | Until used, replaced, or browser storage is cleared |
Some traffic and performance measurement is cookieless. Other product analytics can use browser identifiers and events to measure journeys across the marketing and application subdomains. Where enabled, sampled session replay records rendered interface state and interactions so we can diagnose friction; it is not intended to capture payment-card numbers or AI Twin source media.
Third-party cookies
Some cookies and similar technologies are set by vendors we work with. These can include authentication and account-security cookies, analytics identifiers when analytics is allowed, cookieless traffic and performance measurement, and error or diagnostic events. We restrict these technologies according to their purpose and the choices described in this policy.
The separately deployed Flona Studio editor stores project and media data locally using IndexedDB and the browser's Origin Private File System. Its production deployment can also send limited error telemetry, while session, outgoing-link, and web-vitals tracking are disabled in our current configuration. These editor technologies do not run on the main Flona marketing application.
Your choices
- Cookie preferences. Open the cookie banner any time to review and change your choices: .
- Browser controls. Most browsers let you block or delete cookies from their settings. Blocking strictly necessary cookies will break sign-in.
- Platform opt-outs. When we add third-party marketing pixels, we will link to their opt-out pages here.
- Local editor data. Deleting a project inside Flona Studio removes the browser-local project data selected by that action. Clearing site data in your browser removes the editor's remaining IndexedDB, OPFS, and local-storage data on that device.
Do Not Track and Global Privacy Control
Flona does not sell personal information or share it for cross-context behavioural advertising. We do not currently use Do Not Track or Global Privacy Control signals to automatically disable product analytics because those signals are not wired to our consent manager. Use Cookie Preferences to reject analytics, or contact us to exercise a privacy right. If we introduce processing for which applicable law requires automatic recognition of an opt-out preference signal, we will update this control and this Policy.
Changes to this policy
We may update this Cookie Policy when our cookie usage changes. Material changes are reflected in the "Last updated" date at the top of this page, and where legally required, we will ask for fresh consent through the banner.
Contact
Questions about cookies on Flona? Email support@flona.ai.
