1. Parties
These Terms of Service govern access to and use of the Alethexis platform provided by ALETHEXIS, S.L. (Tax ID (NIF) B88758057), with registered office at C/ Tirso de Molina 36, 08940 Cornellà de Llobregat (Barcelona) ("Alethexis"), and the customer organisation that contracts the service ("the Customer").
The Service is intended exclusively for businesses, organisations and professionals acting for purposes relating to their trade, business or profession. The person accepting these Terms represents that they have authority to bind the Customer and are not contracting as a consumer. If mandatory law nevertheless grants a person consumer status, the rights deriving from it are not excluded by this clause.
2. Purpose
Alethexis is a SaaS platform for AI and GDPR governance aimed at businesses. It allows AI systems to be inventoried, classified by risk level, policies, assessments and evidence to be documented, and documentation to be generated in support of regulatory compliance.
Product Data. For the purposes of these Terms, the Data Processing Agreement (DPA), the Privacy Policy and the Register of sub-processors and providers, "Product Data" means the data, documents and files that the Customer and its Users enter, import or generate in the Service, including inventories, classifications, assessments, policies, evidence and generated documents, whether or not they contain personal data. The Data Processing Agreement governs exclusively the processing of the personal data contained in that Product Data that Alethexis carries out on behalf of the Customer. Data processed by Alethexis as an independent controller are governed by the Privacy Policy.
2 bis. M3 — Advanced management of risks, assessments and documentation of AI systems
Module M3 provides functionality to organise, document and maintain the traceability of assessments, risks, controls and evidence relating to artificial intelligence systems.
It includes documentary support tools aimed at organisations acting as providers of high-risk AI systems, including the preparation and structuring of technical documentation in accordance with Annex IV of Regulation (EU) 2024/1689, risk management, documentation on data governance, the tracking of activities related to conformity assessment, and post-market monitoring.
These features make it possible to generate drafts, organise information, record decisions and maintain evidence provided or validated by the Customer.
Alethexis does not carry out conformity assessments on behalf of the Customer, does not act as a notified body, does not certify AI systems and does not issue or sign EU declarations of conformity on behalf of the provider.
It is for the Customer to verify the accuracy, completeness, sufficiency and legal and technical adequacy of the documentation generated, to carry out the assessments incumbent on it and to take the decisions required by the applicable legislation.
Use of the module does not in itself constitute accreditation, certification or any guarantee of conformity or regulatory compliance.
The foregoing is without prejudice to the obligations and liabilities that legally correspond to Alethexis as the service provider.
3. Plans, cycles, price and taxes
The plan, the billing cycle (annual or monthly), the users included, the add-ons (Agentic Add-on, additional users) and the price applicable are those shown in the order or checkout accepted by the Customer. Prices are stated exclusive of indirect taxes. The Customer shall provide the tax details required, including the VAT identification number where applicable; Alethexis will apply the VAT treatment required by applicable law. The reference prices published on the pricing page may be updated for future periods in accordance with clause 3 ter.
3 bis. Payment and activation
The annual billing cycle is paid by SEPA Direct Debit; the monthly billing cycle is paid by card. Fees are payable in advance for the contracted period.
For the annual billing cycle, Alethexis activates full access when the Customer signs the SEPA Direct Debit mandate, before payment is confirmed. Signing the mandate does not constitute confirmation of payment.
Payment incidents. Alethexis will distinguish the following situations, which it will notify to the Customer's Owner by email and by notice in the Service where they give rise to an outstanding amount or to an action requiring its attention:
- Direct debit rejected or payment failed: the direct debit or charge is not successfully executed.
- Direct debit returned after collection: an amount previously charged is subsequently returned.
- Payment under dispute: there is a payment claim or dispute pending resolution.
- Invoice declared uncollectible: the payment provider classifies an invoice as uncollectible. That classification does not in itself amount to a bank rejection, does not necessarily extinguish the debt and requires the amount actually outstanding and payable to be checked.
- Regularisation: the Customer pays the amount payable or the collection is definitively confirmed.
- Cancellation: the subscription ends in accordance with the contract's termination conditions.
Regularisation. Where there is an amount that is due and payable as a result of a rejected or returned direct debit or of an invoice declared uncollectible, Alethexis will notify the Owner of the incident, the outstanding amount and how to regularise it. The Customer will have 14 calendar days from the verifiable notification to regularise the situation. This period may be extended in the Customer's favour, but not unilaterally shortened for an incident already notified.
During that period, the contracted access will be maintained. In the monthly cycle, the collection retries provided for by the payment provider may be carried out.
Payments under dispute. While there is a formal dispute pending verification, raised in good faith, Alethexis will not automatically suspend the Service on that ground alone. If the outcome confirms a payable debt, the Customer will be notified and granted the corresponding regularisation period.
Reversible suspension. If the regularisation period elapses without the amount payable being paid, Alethexis may, after prior notice, suspend access to the contracted modules. The suspension will be reversible. The Owner will keep access to "Plan and billing" to regularise the payment and to the export functions available. The data will remain subject to the contractual retention and erasure periods. Once the payment has been regularised, the contracted access will be restored.
Penalties and interest. Alethexis will not apply contractual penalties or its own administrative surcharges for a payment incident. This does not exclude late-payment interest or compensation for recovery costs that may be due under applicable law, in particular Spanish Law 3/2004, nor does it extinguish amounts validly accrued.
Customer's rights. The above procedure does not limit the rights to a refund of payment transactions that the Customer has under applicable law and the SEPA instrument used.
Termination for non-payment. If the breach persists after the payment demand and the applicable regularisation procedure, Alethexis may terminate the subscription after notifying the Customer. In that case, the DPA's procedure for the return or erasure of data will apply, without prejudice to amounts validly accrued.
3 ter. Renewal, cancellation and changes
The subscription renews automatically for successive periods of equal duration, at the price in force on the renewal date, unless cancelled before that date from the billing portal. Cancellation takes effect at the end of the period paid for; pro-rata amounts for periods already started are not refunded, save for a legal obligation, a billing error or an express undertaking. Alethexis will give at least 30 days' notice of any price change before the renewal to which it applies.
An upgrade is pro-rated in accordance with the applicable financial terms. A downgrade will take effect at the end of the billing period already paid for. From that moment, the features not included in the new plan will cease to be available, without the change in itself entailing the deletion of the data previously recorded. The Customer will retain the ability to export that data in accordance with the terms of the Service and of the Data Processing Agreement.
4. Trial period
Alethexis offers a 14-day free trial with no payment method, activated on completion of the initial setup. The trial does not convert into a paid subscription unless the Customer expressly contracts a plan.
When the 14-day trial ends without a plan being contracted, access to the modules is deactivated. The data are kept for an additional period of 30 days so that a plan can be contracted and the data recovered. Once that period has elapsed, the export and the erasure procedure described in the Data Processing Agreement begin.
4 bis. Classroom accounts
Classroom accounts, intended for training activities, are also governed by the Classroom Terms Annex, which the Owner accepts expressly, by means of a separate checkbox that is not pre-ticked, before the account gives access, and which is published at /legal/anexo-aula. In matters relating to classroom accounts, the Annex prevails over these Terms.
5. Acceptable use
The Customer undertakes to use the platform in accordance with the law and with these terms, not to introduce unlawful content, to safeguard its credentials and to be responsible for the activity of the users of its account. Alethexis may suspend access in the event of use that compromises the security or integrity of the service.
5 bis. Integrations: read API, outbound notifications, auditor access and single sign-on
(a) API keys. The Customer is responsible for safeguarding the read API keys it generates and for revoking them without delay when they are no longer needed or when it suspects they have been compromised. Each key is shown only once, when it is created, and cannot be consulted again: if it is lost, it is revoked and another is created. All activity carried out with a key is attributed to the Customer.
(b) Usage limits. The Service applies rate and volume limits to the API, as set out in its documentation. Alethexis may suspend or revoke a key whose use compromises the availability or security of the Service, informing the Customer.
(c) Notification recipients. The Customer designates and configures the addresses that receive its outbound notifications, and is responsible for their security — including the encrypted channel, cryptographic verification of the authenticity and integrity of each delivery and access control of the receiving system — and for the legal relationship it has with whoever operates it.
A recipient designated by the Customer is not a sub-processor of Alethexis : Alethexis merely sends it the notification on the Customer's instruction. Its own status — processor of the Customer, independent controller or otherwise — depends on its relationship with the Customer.
(d) Content of the notifications. Outbound notifications carry the event type, identifiers, a status and a timestamp . To obtain the detail, the recipient queries the authenticated API. There are no fields intended to contain personal data.
(e) Personal data in fields not intended for it. The Customer undertakes not to enter personal data in fields not intended to contain it — names of systems, tools, providers, labels and the like. Naming a system after a person turns a field the Service treats as technical into personal data, in the interface, in the API and in the notifications.
(f) External auditors. The Customer is responsible for authorising each auditor, for deciding what they may consult and for ensuring that an adequate legal and confidentiality relationship exists with them . Access always expires — 7, 30 or 90 days —, the Customer may revoke it at any time and may grant it with or without download.
(g) Federated authentication. If the Customer configures single sign-on, it engages and administers the identity provider itself . Alethexis does not create accounts from that identity: only someone already invited to the organisation can sign in.
6. Service availability
Alethexis will use reasonable means, in accordance with the state of the art, to keep the Service operational and accessible on a continuous basis. The Service does not have a contractual Service Level Agreement (SLA) with financial compensation in the M1, M2 and M3 plans of this launch phase; Alethexis may offer a formal SLA as an additional option for Enterprise customers in the future.
Scheduled maintenance tasks will be communicated with a minimum of 48 hours' notice, except for urgent maintenance for security reasons, in which case notice will be given as soon as possible.
7. Limitation of liability
The platform is a methodological support tool. It does not constitute legal advice, nor does it replace the roles, decisions and obligations that the applicable legislation assigns to the Customer. Ultimate regulatory compliance is the responsibility of the Customer.
To the maximum extent permitted by applicable law, the total and aggregate liability of Alethexis towards the Customer for any claim arising from or relating to these Terms or the Service is limited to the amount actually paid by the Customer to Alethexis in the twelve (12) months preceding the event giving rise to the claim.
Neither Party shall be liable to the other for indirect damages, loss of profit, loss of data or loss of business, except in cases of wilful misconduct or gross negligence.
This limitation does not apply: (i) to cases of wilful misconduct or gross negligence; (ii) to breach of confidentiality obligations; or (iii) to liability arising from the processing of personal data, which is governed by the Data Processing Agreement (DPA).
8. Intellectual property
The software, the trade mark, the design and the methodological contents of the platform are owned by Alethexis. The Customer retains ownership of the data and documents it enters into or generates with the platform.
9. Data protection
The processing of personal data is governed by the Privacy Policy and, where Alethexis acts as processor of the Customer's data, by the Data Processing Agreement (DPA) which forms part of the contract.
The activation of the integrations described in clause 5 bis — API keys, notification recipients, identity provider and external auditor access — constitutes a documented instruction of the Customer for the purposes of Article 28 GDPR and of that Agreement.
10. Term and termination
The contract remains in force for the duration of the subscription and its renewals. Either party may terminate it for a material breach not remedied after written notice, or immediately if the breach cannot be remedied. On termination, the Customer may export its data during the grace period and the personal data processed by Alethexis as processor is returned or deleted in accordance with clause 10 of the Data Processing Agreement .
11. Applicable law
These Terms are governed by Spanish law and by directly applicable European Union law. For contractual disputes, the parties submit to the Courts and Tribunals of Barcelona, to the extent permitted by applicable law and without prejudice to the powers of administrative and data protection authorities.
12. Languages, prevalence and entire agreement
The Terms are offered in Spanish and English; both versions form part of the contractual framework and state the same terms. In the event of a discrepancy, the Spanish version prevails, without prejudice to mandatory rules. The order, these Terms and the DPA constitute the applicable agreement; in matters of processing on behalf of the Customer, the DPA prevails.
13. Amendments
Alethexis may amend these Terms for objective and justified reasons, including regulatory changes, security needs, technical changes and the evolution of the features or of the provision of the Service.
Contractual amendments will be notified to the Customer by email and by a notice in the Service, at least 30 calendar days before they take effect.
Exceptionally, where a legal obligation or a duly justified urgent security need prevents that period from being observed, Alethexis may apply the strictly necessary amendments at shorter notice, informing the Customer of their reasons and scope as soon as possible.
Amendments may not unilaterally alter the essential object of the contract or substantially reduce the contracted services during a period already paid for.
Where an amendment is materially unfavourable to the Customer, the Customer may reject it and terminate the contract before it takes effect, without penalty and with a proportional refund of the amounts paid in advance for the period of service not used.
Amendments that require express acceptance under applicable law shall not be deemed accepted by the Customer's mere silence.
Price changes shall be governed by clause 3 ter and shall apply in accordance with its renewal rules. Amendments to the Data Processing Agreement (DPA) shall be governed by its own contractual procedure.
Alethexis will keep a version history that identifies the publication date, the effective date and the main changes introduced.
Version history
| Version | Published | Effective | What changes |
|---|---|---|---|
| 2.2 | 5 November 2026 | Applicable to new contracts from its publication and acceptance. For earlier contracts, from the effective date communicated individually in accordance with the applicable contractual amendment procedure. | Version 2.2 — published for new contracts, which accept it expressly, and notified to earlier contracts by email and notice in the Service at least 30 calendar days in advance (clause 13). Sets the downgrade regime (clause 3 ter) and the end of the trial (clause 4); defines "Product Data" (clause 2); incorporates classroom accounts and their Annex (clause 4 bis) and the procedure for payment incidents, regularisation, reversible suspension and termination for non-payment (clause 3 bis). |
| 2.1 | 26 October 2026 | 26 October 2026 | Version 2.1 — published on 26 October 2026. In force from its publication (26 October 2026) for new contracts. It clarifies payment of the annual cycle — SEPA Direct Debit only, activation upon signature of the mandate and treatment of rejected or returned direct debits — (clause 3 bis) and the terminology for verification of outbound notifications (clause 5 bis, letter c). Prompted by internal decisions D39 and D41 (23/10/2026) and CR_2026_979. |
| 2 | 15 October 2026 | 15 October 2026 | Version 2 — published on 15 October 2026. In force from its publication for new contracts. It adds the definition of module M3 (clause 2 bis), the amendments clause (clause 13) and this version history. On the publication date no third party was bound by the previous version: the only registered organisations were Alethexis's own internal test accounts (check by Alethexis SL on 15 October 2026, repeated on the publication date). |
| 1 | 18 June 2026 | 18 June 2026 | Version 1 — published on 18 June 2026. In force from its publication. Initial version. |