This Data Processing Agreement (the “Agreement”) governs the personal data that Melso, Inc. (“Melso”) processes on behalf of the self-employed person or company that contracts its gestoría service with an AI agent (the “Client”), as Article 28 of Regulation (EU) 2016/679 (“GDPR”) requires, and incorporates the European Union’s standard contractual clauses for its transfer to the United States.
1. Parties and roles
This Agreement supplements Melso’s Terms of Service and includes its five annexes. It is concluded in writing through the signature of both parties, including an electronic one, or through the written acceptance of an owner of the Client’s account that states this version. The binding version is the Spanish one.
The Client is the person or entity that holds the Melso account, identified by its name or company name, its tax ID (NIF) and its address.
The entity that carries out the processing is Melso, Inc., with tax ID EIN 38-4412905, registered address at 625 2nd St, Floor 2, Door 204, San Francisco, CA 94107, United States and registry details Delaware Division of Corporations, file number 10761720; incorporated on September 8, 2026.
Melso’s data protection contact: privacy@melso.ai. Data protection officer: none has been designated. Representative in the European Union: Alejandro Gómez Cerezo (privacy@melso.ai).
The Client acts as controller of the personal data it entrusts to Melso or that Melso obtains on its instructions, because it decides the purposes and means of the processing. Melso acts as processor on the Client’s behalf.
This Agreement does not cover data that the Client itself processes on behalf of a third-party controller. If the Client needs Melso to process such data, the parties will agree on it in writing before it is provided.
The data Melso processes by its own decision to manage its relationship with the Client, such as sign-up, billing and commercial communications, or to meet its own legal obligations, such as identifying the partners of a company that Melso incorporates on the Client’s behalf under Spanish Law 10/2010 on the prevention of money laundering, is governed by Melso’s privacy policy, under which Melso acts as controller. This separation does not allow the data of the Agreement to be used for Melso’s own purposes.
2. Subject matter, purpose and duration
Melso will process the data described in Annex I solely to provide the Client with the contracted service: accounting and record books; the preparation of its returns and procedures and their filing after the Client approves them in the application; payroll calculation and the preparation of Social Security files; invoicing, including sending invoicing records to the Spanish Tax Agency through the VERI*FACTU system when it is active for the Client; the AI agent through web chat, WhatsApp, Telegram or email; support; and the security of the service.
The processing will begin when the Client provides data or gives instructions to obtain it through a function of the service. It will last while the service is provided and, afterwards, only during the return, deletion or legal retention operations provided for in this Agreement.
Suspension of the service for non-payment does not terminate the Agreement. During it, the obligations of security, confidentiality, assistance and management of what happens to the data remain in force.
3. The Client’s instructions and obligations
Documented instructions are this Agreement, its annexes, the actions of the Client’s authorized users within the contracted service, including their approvals in the application and their requests to the agent, and the written requests sent through an email to legal@melso.ai sent from the address of an owner of the Client’s account. An instruction that exceeds the subject matter of the Agreement requires prior written agreement; asking for it in a message to the agent is not enough.
The Client must:
- Ensure the lawfulness of the processing, the legal bases and the information to data subjects that are its responsibility, including its customers, suppliers, employees, partners and directors.
- Provide only data that is adequate and necessary for the service and keep it accurate.
- Hold the authorizations needed to use the digital certificates, documents, bank accounts and apps it connects to the service.
- Manage its team’s accounts and permissions and report any improper access without delay.
- Decide what happens to the data at the end and keep the information the law requires it to retain.
- Assess the risks and, where appropriate, carry out the impact assessment and the prior consultation, with Melso’s assistance.
The Client may require compliance with the Agreement, receive information about the processing, object to changes of sub-processors under section 8, audit it and order the return or deletion of the data.
4. Melso’s obligations and use of AI
Melso will process the data only on the Client’s documented instructions, including with regard to international transfers. If Union or Member State law to which Melso is subject requires other processing, it will inform the Client before carrying it out, unless that law prohibits this on important grounds of public interest.
If it considers that an instruction infringes the GDPR or other Union or Member State data protection provisions, Melso will report it immediately. It will not carry out the affected part while the instruction is clarified or corrected, and will maintain the measures needed to protect the data.
Melso will not sell the data or use it for advertising or other purposes of its own. Nor will it use it, or authorize its use, to train general or shared AI models, and it does not authorize any sub-processor to do so. A licence over content or a general policy does not change this prohibition.
The data sent to AI models and their execution environments will be limited to what the task requires. Melso will apply measures to prevent certificates, passwords or other secrets from being needlessly included in the messages sent to providers. The providers that receive data must be covered by section 8 and Annex III. The AI usage records Melso keeps are subject to Annex V.
AI assists the Client and Melso’s team. This Agreement does not authorize decisions based solely on automated processing that produce legal effects concerning data subjects or similarly significantly affect them. Returns and procedures are filed only after the Client approves them in the application, and communications to authorities or other recipients require sufficient instructions and authorization.
5. Authorized personnel and confidentiality
Melso will limit access to those who need it to provide the service or carry out authorized support. It will ensure that they are bound by confidentiality commitments or an equivalent legal obligation and that they know the instructions and measures that apply to their role.
Confidentiality obligations survive the end of the relationship. Melso will maintain procedures for granting, changing and withdrawing permissions and will control privileged access in accordance with Annex II.
6. Security
Melso will apply technical and organizational measures appropriate to the risks, in accordance with Article 32 GDPR. It will take into account the nature of tax, accounting and employment documents, bank and payroll data, digital certificates and credentials.
The measures are described in Annex II. They cover confidentiality, integrity, availability and resilience, recovery from incidents and regular evaluation of their effectiveness. Melso will keep evidence of their application and will correct the deficiencies detected.
The measures may evolve without reducing the committed level of protection. A change that materially affects the risk will be communicated to the Client with enough information to assess it.
7.1. Data subjects’ rights
If it receives a request concerning data processed on the Client’s behalf, Melso will forward it without undue delay to the authorized contact and will not respond on the merits unless instructed to or legally required. It will help to locate, consult, rectify, restrict, export or delete the necessary information, depending on the nature of the processing and the means available.
Contact for forwarding and assistance: the email of the owners of the Client’s account. Melso will immediately report any impediment that may delay the response.
7.2. Personal data breaches
Melso will notify the Client, without undue delay after becoming aware of it, of any breach affecting the data of the Agreement. The notification will not be conditional on completing the investigation or on Melso assessing a high risk.
Notification channel to the Client and urgent alternative: the email of the owners of the Client’s account and, as an urgent alternative, the telephone number the Client gives Melso. Melso’s incident contact: privacy@melso.ai.
The notice will include, as soon as they are known:
- The nature of the incident, the data affected and the categories and approximate number of data subjects and records.
- Relevant dates, including when Melso became aware of it.
- A contact for further information.
- The likely consequences, the measures taken and the measures proposed to contain and remedy the breach.
Missing information will be provided in phases without undue delay. Melso will keep evidence of the incident, cooperate in its investigation and provide the Client with the necessary documentation.
It is for the Client, as controller, to decide on and make the notifications to the supervisory authority and, where appropriate, to data subjects. The 72-hour period of Article 33.1 GDPR refers to the controller’s notification to the authority, where required.
7.3. Other assistance obligations
Melso will help the Client comply with Articles 32 to 36 GDPR, taking into account the nature of the processing and the information available to it. It will provide information to assess risks, document impact assessments, respond to prior consultations and cooperate with the authorities.
It will keep the records of processing activities that are its responsibility as processor. Legally required assistance will not be refused because of a debt, nor made conditional on accepting an additional service. Extraordinary actions the Client requests beyond the required assistance will be quoted in advance and will not be carried out without its acceptance.
8. Sub-processors
The Client grants general written authorization to engage the sub-processors identified in Annex III, within the role and scope stated there.
Before adding or replacing a sub-processor, Melso will inform the owners of the Client’s account by email of its entity, service, data, location and transfer safeguards. The notice will be given with a lead time of at least 30 days and will allow a reasoned objection on data protection grounds during the 15 days following the notice. The new processing will not begin before that period ends and the objections that prevent its lawful use are resolved.
If there is an objection, the parties will consider an alternative that maintains the safeguards. If that is not possible, the Client may terminate the affected service without penalty, with the return or deletion of the data under section 11.
Melso will check the sub-processor’s guarantees and conclude a contract with it that imposes the same data protection obligations as this Agreement, including instructions, confidentiality, security, assistance, incidents, audit and what finally happens to the data. Further chains must respect the same conditions.
Melso will remain fully liable to the Client for the performance of its sub-processors’ obligations and will provide, on request, sufficient contractual evidence to check this, with only the redactions strictly necessary to protect other parties’ information.
9. International transfers
Melso, Inc. is established in the United States and provides the service from there, so its processing involves an international transfer of the Client’s data. The locations of each processing operation are set out in Annexes I and III.
Melso will not make transfers outside the European Economic Area other than those provided for in this Agreement without the Client’s documented instructions and without complying with Chapter V GDPR. The derogations of Article 49 GDPR will not be used for regular flows.
Melso’s onward transfers to its sub-processors rely, as Annex III states for each one, on Implementing Decision (EU) 2023/1795 on the EU-U.S. Data Privacy Framework, when the sub-processor holds an active certification in the official list (dataprivacyframework.gov), or on the standard contractual clauses of Implementing Decision (EU) 2021/914, Module 3 (processor to processor), concluded between Melso and the sub-processor.
Melso will give the Client, on request, a copy of the applicable safeguards and report any circumstance that prevents compliance with them, such as a sub-processor losing its certification. It will suspend the affected flow until valid safeguards exist. A request from a third-country authority does not, by itself, constitute a lawful instruction from the Client or a sufficient basis for disclosing the data; Melso will act in accordance with Clause 15 of the standard clauses.
9.1. Standard contractual clauses
For the transfer from the Client to Melso, Inc., the parties incorporate into this Agreement, by reference, the standard contractual clauses approved by Commission Implementing Decision (EU) 2021/914 of 4 June 2021, Module Two (transfer controller to processor), in their official version published in the Official Journal of the European Union (OJ L 199 of 7.6.2021, p. 31) (the “standard clauses”). By concluding this Agreement, the Client enters into them as data exporter and Melso, Inc. as data importer.
Options of the standard clauses: Clause 7 (docking clause) is not included; in Clause 9(a), Option 2 applies, general written authorisation, with the notice and objection period of section 8; the option in Clause 11(a) (independent dispute resolution body) is not included; in Clause 17, Option 1 applies, with Spanish law, and in Clause 18(b), the courts of Spain.
Annex I.A of the standard clauses (parties). Exporter: the Client, with the identification and contact details of its account; its activity is that of its own business or profession and it acts as controller. Importer: Melso, Inc., with the details of section 1 and the contact privacy@melso.ai; its activity is the gestoría service with an AI agent of section 2 and it acts as processor. Signing or accepting this Agreement counts as the parties’ signature of that annex.
Annexes I, II and III of this Agreement complete, respectively, Annexes I.B (description of the transfer), II (technical and organisational measures) and III (list of sub-processors) of the standard clauses.
Annex I.C of the standard clauses (competent supervisory authority): the Spanish Data Protection Agency (Agencia Española de Protección de Datos), in accordance with Clause 13.
Assessment of the laws and practices of the country of destination (Clause 14) and supplementary measures: Melso documented it on 20 November 2026. The data are accounting, tax and employment data of self-employed people and companies; they travel and are stored encrypted in Google Cloud. The safeguards of Executive Order 14086, which limits signals intelligence to what is necessary and proportionate, and redress before the Data Protection Review Court apply to every transfer to the United States, whatever its transfer tool, as the Commission assessed in Implementing Decision (EU) 2023/1795, which the General Court upheld on 3 September 2025 (Case T-553/23; under appeal, Case C-703/25 P). At that date Melso had received no request for access from public authorities and, should it receive one, will act under Clause 15. With these safeguards and the measures of Annex II, the assessment concludes that the laws and practices of the United States do not prevent Melso from complying with the standard contractual clauses. Melso will review it every year and whenever those laws, that decision or its own practices change, and will provide it to the Client and to the supervisory authority on request.
In the event of a contradiction, the standard clauses prevail over this Agreement, and this Agreement over the Terms of Service in everything relating to data protection.
10. Information and audits
Melso will make available to the Client the information needed to demonstrate compliance with this Agreement and the standard clauses. It will allow for and contribute to audits, including inspections, conducted by the Client or by an auditor it mandates who is bound by confidentiality.
The parties will coordinate their scope, secure access and proportionate notice. They may use existing reports when they are sufficient, without replacing the right to inspect when necessary. Third parties’ data and the continuity of the service will be protected, without turning those precautions into a ban on auditing.
Urgent audits because of a breach, well-founded signs of non-compliance or a request from an authority will not be subject to a wait that defeats their purpose. Melso will facilitate the corrective actions and the follow-up of their results.
Ordinary notice and allocation of costs: with reasonable notice; each party bears its own costs, unless the audit shows a breach by Melso, which will then bear its reasonable costs.
11. End of the processing
At the end of the service, the Client will choose in writing between receiving the data, having it delivered to the processor it designates, such as a new gestoría, or having it deleted. Melso will ask for that instruction before carrying out an irreversible deletion.
The Client can download at any time from the application its books, its documents and a recovery file with its accounting and tax records; anything that download does not include, such as the conversations with the agent, will be delivered to it in a structured format if it asks through the channel of section 3.
The return will include all the personal data of the Agreement, through a secure channel. Afterwards, Melso will delete the copies it keeps, unless a legal obligation applies, within the periods of Annex V.
If Union or Member State law requires Melso to keep certain data, Melso will identify the law, the data set affected, the period and the access restriction, and will not use the data for any other purpose.
Where appropriate under Article 33.4 of Spanish Organic Law 3/2018 on the Protection of Personal Data and the Guarantee of Digital Rights (“LOPDGDD”), Melso may keep duly blocked data for the period during which liabilities may arise from its relationship with the Client, without it remaining available for the ordinary service, product improvement or commercial uses.
Where a legal provision requires the data to be kept, they will not be destroyed even if the Client asks for their deletion: they will be returned to the Client, which will ensure they are kept for as long as that obligation lasts (Article 33.3 LOPDGDD).
Melso will require the same outcome from its sub-processors and confirm the execution in writing, stating any exceptional retention and its basis. Backups will be kept out of ordinary use until they are replaced, in accordance with Annex V.
12. Liability, governing law and precedence
Each party will fulfil the obligations that correspond to its actual role. Melso’s liability for its sub-processors and the regime of Article 82 GDPR remain, including full compensation to the data subject where appropriate and the right of recourse between those liable for the damage.
No limit agreed between the parties will reduce the rights of data subjects or the powers of the authorities. This Agreement and its standard clauses are governed by Spanish law and their disputes belong to the courts of Spain; the law and courts set by the Terms of Service do not apply to them. This Agreement will be interpreted in accordance with the GDPR and the LOPDGDD.
Annex I. Description of the processing (Annex I.B of the standard clauses)
- Subject matter and purposes: processing of the data of the Client and of the people who appear in its documentation to provide it with the service of section 2.
- Data subjects: the Client when it is a natural person; the Client’s partners, directors, representatives and users; its customers, suppliers and other people who appear in its invoices, statements and documents; its employees, including the director when paid through payroll; and the people who write to Melso on the Client’s behalf.
- Identification and contact: names, NIF, NIE or other identifiers, addresses, telephone numbers and email addresses. A company’s data is included insofar as it makes it possible to identify natural persons.
- Financial and tax data: invoices issued and received, receipts, income and expenses, books, statements, IBAN and bank transactions, returns, notifications and filing receipts.
- Employment and payroll data: contracts, contribution group, salaries, Social Security number, withholdings, registrations and terminations, and other data that payslips and Social Security files require.
- Communications: messages, voice notes and files exchanged with the agent through web chat, WhatsApp, Telegram or email, and the instructions and approvals given in the application.
- Credentials: the digital certificates and passwords the Client keeps in the application and the access authorizations to its bank accounts and connected apps, with reinforced measures.
- Operations: collection through provision, import or authorized connection, recording, organization, storage, consultation, extraction and classification with AI, calculation, modification according to instructions, export, disclosure to the recipients the Client authorizes, restriction and deletion.
- Recipients on the Client’s instructions: the Spanish Tax Agency, Social Security, registries, notaries and other authorities before which the Client entrusts a return or a procedure, which are not Melso’s sub-processors (Annex IV).
- Frequency and duration: continuous transfer while the service is provided, according to the Client’s actions, and later retention only in accordance with Annex V.
- Location: United States, where the application, the database and its backups are hosted (Google Cloud, region us-central1, with backups in its United States multi-region); the sub-processors in Annex III process data in the places stated there.
Special categories of data and criminal data: only those that the payroll and the Client’s employment and Social Security obligations require, such as an employee’s temporary incapacity or disability; Melso does not ask for other data under Articles 9 and 10 GDPR, and any that appear in documents the Client provides are processed only within the record they belong to, with the measures of Annex II.
If data of that nature that is not necessary appears accidentally, Melso will limit its exposure and ask for instructions for its removal or lawful processing.
Annex II. Technical and organisational measures (Annex II of the standard clauses)
Melso applies the following technical and organizational measures:
- Access control by membership of each company and by role, with individual accounts.
- Logical separation of each company’s data.
- Encryption of external connections and of stored data; digital certificates are kept sealed with keys protected by a master key held in Secret Manager.
- Access by Melso’s staff only when needed to provide the service, under a duty of confidentiality.
- Limits on the AI agent, with tools restricted by type of company and role; returns and procedures are filed only after the Client approves them in the application.
- Logging of the service’s operations, kept for 30 days, and an audit log of the queries and changes Melso’s team makes from its administration panel.
- Automatic daily database backups, kept for 14 days, with point-in-time recovery over the last 7 days.
- Management of updates and changes.
- Recording and handling of security incidents, with notice to the Client under section 7.2.
- Deletion of the data at the end, under section 11 and Annex V.
- Sub-processors: selected with security guarantees and bound by a contract with the obligations of section 8, which includes assisting the Client with data subjects’ rights and breaches.
Annex III. Sub-processors (Annex III of the standard clauses)
Melso engages the following sub-processors. For each one, the entity, service, data, location and transfer safeguard are stated:
- Google LLC · hosting of the application, database, file storage, backups, logs and traces (Google Cloud), transcription of voice notes and dictation (Vertex AI), address suggestions (Google Maps Platform) and the Melso team’s email (Google Workspace) · data: all of Annex I · United States, region us-central1; Vertex AI is called on its global endpoint, which may process the request in any Google Cloud location · EU-U.S. Data Privacy Framework (active certification).
- Amazon Web Services, Inc. · AI models for the agent and for reading documents (Amazon Bedrock: Anthropic’s Claude and OpenAI’s GPT) · data: the messages, documents and data each task needs · United States, region us-east-1, with Bedrock’s global inference profile, which may process the request in any AWS commercial Region · EU-U.S. Data Privacy Framework (active certification of Amazon.com, Inc., which covers Amazon Web Services, Inc.).
- Supermemory (San Francisco, United States) · the agent’s memory: it keeps durable facts from conversations, such as the name, role, preferences and company context · data: the person’s messages with the agent · United States: it stores the data there by default, in PlanetScale, TurboPuffer and Cloudflare’s network · standard contractual clauses, Module 3.
- FoundryLabs, Inc. (E2B) · isolated environments where the agent runs code and works with files · data: the files and data the agent copies for each task · United States, on Google Cloud and AWS, according to E2B · standard contractual clauses, Module 3.
- Exa Labs Inc. · the agent’s web search · data: the queries the agent writes, which may include names of third parties, such as a supplier or customer of the Client · United States, the entity’s seat; its policy does not say where it processes data · standard contractual clauses, Module 3.
- Sampark Inc (Composio) · connection to the apps the Client authorizes, such as its Gmail, Google Workspace or Outlook mail, to read invoices and send emails from its account · data: the emails, attachments and access permissions of the connected account · United States: it hosts the data on AWS, in Northern Virginia (us-east-1) · standard contractual clauses, Module 3.
- Typesafe AI, Inc. (Jev) · decision model that reads a self-employed person’s latest messages to tell whether they file VAT monthly or quarterly · data: up to 6 recent messages from the person · United States · standard contractual clauses, Module 3.
- Plus Five Five, Inc. (Resend) · transactional email and the agent’s email channel (agent@melso.ai) · data: the addresses and content of the emails · United States · EU-U.S. Data Privacy Framework (active certification, with its renewal under review).
- WhatsApp Ireland Limited (WhatsApp) · messaging with the agent: if the Client writes to Melso on WhatsApp, its messages reach Melso’s WhatsApp Business account, which Melso connects through a WhatsApp Web client hosted on its Google Cloud infrastructure · data: the messages, voice notes, files and phone numbers of those conversations · Ireland, within the European Economic Area · no transfer to a third country; its sub-processors, other Meta companies, may process them in the United States under the WhatsApp Business Data Transfer Addendum.
- Enable Banking Oy · read-only connection to the bank accounts the Client authorizes · data: account holders, IBAN, balances and transactions · Finland, within the European Economic Area · no transfer to a third country.
- Granola, Inc. · notes and transcripts of the Melso team’s meetings, including those it holds with the Client · data: what is said in those meetings · United States, on Amazon Web Services · standard contractual clauses, Module 3.
- Functional Software, Inc. (Sentry) · diagnosis of application errors · data: technical error traces, which may contain fragments of service data · United States · EU-U.S. Data Privacy Framework (active certification).
- PostHog, Inc. · scrubbed operational logs and product usage analytics · data: identifiers of the account’s users, including their email and name at sign-up, usage events and bounded technical messages, with no documents or conversations · United States · EU-U.S. Data Privacy Framework (active certification).
- Microsoft Corporation (Microsoft Clarity) · recording of how the application is used, with all text and fields masked, with no tax data of the Client · data: clicks, scrolling and page layout, with a pseudonymous user identifier · United States, the entity’s seat · EU-U.S. Data Privacy Framework (active certification).
- Straitly · gateway to the AI models of Melso Agents, Melso’s environment where the agente gestor that carries out procedures at the electronic offices with the Client’s certificate and the triage of support incidents run; the rest of that environment uses sub-processors on this list: Google Cloud (us-central1), E2B, Composio, Resend and PostHog; according to Straitly, it does not keep the requests · data: those of the procedure or incident the agent processes · standard contractual clauses, Module 3.
- Álvaro José Tresserras Torre, tax technician no. 1520 of the Associació Professional de Tècnics Tributaris de Catalunya i Balears (APttCB), an external professional · preparation and filing of the returns and procedures the Client approves or entrusts · data: those of each return or procedure · Spain, within the European Economic Area · no transfer to a third country.
- Anthropic (Claude Code, Claude and Grizzly, the team’s agent, which runs on Claude), OpenAI (Codex) and Anysphere, Inc. (Cursor) · AI tools with which Melso’s team consults, from its administration panel, the data it needs for the service and support · data: what each query reads · United States · standard contractual clauses, Module 3.
Anthropic’s and OpenAI’s models are used through Amazon Bedrock: according to AWS, their makers have no access to the prompts or responses, and they are not Melso’s sub-processors.
Each sub-processor’s certification under the Data Privacy Framework was checked in the official list (dataprivacyframework.gov) on November 19, 2026; Melso will check that it remains active.
Melso will inform the Client of any change to this list under section 8.
Annex IV. Recipients that are not sub-processors
They do not process the data on Melso’s behalf in the service of this Agreement. They are listed so that the Client knows every flow:
- Telegram Messenger Inc. · if the Client writes to the agent on Telegram, Telegram processes the messages as an independent controller, under its privacy policy, which places the data of users in the European Economic Area in the Netherlands.
- Stripe, LLC · collection of the Client’s subscription to Melso, for which Melso is the controller · United States · EU-U.S. Data Privacy Framework (active certification).
- Didit Identity, Inc. (Didit) · verification of the partners’ identity when Melso incorporates a company on the Client’s behalf, an obligation of Melso’s own as an obliged entity under Law 10/2010, for which Melso is the controller · main infrastructure in the European Economic Area, according to Didit.
- Cal.com, Inc. · booking of calls with the Melso team, with the name, email and telephone number of the person booking, for which Melso is the controller · United States · EU-U.S. Data Privacy Framework (active certification).
- Trustpilot A/S · invitation to review Melso after the first payment, with the person’s name and email, on Melso’s behalf as controller · Denmark, within the European Economic Area.
- Advertising measurement · Google (Google Ads and Google Analytics), Meta Platforms (pixel and Conversions API) and OpenAI (ChatGPT Ads conversions) receive, according to the person’s cookie and consent choices, their sign-up and payment at Melso, never the Client’s tax data; Melso is the controller of this measurement, which its privacy policy governs.
- Authorities, registries and notaries: they receive the returns, invoicing records and procedures the Client approves or entrusts, and process them on their own account.
The apps and accounts the Client connects on its own, such as its bank, its accounting software, its email or an external AI assistant, process the data under their own relationship with the Client.
Annex V. Return, retention and deletion
- Tax, accounting and employment records, documents and invoices: during the service; at the end, they are returned, delivered to the processor the Client designates or deleted, as it chooses, unless a legal retention obligation applies.
- Messages with the agent, files and derived data: the same outcome as the records.
- Digital certificates and credentials: deleted with the company.
- The agent’s execution environments: for a limited period, and deleted at the end under section 11.
- AI diagnostics: for a limited period.
- Backups: used only to recover the service, and the database ones are replaced after 14 days.
- Identity documents of the partners of a company that Melso incorporates: ten years, as Melso’s own obligation under Article 25 of Law 10/2010.
- Melso’s own billing: while the relationship lasts and, afterwards, six years.
- Data blocked because of liabilities: only where legally appropriate, blocked and without ordinary use for the limitation period, and destroyed when it ends.
Melso will document the exceptions to a deletion request and confirm to the Client what finally happened to the data.
Contact
Questions about this Agreement can be sent to privacy@melso.ai.
Melso, Inc.
Website: https://melso.ai
Related: Terms of Service · Privacy Policy