Cookie Policy

Last update 21/08/2024

This Cookie Policy applies to the website https://wifirst.com published by Wifirst, a simplified joint-stock company registered with the Paris RCS under number 441 757 614 and whose head office is located at 26, rue de Berri 75008 Paris.
This Policy allows you to better understand why Wifirst uses cookies and how these cookies work as well as the current tools to configure them.

A cookie is a small computer file, a tracer, deposited and read when consulting or using an online service, regardless of the type of terminal used (computer, smartphone, e-reader, video game console connected to the Internet, etc.).

Cookies have multiple uses and allow their issuer to identify the terminal and record certain information relating to the use of the online service (your customer identifier, the choice of a language, the opening of an email, for example).

Some cookies are strictly necessary for the use or provision of the online service and therefore exempt from consent. Others, which do not meet these criteria, require the user's consent before the deposit of these cookies.

During your visit to the https://www.wifirst.com site, cookies may be installed on your terminal by Wifirst or by our partners.

These are 3 types of cookies which pursue the following purposes.

• Ensure the proper functioning of our websites (strictly necessary cookies);
• Measure our audience and collect analytical data on user behavior;
• Improve our users' experience by remembering choices made on previous visits.

Necessary cookies

These are essential cookies that do not require consent.

__hs_opt_out

• This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again.
• This cookie is set when you give visitors the choice to opt out of cookies.
• It contains the string "yes" or "no".
• It expires in 6 months.

__hs_do_not_track

• This cookie can be set to prevent the tracking code from sending any information to HubSpot.
• It contains the string "yes".
• It expires in 6 months.

__hs_initial_opt_in

• This cookie is used to prevent the banner from always displaying when visitors are browsing in strict mode.
• It contains the string "yes" or "no".
• It expires in seven days.

__hs_cookie_cat_pref

• This cookie is used to record the categories a visitor consented to.
• It contains data on the consented categories.
• It expires in 6 months.

__hs_gpc_banner_dismiss

• This cookie is used when the Global Privacy Control banner is dismissed.
• It contains the string "yes" or "no".
• It expires in 180 days.

__hs_notify_banner_dismiss

• This cookie is used when the website uses a Notify consent banner type.
• It contains a boolean value of True.
• It expires in 180 days.

hs_ab_test

• This cookie is used to consistently serve visitors the same version of an A/B test page they’ve seen before.
• It contains the id of the A/B test page and the id of the variation that was chosen for the visitor.
• It expires at the end of the session.

<id>_key

• When visiting a password-protected page, this cookie is set so future visits to the page from the same browser do not require login again.
• The cookie name is unique for each password-protected page.
• It contains an encrypted version of the password so future visits to the page will not require the password again.
• It expires in 14 days.

hs-messages-is-open

• This cookie is used to determine and save whether the chat widget is open for future visits.
• It is set in your visitor's browser when they start a new chat, and resets to re-close the widget after 30 minutes of inactivity.
• If your visitor manually closes the chat widget, it will prevent the widget from re-opening on subsequent page loads in that browser session for 30 minutes.
• It contains a boolean value of True if present.
• It expires in 30 minutes.

hs-messages-hide-welcome-message

• This cookie is used to prevent the chat widget welcome message from appearing again for one day after it is dismissed.
• It contains a boolean value of True or False.
• It expires in one day. 

__hsmem

• This cookie is set when visitors log in to a HubSpot-hosted site.
• It contains encrypted data that identifies the membership user when they are currently logged in.
• It expires in seven days. 

hs-membership-csrf

• This cookie is used to ensure that content membership logins cannot be forged.
• It contains a random string of letters and numbers used to verify that a membership login is authentic.
• It expires at the end of the session.

hublytics_events_53

• This browser storage entry is used by HubSpot Product to temporarily store tracking events created by HubSpot Product until they get dispatched over the network.
• It's stored either on the Browser's Session Storage or Local Storage based on the presence or lack of tracking consent.
•  When tracking consent isn't given, this cookie stays within the current browser session and expires at the end of the session. This "cookie" will remain empty and not store anything.
• It contains metadata regarding tracking events that HubSpot collects throughout the user's journey at HubSpot.
• It doesn't contain personal identifiable information or information that can identify your device or hardware.
• It can't be manually removed and is automatically created whenever conditions are met.

hs.superstore.laboratory.<id>

• It contains an offline cache of cohorts that a user got assigned for HubSpot Product experiments.
• It doesn't contain personal identifiable information or information that can identify your device or hardware
• HubSpot experiments are anonymous and aren't attached to user sessions. However, if tracking consent is given, specific experiments might be tied to identifiable user sessions.
• The individual contents of this storage entry expire automatically upon specific dates determined by HubSpot Product. Often, these are 48 hours.
• It can't be manually removed and is automatically created whenever conditions are met.

__cfruid

This cookie is set by HubSpot’s CDN provider because of their rate limiting policies. It expires at the end of the session. Learn more about Cloudflare cookies. 

__cfuvid

This cookie is set by HubSpot’s CDN provider because of their rate limiting policies. It expires at the end of the session. Learn more about Cloudflare cookies. 

__cf_bm

This cookie is set by HubSpot's CDN provider and is a necessary cookie for bot protection. It expires in 30 minutes. Learn more about Cloudflare cookies. 

Analytics cookies 

These are non-essential cookies controlled by the cookie banner. If you're a visitor to a site supported by HubSpot, you can opt out of these cookies by not giving consent.

__hstc

• The main cookie for tracking visitors.
• It contains the domain, hubspotutk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).
• It expires in 6 months.

hubspotutk

• This cookie keeps track of a visitor's identity. It is passed to HubSpot on form submission and used when deduplicating contacts.
• It contains an opaque GUID to represent the current visitor.
• It expires in 6 months.

__hssc

• This cookie keeps track of sessions.
• This is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie.
• It contains the domain, viewCount (increments each pageView in a session), and session start timestamp.
• It expires in 30 minutes.

__hssrc

• Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser.
• If this cookie does not exist when HubSpot manages cookies, it is considered a new session.
• It contains the value "1" when present.
• It expires at the end of the session.

Analytics cookies also include Google Analytics.

_ga

• Used to distinguish users
• Default expiration date: 2 years.

_ga_[ID]

• Keeps track of session status
• Default expiry time: 2 years

_gcl_au

• Cookie used by Google to remember and track conversions while preserving anonymity.
• Default expiry time: 90 days

Functionality cookies

Chatflow cookie

This is the cookie used for the chatflows tool. If you're a visitor, this allows you to chat with a representative on the site.

messagesUtk

• This cookie is used to recognize visitors who chat with you via the chatflows tool. If the visitor leaves your site before they're added as a contact, they will have this cookie associated with their browser.
• With the Consent to collect chat cookies setting turned on:
  • If you chat with a visitor who later returns to your site in the same cookied browser, the chatflows tool will load their conversation history.
  • The messagesUtk cookie will be treated as a necessary cookie.

• When the Consent to collect chat cookies setting is turned off, the messagesUtk cookie is controlled by the Consent to process setting in your chatflow.
• HubSpot will not drop the messagesUtk cookie for visitors who have been identified through the Visitor Identification API. The analytics cookie banner will not be impacted.
• This cookie will be specific to a subdomain and will not carry over to other subdomains. For example, the cookie dropped for info.example.com will not apply to the visitor when they visit www.example.com, and vice versa. 
• It contains an opaque GUID to represent the current chat user.
• It expires after 6 months.

Chatflow cookie consent text

With the Consent to collect chat cookies setting enabled, HubSpot will prompt visitors for consent to drop a cookie in their browser before the start a chat or when they attempt to the leave the page during a chat conversation. This cookie is used to interact with website visitors and provide a visitor's chat history.

If you choose to display the banner before the visitor starts a chat and the visitor does not give consent, they will not be able to start the chat.

If you choose to display the banner upon exit intent, however, the visitor can start the chat, but if they don't consent to cookies before navigating away from the page, the chat widget will reset and the conversation will end.

With this setting disabled, a visitor can start a chat and give consent to process their information via the Consent to process setting. 

Visitors can also accept or decline cookies on the HubSpot cookie banner if it is enabled on your pages. 

• If a visitor accepts the cookie when they start a chat, but then clicks Decline on the HubSpot cookie banner, the cookie will be removed. 
• If a visitor clicks Decline on the HubSpot cookie banner before starting a chat, HubSpot will not drop a cookie or prompt them to consent to cookies in the chat widget. 

Advertisement cookies

Advertisement cookies are ad pixel cookies (such as Facebook, LinkedIn and Google) that you can opt to install using the HubSpot ads tool.

If you have the Facebook pixel code installed on your website, Facebook may set a cookie in a visitor's browser.

If you use the HubSpot ads tool to select and install your Facebook pixel on pages with the HubSpot tracking code, HubSpot will link the placing of that pixel code to the cookie notification banner. If you require opt-in consent via this banner, the Facebook pixel will not be able to set any cookies until the visitor has have opted in. 

If you manually placed the pixel code on pages (e.g., by editing your site header HTML), HubSpot will not be able to control the visitors Facebook is able to set cookies on.

COOKIES PRESENT ON THE SITE PORTAL-SELFCARE.WIFIRST.NET 

On the “portal-selfcare.wifirst.net” website administered by Wifirst are present only the cookies strictly necessary for the provision of the service which are not subject to the consent of the users.

THE TRACERS PRESENT IN CERTAIN EMAILS

Wifirst uses tracking pixels and tracers included in the form of an image in transactional emails, i.e. in emails following an action/transaction initiated by the user (for example: email summarizing the order placed, email communicating an invoice, email confirming the creation of an account or sending a password). These technologies make it possible to obtain information on the rate of opening of the emails concerned and on the click rate on the links possibly inserted in these emails, in order to allow Wifirst to check and/or confirm the good reception of the emails as well as consultation of the information available via the links provided.

COOKIE MANAGEMENT AND PIXELS

Managing cookies with Wifirst

Wifirst gives you full control over the cookies placed on your terminal, via the information banner that appears when you first connect to our site https://www.wifirst.com.You can choose to accept or refuse the deposit of certain cookies on your terminal, except for strictly necessary cookies which are essential for the proper functioning of our services and are thus automatically deposited.

You can modify your choices of cookies placed at any time by using our preferences configuration module available on the yellow icon at the bottom left of each page of the site.

Please be aware that cookies play an important role in the operation of our services. Therefore, if you refuse or delete cookies, it could affect the availability and operation of the services.

Managing cookies on your internet browser

Most browsers accept cookies by default. However, you can decide to block these cookies or ask your browser to warn you when a site tries to implement a cookie on your device. In this context, we inform you that you can configure your browser to delete or reject cookies by default. For the management of cookies and your choices, the configuration of each browser is different. It is described in the help menu of your browser, which will allow you to know how to modify your wishes in terms of cookies.

 Chrome : https://support.google.com/chrome/answer/95647?hl=fr

Internet Explorer : https://support.microsoft.com/fr-fr/help/17442/windows-internet-explorer-delete-manage-cookies

Safari : https://support.apple.com/fr-fr/guide/safari/sfri11471/mac

Firefox : https://support.mozilla.org/fr/products/firefox/protect-your-privacy/cookies

Opéra : https://www.opera.com/help/tutorials/security/privacy/  

The settings chosen may modify your browsing on the Internet and your conditions of access to certain services requiring the use of cookies.

PERSONAL RIGHTS

If you have any questions or comments about how we use cookies, you can contact Wifirst's Data Protection Officer:

By email to the following email address: donnees-personnelles@wifirst.fr or, By post to the following address Wifirst - Service client : données personnelles, 26 rue de Berri, 75008 Paris

Regarding the third-party cookies placed on our site, they are likely to allow our partners to process your personal data if you accept them. You can view how your personal data is handled on their websites.

To find out more about your rights in terms of personal data protection, you can consult the CNIL website: www.cnil.fr

COMING INTO FORCE

This cookie policy and any amendments come into force on the date of the posting of the latest updated version on the website.