Floral Cookie Policy

Version 2026-09-24.2

This policy explains cookies and similar technologies on floral.so, app.floral.so and other Floral web pages that link to it. It explains their purposes, providers, lifetimes and your choices. Floral ApS, CVR 44598574, Vesterbrogade 29F, st., 1620 Copenhagen V, Denmark, is responsible for this use. Contact [email protected].

Read this policy with our Privacy Policy, which explains personal-data processing, recipients, international transfers, retention and your rights. The analytics choice on floral.so controls optional website analytics there. It does not control usage analytics in the signed-in web or mobile app.

1 Cookies and similar technologies

A cookie is a small value that a website stores in your browser and can receive on later requests. First-party cookies use the domain you visit; third-party cookies use another domain. A first-party cookie can still be set or read by a service provider. Session cookies last for a browser session. Persistent cookies have an expiry and may be renewed when the relevant function is used.

Local storage keeps information until the site or you remove it. Session storage normally lasts for the tab's session. Scripts, pixels and software libraries can also access device information or send usage information without saving a cookie. Optional website analytics is subject to the website choice below even when it uses browser memory or sends requests without cookies.

2 Website analytics choice

We use storage needed for requested functions such as secure sign-in and connecting an integration. On floral.so, optional analytics requires a separate choice before it starts.

Optional analytics on floral.so starts only after you choose to allow it. You can decline it and still use the website. The signed-in app uses PostHog for usage analytics, as described in section 4.

Use the website's Cookie settings control to review or change your website analytics choice. Withdrawing the choice stops new optional website collection. Contact [email protected] if you need help.

3 Browser storage and service functions

The following cookies support the functions indicated. Not every cookie appears on every page or device. Names with an asterisk have a variable suffix. Durations are cookie lifetimes, which are separate from the validity of a login token and retention of server records. Browsers may impose shorter limits.

Cookie or technology and providerPurpose and when usedLifetime
c15t choice cookie and local storage on floral.so; ph_*_posthog cookie and local storage in the web app.c15t remembers your website analytics choice. PostHog recognises the browser for feature flags and usage analytics.Each cookie: up to one year from its latest update. Local storage remains until cleared.
floral_locale. Floral.Supply the interface in the resolved language and remember the language preference.Up to one year from the latest update.
sidebar_state. Floral.Remember the sidebar position you select.Up to seven days from the change.
crm_pipedrive_* connection cookies. Floral.Complete a Pipedrive connection you start.Up to 20 minutes.
__session and its suffixed variant. Clerk.Maintain your sign-in session.Up to one year from refresh. The sign-in token expires sooner.
__client, __client_uat and suffixed variants. Clerk.Recognise your browser for sign-in and security.Up to ten years from issue or renewal, subject to browser limits. This does not keep you signed in for ten years.
clerk_active_context. Clerk.Coordinate the active sign-in context across browser tabs.Browser session.
__cf_bm and _cfuvid. Cloudflare through the sign-in service.Protect sign-in against automated abuse and apply request limits.__cf_bm expires after about 30 minutes of continuous inactivity. _cfuvid is a session cookie.
ph_conv_* local storage. PostHog support.Remember the support conversation and widget state when you open a link to restore a conversation. This is separate from optional analytics.No automatic browser expiry. It remains until cleared by you or reset by the support function.

You can remove browser data through your browser settings. See Clerk's cookie information and Cloudflare's cookie information.

4 Usage analytics

We use analytics to understand use of the website and product and improve them. Analytics can include a browser or account identifier, page or feature category, timestamps and browser or device information. Such data may be personal data even where we use a random identifier or view aggregate reports. We exclude meeting text, transcripts, summaries, private workspace content and private form values from these analytics.

Technology and providerPurpose and scopeBrowser lifetime
Google Analytics 4, including _ga and _ga_*. Google.Website audience and usage measurement after analytics consent. Google Tag Manager loads the website tags.Up to two years from setting or update, subject to configuration and browser limits.
PostHog product analytics. PostHog.Feature and page-use events in the signed-in web app.Cookie and local storage as described above.

Your website choice does not control app usage analytics. See Google's cookie information and PostHog's privacy information.

5 Personal data and external services

Our providers may receive information such as an IP address. Some authentication and website analytics processing may take place outside the EEA, including in the US. Our Privacy Policy explains the recipients, safeguards and your rights.

Payment and identity-provider pages you choose to open may set cookies under their own policies.

Clearing a cookie does not erase information already received by a provider. To request erasure of personal data, use the contact and rights process in our Privacy Policy.

6 Managing browser data and policy changes

Your browser settings let you view, restrict or delete cookies and site storage. Removing sign-in information may sign you out or interrupt the function it supports. Removing a saved website choice means we must ask again before optional website analytics resumes. Declining website analytics does not disable essential functions.

We update this policy when technologies, purposes or relevant settings change and show the version above. We ask for a new choice where required. For questions, contact [email protected]. You can also complain to Datatilsynet about personal-data processing or Digitaliseringsstyrelsen about the Danish rules on cookies and similar technologies.