This article outlines the cookies used on Community Platforms & Community Chat, their purpose, and how they are managed in compliance with data protection regulations.
Community Platforms
The list below shows you the cookies we use for Community Platforms: what they are for, why they are used and how long they are stored in your web browser.
Name |
Domain |
Owner |
Duration |
What it is |
Functional cookie |
Analytical cookie |
apex_test |
Main domain |
Skeepers |
Session |
Checks whether cookies can be placed for the below purposes. |
Yes (Not optional) |
No |
tokyUserId |
Main domain |
Skeepers |
Session |
Giving a unique ID to a user of Skeepers modules. |
||
logglytrackingsession |
Community domain |
Loggly |
Session |
Used to track errors during visitor's session and report them. |
||
.ASPXAUTH |
Community domain |
Skeepers |
13 months |
Authenticates a user. |
||
islogged |
Community domain |
Skeepers |
13 months |
Allows users to be identified. Allows to have a history of questions/answers in the chat. |
||
__cf_bm |
Community domain |
Cloudflare |
30 min |
Necessary to support Cloudflare Bot Management. Currently in private beta. As part of our bot management service, it helps: • Manage incoming traffic that matches criteria associated with bots. |
||
cookieOptinBanner |
Main domain |
Skeepers |
396 days |
Keeps track of the user's choice of whether or not to accept analysis cookies. |
||
|
_gat_gtag_ xxxxxxxxx xxxxxxxxx xxxxxxxxx |
Main domain |
Google Analytics |
Few seconds |
Associated with Google Universal Analytics. It is: • Included in every page request on a site. • Used to calculate visitor, session andncampaign data for site analysis reports. |
No |
Yes (Optional cookie) |
_gid |
Main domain |
Google Analytics |
1 day |
Associated with Google Universal Analytics. It: • Stores and updates a unique value for each page visited. |
||
_ga |
Main domain |
Google Analytics |
400 days |
Associated with Google Universal Analytics. It is: • Used to distinguish unique users (assigning a randomly generated number as a customer ID). • Included in every page request on a site. • Used to calculate visitor, session and campaign data for site analysis reports. |
||
_ga_XXXXXX |
Main domain |
Google Analytics |
400 days |
Associated with Google Analytics 4. It: • Allows to count visits and traffic sources to measure and improve the performance of our site. • Helps us know which pages are the most and least popular. • Helps us see how visitors move around the site. All information this cookie collects is aggregated and therefore anonymous. |
Community Chat
1 - Cookie Policy for Skeepers Community Chat
Skeepers Community Chat uses cookies to ensure the technical operation of the chat and to track user behavior. Also, cookies allow us to track traffic statistics, trends, and types of interactions.
As for all tracers, the deposit and reading of cookies in the context of a chat are governed by Article 82 of the French Data Protection Act. Management of the deposit of cookies required for the operation of the Community Chat.
Cookies are deposited and read on the user's terminal to guarantee the chat's operation, keep its connection history, and remember the user's display choice.
According to the CNIL guidelines, two options are offered for managing cookies. You can modify your wishes at any time regarding the display and management of cookies.
Options and recommendations for managing cookies on your site
Skeepers cookies are not set for all users by default. They are only set when the user interacts with the chat to ask for help.
In this context, the Community Chat is considered strictly necessary for providing an online communication service at the user's express request. Furthermore, as our cookies are not linked to advertising or social networks, no consent is required.
As a result:
- There is no need to obtain user consent for Community Chat cookies (via the cookie banner).
- Skeepers does not set cookies unless a user has interacted with the chat.
- We therefore recommend that you do not obtain consent to enable chat.
If however, you wish to include it in the banner, this is possible.
In this case, the cookie is deposited and activated before the Community Chat is used and it is only displayed when the user has accepted the cookies. We observe from -20% up to -50% visibility among your users if the chat is subject to cookie acceptance.
As a result:
- Consequent loss of visibility of the chat to your visitors.
- 20 to 50% fewer users helped
2 - Table of cookies
The list below shows you the cookies we use for Community Chat: what they are for, why they are used and how long they are stored in your web browser.
Name |
Domain |
Duration |
What it is |
Functional cookie |
Analytical cookie |
|
__cfduid (replace by __cf_bm is link to a community) |
12 months |
Clouflare cookie. Used to identify users with a common IP to secure their connection. |
Yes |
No |
|
toky_state |
brand.xx |
13 months |
Need to know and record the state of the widget desired by the user. Open, minimised, closed widget. |
||
islogged |
13 months |
Allows to identify users. Allows to have a history of questions/answers in the chat. |
|||
TokyUserID |
brand.xx |
100 days |
Giving a unique ID to a user of Skeepers modules |
||
.ASPXAUTH |
13 months |
Session cookie that authenticates a user. |
3 - Data Storage and Retention Policy for Brand Community by Skeepers
Retention of exchanges collected by the community chat :
- Without creating an account on Skeepers, conversations are kept for 8 weeks.
- With a Skeepers account, conversations are kept for 3 years.
- If an account is blocked, data is kept for 1 year.
Location:
Data is stored in Europe, in Amsterdam via Microsoft Azure.