COOKIE POLICY
INTRODUCTION
Please find below information on cookies installed on the website “https://7.design/” (hereinafter the “Website”).
WHAT A COOKIE IS AND WHAT COOKIES ARE USED FOR
A cookie is a small data file which, in the form of a unique anonymous code, is sent to your browser from a web server and then stored on the hard disk of your device (computer, smartphone, tablet).
Cookies may allow the correct use of an internet site (hereinafter “Technical Cookies”), or they may create statistical analyses on the manner you navigate the Website (hereinafter “Analytical Cookies”), or they may check your preferences in the context of your online navigation in order to propose advertising messages (hereinafter “Profiling Cookies”).
Cookies may be stored on your device for a period of time of variable duration (hereinafter “Permanent Cookies”), or they may be deleted on the closure of the browser or be of limited duration (“Session Cookies”).
Cookies may be installed by the website you are visiting (hereinafter “First Party Cookies”) or they may be installed by other websites (hereinafter “Third-Party Cookies”).
COOKIES USED ON THIS WEBSITE AND PURPOSES OF SUCH USE
This Website uses the following cookies:
a) Technical Cookies
The Technical Cookies allow the Website to function correctly, making possible for you to view its content in the related language and market as from your first visit. They are able to recognize the country you are connecting from and to ensure that, on each visit, you are automatically re-directed to the version of the Website applicable for your country.
They also make possible for you to create an account, to log in and to manage orders.
If you are a registered user, thanks to the Technical Cookies the Website will be able to recognise you when accessing the services offered to registered users only.
Technical Cookies are able to tell if you purchase products on the Website through an affiliated or partner site, making possible for us to fulfil our obligations in relation to such partner sites.
Technical Cookies are strictly necessary for the functioning of the Website.
b) Analytical Cookies
The Analytical Cookies are used to create statistical analyses on the way users navigate on the Website (e.g. the device they used, the number of pages they visited or the number of clicks on a particular page they made during navigation).
Their purpose is to improve Website functions.
The results of the analysis arising from the use of Analytical Cookies are processed in an anonymous way and for statistics purposes only.
In the event that they only allow the tracking of anonymous IP addresses (with a portion of the code that is not visible), they are assimilated to Technical Cookies as they do not allow any users’ identification.
c) Profiling cookies
The Website uses Profiling Cookies, through which it registers preferences and habits detected during each users’ visit and thus create profiles, allowing us to send you messages more in line with your preferences and interests (e.g. allowing you to view the products you are looking for more quickly, or to offer you the most similar items).
Profiling Cookies are used by trusted third parties, that make possible for us to display banner ads on other affiliate sites (so called “retargeting”), showing the products that you have recently viewed. While you browse the Website, Profiling Cookies are also used to display other products that may be of your interest, or products similar to the ones that you have just watched based on your browsing schedule.
CHARACTERISTICS OF THE COOKIES USED ON THE WEBSITE
The characteristics of the cookies used on the Website are detailed in the tables below.
a) Technical Cookies
COOKIE NAME |
FIRST PARTY/THIRD PARTY |
DEDESCRIPTION |
EEXPIRY DURATION |
benefit |
Third party |
This cookie allows session to understand benefits associated to a user, informing the front-end.If not set, the user will not be able to access areas of the site/features that are unblocked when the user has certain benefits. |
14 days |
csi |
Third party |
It is a client session identifier. A new client identifier is generated, otherwise every request and user tracking might be lost. Currently used for marketing api integration on newsletter subscription. |
14 days |
ctx |
Third party |
It gives context about users. |
14 days |
ss |
Third party |
It is an auth token for guests and registered users.If not set, a new authentication token is created every time and no state can be kept for the user. |
24 hours |
dfUserSub |
Third party |
It keeps the user chosen or geo-assigned subfolder.If not allowed every time the user comes on a site, it's redirected to its geo-located subfolder. All the experience during the navigation will use the url provided. |
24 hours |
Campaigns |
Third party |
It re-associate a returning client to an ongoing private sale campaign.If not allowed, the guest user will be able to see private sale prices only if it uses the received email link for the referred private sale campaign. |
15 days |
uc |
Third party |
This cookie allows keeping the chosen culture on sites with multiple cultures per country.If not allowed, the user will never be able to see the site on his chosen culture for some base country. |
2 months |
JSESSIONID |
First party |
This cookie ensures that we can monitor the application using New Relic. |
It depends on the session and the tenant - guest sessions expire in about 30min, logged user sessions expire after a few hours or some days |
_cf_bm |
First party |
If visitors pass a Cloudflare validation page, the cookie prevents additional challenges for up to 30 minutes. This cookie is a session cookie that lasts for up to 30 minutes from the time an end user connects with the site. |
30 minutes |
_cfruid |
Third party |
The __cfruid cookie is strictly necessary to support Cloudflare Rate Limiting products. As part of our Rate Limiting solution, this cookie is required to manage incoming traffic and to have better visibility on the origin of a particular request. |
Session |
cf_clearence |
First party |
The challenge system Cloudflare uses is cookie-based. If you solve a challenge correctly, Cloudflare will set a cookie called CF_CLEARANCE for the domain that presented the challenge. |
24 hours |
forterToken |
Third party |
This cookie stores the Forter-generated device identifier. It identifies the browser between browsing sessions. |
5 years |
ftr_ncd |
Third party |
A flag used to make sure data is not sent more than once per predefined timeframe. |
5 years |
lastRskxRun |
Third party |
Fraud prevention cookie |
1 year |
rCookie |
Third party |
Fraud prevention cookie |
1 year |
rskxRunCookie |
Third party |
Fraud Prevention cookie |
1 year |
b) Analytical Cookies
NAME |
FIRST PART/ THIRD PART |
DESCRIPTION |
EXPIRY DURATION |
_ga |
First party |
This cookie provides statistic on use of website |
2 years |
_gid |
First party |
This cookie provides statistic on use of website |
24 hours |
_gat |
First party |
This cookie is used to throttle request rate. |
1 minute |
_hjAbsoluteSessionInProgress |
First party |
This cookie is used to detect the first pageview session of a user. |
30 minutes |
_hjFirstSeen |
First party |
This cookie identifies a new user’s first session. Used by Recording filters to identify new user sessions. |
Session |
_hjIncludedInPageviewSample |
First party |
This cookie sets to determine if a user is included in the data sampling defined by site's pageview limit. |
30 minutes |
_hjIncludedInSessionSample |
First party |
This cookie sets to determine if a user is included in the data sampling defined by site's daily session limit. |
30 minutes |
_hjSession_{site_id} |
First party |
This cookie holds current session data and ensures subsequent requests in the session window are attributed to the same session. |
30 minutes |
_hjSessionUser_{site_id} |
First party |
This cookie sets when a user first lands on a page, persists the Hotjar User ID which is unique to that site and ensures data from subsequent visits to the same site are attributed to the same user ID. |
1 year |
ORA_FPC |
First party |
This cookie is used to distinguish users. |
2 years |
c) Profiling Cookies
NAME |
FIRST PART/ THIRD PART |
DESCRIPTION |
EXPIRY DURATION |
_fbp |
Third party |
This cookie helps to deliver, to measure and to improve the relevancy of ads shown either on Facebook or other digital platforms powered by Facebook. |
90 days |
__adroll |
Third party |
This cookie enables AdRoll to identify the device when user moves between different Digital Properties, so that it can serve targeted advertising. |
1 year |
__adroll_fpc |
Third party |
This cookie enables AdRoll to identify the device when user moves between different Digital Properties, so that it can serve targeted advertising. |
1 year |
__adroll_shared |
Third party |
This cookie enables AdRoll to identify the device when user moves between different Digital Properties, so that it can serve targeted advertising. |
1 year |
__ar_v4 |
Third party |
This cookie is used to Store and track conversions. |
1 year |
_glc_au |
Third party |
This cookie is used to Store and track conversions. |
1 year |
cto_bundle |
Third party |
This cookie presents the user with relevant content and advertisement. The service is provided by third-party advertisement hubs, which facilitate real-time bidding for advertisers. |
13 months |
uid |
Third party |
This cookie is used to distinguish users. |
13 months |
stc{id} |
Third party |
This cookie stores website user ID, traffic source IDs, page view and order count for affiliate program. |
1 year |
rmuid |
Third party |
This cookie stores website user ID, traffic source IDs, page view and order count for affiliate program. |
1 year |