Product How to start Plans FAQ
PLEN
Home

Legal documents

Terms of Service and Data Processing Agreement

Version 1 · Effective from November 19, 2026

Terms of Service and Data Processing Agreement

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

§1. The Service and contact details

  1. Surgentory is a software-as-a-service (SaaS) product that helps medical facilities keep records of and manage their inventory, supplies and instruments. The website is at https://www.surgentory.com and the application is at https://app.surgentory.com.
  2. The Service is offered to entities that use it in connection with their business or professional activities, in particular medical practices and other healthcare providers, irrespective of their legal form (each a “Customer”). The Service is not intended for consumers. Individuals may not order it for purposes unrelated to their business or professional activities. §9 sets out the rules for individuals carrying on a business who are entitled to statutory consumer protection.
  3. A “Clinic” is a distinct unit of the Customer within the application. A “User” is a person who uses an individual Account. One Agreement may cover several Clinics belonging to the same Customer.
  4. The specific offer made to the Customer (the “Offer”) sets out the features, limits, Clinics covered, price and period of paid access. If there is a conflict, an individually agreed Offer takes precedence over the Terms of Service on matters it covers. A “Plan” is a package of features and limits described on the Surgentory website or in the Offer. Plan and price information published on the website is an invitation to enter into an agreement under Article 71 of the Polish Civil Code and does not constitute an offer. The Offer is provided to the Customer individually in documentary form by email.
  5. For support, complaints and data enquiries, contact [email protected]. For billing, contact [email protected]. For privacy and data processing on the Customer’s behalf, contact [email protected]. For security, contact [email protected].
  6. The Terms of Service are available free of charge before the Agreement is concluded, in a form that can be saved and reproduced. The Privacy Policy and Cookie Policy are provided for information.
  7. Before the free trial period (the “Trial”) is activated and before a paid Agreement is concluded, the person acting for the Customer provides the Customer’s name (business name) and Polish tax identification number (NIP). That person declares that they are acting in the Customer’s name and on its behalf in connection with its business or professional activities, and that they have authority to enter into the Agreement and the Data Processing Agreement (DPA). The Service Provider may decline to activate the Trial or enter into the Agreement, in particular if it cannot verify the Customer’s details in a public register (CEIDG, KRS or the Register of Entities Engaged in Medical Activity), or if the Customer’s business is unrelated to medical activities.

§2. Scope, requirements and rules of use

  1. Surgentory may include, in particular, records of items, locations, suppliers, lots and expiry dates, stock levels and movements, orders, reports, statistics, order suggestions and management of User access. The specific features depend on the Offer and the Plan.
  2. Surgentory is neither a medical records system nor a system for billing healthcare services. It is not a diagnostic or therapeutic tool. It does not replace physical checks of stock or storage conditions, or an assessment of whether a product may be released for use.
  3. Users must not enter patient data, Polish personal identification numbers (PESEL), health data, medical records or other data covered by Article 9 or 10 of the General Data Protection Regulation (GDPR). This prohibition also applies to free-text fields, notes and comments, for example entering a patient’s first name, surname or initials against an item intended for that patient. The Customer is responsible for ensuring that its Users comply with this prohibition. If such data is entered, the Customer must delete it without delay. If it cannot do so in the application, it must notify the Service Provider at [email protected] and the Service Provider will delete the data on the Customer’s instructions.
  4. Users use individual Accounts and are responsible for protecting their access credentials. The Customer is responsible for correctly granting and revoking its Users’ permissions.
  5. It is prohibited to use the Service unlawfully, supply illegal content, bypass security or access controls, gain access to another party’s data, introduce malware or disrupt the Service.
  6. Use of the Service requires internet access, an up-to-date browser that supports HTTPS, JavaScript and session management, and a working email address.
  7. Risks specific to electronic services include phishing, malware, compromised access credentials, use of an insecure or outdated device, incorrectly assigned permissions and interruptions to internet access or third-party services. Users should use up-to-date software, protect their login credentials and verify the website address.
  8. The order suggestions feature uses statistical methods to calculate suggestions from the history of stock levels and movements recorded by the Customer. These suggestions are advisory and require a decision by the User. Surgentory does not place orders with suppliers or send orders to external systems. The ordering feature prepares a message that the User can copy and send themselves.

§3. Trial

  1. The Trial provides free access to Surgentory for a limited period. It normally lasts 14 days, counting the activation day as the first day. The Trial Agreement is concluded when a person authorised to act on behalf of the Customer accepts the Terms of Service and the DPA. The Trial may be activated only after that acceptance.
  2. The Service Provider may offer a longer Trial, a different Trial period or an extension. This may arise, in particular, from a promotion, attendance at a conference or event, a promotional code, a referral source, a partner programme or an individual arrangement. The period or end date that applies is the one the Service Provider confirms to the Customer by email before activating or extending the Trial. A promotion may be subject to separate conditions made available before the Customer applies. The Terms of Service govern matters those conditions do not cover.
  3. As a rule, a Customer receives one standard Trial. The Service Provider may grant a further Trial or an extension at its discretion. A new Account, email address or additional Clinic belonging to the same Customer does not automatically entitle the Customer to a new Trial.
  4. The Offer or invitation specifies the scope of the Trial. The Trial may allow the Customer to keep actual records for its own facility, subject to the prohibitions in §2(3).
  5. The Trial does not automatically convert to paid access or result in an automatic charge. If the Customer does not purchase a paid period, operational access expires at the end of the Trial.
  6. If the Customer purchases paid access during the Trial, the paid period normally starts after the Trial ends, unless the Offer expressly provides otherwise.
  7. After the Trial ends, data is retained for 180 days in accordance with §7 and is then deleted, unless the paid Service starts earlier, the Customer requests a copy of its data or the law requires further retention. The provisions on earlier deletion in §7 apply.

§4. Purchase, payment and access period

  1. Paid access is purchased for the period specified in the Offer, normally one month or 12 months, and is paid for in advance by bank transfer. Surgentory does not automatically charge a card or debit an account.
  2. The Offer identifies at least the Customer, the Clinics covered and the scope of the Service, the price and taxes, the access period, the conditions for access to begin and the deadline for accepting the Offer.
  3. Unless the Offer provides otherwise, payment made in accordance with the Offer while it is valid constitutes acceptance and purchase of the specified period, provided the Customer received the Terms of Service and the other required information before paying. The Service Provider confirms the conclusion of the Agreement and its terms on a durable medium.
  4. If specific legal provisions require a separate declaration from the Customer, the Service Provider obtains it separately from payment. This applies in particular where performance is to begin early for a business customer entitled to statutory consumer protection.
  5. If the Customer does not pay, it does not purchase the next paid period or incur a debt for that period. The Customer need not give notice to avoid a further charge.
  6. There is no standard grace period after the paid period ends. Unless the Customer makes a further purchase, access expires at the end of that period.
  7. The Service Provider may, at its discretion, accept bank confirmation of a completed transfer and activate or extend access before the funds are credited. Sending the confirmation alone does not grant access. If the funds do not subsequently arrive, the Service Provider may investigate, restrict or terminate access, seek payment for the Service actually made available and pursue claims arising from misuse, to the extent permitted by law.
  8. Payment for a further period before the current period ends ensures continuity from the next day. If payment is made after a break, the new period begins on the activation date accepted by the Service Provider, unless the parties agree otherwise.
  9. The Service Provider may send reminders or renewal Offers. The absence of a reminder does not extend access or create an obligation to purchase.
  10. A change in price, Plan, number of Clinics or another material aspect of the scope applies to the next period, or may take effect during the current period if individually agreed. The price is not reduced solely because the Customer does not use part of the package it purchased.
  11. A Customer that stops using the Service during a paid period is generally not entitled to a refund for the unused time. A refund is due if required by law, provided for in the Offer, agreed by the parties, or if the Service Provider ends the paid Service early for reasons not attributable to the Customer. In such cases, the refund is calculated in proportion to the unused part of the paid period, unless the law requires a different calculation. This rule also applies if the Agreement ends before the paid period expires at the Customer’s request in connection with switching providers or erasure of data under the Data Act (§7(6)–(9)). The Service Provider does not charge an additional fee on that account. The Customer is informed of this consequence before the Agreement is concluded (Article 29(4) of the Data Act).
  12. The Offer specifies the total amount payable for the stated access period and how VAT is treated. If the sale is exempt from VAT, the price shown in the Offer is the amount payable and the Service Provider does not add VAT. If the Service Provider must charge VAT, the Offer shows the price excluding tax, the amount of VAT at the applicable rate and the total amount payable. Invoices are issued in accordance with tax law, including through the Polish National e-Invoicing System where required.

§5. Availability, support and termination

  1. The Service Provider provides the Service with due care. Unless a separate service level agreement (SLA) provides otherwise, it does not guarantee uninterrupted operation, a particular level of availability or a time limit for resolving every fault.
  2. Support is available at [email protected], normally on working days. Requests may be submitted at any time.
  3. The Service Provider may temporarily restrict or suspend access where justified on security grounds, by a breach of the law or the Terms of Service, by the need to protect other users or by technical work.
  4. In the event of a material breach of the Terms of Service, the Service Provider may terminate the Agreement if the breach is not remedied within a reasonable period after it requests a remedy, unless the nature of the breach or security considerations justify immediate action.
  5. The Service Provider may discontinue Surgentory or a particular Plan. If this brings a paid period to an early end for reasons not attributable to the Customer, the Service Provider refunds the fee in proportion to the unused part of the period and enables the Customer to obtain the data to which it is entitled.
  6. Complaints may be sent to [email protected]. The complaint should identify the Customer and the issue. The Service Provider considers the complaint without undue delay and no later than 14 days after receipt. It sends its response to the email address from which the complaint was submitted, unless the Customer specifies a different address.
  7. An Agreement for paid access runs for the paid period and expires at the end of that period. Before then, the Customer may terminate the Agreement only (a) under the Data Act procedure for switching providers or erasing data (§7(6)–(9)), (b) before an amendment to the Terms of Service takes effect (§10(2)), (c) if it objects to a new subprocessor (Annex 1, section 3(2)), or (d) for good cause, in particular if the Service Provider materially breaches the Terms of Service and fails to remedy the breach within 14 days of being asked to do so. The Customer may terminate a Trial Agreement at any time. The Customer must send notice of termination to [email protected]. §4(11) governs the financial consequences of termination before the paid period expires, and §7 governs the release and deletion of data.

§6. Data rights, confidentiality and intellectual property

  1. The Customer retains the rights to its data. The Service Provider may process that data only as necessary to provide, secure, bill for and terminate the Service, and for other purposes that have an appropriate legal basis.
  2. Customer data is not sold, used for advertising based on the Customer’s non-public records or used to train AI models without a separate basis and agreement.
  3. The Service Provider retains the rights to its software, interface, documentation, marks and proprietary solutions. The Agreement does not transfer any rights in Surgentory’s code or technology to the Customer.
  4. For the duration of the Agreement, the Customer has a non-exclusive, non-transferable right to access and use the Service for its own needs in accordance with the Terms of Service and the Offer. The Customer must not copy, modify or distribute Surgentory software, or attempt to access the Service Provider’s non-public source code or confidential technical information, except where expressly permitted by mandatory law. The Customer must not use Surgentory’s non-public code, trade secrets or other confidential technical information to create or develop a competing solution. This provision does not restrict the Customer’s rights under mandatory law to observe, study or test the functioning of the software, or its rights to interoperability, data export and switching providers.
  5. The parties must keep confidential any non-public information they obtain in performing the Agreement. This obligation continues after the Agreement ends.
  6. The Service Provider may use statistical information once it has been effectively anonymised on the instructions given in the DPA (Annex 1, section 1(6)), or aggregated in a way that prevents identification of the Customer or any individual. This also applies to UTM campaign parameters once any links that allow identification have been removed. The Privacy Policy sets out how and for how long those parameters are retained.
  7. The Customer’s name, mark or logo may be used as a marketing reference only with its consent.

§7. Data after the Service ends, export and the Data Act

  1. While using the Service and for 180 days after it ends in the ordinary course, the Customer may request a copy of its data at [email protected], provided the data has not already been duly deleted. A request submitted before deletion suspends deletion to the extent necessary to fulfil the request properly. The copy is prepared without undue delay, normally within 30 days of a valid request. The method for transferring the data securely is agreed with the Customer. Providing a copy while the Service is active does not in itself end the Agreement or trigger deletion.
  2. The data is provided in a ZIP archive containing datasets in UTF-8-encoded JSON format. The archive also contains a description of the data structure, a file list with checksums and instructions for reading the data. For relationships covered by Chapter VI of the Data Act, the following is the exhaustive list of transferable data and digital asset categories: (a) data identifying the Customer’s Clinics and settings needed to interpret and reconstruct the Customer’s data, (b) inventory records, including items, locations, suppliers, lots, expiry dates and stock levels, (c) inventory transaction data and the retained history and audit trail of the Customer’s use of the Service, (d) data on orders, requests and their line items, including retained statuses and metadata, (e) User, membership, role and permission configuration data for the Customer’s Clinics, (f) content and contact details entered by the Customer in Surgentory’s operational records, (g) available results of reports, statistics and recommendations generated from the Customer’s data, with the metadata needed to interpret them, and (h) identifiers, relationships, data dictionaries and other technical metadata needed to link and read the above data correctly. As at the effective date of the Terms of Service, Surgentory has not identified any separate digital assets of the Customer within the meaning of Article 2(32) of the Data Act.
  3. Only the following categories of data and assets of the Service Provider or third parties fall outside the scope of exportable data, and only to the extent that they do not constitute the Customer’s exportable data: source and executable code, internal algorithms, weights, formulae and the operating logic of the Service, the internal domain model, data schema and technical implementation names (including internal class, table and column names), internal infrastructure and orchestration configuration, internal monitoring, telemetry, anti-abuse and security data, the Service Provider’s internal administrative and commercial records, passwords and their hashes, keys, tokens, secrets and session identifiers, and other Customers’ data. Where data specific to the internal functioning of the Service is excluded under Article 25(2)(f) of the Data Act because disclosure risks breaching a trade secret, the exclusion is limited to the categories listed above and must not impede or delay the required switching process. This provision does not restrict the Customer’s rights under the GDPR or other mandatory law.
  4. When the Service ends in the ordinary course, operational access expires and data relating to the part of the Service that has ended is retained for 180 days so that the data can be provided to the Customer or the Service resumed. A valid request for earlier deletion and the specific rules in paragraph 9 take precedence over this period. If the Service does not resume within that time and there is no basis for further retention, the data is deleted from active systems. Deletion of data relating to the part of the Service that has ended does not extend to other active Clinics or Accounts, or to data needed to support them. Once the data has been deleted, the Service Provider cannot guarantee its recovery.
  5. Data temporarily remaining in backups is protected and is not used for new purposes. When the Service ends in the ordinary course, this data is deleted in the normal retention cycle, no later than 30 days after deletion from active systems, unless the law requires particular data to be retained for longer. If a backup is restored, previous deletion instructions are reapplied before the data is returned to normal use. The normal backup retention cycle does not extend the deadline in paragraph 9 for complete erasure of exportable data and digital assets following successful switching under the Data Act.
  6. If Chapter VI of Regulation (EU) 2023/2854 (the “Data Act”) applies to the relationship, the Customer may request to switch providers, transfer its data to its own infrastructure or have its exportable data erased. Surgentory does not charge a separate fee for switching activities required under the Data Act. Work beyond statutory obligations, such as configuring another provider’s system, building a custom integration or carrying out an additional implementation, may be provided for a fee under a separately agreed Offer.
  7. Surgentory does not require a separate notice period before switching begins. The transitional period starts on receipt of the Customer’s valid request and lasts no more than 30 calendar days, except as provided in the Data Act. If meeting this deadline is technically unfeasible, the Service Provider informs the Customer within 14 working days of receiving the request, gives a duly substantiated explanation of the technical reasons and specifies an alternative transitional period of no more than 7 months. The Service continues throughout the alternative period. The Customer may extend the transitional period once by a period it considers more appropriate for its needs, in accordance with Article 25(5) of the Data Act.
  8. During the required transitional period, the Service Provider gives reasonable assistance to the Customer and the third parties it authorises, exercises due care to maintain continuity of the functions and the Service and a high level of security, supports the Customer’s exit strategy for the Service covered by the Agreement and provides clear information about known switching risks to the continued provision of functions or the Service. For relationships covered by Chapter VI of the Data Act, Surgentory provides a documented open interface for data portability, interoperability and switching, at no separate charge and on an equal basis for the Customer and the relevant destination provider, to the extent required by Article 30 of the Data Act. The primary means of delivering data remains a complete export in commonly used machine-readable formats, accompanied by documentation of its structure. The interface is not a general-purpose public API for the entire application. Surgentory does not undertake to develop technologies, features or services beyond what the law requires, or to implement or configure the Customer’s destination system.
  9. Once switching has been successfully completed, the Agreement ends to the extent covered by the switch, and the Customer receives confirmation. The Customer has at least 30 days after the end of the transitional period to retrieve its exportable data. Once the retrieval period has expired and switching has been successfully completed, the Service Provider fully erases the exportable data and digital assets generated directly by or directly relating to the Customer, including any remaining copies in backups under the Service Provider’s control, unless mandatory law requires specific data to be retained for longer. If the Customer chooses to end the Service and have its exportable data erased instead of switching providers, the Agreement ends to the extent covered by the request, without an additional contractual notice period, subject to the mandatory rules of the Data Act. The Service Provider informs the Customer that the Agreement has ended to that extent.
  10. Paragraphs 6–9 also apply to a Trial during which the Customer keeps actual records for its facility (Article 23(c) of the Data Act).
  11. The Data Act Technical Information forms part of these Terms of Service. The Service Provider hosts the detailed, up-to-date register of exportable data structures and formats referred to in Article 26(b) of the Data Act at https://app.surgentory.com/legal/data-act-export-register. The Customer can access the register after authentication. The Customer may authorise the relevant destination provider to access the register to the extent necessary for switching. The current contents of the register are also available to the Customer on request before the Agreement is concluded. The register describes the export specification. It does not disclose the Service Provider’s internal domain model, code, algorithms, security information, intellectual property or trade secrets, unless disclosure is required by mandatory law.

§8. Liability

  1. Surgentory is a tool that assists with resource management. The Customer makes its own decisions about purchasing, stock levels, releasing products for use and organising work. The Service Provider does not guarantee any particular savings, that stock shortages or expiry will be avoided, or that every suggestion, statistic or report will be free of errors.
  2. To the extent permitted by law, the Service Provider is not liable for damage resulting from incorrect data entered by the Customer, acts or omissions of its Users, a breach of security rules by the Customer, failure of the Customer’s equipment or connections, or failure of third-party systems outside the Service Provider’s reasonable control.
  3. In a business-to-business (B2B) relationship, the Service Provider’s liability for loss of profit and for indirect and consequential loss is excluded to the extent permitted by law.
  4. In a paid B2B relationship, the Service Provider’s total liability for damages in connection with the Agreement is limited to the equivalent of three months’ fees for the then-current scope of the Service, excluding VAT if charged. This amount is calculated pro rata from the price applicable to the period in which the event occurred.
  5. For a free Trial, the Service Provider’s total liability for damages to any one Customer for that Trial, including any agreed extensions, is limited to PLN 1,000. Which limit applies under paragraph 4 or 5 depends on when the event causing the damage occurred, irrespective of when the damage was discovered or the claim was made. Where the damage results from events in both periods, each limit applies to the portion of the damage arising from events in the corresponding period.
  6. The limitations in paragraphs 3–5 do not apply where liability cannot lawfully be limited, in particular to damage caused intentionally or through gross negligence, to individuals’ rights that are mandatorily protected under the GDPR, or in any other case in which liability cannot validly be limited.
  7. The Service Provider is not liable for non-performance to the extent caused by an event beyond its reasonable control that it could not have avoided despite exercising due care.

§9. Statutory protection for individual business customers

  1. If a Customer who is an individual carrying on a business is entitled, in relation to a particular Agreement, to mandatory protection under the Polish Consumer Rights Act, the Terms of Service do not restrict that protection.
  2. In such cases, the Service Provider gives the Customer the information required by law. Where a statutory right to withdraw from a distance contract applies, the time limit, rules and exceptions set out in the Act apply. The Customer may withdraw from the Agreement within 14 days of its conclusion without giving any reason (Articles 27 and 7aa of the Consumer Rights Act). Annex 2 contains the instructions on withdrawal and a model withdrawal form.
  3. If the paid Service is to begin before the withdrawal period expires and the law so requires, the Service Provider obtains the Customer’s express request and provides the required information on withdrawal.
  4. Provisions concerning liability, refunds, the competent court and other rules for business dealings apply only to the extent that they do not infringe the mandatory rights of such a Customer.
  5. The protection referred to in paragraph 1 applies where it is apparent from the Agreement that it is not of a professional nature for the Customer, as determined in particular by the scope of the Customer’s business activities recorded in CEIDG.

§10. Changes to the Terms of Service and governing law

  1. The Service Provider may develop and change the Service, in particular its interface, technical implementation, infrastructure and features, provided that it preserves the material scope for which the Customer has already paid and the Customer’s statutory rights.
  2. Material amendments to the terms do not put the Customer in a worse position for a period already paid for, unless the change is required by law or necessary for security. When purchasing a further period, the Customer receives the current terms before purchase. The Service Provider notifies Customers by email at least 14 days before a change to the Terms of Service takes effect. A Customer that does not accept the change may terminate the Agreement under §5(7) before the effective date of the change (Article 384¹ of the Polish Civil Code).
  3. The Service Provider retains the version of the Terms of Service applicable to each Customer and evidence that the Agreement was concluded.
  4. The Agreement is governed by Polish law, subject to mandatory legal provisions. In a business relationship, jurisdiction lies with the court for the place where the Service Provider carries on its business, to the extent that the law permits the parties to agree on jurisdiction.
  5. A transfer of the Surgentory business to a company or another successor may result in a transfer of rights and obligations under the Agreement to the extent permitted by law, after the Customer has been informed as required and its consent obtained where necessary.
  6. If an individual provision is invalid, the other provisions remain valid if they can continue to apply.

Annex 1 — Data Processing Agreement (DPA)

This Annex forms part of the Terms of Service where the Customer entrusts the Service Provider with the processing of personal data. It also applies during a Trial if personal data is entrusted to the Service Provider for processing.

1. Roles, subject matter and scope

  1. The Customer is either a controller or a processor authorised to engage a subprocessor. The Service Provider acts as a processor or subprocessor accordingly.
  2. The purposes of processing are to make Surgentory available and maintain it, support Clinics and Users, maintain records and transaction histories, provide assistance, ensure security, make backups, and return and erase data.
  3. Processing continues for as long as the Service is used and for the period needed to lawfully return or erase the data.
  4. The data may concern staff, other people working with the Customer, Users and contact persons at suppliers. It may include identification and contact details, roles and permissions, who performed an operation and when, comments, supplier data and operational data linked to a particular individual.
  5. Patient data and the data prohibited under §2(3) of the Terms of Service are not intentionally entrusted to the Service Provider for processing.
  6. The Customer instructs the Service Provider to anonymise personal data processed in Surgentory to prepare the aggregate statistics referred to in §6(6) of the Terms of Service. Anonymisation means permanently removing or aggregating data so that neither an individual nor the Customer can be identified, even when the data is combined with other information available to the Service Provider.

2. Instructions, the Customer’s obligations and security

  1. The Service Provider processes data only on the Customer’s documented instructions, including with regard to transfers, unless the law requires the processing. The Service Provider informs the Customer of any such legal requirement before processing, unless the law prohibits it from doing so.
  2. Within the scope of its role, the Customer is responsible for lawfully entrusting the data to the Service Provider, having an appropriate legal basis for processing, fulfilling its information obligations and ensuring that its instructions comply with the law. If the Customer acts as a processor, it must ensure that it is authorised to engage a subprocessor.
  3. Anyone given access to the data must be authorised and bound by confidentiality obligations.
  4. The Service Provider implements technical and organisational measures appropriate to the risk, in particular access controls, logical isolation of Clinics, safeguards for data transmission and authentication, backup protection, restrictions on administrative access, and incident response and recovery procedures.
  5. If the Service Provider considers that a Customer instruction infringes data protection law, it informs the Customer.

3. Subprocessors and transfers

  1. The Customer gives the Service Provider general authorisation to engage other processors (subprocessors). The current list is published in section 4 of the Privacy Policy under the heading “Current list of subprocessors processing personal data on behalf of the Customer”.
  2. The Service Provider gives the Customer at least 7 days’ advance notice of any intended addition or change of a subprocessor, allowing the Customer to raise a reasoned objection. If the Customer objects, the parties work in good faith to find a solution. If no solution can be found, the Customer may terminate the Agreement with effect from the date of the change and receives a pro rata refund for the unused part of the paid period.
  3. The Service Provider imposes data protection obligations on each subprocessor that meet the requirements of Article 28 of the GDPR. The Service Provider remains liable for the performance of the subprocessor’s obligations to the extent required by law.
  4. Data may be transferred outside the European Economic Area (EEA) only under an appropriate legal transfer mechanism and with the required safeguards.

4. Assistance, breaches and audits

  1. Taking into account the nature of the processing and the information available to it, the Service Provider assists the Customer in giving effect to data subjects’ rights and fulfilling its obligations under Articles 32–36 of the GDPR.
  2. The Service Provider notifies the Customer of a personal data breach affecting data entrusted to it without undue delay after becoming aware of the breach. It provides the information available to it and supplements that information as the investigation progresses.
  3. The relevant controller is responsible for assessing whether the supervisory authority and the individuals concerned must be notified of a breach. The Service Provider cooperates and meets its own statutory obligations.
  4. The Service Provider makes available the information needed to demonstrate compliance with Article 28 of the GDPR and allows audits required by that Article. Unless the nature of the matter requires otherwise, the audit begins with document review and explanations provided remotely. The audit must not compromise security or the rights of other Customers.

5. Return and erasure

  1. When processing ends, the Service Provider returns or erases the data in accordance with the relevant controller’s decision and §7 of the Terms of Service, and deletes all copies, unless the law requires specific data to be retained for longer.
  2. Until deletion, backups remain protected and are not used for other purposes. If a backup is restored, earlier deletion instructions are reapplied before normal use of the data resumes.
  3. At the Customer’s request, the Service Provider confirms that the data has been returned or erased.

Annex 2 — Model withdrawal form

This Annex applies only to a Customer who has a statutory right of withdrawal in the particular contractual relationship.

Instructions on the right of withdrawal

You have the right to withdraw from the Agreement within 14 days without giving any reason. The withdrawal period expires 14 days after the day on which the Agreement was concluded.

To exercise your right of withdrawal, you must inform us of your decision to withdraw from the Agreement by an unequivocal statement, for example by sending a letter by post or by email. Our email address is [email protected]. You may use the model withdrawal form, but you do not have to. To meet the withdrawal deadline, it is sufficient to send your notice that you are exercising the right of withdrawal before the withdrawal period expires.

If you withdraw from this Agreement, we will reimburse all payments we have received from you without undue delay and in any event within 14 days of the day on which we are informed of your decision to exercise your right of withdrawal. We will use the same means of payment you used for the original transaction unless you have expressly agreed otherwise. In any event, you will incur no fees as a result of the reimbursement.

If you requested that we begin providing services before the withdrawal period expired, you must pay us an amount proportionate to the services provided up to the point at which you informed us of your withdrawal from the Agreement.

Model withdrawal form

To: Łukasz Wieczorek, a natural person carrying on unregistered business activity, at Herlinga-Grudzińskiego 49/2, 91-498 Łódź

I hereby give notice that I withdraw from the Surgentory Agreement concluded on .................................

Customer: ................................
Email / Agreement identifier: ................................
Date: ................................
Signature: only if this notice is submitted on paper.

Documents and contents

Legal documents

Terms and DPA Privacy Policy Cookie Policy Data Act Technical Information

Contents

  1. Terms of Service and Data Processing Agreement
  2. §1. The Service and contact details
  3. §2. Scope, requirements and rules of use
  4. §3. Trial
  5. §4. Purchase, payment and access period
  6. §5. Availability, support and termination
  7. §6. Data rights, confidentiality and intellectual property
  8. §7. Data after the Service ends, export and the Data Act
  9. §8. Liability
  10. §9. Statutory protection for individual business customers
  11. §10. Changes to the Terms of Service and governing law
  12. Annex 1 — Data Processing Agreement (DPA)
  13. 1. Roles, subject matter and scope
  14. 2. Instructions, the Customer’s obligations and security
  15. 3. Subprocessors and transfers
  16. 4. Assistance, breaches and audits
  17. 5. Return and erasure
  18. Annex 2 — Model withdrawal form
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.