29 of 70 cards in Use & Processing
Use & Processing · Context
Flo classifies the cookies it and its partners use for the Website as Necessary, Statistics or Marketing. These are the policy’s purpose categories.
The types of cookies used by us and our partners in connection with the Website can be classified into one of three categories:
(i) Necessary
(ii) Statistics
(iii) Marketing
Use & Processing · Company practice
Flo’s first-party necessary cookies support access and visitor identification across subdomains; fraud and bot detection, authentication and secure logins; remembering and sharing cookie-consent choices across subdomains; traffic scheduling and network distribution; and payments.
Functionality: Optimizing and improving access to the Website whilst enabling the identification of a visitor across various subdomains.
Security: Preventing fraud and detecting nonhuman (bot) traffic, including authentication and secure logins
Cookie consent: Remembering your cookie consent preferences and sharing such cookie consents across subdomains to improve user experience
Analysis: Traffic scheduling and network distribution
Billing: The ability to make payments
Use & Processing · Company practice
Analytics and performance cookies help Flo report and evaluate website activity and patterns: pages viewed most often, visitors’ region, interaction with content, errors and tests of design ideas. Flo says its cookies do not process personal health data.
(ii) Statistics
We use analytics and performance cookies to analyze how you use the Website. This helps us to:
See which pages you view most often
Analyze which region you are visiting the Website from
Observe how you interact with the content
Measure any errors that occur
Test different design ideas
The above information is used to report and evaluate your activities and patterns as a user of the Website.
You can also change your consent to each category of cookies at any time via the cookie banner using the toggles. We also may use certain cookies on only a limited number of pages that you visit on our Website and Web Application to avoid unnecessary collection of your personal data. Please note that our cookies do not process any personal health data.
Use & Processing · Company practice
Flo uses marketing cookies to reach you and similar audiences and measure promotion effectiveness. It says it does not use cookies to collect or analyze health information for marketing. Some marketing tools run on servers without setting a browser cookie, and those tools activate only after you consent.
(iii) Marketing
These cookies help us reach you and more people like you to spread the word about the App, as well as analyze whether we do that effectively. Flo does not use cookies to collect or analyze your health information for marketing purposes.
Some marketing tools may operate server-side and do not set a cookie directly in your browser. These are only activated after you provide consent.
Use & Processing · Company practice
Flo’s first-party marketing cookies support campaign improvement, conversion tracking, paid-search keyword identification, identifying traffic sources such as search engines or social media, visitors’ region and interaction with content. Third-party marketing cookies are listed separately in the inventory. The policy excludes collecting or analyzing health information through cookies for marketing.
First-party marketing cookies set by Flo
We use marketing cookies to analyze and improve our marketing campaigns. This helps us to:
Improve our marketing campaigns, including tracking ad conversions
Identify paid search keywords
Identify the source of traffic to the Website, such as search engine, social media, or specific website
Analyze which region you are visiting the Website from
See how you interact with the content
Third-party marketing cookies (set by our partners): See the cookies table below.
These cookies help us reach you and more people like you to spread the word about the App, as well as analyze whether we do that effectively. Flo does not use cookies to collect or analyze your health information for marketing purposes.
Use & Processing · Company practice
Flo’s _is_fba tracks partner activity for affiliate-marketing attribution and lasts one day. Its ttclid entry links a TikTok ad-click identifier appended to a landing-page URL with a campaign for attribution and performance, and lasts 30 days.
Flo _is_fba Affiliate Marketing - Cookie used to track partner activity and ensure accurate attribution. Persistent 1 day
Flo ttclid TikTok Click ID is a tracking parameter appended to a landing page URL when you click on an ad on TikTok, helping TikTok to improve ad attribution and performance by associating your Click ID with a campaign Persistent 30 days
Use & Processing · Company practice
TikTok’s _tt_enable_cookie tracks embedded-service use and lasts 13 months. tt_pixel_session_index counts TikTok-content interactions, and tt_sessionId tracks sessions for ad attribution and analytics; both last a session. _ttp measures and improves advertising performance and personalizes TikTok experiences, including ads, and lasts 13 months. tt_appInfo remembers content settings and preferences for one year.
Tik Tok _tt_enable_cookie Used by the social networking service, TikTok, for tracking the use of embedded services. Persistent 13 months
Tik Tok tt_pixel_session_index Cookie is used by TikTok to check how many times you've interacted with TikTok content Session
Tik Tok tt_sessionId Tracks user sessions for TikTok ad attribution and analytics. Session
Tik Tok _ttp To measure and improve the performance of your advertising campaigns and to personalize the user's experience (including ads) on TikTok Persistent 13 months
Tik Tok tt_appInfo This cookie helps TikTok remember settings and preferences for TikTok content Persistent 1 year
Use & Processing · Company practice
X (Twitter) uses muc_ads for website optimization and ad relevance, guest_id_marketing and _guest_id_ads for ad relevance, and guest_id for visit counts, average visit time and pages loaded to personalize and improve Twitter. Each lasts 13 months. The 1/i/adsct [x2] entry supports website optimization and ad relevance but lasts a session.
X (Twitter) muc_ads It’s used in order to optimize the website and make advertisements on the website more relevant. Persistent 13 months
X (Twitter) guest_id Collects data related to the user's visits to the website, such as the number of visits, average time spent on the website and which pages have been loaded, with the purpose of personalising and improving the Twitter service. Persistent 13 months
X (Twitter) guest_id_marketing It’s used in order to optimize the relevance of advertisement on the website. Persistent 13 months
X (Twitter) _guest_id_ads It’s used in order to optimize the relevance of advertisements on the website. Persistent 13 months
X (Twitter) 1/i/adsct [x2] It’s used to optimize the website and make advertisements on the website more relevant. Session
Use & Processing · Company practice
Impact.com Affiliate’s irclickid is a click ID for its platform and lasts 30 days. The following UTT entries, IR_22205 and IR_GBD, let Flo understand interaction with its pages and last a session. IR_PI is set on clicks on Flo banners, uses UUID keys in UTT functions and lasts two years.
Impact.com Affiliate irclickid Click id for Impact platform Persistent 30 days
IR_22205 Cookie set as a part of the Universal Tracking Tag (UTT) API implementation, which is a minified script placed within Flo’s website. It allows Flo to understand how users interact with our web pages Session
IR_GBD The Universal Tracking Tag (UTT) is a minified script placed within Flo’s website. Cookies set on the base domain of Flo website as part of the Universal Tracking Tag (UTT) system to understand how users interact with our web pages. Session
IR_PI These cookies are set when the user clicks on Flo’s banners. This is part of UTT javascript functions and works based on unique identifier UUID keys. Persistent 2 years
Use & Processing · Company practice
IRLD identifies the last click to remove duplicates during checkout and final conversion, with a six-month duration. brwsr stores a UUID key to recognize a customer later and lasts 24 days. EPERSIST distributes network traffic during a session; its row says it stores no personally identifiable information and expires when the session ends.
IRLD This cookie identifies the "last click" and is used to eliminate duplicate clicks during checkout and the final conversion. Persistent 6 months
brwsr This cookie stores a unique UUID key to help identify a customer later. Persistent 24 days
EPERSIST It helps distribute network traffic efficiently, ensuring optimal performance and reliability during a user's session. This cookie does not store personally identifiable information and expires when the session ends. Session
Use & Processing · Company practice
YouTube’s VISITOR_INFO1_LIVE tries to estimate bandwidth on pages with embedded YouTube videos and lasts 179 days. ytidb::LAST_RESULT_ENTRY_KEY stores player preferences for embedded videos; the table calls it persistent without specifying how long.
YouTube VISITOR_INFO1_LIVE Tries to estimate the users’ bandwidth on pages with integrated YouTube videos Persistent 179 days
YouTube ytidb::LAST_RESULT_ENTRY_KEY Stores the user’s video player preferences using embedded YouTube video Persistent
Use & Processing · Company practice
The YouTube row lists Yt-remote-cast-available, Yt-remote-cast-installed, Yt-remote-fast-check-period, Yt-remote-session-app and yt-remote-session-name as storing preferences for embedded video players, with a session duration.
YouTube
Yt-remote-cast-available
Yt-remote-cast-installed
Yt-remote-fast-check-period
Yt-remote-session-app
yt-remote-session-name
Stores the user’s video player preferences using embedded YouTube video Session
Use & Processing · Company practice
YouTube’s yt-remote-connected-devices and yt-remote-device-id store embedded-video player preferences. Their row says persistent without specifying a period. Separately, YSC records interaction with embedded YouTube videos and lasts a session.
YouTube
yt-remote-connected-devices
yt-remote-device-id
YouTube cookies that store the user’s video player preferences using embedded YouTube video Persistent
YouTube YSC YouTube cookies to understand how a user interacts with embedded YouTube videos on a website. Session
Use & Processing · Company practice
The marketing table lists Google’s _ga to identify and track an individual session with a device, lasting two years. _gcl_au lets Google AdSense experiment with ad effectiveness across websites using its services and lasts three months.
Google _ga Used to identify and track an individual session with a user device Persistent 2 years
Google _gcl_au Used by Google AdSense for experimenting with advertisement efficiency across websites using their services Persistent 3 months
Use & Processing · Company practice
Google’s ads/ga-audiences reengages visitors considered likely to become customers based on behavior across websites. pagead/1p-user-list/# measures advertising efforts and facilitates referral-fee payments between websites. Both have session durations.
Google ads/ga-audiences Used to reengage visitors that are likely to convert to customers based on the visitor’s online behavior across websites Session
Google pagead/1p-user-list/# Set by Google for measurement of advertisement efforts and facilitates payment of referral fees between websites Session
Use & Processing · Company practice
Snapchat’s sc_at delivers ad content, measures its effectiveness and collects visitor data for further segmentation; it lasts one year. blizzard_client_id distinguishes unauthenticated visitors and lasts 30 days.
Snapchat sc_at Used by Snapchat to implement advertisement content. The cookie detects the efficiency of the ads and collects visitor data for further visitor segmentation. Persistent 1 year
Snapchat blizzard_client_id Used to distinguish unauthenticated visitors Persistent 30 days
Use & Processing · Company practice
Snapchat’s EssentialSession saves Essential Session cookie preferences; sc-cookies-accepted records whether cookies were accepted; sc-language remembers the selected language. Each lasts one year. _sctr determines whether a third-party tag will be called in a Snap Ads Pixel and also lasts one year.
Snapchat EssentialSession Used to save Essential Session cookie preferences Persistent 1 year
Snapchat sc-cookies-accepted Used to determine whether a visitor has accepted cookies Persistent 1 year
Snapchat _sctr Used to determine whether a third-party tag will be called in a Snap Ads Pixel Persistent 1 year
Snapchat sc-language Used to remember a visitor’s chosen language preference. Persistent 1 year
Use & Processing · Company practice
Flo’s utm_campaign typically records campaign names, slogans or promo codes to measure online advertising. utm_term identifies paid-search keywords and ad-set names. utm_medium usually travels in tracked-link URLs to identify an advertiser, site or publication; utm_content differentiates similar content or links within an ad. Each lists one year.
Flo utm_campaign A first-party cookie that typically tracks individual campaign name, slogan, promo code, etc., to track the effectiveness of online advertising campaigns 1 year
Flo utm_term Identifies paid search keywords and name of ad sets 1 year
Flo utm_medium Tracking technology typically passed as part of the URL when a user clicks on a tracked link, such as an ad or email campaign, to identify the advertiser, site, or publication 1 year
Flo utm_content Tracking technology typically passed as part of the URL to differentiate similar content or links within the same ad 1 year
Use & Processing · Company practice
The table gives a one-year duration for utm_ad, which identifies a specific ad; utm_exp, which identifies an experiment; utm_source, which identifies the traffic source such as a search engine or social platform; and utm_campaign_id, which identifies an ad campaign.
Flo utm_ad Used to identify the ID of the specific add 1 year
Flo utm_exp Used to identify the ID of the specific experiment 1 year
Flo utm_source Tracking technology used to identify the specific source of traffic to a Website, such as a search engine, social media platform, or specific website 1 year
Flo utm_campaign_id Tracking technology used to identify the specific ID of an ad campaign 1 year
Use & Processing · Company practice
Quora’s m-b is described in terms of pixel necessity, performance, functionality and targeting and lasts two years. The separate qclid is a click ID and lasts 30 days.
Quora m-b Pixel necessity, performance, functionality, targeting Persistent 2 years
Quora qclid It’s used for click ID. Persistent 30 days
Use & Processing · Company practice
The Pinterest row lists _pinterest_ct, _pinterest_ct_ua, _pin_unauth, _derived_epik, _epik and ar_debug for marketing analytics, with a one-year duration. The separate _nccapi_ur and v3/ pixel entries track use of services and last a session.
_pinterest_ct
_pinterest_ct_ua
_pin_unauth, _derived_epik _epik
ar_debug
Cookies for marketing analytics Persistent 1 year
Pinterest _nccapi_ur Used by Pinterest to track the usage of services. Session
Pinterest v3/ pixel Used by Pinterest to track the usage of services. Session
Use & Processing · Company practice
Microsoft’s _uetsid_exp and _uetvid_exp contain expiration dates for the correspondingly named cookies and each lasts 13 months. _uetmsclkid captures the Microsoft Click ID when someone clicks an ad and lands on the website; it lasts 90 days.
Microsoft (Bing) _uetsid_exp Contains the expiry-date for the cookie with corresponding name Persistent 13 months
Microsoft (Bing) _uetvid_exp Contains the expiry-date for the cookie with corresponding name Persistent 13 months
Microsoft (Bing) _uetmsclkid Captures the Microsoft Click ID (MSCLKID) when a user clicks on an ad and lands on your website Persistent 90 days
Use & Processing · Company commitment
The mobile-SDK section says the Flo app is never used to present third-party advertising. That statement concerns ads shown in the app; the section also describes acquisition-campaign measurement and choices about targeted-advertising data.
Our App is never used to present you with third-party advertising. You can browse with full confidence in the protection of your privacy. Access is requested with the purpose of enabling the use of our services and improving their functioning. It is subject to a prior consent request and the possibility of withdrawing this consent. Flo services may still be used even in the event of refusal or withdrawal of consent.
AppsFlyer SDK: Facilitates measurement of performance and analysis of customer acquisition campaigns. Further information about AppsFlyer SDK is available at https://www.appsflyer.com/product/security-and-privacy/. You can deactivate this data processing at any time via https://www.appsflyer.com/optout. In order to do so, you must have the Identifier for Advertisers (IDFA) of your mobile device.
You can also withdraw your consent for the collection of data for targeted advertising or sharing their data with third-party advertisers through Flo privacy settings or your device’s settings.
Use & Processing · User right or choice
AppsFlyer’s SDK measures performance and analyzes customer-acquisition campaigns. Flo points to AppsFlyer’s security/privacy page for more information and its appsflyer.com/optout page to deactivate this processing at any time. That opt-out requires your mobile device’s Identifier for Advertisers (IDFA). The linked pages’ additional terms are not supplied here.
AppsFlyer SDK: Facilitates measurement of performance and analysis of customer acquisition campaigns. Further information about AppsFlyer SDK is available at https://www.appsflyer.com/product/security-and-privacy/. You can deactivate this data processing at any time via https://www.appsflyer.com/optout. In order to do so, you must have the Identifier for Advertisers (IDFA) of your mobile device.
Use & Processing · Restriction or exception
If cookies are deleted or not accepted, Flo warns that some offered features may become unavailable, preferences may not be saved and pages may not display properly. This warning is about cookie-dependent features; the mobile-SDK section separately says Flo services remain usable after refusing or withdrawing SDK-access consent.
Please note, however, that if you delete cookies or do not accept them, you might not be able to use all of the features we offer, you may not be able to store your preferences, and some of our pages might not display properly.
Our App is never used to present you with third-party advertising. You can browse with full confidence in the protection of your privacy. Access is requested with the purpose of enabling the use of our services and improving their functioning. It is subject to a prior consent request and the possibility of withdrawing this consent. Flo services may still be used even in the event of refusal or withdrawal of consent.
Use & Processing · Company practice
Cookies let the Website remember settings such as login, language, font size and display preferences over time, reducing the need to enter them again when returning or moving between pages.
Cookies enable the Website to remember your actions and preferences (such as login, language, font size, and other display preferences) over a period of time, so you don’t have to keep reentering them whenever you come back to the site or browse from one page to another.
Use & Processing · Company practice
The necessary-cookie table lists user_id, session_id and SESS# for state or selections across page requests, each lasting a session. visitor_id preserves visitor state and is persistent for one year. Flo also lists the session cookie 1.gif to count visits, _set_cookie to detect browser cookie acceptance, and progressScreenViewed to prevent the landing-page animation from repeating.
Necessary
Flo user_id Flo.health cookie that preserves users’ session state across page requests Session
Flo session_id Flo.health cookie that preserves users’ selections across page requests Session
Flo visitor_id Preserves the visitor’s session state across page requests Persistent 1 year
Flo 1.gif Used to count the number of sessions to the website. Session
Flo _set_cookie This cookie determines whether the browser accepts cookies Session
Flo SESS# Preserves users’ states across page requests Session
Flo progressScreenViewed It prevents repetitive display of the animation every time a user navigates to the landing page Session
Use & Processing · Company practice
Listed under Statistics, Google Tag Manager’s gtmBrowserID centrally integrates tags or tracking pixels used for conversion tracking, site analytics and remarketing. Flo can assess the organized data for website improvements and remarketing campaigns. The table calls it persistent but gives no specific expiration period.
Statistics
Google Tag Manager gtmBrowserID Tag management system set by Google. Tags are small sections of codes or tracking pixels from third-party tools that can track activities for conversion tracking, site analytics, and remarketing. Via Google Tag Manager, tags can be integrated centrally via a user interface, which means all the data is perfectly organized and ready for us to assess and review for potential site improvements and remarketing campaigns. Persistent
Use & Processing · Company practice
Flo’s user_region stores location or region to provide localized content or services, with a one-year duration. Google’s _gid distinguishes visitors and generates statistics about Website use, with a two-day duration.
Flo user_region Used to store information about a user’s geographic location or region. Flo uses this information to provide localized content or services to the user based on their location. Persistent 1 year
Google _gid Used to distinguish visitors and generate statistical data on how visitors use our Website Persistent 2 days