Cookie Policy - Salecare
Language. This is a translation of the Polish document "Polityka Cookies - Salecare", provided for convenience. The Polish version is the binding one; in the event of any discrepancy between the two, the Polish text prevails.
Introduction
- This Cookie Policy describes which cookies and similar technologies the Salecare service (the Service) uses, for what purpose, and how the User can manage their consents.
- This Policy supplements the Privacy Policy - the rules described in the Privacy Policy apply to personal data processed in connection with cookies.
- The administrator of the Service is Simple Studio Piotr Hyra, ul. Wręczycka 90, 42-133 Bieżeń, Poland, VAT ID (NIP) 5742060804. Contact for cookie and data protection matters: [email protected].
1. What cookies are
- Cookies are small text files saved on the User's device while using the Service. Among other things, they make it possible to maintain a session, remember preferences and - with consent - measure traffic.
- Besides cookies, the Service uses similar technologies with a comparable effect, in particular browser storage (localStorage, sessionStorage), used to remember interface preferences.
- By storage time we distinguish session files (deleted when the browser is closed) and persistent files (stored for a defined period). By origin - first-party files (of the Service) and third-party files (e.g. of an analytics provider).
2. Consent and legal basis
- Necessary files are required for the Service to work and are used on the basis of Article 399(3) of the Act of 12 July 2024 - Electronic Communications Law (PKE) - their use does not require the User's consent.
- Preference files are saved solely as a result of an explicit action by the User - e.g. clicking the language, theme or interface layout switch - and serve only to deliver the function the User requested (remembering the choice made). As files necessary to provide a service explicitly requested by the User, they are used on the basis of Article 399(3) PKE and do not require consent. If the User does not use a given function, no file is saved.
- Analytics files are used solely after obtaining the User's prior consent, given through the consent banner. The basis is Article 399(1) PKE (storing information in, or gaining access to information in, the terminal equipment with consent) and Article 6(1)(a) GDPR (consent) as regards the related processing of personal data.
- The Service does not use marketing or advertising files. Should any be introduced, this Policy will be updated and a separate consent request made beforehand.
- Consent is voluntary. Refusing consent to analytics files does not restrict access to any function of the Service.
- Consent may be withdrawn or changed at any time - with effect for the future, without affecting the lawfulness of processing carried out before the withdrawal (see section 6).
3. Cookie categories
| Category | Requires consent | What they are for |
|---|---|---|
| Necessary | No | Maintaining the session and authentication, protection against attacks (CSRF, the Cloudflare network), protecting the sign-up, contact and access request forms against bots (Google reCAPTCHA), remembering the cookie choice itself. Without them the Service does not work properly. |
| Preferences | No - saved solely at the User's explicit request (Article 399(3) PKE) | Remembering interface settings deliberately chosen by the User, e.g. language and theme (light/dark). They are created only after the relevant switch is clicked. |
| Analytics | Yes | Measuring traffic and how the Service is used in order to improve it (Google Analytics). |
The Service does not use marketing or advertising files (see section 2(4)).
4. Detailed list of files
The list below covers the cookies and similar technologies used in the Service. Which specific files appear depends on whether the User is signed in and which consents they have given.
| Name | Category | Origin | Purpose | Storage time |
|---|---|---|---|---|
salecare-session |
Necessary | First-party | Session identifier, authentication of a signed-in User | Session (up to approx. 2 hours) |
XSRF-TOKEN |
Necessary | First-party | Protection against CSRF attacks | Session |
cookie_consent |
Necessary | First-party | Remembering the cookie choice (so as not to ask again) | Up to 13 months |
cookie_consent_uid |
Necessary | First-party | Identifier of the consent record (accountability) | Up to 13 months |
remember_web_* |
Necessary | First-party | Remembering the sign-in when the User ticks "remember me" | Up to 5 years |
locale |
Preferences | First-party | Remembering the interface language chosen by the User | Up to 12 months |
appearance |
Preferences | First-party | Remembering the theme (light/dark/system) chosen by the User | Up to 12 months |
sidebar_state |
Preferences | First-party | Remembering the state of the side menu set by the User in the panel | 7 days |
lp-theme (sessionStorage) |
Preferences | First-party | Remembering the theme chosen on the landing page within the session | Session |
_GRECAPTCHA |
Necessary | Telling a human from a bot in the sign-up form, the contact form and the access request form (Google reCAPTCHA). Saved once the User starts filling in such a form; no consent required, as a file necessary for security | Up to 6 months | |
cf_clearance |
Necessary | Cloudflare | Confirms that the browser has passed the check of the Cloudflare network, through which traffic to the Service passes. The network checks the browser with a bot-detection script that runs on the Service's pages, and this file spares the browser a check on every visit | Up to 1 year |
__cf_bm |
Necessary | Cloudflare | Telling human traffic from bot traffic on the Cloudflare network. Saved only when that protection sets it | 30 minutes |
_ga, _ga_*, _gid |
Analytics | Traffic measurement and usage statistics (Google Analytics) - only after consent | _ga/_ga_* up to 2 years, _gid 24 hours |
5. Google Analytics
- With consent to analytics files, the Service uses Google Analytics 4 provided by Google Ireland Limited (and Google LLC). The tool helps us understand how Users use the Service and improve how it works.
- The Google Analytics script is loaded only after consent is given - before consent it is not fetched and saves no cookies.
- Using Google Analytics may involve a transfer of data to a third country (the USA). The rules and safeguards for such a transfer (including the EU-US Data Privacy Framework and standard contractual clauses) are described in section 5 of the Privacy Policy.
- Consent to analytics may be withdrawn at any time (see section 6). After consent is withdrawn, the Service stops loading Google Analytics, blocks the already loaded script from sending data and deletes the cookies it saved (
_ga,_ga_*,_gid). Independently of this, the User may install the browser add-on blocking Google Analytics made available by Google.
6. Managing consent and cookies
- Consent banner. On the first visit to the home page or to the pages describing the Service's features, a banner is displayed in which the User can accept all files, choose necessary files only, or set consent by category. The refuse button is just as visible and accessible as the accept button.
- Changing consent. The choice can be changed at any time through the "Cookie settings" link in the footer of the home page and of the pages describing the Service's features.
- Browser settings. Cookies can also be deleted and blocked in the browser settings. Blocking necessary files may, however, prevent the Service from working correctly (e.g. signing in).
7. Changes to the Cookie Policy
- The Operator may update the Cookie Policy, in particular where the files used, the providers or the applicable law change.
- Where the scope of files requiring consent changes materially, the Service will ask the User for consent again.
- The current version of the Policy is available in the Service at all times, together with the date of its last update.