Data processing agreement

Last updated: 29 October 2026.

What this agreement is

When you use Evy for your business, your assistant handles personal data of your customers, suppliers and contacts. That data is yours and you decide about it.

Evy keeps and processes it only to provide the service, on your behalf.

The clauses below govern that: the European Commission's standard contractual clauses (Commission Implementing Decision (EU) 2021/915). They are part of the Terms and Conditions you accept when you sign up.

In them you are the controller and Evy is the processor. The clauses appear exactly as the Commission published them. Where they offer a choice, the General Data Protection Regulation (Regulation (EU) 2016/679) applies and, for changes of sub-processors, a general authorisation with 30 days' notice. The optional Clause 5 is not used. What is specific to Evy is in Annexes I to IV, at the end.

Section I. Clause 1. Purpose and scope

(a) The purpose of these Standard Contractual Clauses (the Clauses) is to ensure compliance with Article 28(3) and (4) of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation).

(b) The controllers and processors listed in Annex I have agreed to these Clauses in order to ensure compliance with Article 28(3) and (4) of Regulation (EU) 2016/679 and/or Article 29(3) and (4) of Regulation (EU) 2018/1725.

(d) Annexes I to IV are an integral part of the Clauses.

(e) These Clauses are without prejudice to obligations to which the controller is subject by virtue of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.

(f) These Clauses do not by themselves ensure compliance with obligations related to international transfers in accordance with Chapter V of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.

Clause 2. Invariability of the Clauses

(a) The Parties undertake not to modify the Clauses, except for adding information to the Annexes or updating information in them.

(b) This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a broader contract, or from adding other clauses or additional safeguards provided that they do not directly or indirectly contradict the Clauses or detract from the fundamental rights or freedoms of data subjects.

Clause 3. Interpretation

(a) Where these Clauses use the terms defined in Regulation (EU) 2016/679 or Regulation (EU) 2018/1725 respectively, those terms shall have the same meaning as in that Regulation.

(b) These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679 or Regulation (EU) 2018/1725 respectively.

(c) These Clauses shall not be interpreted in a way that runs counter to the rights and obligations provided for in Regulation (EU) 2016/679 / Regulation (EU) 2018/1725 or in a way that prejudices the fundamental rights or freedoms of the data subjects.

Clause 4. Hierarchy

In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties existing at the time when these Clauses are agreed or entered into thereafter, these Clauses shall prevail.

Section II. Obligations of the Parties. Clause 6. Description of processing(s)

The details of the processing operations, in particular the categories of personal data and the purposes of processing for which the personal data is processed on behalf of the controller, are specified in Annex II.

Clause 7. Obligations of the Parties. 7.1. Instructions

(a) The processor shall process personal data only on documented instructions from the controller, unless required to do so by Union or Member State law to which the processor is subject. In this case, the processor shall inform the controller of that legal requirement before processing, unless the law prohibits this on important grounds of public interest. Subsequent instructions may also be given by the controller throughout the duration of the processing of personal data. These instructions shall always be documented.

(b) The processor shall immediately inform the controller if, in the processor’s opinion, instructions given by the controller infringe Regulation (EU) 2016/679 / Regulation (EU) 2018/1725 or the applicable Union or Member State data protection provisions.

7.2. Purpose limitation

The processor shall process the personal data only for the specific purpose(s) of the processing, as set out in Annex II, unless it receives further instructions from the controller.

7.3. Duration of the processing of personal data

Processing by the processor shall only take place for the duration specified in Annex II.

7.4. Security of processing

(a) The processor shall at least implement the technical and organisational measures specified in Annex III to ensure the security of the personal data. This includes protecting the data against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to the data (personal data breach). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purposes of processing and the risks involved for the data subjects.

(b) The processor shall grant access to the personal data undergoing processing to members of its personnel only to the extent strictly necessary for implementing, managing and monitoring of the contract. The processor shall ensure that persons authorised to process the personal data received have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.

7.5. Sensitive data

If the processing involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (“sensitive data”), the processor shall apply specific restrictions and/or additional safeguards.

7.6. Documentation and compliance

(a) The Parties shall be able to demonstrate compliance with these Clauses.

(b) The processor shall deal promptly and adequately with inquiries from the controller about the processing of data in accordance with these Clauses.

(c) The processor shall make available to the controller all information necessary to demonstrate compliance with the obligations that are set out in these Clauses and stem directly from Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725. At the controller’s request, the processor shall also permit and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or an audit, the controller may take into account relevant certifications held by the processor.

(d) The controller may choose to conduct the audit by itself or mandate an independent auditor. Audits may also include inspections at the premises or physical facilities of the processor and shall, where appropriate, be carried out with reasonable notice.

(e) The Parties shall make the information referred to in this Clause, including the results of any audits, available to the competent supervisory authority/ies on request.

7.7. Use of sub-processors

(a) The processor has the controller’s general authorisation for the engagement of sub-processors from an agreed list. The processor shall specifically inform in writing the controller of any intended changes of that list through the addition or replacement of sub-processors at least 30 days in advance, thereby giving the controller sufficient time to be able to object to such changes prior to the engagement of the concerned sub-processor(s). The processor shall provide the controller with the information necessary to enable the controller to exercise the right to object.

(b) Where the processor engages a sub-processor for carrying out specific processing activities (on behalf of the controller), it shall do so by way of a contract which imposes on the sub-processor, in substance, the same data protection obligations as the ones imposed on the data processor in accordance with these Clauses. The processor shall ensure that the sub-processor complies with the obligations to which the processor is subject pursuant to these Clauses and to Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.

(c) At the controller’s request, the processor shall provide a copy of such a sub-processor agreement and any subsequent amendments to the controller. To the extent necessary to protect business secret or other confidential information, including personal data, the processor may redact the text of the agreement prior to sharing the copy.

(d) The processor shall remain fully responsible to the controller for the performance of the sub-processor’s obligations in accordance with its contract with the processor. The processor shall notify the controller of any failure by the sub-processor to fulfil its contractual obligations.

(e) The processor shall agree a third party beneficiary clause with the sub-processor whereby - in the event the processor has factually disappeared, ceased to exist in law or has become insolvent - the controller shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.

7.8. International transfers

(a) Any transfer of data to a third country or an international organisation by the processor shall be done only on the basis of documented instructions from the controller or in order to fulfil a specific requirement under Union or Member State law to which the processor is subject and shall take place in compliance with Chapter V of Regulation (EU) 2016/679 or Regulation (EU) 2018/1725.

(b) The controller agrees that where the processor engages a sub-processor in accordance with Clause 7.7. for carrying out specific processing activities (on behalf of the controller) and those processing activities involve a transfer of personal data within the meaning of Chapter V of Regulation (EU) 2016/679, the processor and the sub-processor can ensure compliance with Chapter V of Regulation (EU) 2016/679 by using standard contractual clauses adopted by the Commission in accordance with of Article 46(2) of Regulation (EU) 2016/679, provided the conditions for the use of those standard contractual clauses are met.

Clause 8. Assistance to the controller

(a) The processor shall promptly notify the controller of any request it has received from the data subject. It shall not respond to the request itself, unless authorised to do so by the controller.

(b) The processor shall assist the controller in fulfilling its obligations to respond to data subjects’ requests to exercise their rights, taking into account the nature of the processing. In fulfilling its obligations in accordance with (a) and (b), the processor shall comply with the controller’s instructions

(c) In addition to the processor’s obligation to assist the controller pursuant to Clause 8(b), the processor shall furthermore assist the controller in ensuring compliance with the following obligations, taking into account the nature of the data processing and the information available to the processor:

(1) the obligation to carry out an assessment of the impact of the envisaged processing operations on the protection of personal data (a ‘data protection impact assessment’) where a type of processing is likely to result in a high risk to the rights and freedoms of natural persons;

(2) the obligation to consult the competent supervisory authority/ies prior to processing where a data protection impact assessment indicates that the processing would result in a high risk in the absence of measures taken by the controller to mitigate the risk;

(3) the obligation to ensure that personal data is accurate and up to date, by informing the controller without delay if the processor becomes aware that the personal data it is processing is inaccurate or has become outdated;

(4) the obligations in Article 32 of Regulation (EU) 2016/679.

(d) The Parties shall set out in Annex III the appropriate technical and organisational measures by which the processor is required to assist the controller in the application of this Clause as well as the scope and the extent of the assistance required.

Clause 9. Notification of personal data breach

In the event of a personal data breach, the processor shall cooperate with and assist the controller for the controller to comply with its obligations under Articles 33 and 34 of Regulation (EU) 2016/679 or under Articles 34 and 35 of Regulation (EU) 2018/1725, where applicable, taking into account the nature of processing and the information available to the processor.

9.1 Data breach concerning data processed by the controller

In the event of a personal data breach concerning data processed by the controller, the processor shall assist the controller:

(a) in notifying the personal data breach to the competent supervisory authority/ies, without undue delay after the controller has become aware of it, where relevant/(unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons);

(b) in obtaining the following information which, pursuant to Article 33(3) of Regulation (EU) 2016/679, shall be stated in the controller’s notification, and must at least include:

(1) the nature of the personal data including where possible, the categories and approximate number of data subjects concerned and the categories and approximate number of personal data records concerned;

(2) the likely consequences of the personal data breach;

(3) the measures taken or proposed to be taken by the controller to address the personal data breach, including, where appropriate, measures to mitigate its possible adverse effects.

Where, and insofar as, it is not possible to provide all this information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.

(c) in complying, pursuant to Article 34 of Regulation (EU) 2016/679, with the obligation to communicate without undue delay the personal data breach to the data subject, when the personal data breach is likely to result in a high risk to the rights and freedoms of natural persons.

9.2 Data breach concerning data processed by the processor

In the event of a personal data breach concerning data processed by the processor, the processor shall notify the controller without undue delay after the processor having become aware of the breach. Such notification shall contain, at least:

(a) a description of the nature of the breach (including, where possible, the categories and approximate number of data subjects and data records concerned);

(b) the details of a contact point where more information concerning the personal data breach can be obtained;

(c) its likely consequences and the measures taken or proposed to be taken to address the breach, including to mitigate its possible adverse effects.

The Parties shall set out in Annex III all other elements to be provided by the processor when assisting the controller in the compliance with the controller’s obligations under Articles 33 and 34 of Regulation (EU) 2016/679.

Section III. Final provisions. Clause 10. Non-compliance with the Clauses and termination

(a) Without prejudice to any provisions of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725, in the event that the processor is in breach of its obligations under these Clauses, the controller may instruct the processor to suspend the processing of personal data until the latter complies with these Clauses or the contract is terminated. The processor shall promptly inform the controller in case it is unable to comply with these Clauses, for whatever reason.

(b) The controller shall be entitled to terminate the contract insofar as it concerns processing of personal data in accordance with these Clauses if:

(1) the processing of personal data by the processor has been suspended by the controller pursuant to point (a) and if compliance with these Clauses is not restored within a reasonable time and in any event within one month following suspension;

(2) the processor is in substantial or persistent breach of these Clauses or its obligations under Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725;

(3) the processor fails to comply with a binding decision of a competent court or the competent supervisory authority/ies regarding its obligations pursuant to these Clauses or to Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.

(c) The processor shall be entitled to terminate the contract insofar as it concerns processing of personal data under these Clauses where, after having informed the controller that its instructions infringe applicable legal requirements in accordance with Clause 7.1 (b), the controller insists on compliance with the instructions.

(d) Following termination of the contract, the processor shall, at the choice of the controller, delete all personal data processed on behalf of the controller and certify to the controller that it has done so, or, return all the personal data to the controller and delete existing copies unless Union or Member State law requires storage of the personal data. Until the data is deleted or returned, the processor shall continue to ensure compliance with these Clauses.

Annex I. List of parties

Controller: you, the customer who subscribes to Evy and accepts the Terms and Conditions when signing up.

Controller's name, address and contact details: those in your account and in your billing details.

Controller's signature and accession date: the date on which, before paying, you tick that you accept the Terms and Conditions. We keep it, with the version you accepted, with your subscription at our payment provider.

Processor: Walter Martín Lopes, who provides the Evy service, tax ID (NIF) 45134320V.

Processor's address: Calle Badajoz 2, 3º Derecha, 10400 Jaraíz de la Vera (Cáceres), Spain.

Processor's contact person: Walter Martín Lopes, owner, at contacto@evyagent.com.

No data protection officer has been appointed.

Processor's signature and accession date: Evy is bound by this agreement towards you from the same date on which you accept it.

Annex II. Categories of data subjects whose personal data is processed

Your customers and your suppliers: those who appear in your invoices, quotes, delivery notes, collections and payments.

The people who write to you or talk with you through the channels you connect to your assistant (email, WhatsApp, Telegram and the like), including your customers if you serve them through WhatsApp Business.

The people who appear in your calendar, your meetings, your tasks and the files you give your assistant.

Annex II. Categories of personal data processed

Identification and contact data: name, email, phone number and address, as they appear in your documents, your messages and your calendar.

Your invoicing data: issued and received invoices, pending and overdue amounts, payment reminder drafts, quotes, delivery notes and products.

Content of communications: your conversations with your assistant and the ones it holds through your channels, the photos and files you receive through your channels, the emails it reads, and voice notes and their transcripts.

Calendar and work: calendar appointments, meeting notes and transcripts, tasks and reminders.

What you give your assistant: the files in "My files" (Mis archivos) and what it keeps in its memory.

The credentials and data of the apps you connect to your assistant, such as your invoicing program, your email or your calendar.

Annex II. Sensitive data processed (if applicable) and applied restrictions or safeguards

Evy is not designed to process sensitive data: the data in Clause 7.5, such as health, beliefs, ethnic origin, sex life or criminal convictions. Do not ask your assistant to collect or keep it.

If it appears in a conversation anyway, for example because a customer tells you something about their health on WhatsApp, it is processed like the rest of your data: it is kept on your server and, when it is part of the conversation, sent to the AI model to answer. The safeguards are the same as for everything else, described in Annex III: the encrypted backups only you can open and the instruction to OpenRouter not to send queries to providers that collect the data.

Annex II. Nature of the processing

Keeping your data on a private server, for you alone, in the European Union.

Reading and working with it: your assistant reads it to do what you ask and writes on your server what it prepares, such as payment reminder drafts or the tasks from a meeting when you say yes.

Talking on your behalf through the channels you connect, such as WhatsApp or Telegram.

Sending the AI model what it needs to answer: the conversation, the photos you receive so that it can see them, whatever you ask it to work on and whatever you ask it to generate, such as images or videos.

Transcribing your voice notes, on your own server, unless you choose another transcription service with your own key in the app.

Turning into speech the replies your assistant reads aloud, when you use spoken replies.

Making encrypted backups.

Carrying to your server the files you upload from the panel, and to your browser the ones you download, and relaying the pages your assistant publishes.

Sending Evy short notices of what your assistant does (the type of action, the time and the file name, such as "quote created"), without their content, for the activity log in the panel. Evy also receives the name and the identifier on the channel (depending on the channel, the phone number or the Telegram id) of anyone asking for permission to talk to your assistant, to let you know, and the title, short description and short name of the pages it publishes.

Sending you the service's emails, such as the notice that someone is waiting for your permission to talk to your assistant.

Preparing the download of your data when you ask for it, and deleting everything when the service ends.

Annex II. Purpose(s) for which the personal data is processed on behalf of the controller

Providing you with the Evy service: your assistant working for your business on whatever you ask (keeping your invoicing, preparing your day, looking after your channels) and your data kept safe.

Evy does not use that data for any purpose of its own, does not sell it and does not pass it on.

Annex II. Duration of the processing

For as long as your subscription lasts, subject to what follows.

During the service, your server deletes ended conversations after 90 days without activity, except the ones you pin in the app and unless you turn this off. WhatsApp, Telegram and other channel conversations do not end on their own.

Backups are kept according to your plan: on Compañero, the last 2 monthly copies; on Asistente, the last 2 weekly copies and 2 monthly ones; on Profesional, the last 2 daily copies, 2 weekly and 2 monthly. During the service no copy less than one week old is deleted, so all the copies from the last week are kept.

The activity log in the panel keeps the short notices for 30 days, and incident notices for 180 days. So it can outlast your subscription by at most those days. If you delete your account, it is deleted then. The name and identifier of anyone asking for permission to talk to your assistant are kept like the short notices, for 30 days. The title, short description and short name of the pages your assistant publishes are kept while the pages exist and, at the latest, until you delete your account.

At the end: if you cancel, on the last paid day we delete your server, its data and its backups. If you withdraw within 14 days of your first payment, or if you delete your account, we do it within the following hours. If the subscription ends for non-payment, 10 days later.

Before the deletion, you can download your data from the panel. That download is how we return your data to you.

We only treat the deletion as finished once we have checked that your server, its data disk, its IP address and your stored backups and files no longer exist.

Annex II. Processing by sub-processors: subject matter, nature and duration

The sub-processors are the ones in Annex IV, which says what each one does.

Hetzner keeps your server, your data disk and your backups for as long as the service lasts, and we delete them at the end as set out above.

OpenRouter and the model provider receive the text and images of each query, and whatever you ask to generate, only to answer or generate it.

Supabase keeps files in transit only until they arrive: the ones you upload are deleted as soon as your server collects them; the ones you download, and any left over, are deleted in a daily sweep of those older than one hour. In the central database it keeps the short activity notices for the periods above (30 days, or 180 for incident notices), and the title, short description and short name of published pages while they exist and, at the latest, until you delete your account.

Vercel hosts the panel and its API, through which the activity notices and the panel's requests to your server pass, and relays the pages your assistant publishes, one request at a time, without storing them.

Microsoft receives the text of the replies your assistant reads aloud, when you use spoken replies, only to turn it into speech.

Resend receives each of the service's emails only to send it.

Annex III. Technical and organisational measures including technical and organisational measures to ensure the security of the data

One server per customer: your data lives on a private server used only by your assistant, in a Hetzner data centre in the European Union (Germany or Finland).

Encrypted data disk: your data is stored on a disk encrypted with LUKS. At start-up your server asks Evy for the key, keeps it only in memory and, if it does not arrive, does not open the disk. We manage the key, so our infrastructure can access the data while the server is running.

Backups only you can open: they are encrypted on your server before leaving it, each with its own key, protected by your 12-word recovery phrase. The phrase is created in your browser and never reaches us. If you lose it, nobody can open the backups, not even us.

Complete and protected backups: when each copy is uploaded, the storage checks the checksum of every part, so it is only accepted if it arrives whole. Your server holds no storage credentials: it gets links that expire after 15 minutes and can only access its own copies. Even if someone took over your server, they could not delete the copies from the last week or the first copy of each of the last two months.

Communication with your server: Evy's instructions to your server are authenticated on both sides with certificates (your server's is specific to each customer) and with a signed permission that expires after 60 seconds.

Channel credentials: they travel end-to-end encrypted from your browser to your server. We cannot read them.

Files in transit: the ones you upload or download from the panel go through temporary storage, with links that expire after 5 minutes and without our panel touching their content. The ones you upload are deleted as soon as your server collects them; the ones you download, and any left over, in a daily sweep that removes those older than one hour.

Published pages: their content passes through our systems only while it is transmitted and is not stored. The central system keeps only their title, short description and short name.

Voice notes: they are transcribed on your own server and do not leave it for that, unless you choose another transcription service with your own key in the app.

Connected apps: the program that links your assistant with your apps (Activepieces) runs inside your server, can only be used from the server itself, sends no telemetry and keeps its data on the encrypted disk.

Access to your server: the only way in is SSH with a key, never a password. Repeated attempts are blocked and security updates install themselves. Evy's technical staff only enter your server for maintenance or support, with access keys controlled by Evy, and those entries are logged on the server.

The minimum for Evy: of what your assistant does, Evy only receives short notices (type of action, time and file name), without their content; the name and the identifier on the channel of anyone asking for permission to talk to your assistant, to let you know; and the title, short description and short name of the pages it publishes. The internal support tool that queries the central system only reads. The panel and your server use no third-party analytics or error-tracking tools.

No providers that collect the data: Evy's central system sends your server the instruction that OpenRouter must not send your queries to providers that collect the data, and your server passes it on to OpenRouter in the conversations it holds with Evy's account. In addition, Evy's OpenRouter account does not allow queries to be sent to providers that train on the data, for paid or free models. This also covers the images and videos you ask it to generate.

Limited retention: the deletion periods are the ones in Annex II.

Download and deletion: from the panel you can download your data (your conversations, your memory, your files and your account data). The download is prepared on your server and handed over once; if nobody collects it, it is deleted after a day. You can also delete your account and your server whenever you want.

Annex III. Measures of the sub-processors

Hetzner: keeps your data disk and your backups already encrypted.

OpenRouter: receives each query with the instruction not to send it to providers that collect the data.

Supabase: keeps files in transit with links that expire after 5 minutes; the ones you upload, only until your server collects them, and the others until the daily sweep of those older than one hour.

Vercel: relays published pages without storing them.

Microsoft: receives only the text of the replies that will be read aloud, and only when you use spoken replies.

Resend: receives only what goes in each of the service's emails it sends.

Each sub-processor processes the data according to our instructions and to its own data processing terms.

Annex III. How Evy helps you comply

Data subjects' rights: from the panel you can download your data and delete your account and your server. If someone writes to us to exercise their rights over data we process on your behalf, we pass the request on to you and do not answer it ourselves.

Inquiries, impact assessments and audits: write to contacto@evyagent.com and we will give you the information we have.

Security breaches: if we become aware of a security breach affecting your data, we notify you without undue delay at your account email, with what Clause 9.2 requires: what happened, which data and how many people it affects where known, its likely consequences and what we have done or will do.

Contact point for more information about a security breach: contacto@evyagent.com.

Annex IV. List of sub-processors

This is the agreed list in Clause 7.7(a). If we want to add or replace a sub-processor, we will tell you in writing, at your account email, at least 30 days in advance, so that you can object.

The controller has authorised the use of the following sub-processors:

1. Hetzner Online GmbH. Country: Germany, with data centres in Germany (Nuremberg and Falkenstein) and Finland (Helsinki). What it does: hosts your server and its encrypted data disk, and keeps your encrypted backups in Nuremberg (Germany).

2. OpenRouter. Country: outside the European Economic Area. What it does: receives the text and images of every query your assistant needs to answer, and whatever you ask to generate (such as images or videos), and passes it to the model provider.

3. The AI model providers OpenRouter sends each query to, depending on the model in use. Country: mostly outside the European Economic Area; we cannot guarantee that the query is answered inside the European Union. What they do: receive the text and images of the query and generate the answer, or whatever you ask to generate.

4. Supabase, on Amazon Web Services infrastructure. Where it processes your data: Germany (Frankfurt). What it does: keeps files in transit between the panel and your server, and the central database, which holds your assistant's short activity notices, the name and the identifier on the channel of anyone asking for permission to talk to your assistant, and the title, short description and short name of the pages it publishes.

5. Vercel. Where it processes your data: its functions run in Frankfurt (Germany). What it does: hosts the panel and its API, through which your server's activity notices and the panel's requests to your server pass, and relays, without storing them, the pages your assistant publishes and what is saved from them.

6. Microsoft. What it does: provides your assistant's default voice. When you use spoken replies, it receives the text of the replies your assistant reads aloud and turns it into speech.

7. Resend. What it does: sends the service's emails, including notices that can carry the name of anyone asking for permission to talk to your assistant.

Contact for each sub-processor: through Evy, at contacto@evyagent.com.

Not Evy's sub-processors: the apps you connect (your invoicing program, your email, your calendar), the messaging platforms where you use your own accounts (WhatsApp, Telegram and the like), and the AI provider if you use your own keys. You contract them, under their own terms. Nor are the search engines and websites your assistant consults when you ask it to look something up.