Product How to start Plans FAQ
PLEN
Home

Legal documents

Cookie Policy

Version 1 · Effective from November 19, 2026

Cookie Policy

Effective date: 19 November 2026
Controller: Łukasz Wieczorek, a natural person carrying on unregistered business activity, address: Herlinga-Grudzińskiego 49/2, 91-498 Łódź, email: [email protected].

1. Which mechanisms we use

Surgentory uses cookies and similar mechanisms on https://www.surgentory.com and https://app.surgentory.com.

Mechanism Purpose Status
JSESSIONID login, session management, permissions and operation of the application session cookie necessary to provide the requested Service
surgentory-consent remembering and respecting the user's choice to accept or refuse analytics stores the user's choice for up to 6 months
Cloudflare security cookies, if set to protect network traffic protection against abuse, bots and attacks, and maintaining security used only to the extent necessary for the security and operation of the Service
utm_source and utm_campaign identifying traffic sources and measuring campaign effectiveness, for example for traffic from Facebook, LinkedIn, a conference or a sponsored campaign optional analytics used to identify the source of a request once the required consent has been obtained
surgentory-remember-me Allows the user to log in again in the same browser without entering a password. Optional cookie set when the user selects “Remember me on this device” at login. Valid for up to 30 days. Logging out removes the cookie from the browser.

The only campaign parameters Surgentory uses are utm_source and utm_campaign. At launch, it does not use utm_medium, utm_content or utm_term.

Once the user has consented to analytics, UTM values from a tagged link may be used to identify the source of a visit and may be linked to a Trial request. The website, form and application can all function without these values.

If the user does not consent to analytics, Surgentory does not use UTM parameters to identify the source of the request. The Trial form continues to work.

At launch, Surgentory does not use external analytics or advertising tools.

2. Consent

Before information can be stored or accessed on the user's device, the user must be informed and give consent, unless the mechanism is necessary for transmission or to provide a service the user has expressly requested.

Essential mechanisms may operate without separate consent to the extent permitted by law.

The website, the Trial and the application can all function without measuring campaign sources for analytics. Surgentory carries out this measurement only after the user has consented to analytics.

Closing the notice, continuing to use the website, submitting the form, creating an Account or accepting the Terms of Service does not constitute consent to analytics.

The option to consent to analytics is not selected by default. Refusing consent does not limit the basic functions. The user can withdraw or change their consent as easily as they gave it, using the privacy settings on the website. When the user withdraws consent, Surgentory stops using the UTM parameters and removes their link to the request in accordance with section 5 of the Privacy Policy. Withdrawing consent does not affect the lawfulness of earlier processing.

3. UTM parameters and campaign links

A tagged link might look like this:

https://www.surgentory.com/?utm_source=linkedin&utm_campaign=endoscopy_paid_2026

The utm_source parameter identifies the traffic source, for example linkedin, facebook or conference. The utm_campaign parameter identifies a particular campaign or promotion.

This allows Surgentory to analyse which channels and campaigns lead to Trial requests and subsequent business relationships.

Once linked to a request, UTM parameters may constitute personal data. The Privacy Policy describes the purposes, legal basis and duration of processing.

4. Browser controls

The user can delete or block cookies and site data in their browser settings. Blocking essential mechanisms may prevent the user from logging in or the application from working properly.

Deleting cookies or other site data does not automatically delete data stored on the server or end the Trial or paid access.

5. Changes to analytics mechanisms

The table in section 1 describes the mechanisms currently in use. Before making a change that requires new information about processing, Surgentory updates the relevant information in the Privacy Policy and the Cookie Policy. If a change goes beyond the scope of the existing consent, Surgentory obtains fresh consent to the extent required by law before it starts that processing. A technical change covered by the information already provided and by valid consent does not in itself require fresh consent.

Developing a feature or changing a tool does not in itself require an amendment to the Terms of Service, provided the change does not affect the terms on which the Service is provided or the Customer's rights and obligations under the Agreement.

6. Updates and contact

Surgentory updates this policy when a change to the mechanisms or their purposes affects the information provided to the user.

For privacy enquiries, contact [email protected].

Documents and contents

Legal documents

Terms and DPA Privacy Policy Cookie Policy Data Act Technical Information

Contents

  1. Cookie Policy
  2. 1. Which mechanisms we use
  3. 2. Consent
  4. 3. UTM parameters and campaign links
  5. 4. Browser controls
  6. 5. Changes to analytics mechanisms
  7. 6. Updates and contact
Inventory, batch, supplier and order control for medical facilities.
Privacy settingsTerms and DPA Privacy Policy Cookie Policy Data Act Technical Information
© 2026 Surgentory. All rights reserved.