Table of Contents
Cookie Policy
Overview of Cookies and other trackers
Definition of cookies
A cookie is a small text file placed on your terminal (computer, tablet, smartphone) when you visit a website such as our Site.
When you first connect to the Yogosha website (https://yogosha.com, the “Site”), you are informed by a cookie banner that certain data relating to your navigation may be processed via cookies, trackers or other similar technologies (hereinafter “Cookies”). You are also informed of the purposes of the Cookies used by our Site as well as the methods of collecting your consent to this effect. The present Cookie Policy specifies the different purposes related to these Cookies (1) and explains the steps to follow to set them and to learn more about each type of Cookie (2).
The Cookies on our Site collect personal data related to your navigation on the Site, such as your IP address, connection data, your geographical area, your user name when you are connected to your customer or researcher account, as well as technical data related to the device you are using and your language preferences.
The data collected through Cookies are not kept for more than 13 months after their collection and your consent will be requested every six (6) months.
I. Cookies necessary for the functioning of the Site
These cookies are necessary for the proper functioning of the Site and for your navigation. They allow you to access the main features of the Site. For example, the connection to any private space on the Site as a customer or researcher, in order to ensure your identification on all pages of the Site and to ensure optimal navigation via your account.
In accordance with the applicable laws and regulations and the recommendations of the CNIL, these Cookies are exempt from the prior collection of your consent. In order to ensure the proper functioning of the Site, these cookies can not be disabled.
The YOGOSHA Company uses the following Cookies on its Website:
- The Cookie “__cfduid” affixed by our provider Cloudflare, kept for 1 year, in order to identify users sharing the same IP address and apply specific security settings to each user.
- The “axeptio_cookie” Cookie is set by a script that displays a banner allowing the user to accept Cookies on a case-by-case basis and is kept for 13 months, in order to determine for which Cookies the user has given his consent.
- The “axeptio_all_vendors” Cookie: Lists all available vendors subject to the user’s consent
- The “axeptio_authorized_vendors” Cookie: Lists all cookies validated by the user
- The ” wp-wpml_current_language ” cookie : stores the user’s preferred language
- The ” _ga_123″ Cookie : calculates visitors, session, campaign data and keeps track of site usage for analysis purposes. The cookie stores information anonymously and assigns a randomly generated number to recognize each unique visitor.
- The “_ga” Cookie: used to distinguish users. Data is anonymized by default (GA4).
II. Third party cookies for audience measurement
These cookies are used, necessarily with your prior consent, to evaluate the use of the Site, by collecting information on your navigation. This information is collected in order to carry out measurements of audience, of statistics, with an aim of improving the quality of the services provided by the Site and to offer you a better user experience.
Google Analytics 4
The YOGOSHA Company uses Google Analytics 4 to collect information on the origin of traffic generated on the Site, the activity on the various pages as well as the time spent on the Site for internal analysis purposes.
We use Google Analytics 4 in a proxyfied way in accordance with the recommendations of the French CNIL to make it GDPR compliant. The proxyfication is done via a GTM Server-Side container: the data is passed through our own servers, on French ground, and is completely anonymized before any further use in Google Analytics.
For more information on this type of Cookie, we invite you to read their terms of use at the following link:
- https://support.google.com/analytics/answer/7108387?hl=fr
- https://support.google.com/analytics/answer/7108387?hl=fr
In addition, via your browser, you can manage and deactivate these Cookies directly via the following link: https://tools.google.com/dlpage/gaoptout
Matomo
Matomo is a fully GDPR compliant analytics solution, approved by the CNIL. We use Matomo self-hosted on our own servers, meaning no one can access its data except us. The tool has been configured according to this Matomo configuration guide which exempts it from consent collection, in compliance with the rules of the French CNIL
We do not collect any personal data, but if you wish to opt-out of Matomo tracking, you can do so below.
III. Advertising Cookies
These are Cookies used, necessarily with your prior consent, to present you with offers and information that are personalized and adapted to your centers of interest when you browse the Internet outside our Site.
The Cookies used by the YOGOSHA Company are affixed by the Hubspot Company, in order to know its users, to carry out marketing campaigns and to provide a chat service to Internet users.
For more information on these cookies, we invite you to read their terms of use at the following link: https://knowledge.hubspot.com/fr/articles/kcs_article/reports/what-cookies-does-hubspot-set-in-a-visitor-s-browser
Similarly, you can manage and deactivate these Cookies via your browser, as indicated below in Section 2. The refusal of these Cookies has no impact on the use of the Site.
IV. Social Network Cookies
These Cookies are placed on the Site by social networks and allow you, if necessary and with your consent, to follow us via our pages on social networks in order to be aware of news that are likely to interest you. This also allows us to gain visibility on social networks thanks to you.
On the Site, Twitter, YouTube and LinkedIn sharing buttons are integrated via third-party technologies that collect certain data. You can consult the privacy policies of these social networks via the links listed below to learn more about the associated processing and to be aware of your rights:
– Twitter: https://twitter.com/privacy?lang=fr
– YouTube : https://policies.google.com/privacy?hl=fr&gl=fr
– LinkedIn: https://www.linkedin.com/legal/cookie-policy?_l=fr_FR
How to set up Cookies?
Your browser gives you the possibility to modify its standard settings, but also to delete the existing Cookies deposited on your equipment or terminal, or to inform you if new Cookies are likely to be deposited on your terminal.
However, if you choose to disable Cookies via your browser, you may not be able to take advantage of all the features we offer through the Site and Your browsing experience may be degraded as a result.
To express or revoke your choices at any time, refer to the help menu or the dedicated section of your browser. As an example you can get more information on the following pages:
– For Internet Explorer™: http://windows.microsoft.com/fr-FR/windows-vista/Block-or-allow-cookies
– For Safari™: http://support.apple.com/kb/ht1677?viewlocale=fr_FR
– For Chrome™: https://support.google.com/chrome/answer/95647?hl=fr
– For Firefox™: https://support.mozilla.org/fr/kb/activer-desactiver-cookies
– For Opera™: http://help.opera.com/Windows/10.20/fr/cookies.html
Finally, personal data relating to this Cookie Policy may be processed outside the European Union by certain subcontractors of YOGOSHA who are established in an adequate country, or who present appropriate guarantees within the meaning of the GDPR or who have implemented additional technical measures. For more information on cookies and your rights, you can also consult the website of the CNIL, the French authority for the protection of personal data: https://www.cnil.fr/vos-libertes/vos-traces/les-cookies/
Types of Cookies and purposes
The table below lists the different types of non-functional cookies used by Yogosha and the purposes of these cookies. The list of third party cookies is not exhaustive.
| Cookie | Vendor | Personal Data | Why? | Duration of the collect |
| axeptio_cookie | Axeptio | None | Functional cookie to collect user consent. | 12 months |
| axeptio_all_vendors | Axeptio | None | Lists all the vendors available for the visitor’s consent. | 12 months |
| axeptio_authorized_vendors | Axeptio | None | Lists all the cookies validated by the visitor. | 12 months |
| wp-wpml_current_language | WordPress | None | Stores the current language. | Session |
| _ga_123 | Google Analytics 4 | None | The _ga_# cookie, installed by Google Analytics, calculates visitor, session, campaign data, and also keeps track of site usage for the site’s analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. | 13 months |
| _ga | Google Analytics 4 | None | Used to distinguish users. Data is anonymised by default. | 13 months |
| __hssc | HubSpot | It contains the domain, viewCount (increments each pageView in a session), and session start timestamp. | This cookie keeps track of sessions. It is used to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. | 30 minutes |
| __hssrc | HubSpot | It contains the value “1” when present. If this cookie does not exist when HubSpot manages cookies, it is considered a new session. | Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser. | Expires at the end of the session |
| hubspotutk | HubSpot | It contains an opaque GUID to represent the current visitor. | This cookie keeps track of a visitor’s identity. It is passed to HubSpot on form submission and used when deduplicating contacts. | 6 months |
| __hstc | HubSpot | It contains the domain, utk, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). | HubSpot’s main cookie for tracking visitors. | 6 months |
| _hjSessionUser{site_id} | Hotjar | JSON data type. Related to the user. | Set when a user first lands on a page. Persists the Hotjar User ID which is unique to that site. Ensures data from subsequent visits to the same site are attributed to the same user ID. | 12 months |
| _hjid | Hotjar | UUID data type. Related to the user. | Set when a user first lands on a page. Persists the Hotjar User ID which is unique to that site. Ensures data from subsequent visits to the same site are attributed to the same user ID. | 12 months |
| _hjFirstSeen | Hotjar | Boolean true/false data type. Related to the user. | Identifies a new user’s first session. Used by Recording filters to identify new user sessions. | Session duration |
| _hjUserAttributesHash | Hotjar | Hash data type. Related to the user. | User Attributes sent through the Hotjar Identify API are cached for the duration of the session. Enables us to know when an attribute has changed and needs to be updated. | Session duration |
| _hjCachedUserAttributes | Hotjar | JSON data type. Related to the user. | Stores User Attributes sent through the Hotjar Identify API, whenever the user is not in the sample. Collected attributes will only be saved to Hotjar servers if the user interacts with a Hotjar Feedback tool. Cookie used regardless of whether a Feedback tool is present. | Session duration |
| _hjViewportId | Hotjar | UUID data type. Related to the user. | Stores user viewport details such as size and dimensions. | Session duration |
| hjSession{site_id} | Hotjar | JSON data type. Related to the session. | Ensures subsequent requests in the session window are attributed to the same session. | 30 minutes |
| _hjSessionTooLarge | Hotjar | Boolean true/false data type. Related to the session. | Causes Hotjar to stop collecting data if a session becomes too large. Determined automatically by a signal from the WebSocket server if the session size exceeds the limit. | Session duration |
| _hjSessionRejected | Hotjar | Boolean true/false data type. Related to the session. | If present, set to ‘1’ for the duration of a user’s session, when Hotjar has rejected the session from connecting to our WebSocket due to server overload. Applied in extremely rare situations to prevent severe performance issues. | Session duration |
| _hjSessionResumed | Hotjar | Boolean true/false data type. Related to the session. | Set when a session/recording is reconnected to Hotjar servers after a break in connection. | Session duration |
| _hjLocalStorageTest | Hotjar | Boolean true/false data type. Related to the session. | Checks if the Hotjar Tracking Code can use local storage. If it can, a value of 1 is set. Data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created. | Under 100ms duration |
| _hjIncludedInPageviewSample | Hotjar | Boolean true/false data type. Related to the session. | Set to determine if a user is included in the data sampling defined by our site’s pageview limit. | 30 minutes duration |
| _hjIncludedInSessionSample | Hotjar | Boolean true/false data type. Related to the session. | Set to determine if a user is included in the data sampling defined by your site’s daily session limit. | 30 minutes duration |
| _hjAbsoluteSessionInProgress | Hotjar | Boolean true/false data type. Related to the session. | Used to detect the first pageview session of a user. | 30 minutes duration |
| _hjTLDTest | Hotjar | Boolean true/false data type. Related to the session. | Hotjar tries to store the _hjTLDTest cookie for different URL substring alternatives until it fails. Enables Hotjar to try to determine the most generic cookie path to use, instead of page hostname. It means that cookies can be shared across subdomains (where applicable). After this check, the cookie is removed. | Session duration |
| lidc | To facilitate the selection of data centers | 24 hours | ||
| li_mc | Used as a temporary cache to avoid searches for user consent in the database for the use of non-essential cookies, and used to obtain consent data from the customer to apply their consent | 6 months | ||
| bcookie | Browser cookie to identify each device accessing LinkedIn to detect abuse of the platform and for diagnostic purposes | 12 months | ||
| bscookie | Used to remember that a logged-in user has been verified using two-factor authentication | 12 months | ||
| JSESSIONID | Used for CSRF (Cross Site Request Forgery) protection | Session | ||
| lang | Used to remember a user’s language setting to ensure that LinkedIn displays in the language selected by the user in their preferences | Session | ||
| sdsc | Context cookie for the login data service, used for database routing to ensure consistency across databases when making a change. Used to ensure that user-entered content is immediately available after submission to the submitting user. | Session | ||
| li_gc | Used to store guest users’ consent to use cookies for non-essential purposes. | 6 months | ||
| UserMatchHistory | Synchronization of LinkedIn Ads credentials | 30 days | ||
| AnalyticsSyncHistory | Used to store data about when a synchronization was performed with the lms_analytics cookie | 30 days | ||
| lms_ads | Used to identify LinkedIn users outside of LinkedIn for advertising purposes | 30 days | ||
| lms_analytics | Used to identify LinkedIn users outside of LinkedIn for analytical purposes | 30 days | ||
| li_fat_id | Indirect member identifier for members for conversion tracking, retargeting and analytics | 30 days | ||
| li_sugr | Used to find a probability match with a user’s identity outside the designated countries | 90 days | ||
| _guid | Used to identify a LinkedIn member for advertising purposes via Google Ads | 90 days | ||
| BizographicsOptOut | Used to determine the deactivation status of non-users | 10 years | ||
| li_giant | Indirect identifier for LinkedIn user groups used for conversion tracking purposes | 7 days | ||
| twid | Determines if the user logged in during the browser session, allows tweets and records the number of times a page is tweeted. | 12 months | ||
| guest_id | This cookie is set through Twitter integration and social media sharing capabilities | 13 months | ||
| muc | This cookie is used to identify bots | |||
| personalization_id | This cookie tracks activity outside of Twitter for a personalized experience. | 13 months | ||
| auth_multi | This cookie is for authentication purposes if you have several accounts. | 13 months | ||
| eu_cn | This cookie is for cookie notices. | 12 months | ||
| guest_id_ads | This cookie is intended for advertising in case of disconnection | 12 months | ||
| dnt | This cookie allows you to refuse the personalization of advertisements | 13 months | ||
| _pk_id |
Matomo | None | Used to store a few details about the user such as the unique visitor ID. | 13 months |
| _pk_ref |
Matomo | None | Used to store the attribution information, the referrer initially used to visit the website. | 6 months |
| _pk_ses, _pk_cvar, _pk_hsr |
Matomo | None | Short lived cookies used to temporarily store data for the visit. | 30 minutes |
| _pk_testcookie |
Matomo | None | Is created and should be then directly deleted (used to check whether the visitor’s browser supports cookies) | Instant |
| mtm_consent (or mtm_consent_removed) | Matomo | None | Are created to remember that consent was given (or removed) by the user. | 12 months |
| matomo_ignore |
Matomo | None | 30 years | |
| matomo_sessid |
Matomo | None | It is important to note that it doesn’t contain any data used to identify visitors and is considered an « Essential » cookie. | 14 days |
Contact us
If you need more information on cookies, feel free to reach us at the following email addresses : l[email protected] or [email protected]
