Skip to main content
WEBSALE V8s sets cookies to provide certain shop functions. This page lists all cookies that the shop sets itself, with name, validity, content, and the condition under which each is created. It is the basis for the cookie list in your privacy policy. Cookies set by embedded third-party services are not listed here. For those, see the note below.

​
Which domain the cookies apply to

The shop always sets its cookies for the main domain from the configuration, never for subdomains.
Embedded JavaScripts and other elements from third-party providers, for example from tracking or advertising service providers, often set their cookies across subdomains in the form .meinshop.de. This means they also apply to m.meinshop.de and any other subdomain. WEBSALE has no influence on this; it is the responsibility of the third-party provider and the merchant.Transferring data to third parties via cookies or tracking methods is a sensitive matter. As long as the third party does not declare and maintain a handling of personal data that is recognized as transparent by the EU data protection authorities, you should refrain from any data transfer to these third parties. You are liable. Coordinate the use of cookies with your data protection officer.
The cookies listed here are either strictly necessary or tied to a function that you enable yourself. Strictly necessary cookies are permitted without a specific consent request. For the others, the visitor’s consent is decisive, see below.This page does not replace legal advice.
In the following tables, <shopid> stands for your shop ID and <subshopid> for the identifier of the subshop, usually the language name.

​
Cookies that are always set

These three cookies are created on every shop visit, regardless of the configuration. The security token is only created in SSL mode. On logout, the session cookie and security token are cleared immediately.

​
Advertising success and affiliate programs

These cookies are only created if the shop was opened with a referrer or an affiliate program is connected. The code for the affiliate program is stored in a separate cookie because several affiliate programs can run at the same time. Within the validity period, a purchase is assigned to the matching partner; this is part of the terms of use for affiliate programs.
The recommendation cookie, ws_<shopid>_<subshopid>_taf, is missing from the previous documentation and is added here. It is only set if consent has been given and CookieDays is greater than zero, and it is explicitly deleted after a successful order.
Guide: Running your own affiliate program · Connecting the shop to an existing affiliate program · Tracking advertising success with referrer and subreferrer

​
Convenience functions

These cookies are only created if you enable the corresponding function.
The automatic login cookie is missing from the previous documentation and is added here.The shopping cart cookie is the only one without a subshop identifier in its name. It therefore applies to all subshops of the same shop.
Browsers limit the design cookie to 4 kilobytes. If you write more into it via DC-CookieData_set(), the browser silently discards the cookie.
KeepBasketDays is clamped to the range of 5 to 90 days when read. Smaller values are raised to 5, larger values are reduced to 90. The cookie’s validity is deliberately 10 days longer so that the shopping cart does not disappear before its server-side retention period ends.The cookie shopping cart disables itself in three cases: when the IDS interface is active, when a customer account has been taken over via superuser, and when the shopping cart is saved in the customer account. In these cases, the cookie is not created at all.
Guide: Using the cookie shopping cart · Welcome back function · Onsite personalization · Reference: DC-CookieData_set

​
Redirects

The cookie records that a redirect has taken place so that the shop can display the appropriate notice on the target page. It is cleared on the next visit. Guide: SpecialHandling of products and categories that are no longer available These cookies are only created if you have enabled the AgreementCookies section. In the name of the second cookie, <ID> stands for the service identifier from the shop.config, and <typ> for one of the three values optin, optoutchecked, or optoutunchecked.
The previous documentation states the string yes as the content of both cookies. The service cookie actually contains yes or no, depending on whether the visitor consented or objected. This is corrected here.
Because the type is part of the cookie name, a later change to a service’s Type or ID causes the shop to look for a differently named cookie and not find it. All consents previously given for this service are then treated as nonexistent, and the layer opens again for all visitors.
If the shop is opened from within the WEBSALE app, the shop sets these cookies based on the decision in the operating system’s tracking framework. In this case, a fixed validity of one year applies, not the configured one. This is added here.
Guide: Consent to data processing · Materials: Consent to data processing

​
Security attributes

The previous documentation only lists the SameSite attribute. The shop also sets HttpOnly and Secure. This overview is added here. HttpOnly means that JavaScript cannot read the cookie. Secure means that the browser only sends it over HTTPS. You usually don’t need either attribute in your privacy policy, but they help with troubleshooting and security audits. Guide: Session management · Reference: shop.config, Basic section