Flo uses both session and persistent cookies. Session cookies identify a single visit and expire after a short time or when the browser closes; Flo says they are automatically deleted on closing it. Persistent cookies remain for a specified period after the browser closes, for example to keep you signed in when requested.
Supporting quotations
We use both session cookies and persistent cookies.
A session cookie is used to identify a particular visit to our Website or Web Application. These cookies expire after a short period of time or when you close your web browser after using our Website. We use these cookies to identify you during a single browsing session, and they are deleted automatically once you close your browser.
A persistent cookie will remain on your devices for a set period of time, and the duration will be specified in this Policy. These cookies survive after your browser is closed. For example, we would use a persistent cookie if you asked that we keep you signed in to the Flo service.
Retention & Deletion · Company practice
First-party statistics cookies can last up to 13 months
Flo uses first-party statistics cookies for analytics and web optimization; some have a maximum duration of 13 months. The policy also lists third-party statistics cookies in its cookie inventory.
Supporting quotations
First-party statistics cookies set by Flo:
We use first-party cookies for analytics and web optimization purposes. Some of these cookies have a maximum duration of 13 months.
Third-party statistics cookies (set by our partners): See the cookies table below.
Retention & Deletion · Company practice
Two X advertising cookies have different durations
The table describes X’s personalization_id and _twclid simply as advertising cookies, without giving more specific purposes. personalization_id lasts 13 months and _twclid lasts 30 days.
Supporting quotations
X (Twitter) personalization_id Advertising cookie Persistent 13 months
X (Twitter) _twclid Advertising cookie Persistent 30 days
Retention & Deletion · Company practice
Snapchat’s metrics identifier expires sooner in the EU and UK
The table describes sc-wcid as an anonymous client-side identifier for operational and performance metrics. It lasts one year except in the EU and UK, where it expires after 24 hours.
Supporting quotations
Snapchat sc-wcid Anonymous client-side identifier used for operational and performance metrics Persistent 1 year (excluding EU/UK where expiration is 24 hours)
Retention & Deletion · Company practice
Flo ad-set entries lack a stated expiration
utm_adset and utm_adset_id are both described as identifying the name of the ad set where an ad appeared, with no expiration supplied in either row. The separate utm_ad_id identifies a specific ad and lasts a session. The names alone do not supply missing purposes or durations.
Supporting quotations
Flo utm_adset Tracking technology used to identify the name of the specific ad set in which the ad was displayed.
Flo utm_adset_id Tracking technology to identify the name of the specific ad set in which the ad was displayed.
Flo utm_ad_id Tracking technology to identify the ID of the specific ad Session
Retention & Deletion · Company practice
Flo stores consent for one year and uses local storage for tests
CookieConsent stores consent for the current domain and lasts one year. Flo separately lists __ncbc local storage for A/B testing in its necessary table, without specifying an expiration for that entry. The policy includes similar device-storage technologies within “cookies.”
Supporting quotations
Flo CookieConsent Stores the user’s cookie consent state for the current domain Persistent 1 year
Flo __ncbc Local storage used for A/B test
However, it’s not only cookies that can be used in this way. Functions performed by a cookie can be achieved by other means, too. This Policy on cookies, therefore, also applies to any similar technology that stores or accesses information on your device. This could include, for example, HTML5 local storage, local shared objects, beacons, pixels, and plug-ins. The single term “cookies” refers to cookies and any similar technologies.
Retention & Deletion · Company practice
UserCentrics retains consent records for one year
UserCentrics is listed as the consent-management platform. Its ucString holds ControllerID, SettingsID, language, settings version and services with consent history. ucData holds consent information and ucData_{id} holds cross-domain consent information. Each entry has a one-year expiration.
Supporting quotations
UserCentrics
(consent
Management
platform)
ucString This holds the ControllerID and SettingsID, the language, settings version and services with their consent history. One year
UserCentrics
(consent
Management
platform)
ucData This holds information about user consent. One year
UserCentrics
(consent
Management
platform)
ucData_{id} (e.g ucData_a2Kvswgy3DrVCL) This holds information about user consent for cross-domain consent One year
Retention & Deletion · Company practice
Cookiebot onboarding and consent entries last 365 days
Cookiebot’s cb_admin identifies system onboarding, while CrossConsent stores consent for the current domain. The table gives both a 365-day expiration.
Supporting quotations
Cookiebot cb_admin Identifies the Cookiebot system onboarding 365 days
Cookiebot CrossConsent Stores the user's cookie consent state for the current domain 365 days