Skip to Content

Privacy policy

Who we are


Our website address is: https://ecoledemode.fr.

Comments


When you leave a comment on our site, the data entered in the comment form, along with your IP address and browser user agent, is collected to help us detect spam comments.

An anonymised string created from your email address (also called a hash) may be sent to the Gravatar service to check whether you use it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. Once your comment has been approved, your profile picture will be publicly visible next to your comment.

Media


If you upload images to the website, you should avoid uploading images that contain EXIF GPS location data. Visitors to the website can download and extract location data from those images.

Cookies


If you leave a comment on our site, you can choose to save your name, email address and website in cookies. This is purely for your convenience, so that you do not have to enter these details again when you leave another comment. These cookies last for one year.

If you visit the login page, a temporary cookie will be created to determine whether your browser accepts cookies. It contains no personal data and is deleted automatically when you close your browser.

When you log in, we will set a number of cookies to save your login information and your screen display preferences. A login cookie lasts for two days and a screen options cookie for one year. If you tick “Remember me”, your login cookie will be kept for two weeks. If you log out of your account, the login cookie will be deleted.

When you edit or publish a post, an additional cookie will be saved in your browser. This cookie contains no personal data. It simply indicates the ID of the post you have just edited. It expires after one day.

Essential cookies do not require consent


__hs_opt_out

  • This cookie is used by the sign-up privacy policy to remember not to ask the user to accept cookies again.
  • This cookie is set when you give visitors the option to decline cookies.
  • It contains the string “yes” or “no”.
  • It expires after 6 months.

__hs_do_not_track

  • This cookie may be set to prevent the tracking code from sending information to HubSpot.
  • It contains the string “yes”.
  • It expires after 6 months.

__hs_initial_opt_in

  • This cookie is used to stop the banner being displayed to visitors browsing in strict mode.
  • It contains the string “yes” or “no”.
  • It expires after seven days.

__hs_cookie_cat_pref

  • This cookie is used to record the categories a visitor has consented to.
  • It contains data on the categories that have been accepted.
  • It expires after 6 months.

hs_ab_test

  • This cookie is used to consistently serve visitors the same version of an A/B test page.
  • It contains the ID of the A/B test page and the ID of the variant selected for the visitor.
  • It expires at the end of the session.

<id>_key

  • When a password-protected page is viewed, this cookie is set so that a visitor does not have to log in again if they return to the same page using the same browser.
  • The cookie name is unique to each password-protected page.
  • It contains an encrypted version of the password so that visitors do not have to enter it again on future visits.
  • It expires after 14 days.

hs-messages-is-open

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

hs-messages-hide-welcome-message

  • This cookie is used to prevent the welcome message reappearing on the same day once it has been dismissed.
  • It contains the Boolean value True or False when present.
  • It expires after one day.

__hsmem

  • This cookie is set when visitors log in to a site hosted on HubSpot.
  • It contains encrypted data identifying the member user when they are logged in.
  • It expires after seven days.

hs-membership-csrf

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

hs_langswitcher_choice

  • This cookie is used to record the language selected by the visitor when viewing pages in several languages.
  • It is set when a visitor selects a language using the language switcher and is used as a language preference to redirect them to sites in the chosen language, where applicable.
  • It contains a colon-delimited string with the ISO 639 language code on the left and the private domain it applies to on the right. For example: “EN-US:hubspot.com”.
  • It expires after two years.

__cfruid

This cookie is set by HubSpot's content delivery network provider, in line with its rate limiting policies. It expires at the end of the session. Find out more about Cloudflare cookies.

__cf_bm

This cookie is set by HubSpot's content delivery network provider and is required for bot protection. It expires after 30 minutes. Find out more about Cloudflare cookies.

Analytics cookies


These are non-essential cookies managed by the cookie banner. If you are visiting a site supported by HubSpot, you can decline these cookies by not giving your consent.

__hstc

  • The main visitor tracking cookie.
  • It contains the domain, the utk, the initial timestamp (first visit), the last timestamp (last visit), the current timestamp (current visit) and the session number (which increases with each subsequent session).
  • It expires after 6 months.

hubspotutk

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

__hssc

  • This cookie tracks sessions.
  • It is used to determine whether HubSpot should increase the session number and the timestamp data in the __hstc cookie.
  • It contains the domain, the view count (which increases with each session) and the session start timestamp.
  • It expires after 30 minutes.

__hssrc

  • When HubSpot changes the session cookie, this cookie is also set in order to determine whether the visitor has restarted their browser.
  • If this cookie is absent when HubSpot processes cookies, the session is treated as new.
  • It contains the value “1” when present.
  • It expires at the end of the session.

If you log in to HubSpot, HubSpot will set additional authentication cookies. Find out more about the cookies set in the HubSpot product. You can also see whether a contact has accepted these cookies on their timeline.


Functionality cookies


Chatflow cookie

This cookie is used for the Chatflows tool. As a visitor, you can chat with a representative on the site.

messagesUtk

  • This cookie is used to recognise visitors who chat with you through the Chatflows tool. If the visitor leaves your site before being added as a contact, this cookie will be associated with their browser.
  • With the Consent to collect chat cookies setting enabled:

    • If you chat with a visitor and they later return to your site using the same 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 disabled, the messagesUtk cookie is controlled by the Consent to process data setting in your chatflow.
  • HubSpot will not disconnect the messagesUtk cookie for visitors who have been identified through the Visitor Identification API. The analytics cookie banner will not be affected.
  • This cookie will be specific to a subdomain and will not be transferred to other subdomains. For example, the cookie for info.exemple.com will not apply to a visitor to www.exemple.com, and vice versa.
  • It contains an opaque GUID representing the current chat user.
  • It expires after 6 months.

Chatflow cookie consent text

When the Consent to collect chat cookies setting is enabled, HubSpot will ask visitors to consent to a cookie being set in their browser before they start a chat, or if they try to leave the page during a chat. This cookie is used to interact with visitors to your website and to provide a visitor's chat history.

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

However, if you choose to display the banner when the visitor tries to leave the page, they can start the chat, but if they do not consent to cookies before leaving the page, the chat widget will reset and the conversation will end.

If this setting is disabled, a visitor can start a chat and consent to their information being processed through the Consent to process data 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 starting a chat but then clicks Decline on the HubSpot cookie banner, the cookie will be deleted.
  • If a visitor clicks Decline on the HubSpot cookie banner before starting a chat, HubSpot will not be able to set a cookie or ask the visitor to consent to cookies in the chat widget.


Advertising cookies


Advertising cookies are advertising pixel cookies (such as Facebook, LinkedIn and Google) that you can add to the HubSpot Ads tool.

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

If you use the HubSpot Ads tool to select and install your Facebook pixel on pages containing the HubSpot tracking code, HubSpot will link the placement of that pixel code to the cookie notification banner. If you ask for the visitor's consent through this banner, the Facebook pixel will not be able to set cookies until the visitor has given their consent.

If you have placed the pixel code manually on pages (for example, by editing the HTML code of your site header), HubSpot will not be able to identify the visitors for whom Facebook may place cookies.

For more information, see the Facebook Business Tools Terms and the Facebook Cookie Consent Guide for Sites and Apps.


Embedded content from other websites


Articles on this site may include embedded content (for example videos, images, articles, and so on). Embedded content from other websites behaves in exactly the same way as if the visitor had gone to that other website.

These websites may collect data about you, use cookies, embed third-party tracking tools and monitor your interaction with that embedded content if you have an account and are logged in to their website.


Use and sharing of your personal data


If you request a password reset, your IP address will be included in the reset email.


How long we keep your data


If you leave a comment, the comment and its metadata are kept indefinitely. This allows us to recognise and approve any follow-up comments automatically instead of holding them in the moderation queue.

For accounts that register on our site (where applicable), we also store the personal data provided in their profile. All accounts can view, edit or delete their personal information at any time (except their username). Site administrators can also view and edit that information.


The rights you have over your data


If you have an account or have left comments on the site, you can request to receive a file containing all the personal data we hold about you, including anything you have provided to us. You can also request that we delete the personal data we hold about you. This does not cover data stored for administrative or legal purposes, or for security reasons.


Sharing your personal data

Visitors' comments may be checked using an automated spam detection service.