Cookie Policy of the Safetysoftware.eu website

Cookie Policy of SafetySoftware.eu – rules for the use of cookies and similar technologies, consent settings, sessions, login, and embedded external content.

ID: CO-2026-V1 Updated: 01.04.2026
Print / PDF

§1. General provisions

  1. This Cookie Policy sets out the rules for the use of cookies and similar technologies in connection with the use of the SafetySoftware.eu Service, including:
    1. the public website,
    2. contact and sales forms,
    3. the client area,
    4. features available after logging in to the SaaS application.
  2. The Policy applies to users visiting the Service and to users using their account and application features.
  3. This document specifies:
    1. what technologies are used,
    2. for what purposes they are used,
    3. which of them are necessary for the operation of the Service,
    4. which of them require the user's consent,
    5. how the user can manage their settings.

§2. Controller

  1. The Controller of the Service and the entity responsible for the use of cookies and similar technologies is:

Safety Software Spółka z ograniczoną odpowiedzialnością
ul. Półłanki 80
30-740 Kraków
Poland
KRS: 0001196649
NIP: 6793342803
REGON: 542821668

  1. The Controller can be contacted at:
    1. office@safetysoftware.eu – for general and commercial matters,
    2. legal@safetysoftware.eu – for formal, legal and privacy matters.

§3. Definitions

  1. Cookies – computer data, in particular small text files, stored on or read from the user's terminal device in connection with the use of the Service.
  2. Similar technologies – technical solutions used to store information, maintain the session state or enable specific features of the Service, which do not always take the form of a classic cookie, in particular:
    1. session identifiers,
    2. sessionStorage,
    3. localStorage,
    4. mechanisms for remembering the user's decision,
    5. embedded external content.
  3. Service – the SafetySoftware.eu website together with its public and application parts.
  4. User – any person visiting the Service or using features available after logging in.

§4. Scope of technologies used

  1. Only two categories of technologies are used in the Service:
    1. necessary,
    2. functional technologies and embedded external content.
  2. Under this model, the Controller does not use:
    1. advertising cookies used for profiling,
    2. third-party marketing cookies,
    3. analytics cookies within the meaning of tools such as Google Analytics 4.

§5. Necessary technologies

  1. Necessary technologies are used only to the extent necessary to ensure the proper operation of the Service and the application.
  2. Necessary technologies include in particular:
    1. mechanisms for maintaining the user's session,
    2. authentication mechanisms and mechanisms for maintaining the logged-in state,
    3. “remember me” mechanisms, if the user uses the remember-login feature,
    4. mechanisms for remembering the user's choice regarding cookie settings,
    5. technical session identifiers and session-related security mechanisms.
  3. Necessary technologies serve in particular to:
    1. log the user in to the account,
    2. maintain an active session,
    3. ensure the secure use of the application,
    4. protect against abuse and unauthorized access,
    5. respect the user's decision regarding cookies.
  4. Necessary technologies are not used for behavioral advertising or user profiling for marketing purposes.
  5. The use of necessary technologies does not require the user's consent, because they are necessary for the provision of the service by electronic means and to ensure the security and integrity of the Service.

§6. Functional technologies and embedded external content

  1. The category “functional technologies and embedded external content” includes technologies that are not necessary for the operation of the Service itself, but enable the user to use additional features or display content originating from external providers.
  2. This category may include in particular:
    1. embedded maps,
    2. embedded videos,
    3. other external content loaded at the user's request.
  3. Content in this category is activated only after the user's consent has been obtained.
  4. Lack of consent to this category does not prevent the use of the basic features of the Service, but may result in some elements, such as a map or a video, not being displayed.

§7. Google Maps and videos

  1. Embedded external content may be made available in the Service, in particular:
    1. Google Maps,
    2. videos from YouTube.
  2. Content of this kind should only be loaded after the user has given consent to the category “functional technologies and embedded external content”.
  3. In the case of videos, the Controller seeks to use solutions limiting the scope of data processing, in particular the youtube-nocookie variant and a placeholder mechanism requiring the user to deliberately activate the content.
  4. After such content is activated, a connection may be established with the external provider's servers and that provider may apply its own technologies in accordance with its own rules and policies.

§8. Campaign data and UTM parameters

  1. The Administrator may process information about the source from which the user accessed the Service, including campaign parameters such as UTM tags.
  2. These parameters are not stored in the user's browser in the form of:
    1. marketing cookies,
    2. localStorage,
    3. browser-side sessionStorage.
  3. Information about the access source may be maintained exclusively in the server-side session for the time necessary to ensure consistent operation of the Service and to handle the current session.
  4. This solution does not constitute behavioral analytics or advertising profiling of the user.

§9. SessionStorage, localStorage and similar technologies

  1. This Policy also covers technologies other than classic cookies if they are used to store information or affect the way the Service operates.
  2. This applies in particular to:
    1. sessionStorage,
    2. localStorage,
    3. technical session identifiers,
    4. mechanisms for loading external content,
    5. solutions used to remember privacy settings.
  3. If a given technology performs a function corresponding to a necessary technology, the rules applicable to the necessary category apply to it.
  4. If a given technology is used to load embedded content or additional functionalities, the rules applicable to the category of “functional technologies and embedded external content” apply to it.

§10. Legal bases for the use of technologies

  1. Necessary technologies are used on the basis of:
    1. the need to ensure the proper operation of the Service and the application,
    2. the need to provide the service by electronic means,
    3. the Administrator's legitimate interest in ensuring the security, integrity, and continuity of operation of the system.
  2. Functional technologies and embedded external content are used solely on the basis of the user's consent.

§11. Method of giving consent

  1. During the first visit to the Service, the user is given the option to choose cookie settings.
  2. The consent model in the Service is based on two levels:
    1. necessary technologies only,
    2. necessary technologies as well as functional technologies and embedded external content.
  3. Consent to optional technologies:
    1. is voluntary,
    2. may be given knowingly by the user,
    3. may be withdrawn or changed at any time.
  4. The lack of consent to optional technologies does not affect the ability to use the basic functions.

§12. Changing cookie settings

  1. The user may change their settings regarding cookies and similar technologies at any time.
  2. Changing settings is available via the “Cookie settings” function made available in the Service, in particular from the footer or another persistent interface element.
  3. Withdrawal of consent takes effect for the future and does not affect the lawfulness of actions taken before it was withdrawn.

§13. Retention period

  1. The retention period of individual technologies depends on their purpose and the technical configuration of the environment.
  2. As a rule:
    1. session technologies are stored for the duration of the session or until it expires,
    2. mechanisms for remembering the login may be stored for a period longer than an ordinary session,
    3. the mechanism for remembering the cookie choice is stored for the period necessary to respect the user's decision,
    4. data on the access source, if maintained in the server-side session, remain active only for the duration of that session.
  3. Due to the environment-specific and configuration-related nature of some settings, precise technical values may differ between environments or implementation versions.

§14. Managing settings in the browser

  1. Regardless of the tool made available by the Administrator, the user may also manage cookies through their web browser.
  2. The browser may enable, among other things:
    1. blocking the storage of cookies,
    2. deleting stored cookies,
    3. limiting the operation of selected technologies,
    4. notifying about an attempt to store information on the device.
  3. However, limiting the operation of necessary technologies may result in the improper operation of the Service or the inability to use some functions, including logging in and maintaining the session.

§15. No transmission of marketing-related decisions to the advertising system

  1. The Administrator does not use this cookie mechanism to conduct behavioral advertising or remarketing based on the user's activity in the Service.
  2. The Policy does not cover the consent model for third-party marketing cookies, because solutions of this kind are not part of the adopted cookie model for the Service.

§16. Changes to the Cookie Policy

  1. The Administrator may amend this Cookie Policy in the event of:
    1. changes in legal regulations,
    2. changes in technologies used in the Service,
    3. changes in the manner in which the Service or the application operates,
    4. implementation of new functions or new external embeds,
    5. the need to clarify the provisions of the document.
  2. The current version of the Cookie Policy is published in the Service.

§17. Final provisions

  1. This Cookie Policy constitutes an informational document related to the use of the SafetySoftware.eu Service.
  2. To the extent not regulated in this Policy, the relevant provisions of the Privacy Policy, the Terms of Service, and applicable laws, including provisions concerning the protection of personal data and the provision of services by electronic means, shall apply.
  3. In matters concerning this Policy, the Administrator may be contacted using the details indicated in §2.