Legal

Cookie Policy

Last updated: October 12, 2026

This Cookie Policy explains how Flidu uses cookies, local storage, and similar browser technologies on the Flidu website, dashboard, and widgets — and the choices you have.

On This Page

01What Cookies And Similar Technologies Are 02How Flidu Uses These Technologies 03Strictly Necessary Technologies 04Preference Technologies 05Analytics And Product Usage 06Session And Persistent Storage 07Third-Party Services 08Managing Your Cookie Preferences 09Browser-Level Controls 10Widgets On Customer Websites 11Changes To This Policy 12Contact

What Cookies And Similar Technologies Are

Cookies are small text files a website stores in your browser. Similar technologies — such as local storage and session storage — let a site remember information between page views in comparable ways. Together, these technologies help a product stay signed in, remember settings, and operate reliably.

How Flidu Uses These Technologies

Flidu uses cookies and similar technologies to operate the product — not to build advertising profiles. The main purposes are:

Keeping users signed in to the dashboard

Protecting sessions and preventing abuse

Remembering preferences and settings

Carrying sign-in and sign-up steps from one screen to the next

Flidu does not use advertising or marketing cookies. If optional analytics or marketing technologies are added in the future, this policy will be updated before they are used.

Strictly Necessary Technologies

Some technologies are required for Flidu to work at all. These cover secure sign-in, session protection, security and abuse prevention, and the basic operation of the dashboard. Because the product cannot function without them, they are always active.

Preference Technologies

Preference technologies remember choices you make — for example the light or dark appearance of the dashboard and the sign-in method you used last — so you do not have to set them again on every visit. Clearing or blocking them in your browser does not break the product, but those settings will not persist between visits.

Analytics And Product Usage

Flidu may collect basic product usage signals — such as widget opens, channel clicks, and usage counters — to operate features like analytics dashboards and plan limits. These signals are product functionality shown to website owners, and the widget sends them without cookies or browser storage; they are described in the Privacy Policy.

The Flidu website does not use analytics cookies or third-party analytics scripts. If that changes, each one will be listed here with its provider, purpose, and duration before it is used.

Session And Persistent Storage

Technologies used by Flidu can be session-based or persistent:

Session storage lasts only while your browser tab or session is open — used for short-lived state.

Persistent storage remains after you close the browser — used for things like staying signed in and remembering preferences until they expire or are removed.

The cookies and browser storage Flidu sets are:

flidu.session_token keeps you signed in. It carries the __Secure- prefix on secure connections, lasts up to 7 days, and is renewed while you keep using the dashboard.

Short-lived sign-in cookies whose names begin with flidu (for example flidu_auth_continuation and flidu_signup_email) carry a sign-in, sign-up, verification, or invitation step from one screen to the next. They expire on their own, typically within 5 to 60 minutes.

flidu.last_used_login_method remembers the sign-in method you used last. It lasts 30 days.

flidu-theme and flidu-theme-resolved remember the light, dark, or system appearance of the dashboard. They last 1 year and are mirrored in local storage under the same names.

Local storage entries (flidu-setup-guide-v1 and your recent dashboard searches) remember the Setup Guide steps you marked as done and what you searched for recently. Both stay in this browser only.

Session storage entries (flidu.signup.prefill and flidu.signup.completion) hold what you typed during sign-up so it is not lost between steps.

Third-Party Services

Flidu is operated using trusted service providers in categories such as hosting and infrastructure, database and storage, email delivery, payment processing, AI processing for Ask AI features, and security and abuse prevention. Where such a service is involved in delivering Flidu, it may set or read technologies needed for its function — for example, a payment provider protecting a checkout session. If you choose Continue with Google to sign in, you are taken to Google's sign-in page, where Google's own cookies apply.

The Flidu website serves its fonts from its own domain, so loading a page does not contact a third-party font service.

Flidu does not sell personal information and does not place third-party advertising cookies. See How We Share Information in the Privacy Policy for the services Flidu relies on.

Managing Your Cookie Preferences

Flidu sets only the strictly necessary and preference technologies described above. It sets no analytics, advertising, or marketing cookies, so there is nothing optional to accept or reject and no consent banner is shown. You can remove or block cookies and site data at any time in your browser, as described in Browser-Level Controls below.

What Flidu Uses Today

Strictly Necessary

Sign-in, session protection, security, and core operation.

Always On

Preferences

Remembers the dashboard appearance, the sign-in method you used last, your recent dashboard searches, and your Setup Guide progress.

In Use

Analytics

Flidu sets no analytics cookies and loads no third-party analytics scripts.

Not Used

Advertising And Marketing

Flidu sets no advertising or marketing cookies.

Not Used

Browser-Level Controls

Your browser also gives you control. Most browsers let you view, block, or delete cookies and site data through their settings, either for all websites or per site. Blocking strictly necessary technologies may prevent parts of Flidu — such as sign-in — from working.

Widgets On Customer Websites

When a website owner installs a Flidu widget, the widget does not set cookies and does not write to local or session storage on that website. It keeps what it needs in the page's memory, which is cleared when the visitor leaves or reloads the page. The widget sends requests to Flidu to load its settings, record usage, and deliver submissions. If the website owner turns on the Google Analytics 4 Integration, the widget passes selected interaction events to the Google tag already on that website; Flidu does not install Google Analytics. External messaging channels open in their own apps or sites; Flidu does not read or store those conversations because a visitor selected the channel. Website owners are responsible for the notices and permissions required on their own sites.

Changes To This Policy

We may update this Cookie Policy as the product, legal requirements, or operational practices change. When we do, we will change the "Last updated" date at the top of this page. Related terms are in the Privacy Policy and the Terms of Service.

Contact

If you have a question about cookies or this policy, contact the Flidu team through the Contact page; the form opens with the topic "Legal" already chosen.