ContractPilot.hu
Terms of use
Terms for business and organisational use of ContractPilot: access, privacy, AI, integrations, support and data handover.
Operator and contact
- Provider
- Gyárfás Tamás Jenő
- Registered address
- 1048 Budapest, Lakkozó u. 26.
- Registration number
- 53948001
- Tax number
- 69969281-1-41
- tamas@merlogic.hu
1. Scope and definitions
These terms set out the framework for business and organisational use of ContractPilot. The Customer is the business, sole trader or other organisation ordering the service; a User is a person authorised by the Customer to access it. The Provider’s identity and contact details appear on this page.
These terms cover the application and related services ordered by the Customer. A separate privacy notice explains personal data processing on the public product website. Consumer subscriptions are not offered. This does not limit individual Users’ mandatory privacy or other rights.
2. Contract formation and document precedence
Access is based on an accepted service or licence agreement between the Provider and Customer. These terms form part of that agreement only where the Customer could review and accepted them before contracting. Visiting the website or booking a demonstration does not itself create a paid subscription.
Mandatory law prevails, followed by individually negotiated contractual provisions. The data processing agreement governs personal data processing; the SLA governs service commitments. Where the law requires separate notice and express acceptance of a provision materially departing from usual practice or statutory rules, those requirements must be met.
3. Service scope
ContractPilot supports management of contracts, documents, registered records, projects, tasks, approvals, customer service cases and related financial information. The agreement defines available modules, user numbers, storage, usage allowances, integrations and additional services.
Public feature descriptions provide guidance. Availability can depend on permissions, configuration, hosting and third-party connections. Roadmap items, development ideas and custom solutions demonstrated without a separate accepted offer do not automatically become contractual commitments.
4. Accounts, authority and access
A person acting for the Customer must have the necessary authority. The Customer appoints administrators, manages User permissions and updates or revokes access when roles or relationships change.
Personal credentials must not be shared. Users must protect passwords, authentication devices and access links and apply required security settings. Suspected unauthorised access must be reported promptly to the Customer’s administrator and the Provider.
5. Licence and intellectual property
The Customer receives a non-exclusive right to use ContractPilot for the agreed term and within the agreed scope. This transfers no ownership of software, source code, branding or documentation. Reselling access, offering it as a separate service or operating it for other organisations requires a separate agreement.
Copying, modifying, reverse engineering or circumventing protections is permitted only with express authorisation or where mandatory law allows it. Statutory interoperability and other mandatory rights remain unaffected. Rights in custom developments and their delivery are governed by the relevant development agreement.
6. Customer data and uploaded content
Rights in Customer data and documents remain with the Customer or original rights holder. The Provider may process them only as necessary to deliver, support and secure the service and meet legal obligations, under the agreement and data processing agreement. Uploading grants no general right to sell or publish that content.
The Customer is responsible for the necessary upload and processing permissions, lawful content and accuracy of information it provides. Only necessary data should be submitted. Before processing special-category personal data or other regulated or highly sensitive content, the parties must verify the legal basis and contractual and technical safeguards.
7. Privacy, confidentiality and security
For personal data processed for purposes determined by the Customer, the Customer will generally be controller and the Provider acting on its behalf will be processor. Roles must be assessed for each processing activity. The GDPR data processing agreement must address instructions, safeguards, subprocessors, assistance with individual rights, transfers and return or deletion of data.
Each party keeps the other’s non-public business and technical information confidential and limits access to persons who need it for performance and are bound by confidentiality. Legally required disclosures remain permitted. The Provider handles and reports personal data breaches under applicable contractual and legal obligations. The product website’s privacy notice does not replace the application’s data processing agreement.
8. Acceptable use
Unlawful, deceptive or rights-infringing use, malicious code, unsolicited bulk messaging, bypassing permissions, accessing other organisations’ data and deliberately disrupting the service are prohibited. Security or load testing requires prior written authorisation.
Automated access and transfers must use authorised interfaces and comply with contractual allowances and third-party rules. The Provider applies proportionate safeguards, investigates reported abuse and, where possible, limits intervention to the affected operation or access.
9. Approvals and electronic signatures
Internal approval, acceptance of a proposal and electronic signing have different legal effects. The Customer determines approval rules, representative authority and the required signature form. A recorded action or approval does not itself guarantee a document’s validity, evidential value or compliance with formal requirements.
Third-party signing is also subject to that provider’s terms. The signature level must suit the transaction; using ContractPilot does not automatically provide a qualified electronic signature. Authorised Users must check recipients, permissions and validity of external sharing links.
10. Invoices, reports and business decisions
The Customer verifies entered and imported information, currencies, tax rates, delivery details, accounting allocations and document relationships. Authorised Users must perform the necessary checks before invoice issuance, approval, transfer or accounting export.
ContractPilot and its reports do not replace legal, tax or accounting advice. Accounting export files support validation and processing in the receiving accounting system. Analytics, predictions and alerts use available information and do not guarantee a business outcome.
11. AI features and human review
Features involving external AI processing require appropriate organisational authorisation and settings. Before enabling them, the Customer must review the affected data, provider and processing terms, including any international transfers. Information sent to AI must be limited to what is necessary.
AI responses, text recognition and automatically extracted data can be incomplete or incorrect. Results must be checked against the original source, particularly before legal, financial or personal-data decisions. The AI assistant does not represent the Customer; its output is not professional advice or independent contractual approval. Permission to provide the service does not itself authorise use of Customer data to train models.
12. Third-party services and integrations
Email, invoicing, signing, storage and other connections may require separate accounts, permissions, licences or charges. The agreement allocates costs and configuration tasks. The Customer supplies permissions for accounts it controls and protects access keys.
Each third-party provider governs its own operations, limitations and terms; changes may affect an integration. This does not release the Provider from its own contractual duties. Connections involving new categories of data or materially different processing must not be enabled without the required notice and authorisation.
13. Hosting, Customer infrastructure and backups
The parties define who operates the application, database and document storage, installs updates and is responsible for access, backups and recovery. Customer-controlled document storage does not itself mean that all application data is located on Customer infrastructure.
The operations agreement defines backup frequency, coverage, retention and recovery commitments. External document storage, server infrastructure and credentials may need separate backups. An available backup feature does not replace an agreed backup policy and regular recovery checks.
14. Support, availability and maintenance
The agreement or SLA defines support channels and hours, priorities, response and resolution commitments, availability and any credits. Without an express commitment, there is no universal guarantee of uninterrupted availability or immediate repair for every Customer.
Planned maintenance involving material downtime is notified in advance through the agreed channel. Urgent security or incident work may be performed immediately, with notice as soon as practicable. Customers provide information needed to investigate reported issues without unnecessarily disclosing credentials or sensitive information.
15. Fees, payment and evaluation access
The accepted offer or agreement defines charges, taxes, currency, billing periods, payment deadlines, usage allowances and any excess usage charges. Renewal and price changes follow accepted contractual rules only; these terms do not themselves impose automatic renewal or price changes.
Late payment is governed by the agreement and applicable law. Before restricting access for non-payment, the Provider gives notice and an appropriate opportunity to resolve it. Demonstration or evaluation access is limited to its stated purpose and scope; paid access requires agreement.
16. Restricting access
The Provider may restrict affected access to the extent necessary for a substantiated security risk, unlawful use, material breach or binding authority instruction. It informs the Customer of the reason and restoration requirements unless disclosure is prohibited by law or would undermine the intervention.
Where there is no immediate threat or mandatory legal action, an appropriate opportunity to remedy the issue must be given. Restriction does not automatically delete data or remove statutory or contractual data-transfer rights. Access must be restored without undue delay once the reason ends.
17. Term and termination
The individual agreement governs the term, ordinary termination, renewal and financial settlement. Material breaches may give rise to termination rights under the agreement and law, with prior notice and an appropriate cure period where required.
On termination, use rights end as agreed, but agreed data handover, lawful settlement, confidentiality and surviving obligations remain to be performed. Termination does not retrospectively legitimise unauthorised use or extinguish accrued claims.
18. Data handover, switching and deletion
The exit agreement specifies all transferable data and digital assets, formats, methods, responsibilities and deletion rules. Handover uses available exports or an agreed technical procedure; automatic compatibility with every other system is not promised.
Where EU Data Act switching rules apply, initiation notice is at most two months, transition is normally at most 30 calendar days, and subsequent data retrieval lasts at least 30 calendar days. Permitted exceptions, assistance and charges follow the Regulation. Apart from lawful retention duties, data must be deleted under the agreed policy after handover and retrieval; backup disposal must also be addressed.
19. Liability and mitigation
Each party is liable for contractual breaches under applicable law and must take reasonable steps to mitigate losses. Customer verification or security duties do not themselves exclude Provider liability. The system does not guarantee correctness of Customer input or the outcome of Customer business decisions.
These terms establish no automatic damages cap or general exclusion of liability. Different limits require a lawful and properly accepted agreement. Liability for intentional breaches or breaches harming human life, physical integrity or health, and any other mandatory liability, cannot be excluded or limited.
20. Changes and notices
Material changes affecting a Customer are notified in advance in a demonstrable manner, explaining the change, reason and application. Publishing new wording does not itself retrospectively change existing contracts. Acceptance and any termination rights follow the agreement and applicable law.
The parties retain the wording and attachments accepted when contracting and maintain current contact and legal-notice addresses. Contractual notices must use the agreed channel; marketing communications do not replace required legal notices.
21. Complaints and governing law
Service or contract complaints may be sent to the Provider’s email on this page. Identifying the Customer, issue and requested resolution helps investigation. The parties first seek direct resolution, without limiting access to authorities or courts.
Hungarian law governs, without prejudice to mandatory EU or other applicable law. Court competence and jurisdiction follow legislation or a lawful agreement. If a provision is invalid, the remainder continues where the law permits. The English text supports understanding; the Hungarian text prevails in a conflict unless expressly agreed otherwise.