Flourish Cookies Policy
This cookies policy applies to the Flourish website (flourish.studio) and other connected websites operated by Flourish that link to this policy.
To provide a great product experience and for certain functions, we use so-called cookies. Cookies are small text files that are stored on your device. You can find an overview of all cookies we use, their purpose, retention period and usage class below.
Any information that we collect through cookies will be used in accordance with our Privacy Policy. If you do not accept the use of these cookies, you can disable them by following the instructions under the heading “Cookie Settings” below.
1. What are cookies?
Cookies are small text files that uniquely identify your browser or device. The cookie file is stored on your browser. When you return to that website (or visit websites that use the same cookies) these websites recognize the cookies and your browsing device.
Cookies do many different jobs, like letting you navigate between pages efficiently, remembering your preferences, and generally improving your experience. Cookies can tell us, for example, whether you have visited our websites before.
2. Are there different types of cookies?
There are different types of cookies, including first party cookies (which are served directly by us to your computer or device) and third party cookies (which are served by a third party on our behalf). Third party cookies enable third party features or functionality to be provided on or through the website (e.g. advertising, interactive content and analytics). The parties that set these third party cookies can recognise your computer both when it visits the website in question and also when it visits certain other websites.
Cookies can remain on your device for different periods of time. Some cookies are session cookies, meaning that they exist only while your browser is open and are deleted automatically once you close your browser. Other cookies are permanent cookies, meaning that they survive after your browser is closed. They can be used to recognise your computer when you open your browser and browse the Internet again.
3. What are cookies used for?
Cookies are used for different purposes.
Essential cookies are needed to provide you with the website and to use some of its features, such as access to secure areas. Without these cookies, we would not be able to provide you with the website and services that you have asked for.
Functionality cookies record information about choices you have made and allow us to provide relevant content and tailor our websites for you.
Performance cookies help us to measure traffic and usage data and to analyze how our websites are used in order to provide you with a better user experience and maintain, operate and improve our services.
Targeting cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same advertisement from continuously reappearing, ensuring that advertisements are properly displayed and, in some cases, selecting advertisements that are based on your interests.
4. What cookies do we use?
We use first party and third party cookies for several reasons. The specific types of first and third party cookies served through our website and the purposes they perform are described in the table below. Please be aware that the cookies we use may depend on the website you are visiting, the features you are using and the device, browser or operating system you are using.
4.1 First party cookies (set by Flourish):
| Cookie Name | Purpose | Retention Period | Class |
|---|---|---|---|
| inbound_fields | Stores the referrer and landing page | 30 days | Essential |
| flourish | Session cookie | 1 month | Essential |
| PLAY_SESSION | Used by Help Scout on help.flourish.studio to track which documentation was viewed | 1 year | Targeting |
| visitor_id | Thinkific operational cookie used on training.flourish.studio that creates an id for specific visits to the Thinkific site | Session | Functionality |
| _thinkific_session | Thinkific operational cookie that stores the authentication for the user’s session | Session | Functionality |
4.2 Cookies set by third parties:
| Set by | Cookie Name | Purpose | Retention Period | Class |
|---|---|---|---|---|
| AWS | AWSALB |
Used to provide load balancing functionality | 1 week | Functionality |
| AWSALBCORS | ||||
| Cloudflare | __cfruid | Used for rate limiting policies | Session | Functionality |
| _cf_bm | Used to read and filter requests from bots | 30 minutes | Functionality | |
| cf_use_ob | Used for the always online feature (offline browsing) | 30 seconds | Functionality | |
| cf_ob_info | Used for the always online feature (offline browsing) | 30 seconds | Functionality | |
| __cflb | Used to optimize network resource usage | 2 days | Functionality | |
| Git Hub | logged_in | logged_in is used to signal to us that the user is already logged in | 1 year | Functionality |
| _octo | _octo is used for session management including caching of dynamic content, conditional feature access, support request metadata, and first party analytics | |||
| _gh_sess | _gh_sess is used for temporary application and framework state between pages like what step the user is on in a multiple step form | |||
| Google Analytics | _ga | Used by Google Analytics to distinguish between different users | 2 years | Performance |
| _gat | Used by Google analytics to limit the number of requests | 10 minutes | Performance | |
| _gid | Used by Google Analytics to distinguish between different users | 1 year | Performance | |
| _gat_gtag_xxxxxxxxxxxxxxxxxxxxxxxxxxx | Identification code of website for tracking visits | 1 day | Performance | |
| Loom | loom_referral_video | loom_referral_video is used to detect referrals in relation to the embedded video-player | Session, 1 month | Functionality |
| connect.sid | connect.sid is necessary for secure log-in and the detection of any spam or abuse of the website | Session, 1 month | Functionality | |
| loom_anon_comment | loom_anon_comment is used to track comments on videos | Session, 1 month | Functionality | |
| Mouseflow | mf_[session] | Used to identify the browser session | Session | Performance |
| mf_user | Used to establish whether the user is a returning or first-time visitor | 90 days | Performance | |
| New Relic (nr-data.net) | JSESSIONID | Used to store a session identifier | Session | Performance |
| reCaptcha | _GRECAPTCHA | Used by Google reCAPTCHA for risk analysis in spam protection | 180 days | Functionality |
| Vimeo | Vuid | Used to store the user's usage history | 2 years | Functionality |
| Wordpress | wordpress_google_apps_login | This cookie allows the users to login to the site with their Google account. | Session | Functionality |
| YouTube | CONSENT | Used to store cookie consent preferences. | 20 years | Targeting |
| YSC | Used to remember user input and associate a user’s actions | Session | Targeting | |
| VISITOR_INFO1_LIVE | Used as a unique identifier to track viewing of videos | 6 months | Targeting | |
| VISITOR_PRIVACY_METADATA | Stores the user's cookie consent state for videos embedded on Flourish blog posts | 180 days | Targeting | |
| OneTrust | OptanonConsent | stores information about the categories of cookies the site uses and whether visitors have given or withdrawn consent for the use of each category. | 1 year | Functionality |
| OptanonAlertBoxClosed | Is set after visitors have seen a cookie information notice and, in some cases, only when they actively close the notice down. | 1 year | Functionality | |
| Medium | _cfuvid | Cloudflare denial of service protection. This cookie is used to distinguish users from the same IP address. | Session | Essential |
5. Web storage
Cookies are not the only way to recognize or track visitors to a website. We use various third party utilities, including a Zendesk Widget and Helpscout’s Beacon, to allow you to contact us from the website and present documentation relevant to the page you’re on. The beacon uses web storage (in particular local storage) to store information about you and data that might be useful for providing support. The local storage keys are:
Local storage key: persist:hs-beacon-[Beacon ID] Purpose: Identifying token and details of Helpscout usage Type & duration: Local storage, no expiry date
Local storage key: persist:hs-beacon-message-[Beacon ID] Purpose: Information about any current draft message Type & duration: Local storage, no expiry date
6. Cookie settings
Some of the cookies listed above are essential and we cannot provide our service to you without them, but there are others that can be turned off. Please note that turning off certain cookies will disable some of the features available to you through our website. We cannot guarantee that your experience on our website will be as good as it could otherwise be.
6.1 Cookie preferences:
To change your cookie preferences, please click the button below.
6.2 Browser settings:
You can also change your preferences by changing the settings in your browser. For more information on how to manage the most popular browsers, please see below:
If you want to change your settings at any time (for example, if you accept all cookies but later decide you do not want a certain type of cookie), you’ll need to use your browser settings to remove any third party cookies dropped on your previous visit.
6.3 Third party cookies:
In addition to managing cookies in your browser settings, you can also opt out of certain third party cookies. For example, we use Google Analytics and Mouseflow to help us understand how users engage with our websites, compile reports and improve our services. You can opt out of these cookies without affecting how you visit our websites.
For more information on Google Analytics, see here, and to opt out from being tracked by Google Analytics, see here. You can view Mouseflow’s security policies and choose to opt out of Mouseflow tracking.
Certain pages on our site may set other third party cookies. For example, on our blogs we may embed content, such as videos, from another site that sets a cookie. Or a customer-coded Flourish template may include cookies from the customer’s own analytics system. While we try to minimize exposure to third-party cookies (for example we do not link to customer-specific templates), we can’t always control what cookies this third-party content sets.
7. Changes to this policy
We may update this policy from time to time to reflect our current practice and ensure compliance with applicable laws. When we post changes to this policy, we will revise the “Last Updated” date at the top of this policy. We recommend that you check this page from time to time to inform yourself of any changes.
8. How to contact us
If you have any questions, suggestions or concerns about our use of cookies or this cookies policy, please email us at [email protected] or write to us at: Kiln Enterprises Ltd, 33-35 Hoxton Square, London, N1 6NN
