AI Integration Terms — Librent
Version: 1.0.1-2026-11-10 · Effective date: 10 November 2026
Translation notice. This English translation is provided for information only and is pending legal review. The Polish version is the binding version and prevails in the event of any discrepancy.
These AI Integration Terms supplement the Terms of Service of the Librent service. They set out the rules for connecting an Organisation to an external artificial intelligence service through an MCP server. The Service Provider makes them available free of charge before the integration is enabled. Capitalised terms have the meanings given in the Terms of Service and the Data Processing Agreement.
1. What the AI Integration is
- The AI Integration lets people use Organisation data in a conversation with an external AI service (the "AI Service"). The AI Service currently supported is Claude by Anthropic.
- The AI Service is not part of the Service. Its provider is not a subcontractor or Sub-processor of the Service Provider, and the Service Provider is not a party to the agreement with that provider. Naming an AI Service is not a recommendation.
- The AI Integration is optional and disabled by default. It does not concern the AI Assistant described in § 6 of the Terms of Service.
- An account with the AI Service is needed to use the AI Integration.
2. Enabling, connecting and acceptance
- An owner or admin of the Organisation enables the AI Integration in the settings. A connection to the AI Service is also created by an owner or admin, who signs in to the Service, selects the Organisation and confirms consent with their password.
- Enabling the integration and creating a connection mean acceptance of this document on behalf of the User. The person doing so declares that they are authorised to do so. The Service records who did so, when, and the version of this document.
- A connection is read-only by default. Write access is turned on separately when the connection is created.
- A connection covers one Organisation and works with the permissions of the role of the person who created it. It expires no later than 180 days after consent.
3. Data sent to the AI Service
- The integration's tools send the following to the AI Service:
- about clients: first name, last name, company name, email address, telephone, address and identifier;
- about bookings: dates, status, equipment, amounts, deposits, notes and the client's name;
- about equipment: name, description, rates, deposit, quantity and status.
- The tools do not send identity document numbers, tax identification numbers, documents, signatures, WhatsApp or AI Assistant conversations, the activity log or data of members of the Organisation.
- Text fields such as notes and company name are sent in full, with whatever someone typed in them. The User does not enter in them any data that it does not want to pass to the AI Service.
- Which data is read depends on the user's instructions and on how the AI model works. Encryption of the Service's database does not cover data sent to the AI Service.
4. Write operations
- Once write access is enabled, the AI Service may, within the role of the person who created the connection: create, change and delete clients, create and change bookings, change their status, and create and change equipment.
- Confirming or cancelling a pending booking sends the Client a fixed email. Custom messages to Clients can only be sent from the panel.
- Bookings created by the AI Service count towards limits and fees.
- Actions carried out by the AI Service through a connection are treated as actions of the Account on which the connection was created (§ 4(2) of the Terms of Service).
- The User checks write operations before approving them. Decisions with legal or similarly significant effects for Clients, in particular refusing to conclude a contract, are made by a human.
5. Choosing the service and account type
- The User chooses the AI Service and account type itself and is responsible for that choice. Before enabling the integration, it checks the provider's terms and the account's privacy settings.
- Plans for private individuals usually do not provide a data processing agreement, may allow the provider to train models on the data, and the provider's terms may prohibit business use on them. This is the case, for example, in Anthropic's EEA terms as worded on the date of this document. Plans for businesses usually do not have these limitations.
- The User declares that:
- it may share the data in point 3 with the AI Service;
- it has a legal basis for that sharing and informs the data subjects about it;
- it has the agreement with the provider required by law, including a data processing agreement, and a basis for transferring data outside the EEA, where these are required.
- The Service Provider does not check the User's plan or its agreement with the provider.
6. Threats
- An AI model may make mistakes.
- Content read by the model may contain hidden instructions, known as prompt injection. This applies especially to text entered by Clients or other people in public forms. The model may follow such an instruction instead of the user's instruction.
- Without write access, such an instruction will not change data in the Service, but the model may use other tools connected to the AI Service account, including to send data elsewhere.
- The User limits these risks: it does not connect tools it does not need to the same account and checks operations carefully.
7. Personal data
- With respect to Clients' data, the User is the controller and the Service Provider is the processor. Enabling the AI Integration is an instruction within the meaning of § 6(5) of the Data Processing Agreement.
- The Service Provider processes Account data related to a connection in accordance with the Privacy Policy.
- The Service records the creation and ending of a connection, data changes and the number of records read. It does not record the content of conversations with the AI Service or which records were read.
8. Liability
- The Service Provider is liable for the operation of the MCP server under § 13 of the Terms of Service.
- The Service Provider is not liable for:
- the operation of the AI Service and its provider, including data retention, model training and transfers of data outside the EEA;
- answers and content generated by the AI model;
- operations carried out by the AI Service through a connection, including where the model followed an instruction contained in content it read;
- the consequences of choosing the AI Service and account type.
- Paragraph 2 does not apply to damage resulting from a defect in the MCP server. § 13(3) and (4) of the Terms of Service apply accordingly. This document does not limit liability towards data subjects under Art. 82 GDPR.
- If a third party brings a claim against the Service Provider because the User has breached this document, the User reimburses the amounts awarded and reasonable defence costs. The Service Provider promptly notifies the User of the claim and allows it to respond. This paragraph does not apply to persons referred to in § 13(4) of the Terms of Service or to damage caused by the Service Provider's fault.
9. Disconnecting and ending
- An owner or admin may disconnect a connection or disable the AI Integration at any time. A connection also ends after a password change, loss of the role or removal of a member.
- Ending has effect for the future. It does not delete data that has already reached the AI Service and does not undo operations carried out. Data at the provider is deleted under the provider's rules, and operations are undone manually in the Service.
- The Service Provider may disconnect a connection or block the AI Integration where required by security, the stability of the Service or the law, or where the User breaches this document. § 11(4) of the Terms of Service applies accordingly.
- The Service Provider may change the scope of the tools, in particular limit them for security reasons. The User may stop using the AI Integration without affecting other services.
10. Final provisions
- The Terms of Service apply to matters not covered here. In matters of the AI Integration this document prevails over the Terms of Service, and in matters of personal data the Data Processing Agreement prevails.
- This document is amended under the procedure in § 16 of the Terms of Service. Extending the scope of data in point 3 also requires an amendment to the Data Processing Agreement.
- Complaints are handled under § 14 of the Terms of Service.
- The Polish version is binding.