Cookie Notice
Last updated: 10 July 2026
This notice explains how letbloom.io ("letbloom", "we", "us" or "our") uses cookies and similar browser technologies, including local storage and session storage. It should be read with our Privacy Policy.
1. Your choices
We use essential technologies to provide and secure the service. These remain active because the service cannot operate as requested without them, or because you have asked us to remember a functional preference.
We use optional browser analytics only after you select Accept. Selecting Reject does not prevent you from using letbloom. You can change your choice at any time using Cookie settings on this Cookie Notice or our Privacy Policy.
Your choice is stored on this browser for 180 days in __Host-lb_cookie_consent in production (lb_cookie_consent in local development). It records the version of this notice, whether browser analytics were accepted, and when the choice was made. We ask again when that record expires or when our analytics purposes, provider, or notice materially changes.
2. Essential and functional technologies
| Technology | Provider | Purpose | Category | Typical duration |
|---|---|---|---|---|
__Host-lb_cookie_consent / lb_cookie_consent |
letbloom | Remembers your browser analytics choice and notice version. The secure __Host- name is used in production. |
Essential consent record | 180 days |
lb_refresh / __Host-lb_refresh and lb_csrf / __Host-lb_csrf |
letbloom | Keeps signed-in sessions working and protects authenticated requests. | Strictly necessary | Normally up to 24 hours; refreshed while the session remains valid |
lb_oauth_state |
letbloom | Secures sign-in through an external identity provider. | Strictly necessary | About 10 minutes |
lb_locale |
letbloom | Remembers your selected language. | Functional | 180 days |
lb_billing_currency |
letbloom | Remembers the currency selected for pricing and billing displays. | Functional | 180 days |
lb_webchat_session / __Host-lb_webchat_session |
letbloom | Maintains the guest web-chat session requested by the visitor. | Strictly necessary for web chat | Up to 30 days |
lb_guest_concierge_passkey cookie and local storage |
letbloom | Remembers guest concierge access on the device when requested. | Functional | Cookie: 30 days; local storage: until removed or browser data is cleared |
lb-theme |
letbloom | Remembers light or dark appearance. | Functional | Until changed or browser data is cleared |
lb_active_property_id |
letbloom | Remembers the property currently selected in the dashboard. | Functional | Until changed, sign-out, or browser data is cleared |
lb-referral-code, lb-referral-landing-path, and lb-referral-metadata |
letbloom | Carries an explicit referral selection through signup so it can be honoured. | Functional | Up to 90 days or until signup completes |
lb-auth-refresh-lock |
letbloom | Coordinates authentication refresh across tabs and avoids duplicate refresh requests. | Strictly necessary | Short-lived and removed when the refresh workflow finishes |
billing-pending-checkout:v1 and billing-return-pending-completion:v2:* |
letbloom | Completes and validates a billing flow requested by the signed-in manager. | Strictly necessary for billing | Current browser tab and only while the billing workflow requires it |
lb-last-meaningful-route, lb-shell-document-transition:v1, and lb-app-mount-count |
letbloom | Restores requested navigation, prevents stale transition UI, and coordinates the active interface. | Strictly necessary / functional | Current browser tab |
Cookie names can vary where the secure __Host- prefix is used in production. Browser settings may let you delete or block these technologies, but blocking essential items can prevent the related feature from working.
3. Optional browser analytics
| Technology | Provider | Purpose | Category | Typical duration |
|---|---|---|---|---|
ph_<project-token>_posthog and related PostHog cookie and session-storage keys |
PostHog EU Cloud | Provides the pseudonymous browser and session state needed for accepted product analytics and selected session replay. | Analytics | Cookie: up to 180 days; session items end with the browser session |
_gcl_* cookies such as _gcl_aw and _gcl_gs, plus _gcl_ls in local storage (when Google Ads tracking is enabled) |
Google Ads | Stores ad-click information so selected actions can be attributed to advertising campaigns. | Advertising measurement | Up to 90 days |
lb-acquisition-attribution |
letbloom | Stores first- and last-touch UTM values, referring host, landing path, and advertising click identifiers and type after consent. | Analytics | Up to 90 days |
If you accept analytics, we use PostHog EU Cloud to understand page views, product interactions, journeys through the service, errors, audiences, and selected activation flows. When enabled, we also use Google Ads conversion tracking to measure whether an interaction with an advertisement led to a selected action on letbloom. Depending on the enabled diagnostics, this can include a pseudonymous browser identifier, a session identifier, ad-click identifiers, URLs after sensitive values are removed, browser and device information, coarse network-derived location, account or property identifiers, and product-event or conversion metadata.
PostHog durable browser persistence uses expiring cookies limited to 180 days; its session-storage items end with the browser session. Google Ads click-measurement cookies and local storage are retained for up to 90 days. We also store first- and last-touch campaign information such as UTM parameters, the referring host, and the type of advertising click identifier in lb-acquisition-attribution for up to 90 days. We do not start this storage, send PostHog or Google Ads browser events, attach PostHog identifiers to API requests, or start session replay unless analytics has been accepted.
If you reject or later withdraw analytics, letbloom stops browser capture and removes the PostHog, Google Ads, and acquisition-attribution state available to the browser. Events that occurred before acceptance are not queued or sent later.
The banner controls browser analytics technologies. letbloom may separately create limited cookie-independent server events about authentication and billing outcomes for security, service administration, reliability, and business operations, as described in our Privacy Policy. These events do not read the browser analytics choice or use PostHog browser identifiers when browser analytics is off.
4. YouTube videos
We do not load embedded YouTube content automatically. A local placeholder explains that selecting Load video will connect your browser to YouTube and may share information with Google. Only that informed click creates the privacy-enhanced YouTube iframe. You can instead use the direct YouTube link.
YouTube and Google may then process device, network, viewing, and interaction information under their own terms and privacy notices. Loading one video does not change your persistent browser analytics choice.
5. Withdrawing consent and privacy requests
Use Cookie settings on this Cookie Notice or our Privacy Policy to reject or accept browser analytics at any time. Withdrawal takes effect immediately for future browser capture and clears accessible analytics storage on that device.
To ask about this notice, exercise a privacy right, or request deletion of analytics information already received by a provider, contact info@letbloom.io. We may need information that lets us locate the relevant record without collecting more data than necessary.
6. Changes to this notice
We may update this notice when our technologies or purposes change. If the change materially affects optional browser analytics, we will change the notice version and ask for a new choice.