Reevals Terms of Service

1. SCOPE OF THE TERMS AND FORMATION OF THE AGREEMENT

1.1 Scope

These Terms of Service govern access to and use of the Reevals platform, including the web application, Documentation, APIs, exports, Integrations, data monitoring, pricing workflows and functions that use artificial intelligence.

The Terms apply to free trials, paid Subscriptions and functions made available under an individual Order, unless a separate written agreement provides otherwise.

1.2 Business users only

The Service is intended exclusively for entrepreneurs and other persons who use it in connection with their business or professional activities. It is not intended for consumers. A natural person may use the Service as an entrepreneur or as an authorised representative of the Customer.

A person who accepts these Terms on behalf of a legal entity or other organisation confirms that they are authorised to bind that entity. If they do not have such authority, they must not confirm the Order or use the Service.

1.3 Formation of the Agreement

The Agreement is formed at the earliest of the following: (a) confirmation of acceptance of the Terms during registration or ordering, (b) activation of the account by the Provider, (c) confirmation of the Order by the Provider or (d) commencement of use of the Service. Before entering into the Agreement, the Customer must have an opportunity to save and review the Terms.

If the parties sign a separate master agreement, order form, SLA or DPA, the order of precedence in Section 22.1 applies.

2. DEFINITIONS

The following terms have the meanings set out below in these Terms:

• “AI Functions” means functions that use machine learning, generative models or other automated methods for suggestions, explanations, classification, matching, diagnostics or recommendations.
• “Price List” means the Provider's current pricing and functionality offer displayed during ordering or stated in an individual offer.
• “DPA” means a data processing agreement under Article 28 of the GDPR where the Provider processes personal data for the Customer.
• “Documentation” means the user, technical, security and integration documentation for the Service that the Provider makes available from time to time.
• “Order” means an online order, order form, quotation or other document specifying the plan, Subscription term, price, limits and any special terms.
• “Authorised User” means a natural person for whom the Customer has created or permitted individual access to the Service in accordance with the plan.
• “Provider” means CREALAB s.r.o., whose identification details are set out in Section 23.
• “Subscription” means the time-limited right to use the Service within the scope of the plan or Order.
• “Service” or “Platform” means the Reevals cloud platform and related functions made available to the Customer under the Agreement.
• “Outputs” means data, comparisons, matches, analyses, simulations, recommendations, configuration suggestions, reports and other results created by the Service from Customer Data or Source Data.
• “Customer” means an entrepreneur or other person using the Service as part of its business or professional activities that has entered into the Agreement with the Provider.
• “Customer Data” means data, files, configurations, access permissions, instructions and other content that the Customer or its Authorised Users submit to the Service or make available through an Integration.
• “Source Data” means information obtained from public websites, feeds, APIs, files or other third-party sources selected by the Customer.
• “Agreement” means the contractual relationship consisting of the Order, these Terms and documents expressly incorporated into the Agreement.

3. THE REEVALS SERVICE

3.1 Functions

Reevals is a B2B pricing-decision platform for e-commerce. Depending on the selected plan, configuration and technical availability, it may in particular:

• collect and normalise product, price, stock, delivery and other market information from configured websites, feeds and selected APIs.
• match the Customer's own products with competing products and display evidence, confidence levels and queues for manual review.
• monitor prices, availability, sellers, ratings, changes and the freshness of Source Data.
• create pricing strategies, policies, campaigns, simulations and explainable recommendations with rules, limits, approvals and an audit history.
• support controlled publication or delivery of approved prices through exports, APIs and configured Integrations.
• connect data from e-commerce, analytics and other systems, including selected feeds and analytics services.
• provide AI assistance with explanations, suggestions, diagnostics and preparation of reviewable changes.

Specific functions, quotas, sources, frequencies, storage, user numbers and support levels are determined by the Order, Price List and Documentation. Display of a function in the interface does not mean that it is included in every plan.

3.2 Changes and development of the Service

The Provider may continuously fix, update, change or replace the Service, in particular for security, legal compliance, technological development or supplier changes. During a period that has already been paid for, it will not materially reduce the core functionality agreed in the Order without reasonable grounds.

If a planned change materially reduces core functionality and the Provider does not offer a reasonable replacement, the Provider will give advance notice and the Customer may terminate the Agreement when the change takes effect. The Provider will refund the pro rata portion of prepaid fees for the unused period.

3.3 Beta and experimental functions

Functions marked as beta, preview, experimental or free may be changed or discontinued without compensation, may be incomplete and are not subject to an SLA unless the Order expressly provides otherwise. The Customer must not use them for critical decisions without its own verification and fallback procedure.

3.4 Implementation and cooperation

The Customer will provide complete and usable Customer Data and Source Data, necessary access and credentials, technical and business contacts, mappings and decisions in a timely manner. It will also provide reasonable cooperation with configuration, testing and deployment of the Service.

Implementation dates and estimates are indicative unless the Order expressly states that they are binding. The Provider's deadlines will be reasonably extended for delay by the Customer or a third party, source unavailability, missing or changed data and any other obstacle beyond the Provider's reasonable control. During such an obstacle, the Provider is not in delay to the extent that the obstacle prevents performance.

3.5 Changes in scope and acceptance

A change to a source, mapping, Integration, scope or volume, or a request for new custom development, may affect the price and schedule. If the work is outside the scope of the Order, the Provider will perform it after a written change, amendment or separate offer is agreed.

Acceptance criteria are determined by the Order or project plan. If none are specified, an implementation or configuration is deemed accepted when deployed to production use by the Customer or when 10 business days have passed after notice that it is ready, unless the Customer reports a specific material non-conformity with the agreed scope during that period. This rule does not affect latent defects or rights that cannot lawfully be limited.

4. ACCOUNTS AND AUTHORISED USERS

4.1 Registration and account administration

The Customer will provide accurate, complete and current registration, billing and contact details. It will appoint an account administrator who manages Authorised Users, roles, approval permissions, Integrations and security settings.

Each Authorised User must use their own login credentials. Sharing one user account among multiple persons is prohibited unless the Provider expressly supplies a technical account intended for that purpose.

4.2 Account security

The Customer and Authorised Users will protect passwords, API keys, tokens and multi-factor authentication methods, will not use them contrary to the Documentation and will report suspected unauthorised access without delay. The Customer is responsible for activity carried out through its accounts to the extent that it could reasonably control that activity.

The Provider may temporarily block a specific account, key or Integration if it reasonably suspects compromise, misuse or a security risk. Where circumstances permit, it will inform the Customer without delay.

4.3 Audit records

The Service may record logins, configuration changes, approvals, rejections, publications, API calls and other operational events. These records are used for security, support, billing, audit and evidence of actions taken. Their scope and retention are governed by the Documentation, DPA and legal obligations.

Unless the Customer proves otherwise, the Service's audit and billing records constitute rebuttable evidence of actions, approvals, API calls, volumes, times and consumption. The Customer will report a specific discrepancy without undue delay and no later than 30 days after the relevant invoice or record is made available where the nature of the discrepancy permits. Late notice may make the discrepancy more difficult to reproduce but does not affect rights that cannot lawfully be limited.

5. SUBSCRIPTION, PRICE AND PAYMENTS

5.1 Plans, limits and excess use

The Subscription scope, price, currency, billing cycle, quotas and any additional charges are set out in the Order or Price List. The Customer must not circumvent limits by dividing accounts, keys, sources or requests.

If the plan permits excess use, the Provider may charge for it under the Price List. If the plan does not permit it, the Provider may limit the relevant function until the start of the next period or until a higher limit is purchased.

5.2 Billing and automatic renewal

The Subscription is billed in advance monthly, annually or on another cycle specified in the Order. Unless the Order states otherwise, the Subscription automatically renews at the end of the period for another period of the same length. The Customer may disable renewal in the account settings or by following the procedure in the Order before the next period begins.

Cancelling automatic renewal does not terminate access immediately. The Subscription normally continues until the end of the paid period.

Disabling renewal, restricting use or early termination for a reason attributable to the Customer does not release the Customer from the obligation to pay fees that are due or fees agreed for a committed period unless the Agreement expressly permits earlier termination without that obligation.

5.3 Trial period

The duration, functions, limits and payment terms of a trial period are displayed upon activation. If the Customer authorises a future recurring payment when activating the trial, the Subscription converts to a paid Subscription at the end of the trial and the first payment will be made under the Order unless the Customer cancels it beforehand.

The Provider may refuse or terminate trial access in the event of repeated registrations, misuse, fraud or circumvention of limits.

5.4 Payment providers

Payments may be processed by third parties, in particular Stripe or PayPal. Their terms also apply to the Customer's payment. The Provider does not process or store the full payment-card number or security code. It may, however, retain a payment identifier, status, the final digits of the card and data needed for billing and complaint resolution.

5.5 Late payment

If a payment fails or is overdue, the Provider may, after notice, mark the Subscription as unpaid, restrict functions, stop new tasks or suspend access. This does not affect the obligation to pay amounts due or the statutory right to default interest and costs associated with enforcing the claim.

5.6 Taxes

Prices exclude VAT and other taxes unless expressly stated otherwise. The Customer will provide data needed for the correct tax treatment and pay taxes and charges that must be added to the price by law. The Provider bears taxes on the Provider's income.

5.7 Refunds

Fees are non-refundable after the relevant period begins, except where expressly stated in these Terms, the Order or mandatory law. If the Provider terminates a paid Agreement without a breach by the Customer, it will refund the pro rata portion of prepaid fees for the unused period.

5.8 Price changes

The Provider will notify a change to a recurring price at least 30 days before the start of the period in which the new price will apply. The change does not affect a period that has already been paid for. If the Customer does not agree to the new price, it may disable renewal of the Subscription.

6. RIGHT TO USE THE SERVICE, API AND DOCUMENTATION

6.1 Limited right of use

During the Subscription, the Provider grants the Customer a limited, non-exclusive, non-transferable and non-sublicensable right to permit Authorised Users to use the Service for the Customer's internal business purposes in accordance with the Agreement.

A contractor or affiliate of the Customer may use the Service only if permitted by the plan or Order, if it acts for the Customer and is bound by obligations at least as protective as these Terms. The Customer is responsible for that party's use of the Service.

6.2 API and technical accounts

The API may be used only in accordance with the Documentation, allocated permission scopes and limits. API keys and technical tokens are confidential. The Customer must not change headers, identifiers or call methods in order to circumvent quotas, authorisation, audit or security controls.

The Provider may introduce reasonable rate, request-size and task-concurrency limits and may reject calls that threaten the stability, security or fair use of the Service.

6.3 Documentation

The Customer may use and reproduce the Documentation internally to the extent needed to use the Service. It must not distribute the Documentation publicly, remove proprietary notices or use it to create a competing service.

7. CUSTOMER DATA, SOURCES AND OUTPUTS

7.1 Customer Data

The Customer retains its rights in Customer Data. For the period needed to provide the Service, the Customer grants the Provider and its subcontractors non-exclusive permission to host, copy, transmit, validate, transform, analyse, display and otherwise process Customer Data solely for performance of the Agreement, support, security and compliance with legal obligations.

The Customer is responsible for the lawfulness, accuracy and quality of Customer Data and for obtaining the rights, consents and fulfilment of information obligations needed for the Customer Data and instructions it provides. It must not submit data to the Service whose processing is not permitted by the Agreement, Documentation or law.

7.2 Instructions for collection and access to sources

If the Customer designates a website, feed, file, API, account or other source, it confirms that it is authorised to designate that source and that the selected scope of access and use is lawful. For a non-public or authenticated source, the Customer must have express authority to give the Service access.

The Customer must not request circumvention of access restrictions, technical protection measures, paid access, a prohibition on automated access or other measures that it is not entitled to circumvent.

The Provider may refuse, restrict or stop collection from a particular source or by a particular method where required by law, an authority's decision, a legitimate third-party request, security, technical feasibility or reasonable risk management.

7.3 Nature of Source Data

Source Data may originate from publicly available websites, feeds and third-party services. Its availability, structure, meaning, timestamp and accuracy depend on the source and may change without notice. The Provider does not own third-party content and its processing does not change the original owner's rights.

The Service may temporarily retain technical responses, HTML, screenshots, validation evidence and operational metadata where needed for diagnostics, review and evidence of data origin. Retention periods are governed by the Documentation, DPA and Privacy Policy.

7.4 Accuracy, freshness and verification

The Provider uses reasonable validation and control mechanisms but does not guarantee that Source Data or Outputs are always complete, current, error-free or suitable for a particular decision. Source failure, a website change, ambiguous matching, currency, VAT, delivery, stock, product variants or a synchronisation delay may affect the result.

Before using Outputs, the Customer must review their source, time, context, rules, assumptions, available evidence and approval status, particularly for prices with a significant business or legal impact.

7.5 Use of Outputs

The Customer may use Outputs for its internal business purposes and export them within the scope of its plan. Further publication, sale, licensing or distribution to third parties is permitted only with the Provider's consent and to the extent of the rights in the relevant Source Data. The Customer is responsible for the lawfulness of its specific use of Outputs.

7.6 Data review and reproduction

Before activating automation, the Customer will verify a representative sample of product matching, source mapping, currency, VAT, delivery, stock, data freshness and configured thresholds. The Customer will continuously review whether changes to a source or its product range require configuration changes.

The Customer will report a specific defect in a data set or historical collection without undue delay, generally within 14 days after it is made available. The report must identify the affected source, time, product or other identifier and a representative example so that the defect can be reproduced.

After retention periods or the operational review period expire, the Provider may delete raw technical responses and evidence. It may then be impossible to reproduce the source's earlier state. This review period does not constitute a waiver of claims or limit rights that cannot lawfully be limited.

8. PRICING DECISIONS, AUTOMATION AND AI

8.1 Decision-support tool

Reevals is a business decision-support tool. The Provider is not the Customer's pricing, tax, accounting or legal adviser and does not assume the role of seller to end customers. The Customer remains solely responsible for the final price, discount, segment, campaign, publication and business consequences of its decision.

The Customer must ensure compliance in particular with competition, consumer-protection, prior-price and discount, personalised-pricing, non-discrimination and tax rules, supplier contracts and marketplace rules.

Matching, averaging, imputation, availability assessment, rounding and other methodological assumptions may materially affect Outputs. Before use, the Customer will verify that the assumptions and settings made available in the Documentation or interface are appropriate for its use case.

8.2 Competition

The Customer must not use the Service to agree or coordinate prices, divide markets, restrict production or sales, exchange non-public competitively sensitive information or engage in any other anti-competitive practice. The Service is intended for the Customer's independent decision-making based on lawfully available inputs and its own rules.

8.3 AI Outputs

AI Functions generate probabilistic outputs and may be inaccurate, incomplete, out of date or unsuitable. AI output is not an authoritative source of factual claims or a substitute for professional review. The Customer must not automatically rely on free-form AI text for a decision that may have a significant financial, legal or reputational impact.

The Customer must not submit passwords, secret keys, special categories of personal data or data subject to a special regime to AI Functions unless expressly permitted by the Documentation and DPA.

8.4 Approval and execution

A generative AI output does not by itself authorise publication of a price or another external change. Execution occurs only through an enabled workflow, permissions, technical validations, protective rules and an approval or automation mode configured by the Customer.

If the Customer enables automatic approval, scheduling or publication, it is responsible for the selected thresholds, scope, rules, sources, credentials and ongoing review. The Customer must maintain reasonable human oversight and an emergency procedure for stopping or correcting an erroneous change.

8.5 Acceptance of automation configuration

Before launch, the Customer will approve or itself activate the automation rules, thresholds, safeguards and target systems. Production use or express approval confirms that the configuration reflects the Customer's instructions at that time.

The Provider is not responsible for a consequence to the extent caused by a configuration approved by the Customer, a later change to it, incomplete inputs, an ignored warning or insufficient Customer oversight. This provision does not exclude the Provider's liability for its own breach of obligation.

9. INTEGRATIONS AND THIRD-PARTY SERVICES

9.1 Integrations

The Service may communicate with third-party payment, hosting, analytics, e-commerce, ERP, data, communication and AI services. By activating an Integration, the Customer instructs the Provider to send and receive data and perform technical actions on the Customer's behalf within the configured scope.

The Customer will secure the permissions, licences, accounts and consents needed for an Integration. It may revoke access tokens and credentials at any time, but doing so may immediately disable the Integration.

9.2 Third-party terms and availability

Third-party services are subject to their own terms and policies. The Provider is not liable for their acts, outages, API changes, prices, security incidents or discontinuation unless the damage was caused by the Provider's breach of its obligations in selecting, configuring or using such a service.

If a third party changes or discontinues a function needed for an Integration, the Provider may modify, restrict or discontinue the Integration. Section 3.2 applies as appropriate to a material paid Integration.

The Customer will maintain supported versions of connected systems, valid credentials, required licences, connectivity and current configuration. The Provider is not required to support an obsolete, non-standard modified or vendor-unsupported version of a system.

The Provider may separately price work caused by a change to the Customer's or a third party's system or API that is not included in the Order. It will carry out the work after the Customer approves the offer.

10. ACCEPTABLE AND PROHIBITED USE

10.1 Permitted use

The Customer may use the Service only lawfully, for its own internal business purposes and in accordance with the plan, Order, Documentation and third-party rights.

10.2 Prohibited conduct

Neither the Customer nor an Authorised User may:

• make the Service available to, rent it to, sell it to, sublicense it to or provide it as a service to a third party unless expressly permitted by the Order.
• copy the Service, create derivative works from it, decompile it, reverse engineer it or attempt to obtain its source code except to the extent expressly permitted by mandatory law.
• circumvent authentication, permissions, quotas, approval, protective rules, audit, security measures or technical restrictions.
• extract data from the Platform itself by automated means outside the permitted API or place an unreasonable load on the infrastructure.
• transmit malware, harmful code, unsolicited communications or content that infringes third-party rights.
• conduct penetration testing, vulnerability scanning or disruption attempts without the Provider's prior written consent.
• use the Service to develop, train or operate a product whose principal purpose is to compete with the Platform by using non-public elements of the Service or the Provider's Confidential Information.
• collect or process personal data without a legal basis, transparency and the required permissions.
• use Outputs for fraud, deception, unlawful price manipulation, coordination with competitors or breach of sanctions and export-control rules.

10.3 Response to a breach

The Provider may reasonably investigate a suspected breach, request remediation, restrict a specific function, block harmful content or temporarily suspend access. It will limit the intervention to what is reasonably necessary to protect the Service, the Customer, other users or third parties, or to comply with a legal obligation.

10.4 Verification of purpose and risk

The Provider may request information and documents reasonably necessary to verify the Customer's identity and business activities, intended use, right to designate a source and the lawfulness of processing. The Customer will provide reasonable cooperation and keep that information current.

The Provider may refuse or restrict a particular source, method or function and may reasonably suspend access if it has a reasonable suspicion of unlawful or fraudulent use, a security risk, infringement of third-party rights or disproportionate regulatory risk. It will limit the intervention to necessary measures and inform the Customer where permitted by law, security and the circumstances.

11. PERSONAL-DATA PROTECTION AND SECURITY

11.1 Roles of the parties

The Provider processes contact, user, billing and operational personal data on its own behalf under the Privacy Policy. The Privacy Policy is an information document and acceptance of it is not required where consent is not the legal basis for processing.

If the Provider processes personal data contained in Customer Data solely on the Customer's instructions, the Customer is the controller and the Provider is the processor. Before such processing begins, the parties will enter into a DPA electronically or in another written form.

11.2 Customer obligations

The Customer determines the purpose and lawfulness of personal data that it submits to the Service or instructs the Service to collect. It will ensure a legal basis, provision of information to data subjects, handling of their rights, appropriate data minimisation and setting of retention periods.

11.3 Security measures

The Provider maintains appropriate technical and organisational measures, taking into account the nature of the Service, the state of the art, costs and risks. No internet service is completely secure, however. The Customer is responsible for the security of its own devices, networks, accounts, Integrations and exports and for the correct configuration of roles and approvals.

The Provider will report and address a security incident involving Customer Data to the extent and within the periods required by law and the DPA.

11.4 Subcontractors and transfers

The Provider may use subcontractors and subprocessors. Their engagement and replacement, international transfers and personal-data protection safeguards are governed by the DPA and Privacy Policy.

12. INTELLECTUAL PROPERTY

12.1 Provider rights

The Platform, software, interface, algorithms, workflows, schemas, Documentation, design, trade marks and all related rights belong to the Provider or its licensors. The Agreement does not transfer ownership of the Service or any part of it to the Customer.

12.2 Customer and third-party rights

The Customer retains its rights in Customer Data. Rights in Source Data remain with their original holders. To the extent that an Output contains elements of the Platform, the Provider grants the Customer a non-exclusive right during and after the Agreement to use that Output for the purposes permitted by Section 7.5.

12.3 Feedback

If the Customer voluntarily provides a suggestion, feedback or idea, the Provider may use it without charge to develop the Service but must not disclose Confidential Information or identify the Customer without consent.

12.4 Aggregated and anonymised data

The Provider may create and use statistical, aggregated and anonymised data for operation, security, performance measurement and improvement of the Service only if the data cannot reasonably identify the Customer, an Authorised User or another natural person and does not reveal the Customer's Confidential Information.

12.5 Public Source Data

The Provider must not use Customer Data for its own business purposes unrelated to providing, securing or improving the Service to the permitted extent. This restriction does not prevent the Provider from independently collecting, retaining, normalising and reusing publicly available Source Data or using data under Section 12.4, provided that it does not identify the Customer, reveal its strategy or breach its Confidential Information.

12.6 Customer name and logo

During the Agreement, the Customer grants the Provider non-exclusive, royalty-free and revocable permission to display its business name and logo on the Provider's website, in a customer list, business presentations and reasonable marketing materials as an indication that it is a customer of the Service. The Provider must not use them to suggest an endorsement, partnership or approval beyond the customer relationship and will use the current form of the designation in a reasonable manner.

The Customer may object to such use or revoke the permission in writing at any time. The Provider will remove the name and logo from new and electronic materials within a reasonable period and no later than 30 days. Revocation does not apply to materials that have already been printed or irrevocably ordered.

A case study, quotation, reference containing specific results or metrics, or a detailed description of the use of the Service requires the Customer's prior written consent.

13. CONFIDENTIALITY

13.1 Confidential Information

Confidential Information means non-public business, technical, security, pricing, product and other information of a party that is marked confidential or whose confidential nature is apparent from the circumstances. Customer Data and non-public elements of the Service are the Confidential Information of the relevant party.

13.2 Recipient obligations

The recipient will use Confidential Information only to perform the Agreement, protect it at least as carefully as its own information of a similar nature and disclose it only to persons who need to know it and are bound by confidentiality. It will not disclose it to another person without consent.

13.3 Exceptions and required disclosure

The obligation does not apply to information that the recipient can demonstrate it knew without restriction, developed independently, lawfully obtained from a third party or that became public without its breach. If disclosure is required by law or a public authority, the recipient will inform the other party in advance to the extent permitted and disclose only what is necessary.

13.4 Duration

The confidentiality obligation applies during the Agreement and for five years after its termination. For trade secrets and personal data, it continues for as long as their nature or the law requires protection.

14. AVAILABILITY, MAINTENANCE AND SUPPORT

14.1 Availability

The Provider uses reasonable business and technical efforts to make the Service available. Unless the Order or a separate SLA expressly specifies an availability level, credit or particular remedy, no percentage-availability guarantee is provided.

Availability excludes scheduled maintenance, emergency security measures, force majeure, Customer or third-party outages, blocking or changes to sources, incorrect configuration and suspension under the Agreement.

14.2 Maintenance

The Provider may perform scheduled and emergency maintenance. Where reasonably practicable, it will give reasonable advance notice of scheduled maintenance with a significant impact. Emergency maintenance may begin without prior notice.

14.3 Support

The scope, channel, hours and target response times for support are determined by the plan, Order or SLA. When reporting an issue, the Customer will provide reasonable diagnostic information and will not send passwords, full payment details or unnecessary personal data.

14.4 Customer backups

The Service is not an archive or backup system unless expressly stated in the Order. The Customer should regularly export data, configurations and decisions that it needs to retain outside the Service or under the law.

15. REPRESENTATIONS AND WARRANTIES

15.1 Mutual representations

Each party represents that it has authority to enter into the Agreement and perform its obligations. The Provider will provide the Service with professional care appropriate to the nature of a B2B SaaS service and in material conformity with the Documentation.

15.2 Remedy for a defect

If the paid Service materially fails to conform to the Documentation and the Customer describes the defect sufficiently, the Provider will make reasonable efforts to correct it or provide a workaround. If this is not possible within a reasonable period and the defect materially prevents use, the Customer may terminate the affected part of the Agreement and receive the pro rata portion of prepaid fees for the unused period.

15.3 Exclusions

The remedy does not apply to defects caused by use contrary to the Agreement, an unsupported environment, intervention by the Customer or a third party, an unauthorised Integration, a source change or a circumstance beyond the Provider's reasonable control. Free, trial and beta functions are provided as available.

The Provider does not guarantee a specific economic result, increased profit, the correctness of a business strategy, continuous availability of every source, correction of every error or that Outputs will be suitable without Customer review.

16. LIABILITY FOR DAMAGE

16.1 Scope of liability

Each party is liable for damage caused by breach of its obligation under applicable law. In assessing causation, foreseeability and the extent of damage, account will be taken of the nature of the Service as a support tool, the Customer's duty to verify Outputs and automation settings and the injured party's duty to prevent and mitigate damage.

16.2 Cap

To the extent permitted by mandatory law, the Provider's total aggregate liability arising out of or in connection with the Agreement will not exceed the fees excluding VAT that the Customer paid or was required to pay for the Service during the 12 months immediately preceding the event giving rise to the claim. For a Subscription shorter than 12 months, the fees for the actual period apply.

16.3 Indirect and business consequences

To the extent permitted by mandatory law, the Provider is not liable for indirect or consequential damage, loss of profit, business opportunity, reputation or anticipated savings where these were not a reasonably foreseeable consequence of the particular breach when the Agreement was entered into.

16.4 Specific sources of risk

The Provider is not liable for damage to the extent caused by inaccurate or changed Source Data, a Customer decision, configuration of its rules, insufficient approval, an unauthorised Integration, an act of a third party or the Customer's breach of the Agreement. This provision does not exclude the Provider's liability for its own breach of obligation.

16.5 Exceptions

The limitations do not apply to wilful misconduct, gross negligence, personal injury or other liability that cannot lawfully be limited. The limitation is interpreted as an agreement on the permitted scope and method of determining compensation, not as a waiver of a claim before a breach of obligation contrary to Section 386 of the Slovak Commercial Code.

17. THIRD-PARTY CLAIMS

17.1 Customer-related claims

The Customer will reimburse the Provider for reasonable and evidenced costs and amounts finally awarded or approved in a settlement as a result of a third-party claim arising from unlawful Customer Data, an unauthorised instruction to access a source, infringement of third-party rights or use of the Service contrary to the Agreement, unless the Provider caused the claim through its own breach.

17.2 Intellectual-property claims

If a third party claims that the paid Platform, when used under the Agreement, infringes its intellectual-property right, the Provider will, at its option, secure the right to continue use, modify or replace the affected part with a comparable function, or discontinue it and refund the pro rata portion of prepaid fees. This does not apply to Customer Data, Source Data, Customer instructions, combinations outside the Documentation or unauthorised modifications.

17.3 Procedure

The party seeking protection will notify the claim without delay, provide reasonable cooperation and, without the other party's consent, will not enter into a settlement that imposes an obligation, admission or restriction on the other party. Delay releases the other party from its obligation only to the extent that the delay demonstrably prevented its defence.

18. TERM, SUSPENSION AND TERMINATION

18.1 Term

The Agreement continues from formation under Section 1.3 for the trial or paid period and renews under Section 5.2 unless terminated.

18.2 Termination by the Customer

The Customer may disable renewal of the Subscription at any time in the manner specified in the account or Order. If the Provider materially breaches the Agreement and does not remedy the breach within 15 days after sufficiently specific written notice, the Customer may terminate the affected Agreement and claim the pro rata portion of prepaid fees for the unused period.

18.3 Suspension and termination by the Provider

The Provider may reasonably suspend access for late payment, a security risk, unlawful use, a threat to a third party or a serious breach. If remediation is possible and the matter is not urgent, it will provide a reasonable period to remedy it.

If either party materially breaches the Agreement and does not remedy the breach within 15 days after written notice, the other party may terminate the Agreement. Immediate termination is possible in the event of wilful unlawful use, repeated compromise, insolvency to the extent permitted by law or a breach that cannot be remedied.

The Provider may also terminate a paid Agreement without a Customer breach by giving at least 30 days' notice. In that case, it will refund the pro rata portion of prepaid fees for the unused period.

18.4 Effects of termination and export

Upon termination, the right to use the Service ends and the Customer must stop using APIs, tokens and Documentation except for lawfully retained copies. Before termination, the Customer is responsible for exporting the data it needs.

Where technical and security conditions permit, the Customer may request an available standard export of its Customer Data in writing within 30 days after termination. After that period, the Provider may delete or anonymise it in accordance with the DPA, internal periods, backups and legal obligations. Restoration from backups is not guaranteed.

18.5 Surviving provisions

Provisions intended by their purpose to survive remain effective after termination, in particular provisions on payments, confidentiality, personal-data protection, intellectual property, Outputs, liability, third-party claims and dispute resolution.

19. CHANGES TO THE TERMS

The Provider may change the Terms because of a change to the Service, law, security or business model. It will notify a material change at least 30 days before it takes effect by email or a prominent notice in the Service. A change required by law or urgent security needs may take effect sooner. The Provider will state the reason where permitted by law.

If a material change worsens the Customer's position during a paid period and the Customer does not agree to it, the Customer may terminate the Agreement when the change takes effect and claim the pro rata portion of prepaid fees for the unused period. Otherwise, continued use after the effective date constitutes acceptance of the updated Terms.

20. NOTICES AND ELECTRONIC COMMUNICATION

Contractual notices may be delivered to the account contact email, through the Service or in the manner specified in the Order. The Customer will keep contact details current. Operational messages, security alerts and invoices may be delivered electronically.

A notice of material breach, termination or legal claim must also be sent to the other party's legal contact if known. Notice is deemed delivered when it is demonstrably sent without an error message and no later than the next business day. This does not affect mandatory service-of-notice rules.

21. GOVERNING LAW AND DISPUTES

21.1 Governing law

The Agreement is governed by the laws of the Slovak Republic, in particular Act No. 513/1991 Coll., the Slovak Commercial Code. The parties enter into it as an agreement under Section 269(2) of the Slovak Commercial Code. Conflict-of-law rules and the United Nations Convention on Contracts for the International Sale of Goods do not apply.

21.2 Negotiation and courts

Before commencing court proceedings, the parties will attempt to resolve a dispute through negotiations between authorised representatives for at least 30 days after written notice of the dispute, unless a risk of harm or expiry of a limitation period requires faster action.

The courts of the Slovak Republic having subject-matter and territorial jurisdiction have jurisdiction over disputes. To the extent permitted by procedural law, the parties agree to the territorial jurisdiction of the court for the Provider's registered office.

21.3 Consumer mechanisms

Because the Service is intended exclusively for entrepreneurs and professional use under Section 1.2, provisions on consumer withdrawal, alternative consumer-dispute resolution and other special consumer-protection mechanisms do not apply to the Agreement.

22. FINAL PROVISIONS

22.1 Entire Agreement and order of documents

The Agreement constitutes the entire agreement concerning the Service. In the event of a conflict, the following order applies: (a) an individual master agreement or signed Order, (b) the DPA for personal-data processing matters, (c) the SLA for availability and support, (d) the Order for other matters, (e) these Terms and (f) the Documentation and Price List. A later document takes precedence over an earlier one only to the extent of an express conflict.

22.2 Severability and interpretation

Invalidity or unenforceability of part of the Agreement does not affect the remaining provisions. The parties will replace it with a valid provision that comes as close as possible to the economic purpose. Headings are for convenience. Terms in the singular include the plural as the context requires.

22.3 No waiver

Failure or delay in exercising a right does not constitute a waiver. A waiver must be express and applies only to the specific case.

22.4 Assignment

The Customer must not assign the Agreement or a material part of its rights and obligations without prior written consent. The Provider may assign the Agreement to an affiliate or legal successor in a merger, transformation or transfer of a substantial part of its business, provided that this does not materially reduce the Customer's rights.

22.5 Subcontractors

The Provider may perform through subcontractors but remains responsible for their performance as for its own unless the Agreement or mandatory law provides otherwise. Processing of personal data by subprocessors is governed by the DPA.

22.6 Force majeure

A party is not liable for delay caused by an extraordinary, unforeseeable and unavoidable obstacle beyond its reasonable control, in particular a widespread infrastructure outage, attack, natural event, war, decision of an authority or outage of a critical supplier. The affected party will reasonably inform the other party and mitigate the consequences. Force majeure does not release the Customer from payment for Service already provided.

22.7 Independent parties

The parties are independent contracting parties. The Agreement does not create agency, employment, a joint venture or partnership and neither party may bind the other without express authority.

22.8 Language

The Slovak version of the Terms is binding. A translation is for information only unless the Order expressly provides otherwise.

23. PROVIDER AND CONTACT DETAILS

Business name: CREALAB s.r.o.

Registered office: Terézie Vansovej 1167/1, 050 01 Revúca, Slovak Republic

Company ID No.: 50 156 896

Tax ID No.: 2120193977

VAT ID No.: SK2120193977

Register entry: Commercial Register of the District Court Banská Bystrica, Section Sro, Insert No. 29215/S

Legal notices and support: support@reevals.com

Business contact: contact@reevals.com

Website and Service: https://www.reevals.com

Privacy Policy: https://www.reevals.com/privacy

Cookie Policy: https://www.reevals.com/cookies

DPA: https://www.reevals.com/data-processing-agreement

These Terms take effect on 25 August 2026.

© 2026 CREALAB s.r.o. – all rights reserved.