Legal documents
Privacy Policy
Privacy 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. Scope and contact details
This Privacy Policy applies to people who use https://www.surgentory.com and https://app.surgentory.com, in particular those who contact Surgentory or request a Trial, Customer representatives, Users, people invited to join Clinics and people listed as supplier contacts.
Privacy enquiries: [email protected].
Security incidents: [email protected].
The controller has not appointed a data protection officer.
2. Roles of the parties
Surgentory acts as controller when processing data for its own purposes. These include handling sales leads and Trial requests, contacting Customer representatives, entering into and performing the Agreement, handling Offers, billing and invoices, managing commercial relationships, administering Accounts at a technical level, maintaining the security of its own platform, handling complaints and claims, and carrying out marketing and UTM analytics on the basis of consent.
Surgentory acts as a processor or subprocessor when it processes personal data in the Clinic’s operational records on the Customer’s instructions. These data include staff and User profiles, roles and permissions assigned by the Customer, records of who performed each operation and the history of those operations, comments, supplier contacts and other personal data in those records. The Data Processing Agreement (DPA), annexed to the Terms of Service, sets out the terms of processing. The relevant controller determines the legal basis for processing and fulfils its obligations to provide information. Surgentory assists the controller in accordance with the DPA.
Surgentory may process the same identifying details, such as a User’s email address, in different roles for separate purposes. For example, it may use the address to contact the User about their Account or platform security, and also process it as part of a Clinic profile or operational history. The existence of an Account does not in itself make Surgentory the controller of all the User’s data in the Clinic.
Surgentory is not intended for processing patient data, data concerning health, Polish personal identification numbers (PESEL), medical records or other data prohibited by the Terms of Service.
3. What data we process and why
| Purpose | Surgentory’s role | Typical data | Legal basis or terms of processing |
|---|---|---|---|
| Handling enquiries and Trial requests and preparing an Offer, including verifying the Customer against public registers | controller | full name, business or facility, tax identification number (NIP) and data from public registers (CEIDG, KRS and the Register of Entities Engaged in Medical Activity), email address, telephone number, message content, manually supplied referral source, preferred Plan | Article 6(1)(b) of the General Data Protection Regulation (GDPR) where the steps concern a contract with a natural person. In other cases, Article 6(1)(f) of the GDPR for managing B2B relationships |
| Measuring campaign sources | controller | utm_source, utm_campaign, landing page, when the consent choice was made and link to the Trial request | consent under Article 6(1)(a) of the GDPR where the information constitutes personal data. The consent requirement under the Polish Electronic Communications Law (PKE) applies independently |
| Technical administration of Accounts and security of Surgentory’s own platform | controller | Account identification and contact details, authentication and session data, security events | Article 6(1)(b) of the GDPR where the administration concerns a contract with a natural person. In other cases, Article 6(1)(f) of the GDPR for managing access and protecting the platform |
| Maintaining the Clinic’s operational records and providing support relating to the data in those records on the Customer’s instructions | processor or subprocessor | staff profiles, the Customer’s roles and permissions, records of who performed each operation and the history of those operations, comments, supplier contacts and other personal data in the records | the legal basis is determined by the relevant controller. Surgentory acts on documented instructions in accordance with the DPA and Article 28 of the GDPR |
| Agreement and billing | controller | details of the Customer and its representative, Offer, price, payment, confirmations, evidence of acceptance of the Terms of Service and the DPA (date, time, IP address, document version, wording of the declaration), invoices, correspondence | Article 6(1)(b), (c) or (f) of the GDPR |
| Managing the Customer relationship and handling support requests, complaints and claims | controller | contact details and correspondence relating to the matter. Surgentory’s role in relation to data from the records entrusted to it for technical support remains the same | Article 6(1)(b), (c) or (f) of the GDPR |
| Surgentory’s optional newsletter, commercial communications and direct marketing | controller | contact details and information about the consent given | consent under Article 6(1)(a) of the GDPR and, where applicable, consent to marketing communications as required by Article 398 of the PKE |
Surgentory’s legitimate interests include managing B2B relationships with Customer representatives, keeping the platform secure, providing support and establishing, exercising or defending legal claims.
Messages necessary to administer the Trial, Account or Agreement, maintain security, process payments or provide support do not require marketing consent. These messages are separate from the optional newsletter and promotional communications.
The utm_source and utm_campaign parameters help determine how a user reached Surgentory, for example via Facebook, LinkedIn, a sponsored campaign, a conference or another tagged link. They are also used to analyse the effectiveness of campaigns and Trial promotions.
At launch, campaign measurement is limited to the UTM parameters described above, without external analytics or advertising tools. The Cookie Policy explains how we provide information about changes to these mechanisms and obtain any required consent.
Automatic measurement of the campaign source is optional when submitting the Trial form. Withholding analytics consent does not limit the basic functions of the website or the form.
We obtain data from the individual, the Customer or the person sending the invitation. We also obtain data identifying the Customer and people acting on its behalf from public registers (CEIDG, KRS and the Register of Entities Engaged in Medical Activity). Technical information is generated during use of the site. If Surgentory obtains an individual’s data indirectly and processes them in its own capacity as controller, it provides the information that Article 14 of the GDPR requires in the circumstances, unless a statutory exception applies.
Providing data is voluntary. If data needed to make contact, create an Account, enter into the Agreement or handle billing are missing, it may be impossible to carry out the relevant activity.
4. Recipients, subprocessors and transfers
Data may be shared with providers of hosting and infrastructure, mail, email communications, backup services and technical tools, as well as with banks, accountants, advisers and public authorities where necessary or required by law.
Current list of subprocessors processing personal data on behalf of the Customer
The DPA refers to the list of subprocessors below. It covers each provider to the extent that it participates in processing data entrusted by the Customer. Other categories of recipients, such as banks, accountants, advisers and public authorities, are not classed as subprocessors solely because they receive data.
| Provider | Purpose | Location and transfer |
|---|---|---|
| Railway Corporation | hosting and data storage | the primary region is the Netherlands. The provider is based in the US. Appropriate transfer mechanisms apply, including standard contractual clauses where required |
| Cloudflare, Inc. | delivering and securing the Service and storing backups | global network. Cloudflare specifies the European Union as the jurisdiction for backups and export packages. The provider is based in the US. Transfers take place in accordance with the DPA and applicable legal mechanisms |
| GitHub, Inc. | supporting the backup process | depending on the service, processing may take place in the US and other locations. Appropriate transfer mechanisms apply to the extent required by law |
| Sinch Email / Mailgun | sending and delivering messages | messages use a European configuration. Further processing takes place in accordance with the provider’s terms and DPA |
| Google Cloud Poland Sp. z o.o. / Google Workspace | business email and correspondence to the extent that they contain data entrusted by the Customer | service for a Customer in the EEA. Google may use global infrastructure in accordance with the Workspace terms and the Data Processing Amendment |
Any change of subprocessor takes place in accordance with the DPA. Data are transferred outside the EEA only under a mechanism provided for in the GDPR, in particular an adequacy decision, the Data Privacy Framework to the extent covered by the relevant certification, or standard contractual clauses with supplementary safeguards where needed.
For information about the safeguards used for transfers, contact [email protected].
5. How long we retain data
- We retain the Clinic’s operational data while the Service is in use and for 180 days after it ends in the ordinary course, in accordance with §7 of the Terms of Service, unless the data are duly erased earlier or further retention is necessary to fulfil a request or comply with a legal obligation. This period does not extend the deadline for full erasure after switching set out in §7(9) of the Terms of Service.
- Surgentory retains data that it processes as controller for the technical administration of an Account for as long as the Account is needed for at least one active Customer relationship. Once that relationship ends, it retains the data for as long as necessary to close access, meet justified security obligations and establish, exercise or defend legal claims. Separate retention periods continue to apply to data entrusted by the Customer, contractual records and data that must be retained by law.
- When the Service ends in the ordinary course, residual data in routine backups are retained for no more than 30 days after erasure from active systems, subject to exceptions required by law. This period does not extend the deadline under §7(9) of the Terms of Service for full erasure of the data, including residual copies in backups, once switching has been successfully completed.
- We retain closed Trial requests and enquiries that do not lead to a business relationship for up to 2 years after the matter is closed.
- We retain utm_source and utm_campaign data linked to a specific request until consent is withdrawn, for a maximum of 2 years from collection. When this period expires, or if consent is withdrawn earlier, Surgentory removes the links between these parameters and the request, the Account and other identifying data. UTM values may be retained for statistical analysis only in genuinely anonymous form that does not allow an individual or the Customer to be identified. Otherwise, they are erased.
- We process data used for the optional newsletter and direct marketing until consent is withdrawn or the relevant communication channel is discontinued. We may retain evidence that consent was given or withdrawn for as long as necessary to demonstrate compliance with the law and defend against legal claims.
- We generally retain routine technical logs under Surgentory’s control for up to 30 days, unless a particular entry is needed for longer because of an incident or dispute.
- We retain Agreements, evidence of acceptance, billing records and tax documents for the period required by law or as long as necessary to establish, exercise or defend legal claims.
6. Your rights
In the circumstances provided for in the GDPR, you have the right to access your data, to have them rectified or erased, to obtain restriction of processing, to data portability and to object to processing. You may withdraw your consent at any time without affecting the lawfulness of processing before its withdrawal.
Right to object: You may object at any time, on grounds relating to your particular situation, to processing based on Surgentory’s legitimate interests under Article 6(1)(f) of the GDPR (Article 21(1) of the GDPR). If you object, we will stop processing the data for that purpose unless we demonstrate compelling legitimate grounds for the processing which override your interests, rights and freedoms, or grounds for the establishment, exercise or defence of legal claims.
You may send requests to [email protected]. We may ask for information needed to verify your identity or authority to make the request. We do not require a copy of an identity document in advance.
You may lodge a complaint with the President of the Polish Personal Data Protection Office or another competent supervisory authority.
If your request concerns data that Surgentory processes solely on the Customer’s instructions, we assist the relevant Customer in fulfilling it in accordance with the DPA.
7. Automated decisions and security
Surgentory does not make decisions based solely on automated processing that produce legal effects concerning an individual or have a similarly significant effect on them. Suggestions relate to inventory management and require a decision by the User.
We apply technical and organisational measures appropriate to the risk, in particular access controls, logical isolation between Clinics, encrypted transmission, protection of authentication credentials, backups, restrictions on administrative access, and incident response and recovery procedures.
8. Cookies, changes and contact details
The Cookie Policy describes cookies, UTM parameters and similar mechanisms.
This Privacy Policy may be updated when the purposes of processing, providers or the way Surgentory operates change. The current version is published on the website. A change to the Privacy Policy does not in itself constitute fresh consent or amend an existing Agreement.
Contact: [email protected].