Privacy Notice on the processing of personal data
Evolus platform, app.evolus.ai and mobile applications
Version 2.8, published on 19 November 2026, effective from 19 November 2026.
SHA-256 fingerprint: accd30453897c4c409348df1c92cce8cedc2edcbdebea62a39aee6c34de54d9f
Download the canonical text (.md)This is a courtesy translation. In case of discrepancy, the Italian version prevails.
This notice is provided pursuant to articles 13 and 14 of Regulation (EU) 2016/679 ("GDPR") and describes how the personal data of users who access and use the Evolus platform through the portal app.evolus.ai and through the Evolus and Evo Assistant mobile applications are processed. The processing specific to the Evo Assistant app is described in section 12, that of the Messenger and Instagram channels in section 17. The processing carried out by Evo, the work assistant in the portal, is described in section 13.
This notice concerns exclusively the Evolus platform and is distinct from the privacy notice of the evolus.ai showcase website.
1. Data controller
The data controller is CodeDesign S.r.l., with registered office at Via Nino Pesce 38, 18018 Taggia (IM), VAT No. IT01739830089 (hereinafter "CodeDesign" or "Provider").
For any request relating to the processing of personal data and for the exercise of the rights provided for by the GDPR, you may write to: privacy@codedesign.it.
CodeDesign has not designated a data protection officer pursuant to art. 37 of the GDPR, having assessed that the conditions for doing so do not apply. The privacy@codedesign.it mailbox is monitored by the data protection contact person.
2. CodeDesign's role and scope of the notice
In providing the Evolus platform, CodeDesign acts in a dual role:
- a) as data controller, for the data relating to the creation and management of accounts, to authentication, to the use of the platform, to security, to assistance and to compliance with legal obligations;
- b) as data processor pursuant to art. 28 GDPR, for the personal data that are processed on behalf of the Customer (the organisation that subscribed) through the Employee AI and the platform's features. Such processing is governed by the Data Processing Agreement, which constitutes Annex A to the General Conditions of Use and which the Customer accepts online at the same time as the Conditions, without a separate signature. The Agreement identifies the Customer as the Controller of such data and is published at https://evolus.ai/en/data-processing-agreement; the General Conditions of Use are published at https://evolus.ai/en/terms-of-use.
For the data processed on behalf of the Customer, the notice to data subjects and the collection of any legal bases are the responsibility of the Customer. This notice mainly describes the processing operations for which CodeDesign acts as Controller and provides transparency on the entire processing architecture of the platform.
3. Categories of personal data processed
Depending on the features activated, the following categories of data may be processed:
Account and profile data
Access to the portal and to the mobile applications takes place through the Keycloak identity system (identity.evolus.ai). The following are processed: first name, last name, username, email address, role and groups of membership, preferred language and any profile image (avatar).
Billing data
When an organisation is activated, from the portal or from the Evo Assistant app, the name, the tax country and, depending on the case, the tax code of the natural person not acting as a professional or the VAT number are processed.
Data relating to the acceptance of contractual documents and to consents
When the General Conditions of Use are accepted, from the portal or from the Evo Assistant app, the following are recorded as evidence of the act: name and verified email address of the person accepting, their roles in the organisation, the billing data of the contracting party, date and time, IP address, identifier of the software used (user agent), the text of the statement of powers and the versions of the documents accepted. Any consent to receive commercial communications, and its withdrawal, are recorded as separate acts.
Usage and technical data
Data relating to the use of the Service, technical logs (including the IP address and the address of the requests received by the servers), session identifiers, diagnostic and operational telemetry data, audit trail records of the activities performed on the platform.
Content entered into the platform
- content of conversations and messages exchanged with the Employee AI via web chat, instant messaging and email;
- recordings and transcriptions of voice conversations, where the voice feature is activated;
- documents, files and content uploaded to the Knowledge Base for information retrieval (RAG);
- identification and contact data present in the address book (verified contacts) and in the content managed by the Employee AI;
- configurations, instructions and automations defined by the Customer;
- messages received and sent through the Messenger and Instagram channels connected by the Customer, with the data described in section 17;
- content processed by the Evo Assistant app, which resides on the user's phone and reaches the platform servers only in the cases described in section 12.
- where Evo, the work assistant in the home of the portal, is active: the conversations with Evo, with their complete history, the files uploaded by the person and those produced by Evo (including images, narrated audio and videos), the confirmation requests that Evo proposes, Evo's memory, personal and company, and the activity and consumption data, as described in section 13;
- where Evo editable documents and whiteboards are active: text documents, spreadsheets, presentations and whiteboards, with their versions, comments and votes; the data of outside people whom the controller invites or gives a link to (chosen name, email address, access), as described in section 18;
The content may include personal data of third parties (employees, collaborators, customers and contacts of the Customer). The Customer is responsible for the lawfulness of their entry and for the provision of the related notices.
Data relating to purchases made through the stores
For the subscriptions and top-ups purchased in the Evo Assistant app through the App Store or Google Play, the data described in section 14 are processed.
5. Purposes and legal bases of the processing
The data are processed for the following purposes and on the following legal bases:
- a) provision of the Evolus platform, of the Employee AI features, of Evo (the work assistant in the portal) and of the Evo Assistant app, management of the account and of authentication, management of subscriptions and purchases, legal basis: performance of the contract (art. 6.1.b GDPR);
- b) assistance and technical support to the user, legal basis: performance of the contract and legitimate interest (art. 6.1.b and 6.1.f GDPR);
- c) security of the platform, prevention of abuse and audit trail (Safety Engine), legal basis: the Provider's legitimate interest in ensuring the integrity and security of the Service (art. 6.1.f GDPR);
- d) compliance with legal, accounting and tax obligations, legal basis: legal obligation (art. 6.1.c GDPR);
- e) ascertainment, exercise or defence of a right in legal proceedings, legal basis: legitimate interest (art. 6.1.f GDPR);
- f) sending of commercial communications from CodeDesign about Evolus, new features, events and offers, legal basis: consent (art. 6.1.a GDPR), optional and revocable at any time from the profile settings in the portal or from the "You" section of the Evo Assistant app;
- g) diagnostics of the operation of the Evo Assistant app, described in section 12, legal basis: the Provider's legitimate interest in the correct operation of the app (art. 6.1.f GDPR), with the possibility for the user to disable it at any time from the app.
The Customer's data and content are not used by CodeDesign for its own purposes, nor to train, retrain, fine-tune or evaluate artificial intelligence models of its own. On the use of the content by the model providers, see section 7.
6. Processing methods and security measures
The processing is carried out with automated tools and, where necessary, with authorised manual interventions. CodeDesign adopts technical and organisational measures adequate pursuant to art. 32 GDPR, including:
- access control: centralised identity separate from the application, mandatory verification of the email address, granular permissions checked on every request with fail-closed behaviour, second authentication factor available by means of a one-time code sent by email;
- encryption of data in transit: all communications between the clients and the platform take place over a channel encrypted with the TLS protocol;
- application-level encryption of data at rest with the AES 256-bit algorithm in GCM mode, applied to the credentials and access keys of the services configured by the Customer, to the signing secrets of the channels and of the webhooks, to the credentials of the mailboxes and of the workflows, as well as, for the Evo Assistant app, to the transcripts and results of the meetings, to the requests and results of the daily brief and to the answers awaiting delivery to the phone. The content of the chat conversations and the documents uploaded to the knowledge libraries are not encrypted at the application level: they are protected by the access controls and by the encryption at rest of the underlying storage;
- infrastructure: hosting on datacenters located in the European Union;
- audit log of accesses and administrative operations, with the author, subject, date and time of each access and of each operation: the entries of accesses are retained for 12 months, the others for 24 months, and then automatically deleted;
- Safety Engine: system protecting against prompt injection, data exfiltration and improper use of the AI tools, with protections that the Customer cannot disable;
- business continuity: hourly backups of the digital employees, encrypted at source before transmission to the remote archive, with an automatic restore check every 6 hours and a documented real restore test.
The complete and up-to-date list of the technical and organisational measures is published in Annex B to the General Conditions of Use, at https://evolus.ai/en/security-measures.
7. Artificial intelligence and model providers
To provide the conversational, synthesis and automation features, the platform transmits the necessary content to providers of artificial intelligence models and voice services (sub-processors indicated in section 8).
The Employee AI is a support and automation tool: it may generate inaccurate or incomplete outputs. The outputs do not replace human judgement and must be verified before relying on them for significant decisions.
Use of the content for training. CodeDesign selects providers whose terms contractually exclude the use of the content transmitted for the training of their own models, and activates, with the providers that allow it, the settings that disable the retention and the use of the content for their own purposes, including the opt-out parameters to be transmitted with each individual request where the provider offers that method. This exclusion is today guaranteed by the contractual terms of the providers and by the settings of CodeDesign's accounts, not by a technical control applied to each individual call by the platform software. The status provider by provider is published on the sub-processors page, at https://evolus.ai/en/subprocessors, and updated with each version of the page.
Evo. Where Evo is active, its requests to the models (the conversation, the title of the conversations, the extraction of memory entries, the vectors of the memory and the Evolus tools that Evo uses, for example the translation and summarisation of documents) pass through the Evolus AI gateway, a CodeDesign component that runs on Hetzner infrastructure in Germany, and are served by the model providers indicated in section 8, in compliance with the data rules chosen by the Customer (for example European routing and zero retention, where activated). Evo is a support tool: it may produce inaccurate answers, and it does not take decisions based solely on automated processing that produce legal effects on people (Article 22 GDPR): it proposes actions and only the person confirms them. Evo may also produce documents, images, narrated audio and short videos, and talk to the person by voice ("Talk"). To create images, narrated audio and videos, the text of the request, any reference images indicated by the person and, for narrated audio, the text to be read are sent, through the same gateway, to specialised external model providers already listed in section 8, including in the United States (section 9); where European routing ("EU only") is active, Evo does not create images or videos. In "Talk" the audio of each sentence is transcribed by an external voice transcription provider and the answer is read aloud by an external speech synthesis provider, both already listed in section 8. The generated content is made recognisable as created by artificial intelligence (section 13). The text of the web pages, documents and other third-party content that Evo reads is data, never an instruction.
8. Recipients and sub-processors of the processing
The data may be communicated to external providers appointed as processors or sub-processors of the processing, selected from among entities that offer adequate guarantees regarding data protection and bound by contract with obligations equivalent to those assumed by CodeDesign. The sub-processors belong to the following categories:
- cloud infrastructure, hosting and storage in the European Union: Microsoft (Microsoft Azure) and Hetzner Online GmbH;
- routing of requests to language models: OpenRouter, Inc. and the downstream inference providers to which OpenRouter assigns the individual request;
- voice transcription, voice synthesis, voice agents and speaker diarisation of meetings: ElevenLabs;
- push notifications to the mobile apps: Expo (650 Industries, Inc.), Apple Inc. and Google LLC as the final transport;
- web search engines used by the agents, when the search feature is activated;
- payment processing and subscription management: Stripe;
- third-party services activated by the Customer with its own credentials, such as Microsoft 365, Google Workspace, the Meta Platforms WhatsApp, Messenger and Instagram channels, the mail servers indicated by the Customer and the catalogue connectors. These services are not sub-processors of CodeDesign: they are recipients chosen by the Customer, which is answerable for them as controller of the related processing.
To distribute the updates of the code of the Evo Assistant app, CodeDesign uses, as controller, the Expo service of 650 Industries, Inc., United States, which receives only the technical data described in section 12. For purchases made in the Evo Assistant app, Apple and Google act as sellers and process the payment data as independent controllers, according to their own privacy notices (section 14).
The complete, named and up-to-date list of the sub-processors is published at https://evolus.ai/en/subprocessors, indicating for each of them the activity carried out, the country of establishment, the categories of data processed and the legal basis of any transfer. Changes to the list are communicated to the Customer's administrators at the latest on the date the processing starts, with 30 days for reasoned objection. The data are not subject to dissemination or sale to third parties.
9. Transfer of data to third countries
The infrastructure for processing and storing the data is located in the European Union: the application services, the database, the file storage, the document search indexes, the identity system and the optical recognition of documents are hosted on European cloud infrastructure; the digital employees and their archives reside on a server in Germany; the backups are kept in Finland. Evo's isolated execution environments (section 13) are hosted on European cloud infrastructure; the platform's AI gateway and the model that calculates the vectors of Evo's memory run on servers in Germany.
The provision of the Service nonetheless entails transfers of personal data to third countries, and in particular to the United States of America, for the routing of requests to language models, for the voice services, for voice transcription, for the delivery of push notifications and for the distribution of the updates of the code of the Evo Assistant app. CodeDesign does not represent that the data remain entirely within the European Economic Area.
Each transfer takes place, in the following order:
- a) on the basis of an adequacy decision of the European Commission (art. 45 GDPR), where applicable to the country of the recipient;
- b) for recipients established in the United States of America, on the basis of the EU-US Data Privacy Framework, where the entity is certified in the official register and for the categories of data covered by the certification;
- c) in the absence of the preceding conditions, on the basis of the Standard Contractual Clauses adopted by Implementing Decision (EU) 2021/914, module 3, incorporated into the agreement with the provider;
- d) residually, on the basis of one of the derogations provided for by art. 49 GDPR.
The certification status of each recipient is indicated on the sub-processors page, at https://evolus.ai/en/subprocessors, and updated at each change.
Features that reduce transfers. Requests to the language models of the Evo Assistant app are in any case served only by providers that do not retain the content, as indicated in section 12. For Customers on the Enterprise Plan, European routing of the requests to the models, routing solely to zero-retention endpoints, the restriction of the model providers for the individual organisation and the European region of the voice, on request and with a dedicated voice workspace in a European region, are available. These features are activated for the Customers whose accepted commercial proposal provides for them. For the other plans, global routing, the inference providers on the published list and the global voice region apply. The plans are described in the price list published at https://evolus.ai/en/pricing.
10. Retention period
Personal data are retained for the time strictly necessary to achieve the purposes for which they are processed and, in any case:
- account data and the Customer's content are retained for the duration of the contractual relationship. Upon termination, at the Customer's choice, they are returned or deleted: deletion from the production systems is completed within 60 days of termination and the copies present in the backups are overwritten by the normal rotation cycle within a further 30 days, save for legal retention obligations;
- documents of the knowledge libraries that a person deletes by hand, from the portal, through the APIs or through an artificial intelligence assistant of the platform: in the libraries where the trash is active they remain in the trash for 30 days. During this period they are no longer visible in the library or used by artificial intelligence (their search indexes are removed at once), and whoever can edit the library may restore them or delete them at once for good, including by emptying the trash. Through the APIs, permanent deletion can also be requested without going through the trash. After the 30 days the file and its content are permanently deleted. Automatic deletions (for example periodic cleanups of the platform or the deletion of an entire library) do not go through the trash and are final, except for the moving of expired files described in the next point; in the libraries where the trash is not active, the deletion of a document is immediate and final;
- the files of the knowledge libraries are retained for the period chosen by the Customer in the "Data retention" page, "Library files" type (from 1 day to 10 years, or "Never"; "Never" if no choice is made); each library may have a shorter period, and the shorter of the library's period and the space's period applies. The days are counted from the last use of the file: a use occurs whenever the file is found in a search or read by Evo or by an agent, opened, previewed, downloaded, modified, saved as a new version, used in a conversation, copied or transferred, or restored from the trash; the presence in a list, the search by name, the renaming and the moving between libraries are not. In the days following expiry the file is moved to the library's trash, where it is no longer used by artificial intelligence, and it remains there for 30 days, during which whoever can edit the library may restore it; where the trash is not active, the expired file is nevertheless moved to the trash, which is not visible, and cannot be restored. After the 30 days the file is permanently deleted;
- chat conversations, including those of the WhatsApp, Messenger and Instagram channels, are deleted once they have had no new messages for the period chosen by the Customer in the "Data retention" page of the portal (from 1 to 730 days; 730 days if no choice is made), and in any case at the end of the contract or at the Customer's request;
- where Evo is active: the conversations with Evo and their histories are retained for the period chosen by the Customer in the "Data retention" page, "Conversations and channels" type (from 1 to 730 days, 730 days by default), counted from the last message; the files in "My files" for the period of the "Personal files" type (from 1 to 730 days, 730 days by default), counted from the last use of the file as for the library files, and on expiry they are permanently deleted, without trash, with all their versions. The person can delete at any time a conversation, which is deleted at once with its history, including from Evo's execution environment (except for a temporary unavailability of the service that governs the environments, in which case the deletion from the environment is completed as soon as the service is available again), or a file, which is deleted at once and for good, with all its versions and the copies that the person has sent to other conversations. The text of a file that Evo has read remains in the history of the conversation in which it read it, until that conversation is deleted. When a conversation is deleted, by the person or on expiry, the conversations of the agents that Evo has asked are deleted with it; the memory entries that Evo has drawn from it are not deleted with it and the person manages them in "What I remember". Deletion from the systems in use, for Evo's data as for any other, does not entail immediate deletion from the backup copies, which remain for the time provided by their rotation cycles;
- Evo's memory: the memory entries, personal and company, are deleted with their search indexes, revisions and links when, for the period chosen by the Customer in the same page (730 days by default), they have been neither updated nor used by Evo; archived, expired or superseded memory entries and the revisions of their texts are deleted after 30 days; the texts awaiting the memory extractor are deleted when processing ends and in any case within 24 hours. The person can delete at any time an entry, a node or the whole of their memory;
- Evo's confirmation requests that go unanswered expire after 24 hours and their arguments are deleted after 30 days, or earlier with the conversation to which they refer;
- the Evo execution environment of a person who has not used Evo for 30 days is deleted, with what it contains; the history of the conversations remains in the platform for the period indicated above;
- the person who loses the permission to use Evo but remains in the space does not lose the conversations, files and memory entries, which remain and follow the periods indicated here and become available again if the permission is restored; their execution environment is deleted after 30 days without use, as for any other person;
- Evo's activity records (when and for how long Evo has worked for a person and which resources it has used) are deleted together with the conversation to which they refer; the records of the start-ups of the execution environment are deleted together with the environment and in any case when the period chosen by the Customer for the conversations with Evo expires;
- where Evo is active, the images, narrated audio and videos created by Evo are files in "My files" and follow the period of the "Personal files" type indicated above; the job of each content (type, outcome, quantity and cost, without the text of the request) is deleted when the period of the conversations with Evo expires and, when the conversation is deleted, loses the title and the links to the conversation. A content being prepared is completed even if the conversation is deleted (the file arrives in "My files" and the credits are charged); if the person leaves the space, deletes the account or the space is deleted before delivery, the content is completed, the credits are charged and the file is discarded;
- the audio of "Talk" is not kept; the register of fingerprints of the content generated by Evo (fingerprint, type, provider, outcome, technical identifiers of space and conversation, date; no person, no content) is retained for 730 days from the creation of the content, even after the deletion of the conversation, of the account or of the space, and is then deleted;
- voice conversations are retained according to the period configured by the Customer for each voice agent, and a mode without retention of the content is available;
- meeting recordings captured by means of the automatic participant are deleted after 30 days;
- the audio of the meetings sent by the Evo Assistant app is deleted from the servers at the end of the transcription, or when the processing fails definitively; the results of those meetings are deleted after 7 days, reduced to 6 hours from the first consultation;
- the results of the daily brief processed for the Evo Assistant app are deleted after 7 days, reduced to 6 hours from the first consultation; the content sent from the phone to prepare it is deleted at the end of the processing;
- the answers of the Evo Assistant app awaiting delivery to the phone, described in section 12, are deleted when the phone confirms their receipt, normally after a few seconds, and in any case after 30 days;
- the audit log: the entries of accesses are retained for 12 months, the others for 24 months; when a person is deleted, the name, the email address and the IP address in their entries remain visible to the Provider's personnel alone for 12 months and are then removed; the identity system deletes its own access events after 90 days;
- in the consumption detail of the digital employees, after 13 months the identifier and the name of the person interacting with the digital employee and the reference to the conversation are removed; the link to the platform account to which that person may have been traced remains;
- the notifications in the portal are deleted after 90 days;
- the temporary files produced by assisted processing are deleted within 24 hours;
- the data stored on the phone by the Evo Assistant app remain on the phone, save for the shorter terms indicated in section 12, until the user deletes them, uninstalls the app or deletes the account, as described in sections 12 and 15;
- where Evo editable documents and whiteboards are active: they are kept with everything they contain (saved versions, Evo interventions, comments, votes) until the person deletes them and for the duration chosen by the Customer for the type of file they are in ("Personal files" in "My files", "Library files" in a library), counted from the last use; each document and each whiteboard keeps the last 20 saved versions and, for whiteboards, the last 20 Evo interventions, which are replaced by number and not by days;
- outside people invited to a whiteboard: their access, session, confirmation code and the invitation's email address are deleted 30 days after the access expires; the address of whoever asks to edit, 30 days after the request has been handled or, if not handled, 30 days after the link expires; the chosen name stays next to comments as long as the whiteboard exists, unless the controller anonymises it; the security log of entries (chosen name, IP address, date and time) is kept for 24 months; the server's technical logs, which contain the IP address, are kept for 90 days;
- the live transcript lines of meetings with a whiteboard (speaker, text, minute) are deleted after 7 days, or with the meeting if deleted earlier;
- the server's technical logs (with the IP address and the address of the requests) and the application logs are retained for 90 days, the traces of the requests for 30 days, the operating metrics for 12 months; the telephony system logs, in which telephone numbers appear with the last digits masked, for 30 days; the system logs of the server that hosts the digital employees for at most 30 days;
- the infrastructure access logs (databases, the service that keeps the secrets, the software image registry) are retained for 365 days; those of the requests received by the service that hosts the platform's interfaces, with the IP address, for 90 days;
- content awaiting or undergoing deferred processing remains in the processing systems for at most 14 days, 24 hours if the processing succeeds;
- errors of the calls to artificial intelligence models are deleted after 30 days;
- attachments uploaded for a conversation and never sent are deleted 7 days after upload;
- of the digital employees, the technical activity logs are retained for 90 days, the security log for 12 months and the resume state of a conversation for 90 days from the last use;
- of the messages that the Provider sends from the platform to the people of the spaces, the list of the recipients with the outcome of the sending is deleted 12 months after sending; the text of the messages and the counts remain;
- files deleted from the platform's file storage remain recoverable by the Provider alone, as protection against accidental deletions, and are permanently removed within 30 days of deletion; the backup copies of the digital employees' environment are retained for up to 30 days;
- data processed for accounting and tax obligations are retained for the terms provided for by applicable law.
11. Rights of the data subject
Data subjects may exercise at any time the rights provided for by articles 15-22 GDPR, and in particular:
- access to their personal data;
- rectification of inaccurate data and integration of incomplete data;
- erasure of data (right to be forgotten);
- restriction of processing;
- data portability;
- objection to processing based on legitimate interest;
- withdrawal of consent, where the processing is based on consent, without prejudice to the lawfulness of the processing carried out before the withdrawal.
Requests may be sent to privacy@codedesign.it; CodeDesign responds within one month of the request. Where the data subject is an employee, collaborator or contact of the Customer and the data are processed by CodeDesign on behalf of the Customer, the request will be forwarded to the Customer, as Controller, within 5 working days and without undue delay, and the data subject will be informed of this. Where an erasure request concerns a document held in the trash of a library, the document is permanently deleted without waiting for the 30 days to expire.
Users of the Evo Assistant app can also view, correct and delete from the app the memories stored on the phone. The account can be deleted directly from the app or from the portal, with the effects described in section 15.
Those who use Evo, where it is active, may also exercise their rights directly in the portal: consult in "What I remember" the whole of their personal memory (entries of every status, nodes, sources and dates), correct it, delete an entry, a node or the whole memory (even when the memory is switched off), export it in JSON or Markdown format, switch it off for all conversations, for a single conversation or for a single entry, and delete their own conversations and files. Evo proposes memory entries only on the basis of the text written by the person and refuses secrets, special categories of data and evaluations of people (section 13).
Outside people invited to a whiteboard do not have an account: they can ask for access to, correction or deletion of their data, and for their name in comments to be made anonymous, by writing to privacy@codedesign.it; the request is forwarded to the controller (the organisation that shared the whiteboard) within 5 working days, as described above.
The data subject also has the right to lodge a complaint with the competent supervisory authority (in Italy, the Garante per la Protezione dei Dati Personali, the Italian Data Protection Authority, www.garanteprivacy.it).
12. Evo Assistant app
Evo Assistant is the Evolus mobile application for iOS and Android that acts as a personal work assistant. It is used with an Evolus account, within an Evolus organisation. This section describes which data the app stores on the phone, which data it transmits to the platform servers and to which third parties.
Data stored on the phone
The app stores on the phone, in a separate database for each pair of organisation and user: the conversations with the assistant, the memories, the standing instructions (behaviours), the transcripts, summaries and items of the meetings, the outcomes of the daily brief, the alerts scheduled by the assistant with the history of the last 30 days and the log of the operations carried out by the assistant, which also includes an initial extract, of no more than 400 characters, of the result of the readings, and whose entries older than 30 days are deleted when new operations are recorded. While an answer is in progress, the database also keeps the state of the answer, including the results of the readings carried out by the assistant, and deletes it when the answer ends. In the same area of the app, the attachments of the conversations (photos, voice messages, documents generated by the assistant) and the audio of the meetings recorded or imported are stored as files.
These data are not synchronised with the Evolus servers and there is no backup copy managed by Evolus. The database is not encrypted by the app with a key of its own: it is protected by the isolation that the operating system reserves for the data of each app. The database and the attachments are included in the phone backups made by the operating system, if the user has enabled them; the audio of the meetings is excluded from them.
The audio of the meetings remains on the phone until the user deletes it, unless the user has chosen in the settings automatic deletion after a number of days; deleting the audio does not delete the text of the meeting.
Signing out of the account does not delete the data stored on the phone, which become available again at the next sign-in of the same user in the same organisation and are not accessible to another user who signs in from the same phone. Uninstalling the app removes the database and the files of the app from the phone. On iOS the access token and the mail passwords, stored in the system keychain, may survive the uninstallation: the app deletes them at the first launch after a new installation. The deletion of the account is described in section 15.
Data transmitted to the platform servers to generate the answers
To produce each answer, the app transmits to the platform servers the name, language and time zone of the user, the country and the time format (12 or 24 hours) set on the phone and, where the phone's system makes it available, the first day of the week, the user's message, the recent part of the conversation and its summary, the relevant memories and behaviours, the text of the attached documents, the attached photos and the results of the readings carried out by the assistant while answering, for example the text of an email message, of an event or of a contact. The servers compose the request and forward it, through OpenRouter, to the provider of the language model. Together with the request, a stable session identifier, derived in a non-reversible form from the organisation and the user, is also transmitted to OpenRouter. For searching the memories, the texts of the memories are sent to the servers, and from these to OpenRouter, for the calculation of the numerical representations used in the search. In the same way, without retention by the Evolus servers, the title and summary of the conversations, the extraction and merging of the memories and the proposals of memories and labels derived from the meetings are processed.
So that an answer is not lost if the app is closed or the phone loses its connection while the assistant is preparing it, in chat conversations the Evolus servers retain, encrypted, the outcome of each step of the answer until the phone confirms its receipt: normally for a few seconds and at most for 30 days, if the app is not reopened, after which the outcome is deleted automatically. The outcome includes the text of the answer, the actions proposed to the user for confirmation, the sources consulted and the messages of the step, that is the user's message with the text of the attached documents, the results of the readings carried out by the assistant, for example from the email, the calendar, the address book or the connected services, and the memories recalled. The attached photos and PDF files are not retained: in their place an indication of the attachment remains. The outcome is also deleted with the deletion of the account and when the user is removed from the organisation. If the phone disconnected before receiving the answer, the servers send a notification inviting the user to open the app, without the content of the answer. In the voice conversation the outcome is not retained.
Apart from the outcome awaiting delivery, the Evolus servers do not record the content described above in databases or file archives: they process it for the duration of the request. A consumption record remains, with the user, the organisation, the model and the quantities consumed, without the content. The requests to the language models of the Evo Assistant app are served, through OpenRouter, exclusively by providers that do not retain the content received: the constraint is set in the configuration of CodeDesign's account with OpenRouter.
Voice messages, and the sentences spoken in the voice conversation, are sent to the servers for transcription and from these to the platform's transcription provider, ElevenLabs; the audio is not retained by the Evolus servers, and the transcribed text enters the conversation like the other messages. In the voice conversation, the text of the assistant's answers is sent to ElevenLabs for voice synthesis and is not retained by the Evolus servers.
When the assistant reads a web page or carries out a web search, the address of the page or the search is transmitted, through the Evolus servers, to OpenRouter, which reads the page or carries out the search through the engines indicated on the sub-processors page.
Meetings
The user can record a meeting, even with the screen locked, or import its audio. The audio is sent once to the platform servers, together with any names of the participants indicated by the user, the date and the time zone, and is transcribed by ElevenLabs with attribution of the contributions to the participants; the text is then summarised by means of the language models. The audio is deleted from the servers at the end of the transcription. The transcript, the summary and the names of the participants remain on the servers, encrypted, until they are collected by the app and in any case not beyond the terms indicated in section 10; when the app has saved the result on the phone, it requests its deletion from the servers. The notification announcing that the meeting is ready shows the title of the meeting.
Whoever records a meeting should inform the participants of it: the app reminds the user of this in the presentation of the feature and in the recording screen.
The user can connect mailboxes to the app through the IMAP and SMTP protocols. The password is stored in the phone's keychain, is not included in backups and is not transmitted to the Evolus servers. The app connects directly to the mail server indicated by the user, over an encrypted channel, and reads the messages on demand, without keeping a copy of them on the phone. The daily brief keeps the subject and the sender of the messages it mentions, and the assistant's answers, saved in the conversation, may report their content; of the messages read by the assistant, an extract in the log of the operations and, while the answer is in progress, the text in the state of the answer also remain on the phone, as described above. When the assistant reads a message in order to answer, its text is transmitted to the platform servers and to the model provider in the ways described above. A message is sent only after the user's confirmation.
To suggest the mail server parameters, the app may query Mozilla's automatic configuration service, to which it transmits only the domain of the email address.
Calendar, reminders, notifications, contacts and photos of the phone
With the permissions granted by the user in the operating system, the app reads on the phone the calendar, the reminders and the address book when the user asks the assistant to; it also reads the calendar and the reminders to prepare the daily brief, and the calendar to suggest the title and participants of a meeting that the user is about to record. The reading of events includes, where present, the organiser and the participants, with name and email address. It creates, modifies or deletes events, reminders and contacts, including recurring ones, only after the user's confirmation. What the app reads reaches the platform servers only within a request for an answer, the daily brief or the sending of a meeting. The app does not ask for access to the location.
The address book can be searched by name, by phone number or by email address: the comparison takes place on the phone and only the contacts found reach the servers. On Android the assistant also reads and modifies the note of the contact; on iPhone the note is neither read nor modified. On iPhone with iOS 18 or later versions, if the user has granted access only to some contacts, the app allows the user to extend the selection with the system picker, without asking for access to the whole address book.
The assistant can prepare a call or an SMS to a number: after the user's confirmation, the app opens the system Phone or Messages app with the number and, for the SMS, with the text already written. The call and the sending of the SMS remain with the user, in the system app, and nothing is transmitted to the platform servers beyond what is already part of the conversation.
The notifications and alerts scheduled by the assistant, including recurring ones, are scheduled on the phone as local notifications of the operating system and do not pass through the push notification services. The list of scheduled alerts, with the history of the last 30 days, remains on the phone, where the user can consult it, modify it and cancel the alerts from the "Scheduled alerts" view of the app.
Of the photos, the app receives only those chosen by the user with the system picker, up to 5 per message, and does not access the phone's library. The user can also take a photo with the camera, from the chat or when the assistant opens it in the course of the answer; the authorisation to use the camera is requested at the first use and the shot is not saved in the phone's gallery. The photos chosen or taken are reduced in size on the phone before being sent and are treated like the other attached photos. In the voice conversation the assistant does not use photos or the camera.
Daily brief
If the user uses it, the app collects on the phone, from the connected sources, the items of the day (for example titles of events, reminders, subject and sender of messages, memories, meetings) and sends them to the platform servers, which prepare the text by means of the language models and may consult the services connected by the organisation. The content sent and the identity used for the connected services are deleted at the end of the processing; the result remains on the servers, encrypted, for the terms indicated in section 10. The notification announcing that the brief is ready does not show its content.
Services connected by the organisation
If the organisation has connected services from the catalogue, such as Microsoft 365 or Google Workspace, the user's authorisation is granted in the browser and the related tokens are stored on the platform servers, encrypted, and not on the phone. The assistant's requests to these services pass through the platform servers, which retain their content only in the outcome of an answer awaiting delivery, in the ways and for the times described above. The tokens of a connection not used for 90 days are deleted.
Push notifications
If the user allows notifications, the app registers on the platform servers the notification token of the device, with the operating system and the indication of the app. The token is deleted when the user signs out of the account and when the account is deleted.
App updates
At every launch the app checks for updates of its own code with the Expo service, to which it transmits technical data (platform, version and channel of the app, update in use) and a random identifier generated by the app, without content and without account data.
Diagnostics and reports
The app automatically sends diagnostic data to the observability infrastructure managed by CodeDesign: crashes and errors, of which the type and position in the code are transmitted but not the text; duration and outcome of the app's requests to the platform servers, with the address of the request including its parameters, without their content; usage sessions and screens visited; version of the app; characteristics of the device, including manufacturer, model, operating system, memory, battery level and mobile carrier, and, on Android devices, the name assigned to the device; a random identifier of the installation, which stays the same as long as the app remains installed. The name, the email address and the account identifier of the user are not transmitted, nor is the content of conversations, memories, email, meetings or documents. These data are retained for the terms of the technical logs indicated in section 10. The user can disable the sending at any time from the "You" section of the app, with immediate effect.
On the phone the app also keeps a technical error log, limited to the last 500 lines, which contains neither content nor the text of the errors and is not sent automatically.
The user can also report a problem from the app. The report is transmitted to the platform servers, linked to the account, with the text written by the user, the photos the user chooses to attach, the version of the app and of the operating system, the language and an excerpt of the technical log kept on the phone, which the user sees before sending and which contains no content. For support purposes, the diagnostic data of the organisation relating to the previous 24 hours may be associated with the report, and the subject and text of the report may be analysed by means of a language model to route it and to prepare a draft reply for the internal use of the support staff.
13. Evo, the work assistant in the portal
Evo is the work assistant found in the home of the portal app.evolus.ai. The person writes to it in a conversation and Evo works for them with the documents, knowledge libraries, agents, connectors and APIs that the organisation has made available, and may produce documents, images, narrated audio and short videos through the model providers already listed in section 8, and talk to the person by voice. Evo is distinct from the Evo Assistant app, described in section 12, which keeps its own data on the phone and has a memory of its own.
This section applies where Evo is active. Evo is available only in the spaces of the organisation for which the feature is activated; where it is not active, the processing described here does not take place.
CodeDesign's role and purposes
The conversations, files and memory of Evo are the Customer's content: for them CodeDesign acts as data processor (section 2), to make Evo available to the people who use it and in accordance with the Customer's instructions; the legal basis of the processing is determined by the Customer, which is the data controller. The consumption, activity and audit data and the register of fingerprints of the generated content (described later in this section) are processed by CodeDesign as data controller, to manage the Service, security and invoicing and to comply with the transparency obligations on content generated by artificial intelligence, on the basis of performance of the contract, of a legal obligation and of legitimate interest (art. 6.1.b, 6.1.c and 6.1.f GDPR). Evo does not take decisions based solely on automated processing that produce legal effects on people or similarly significantly affect them (Article 22 GDPR): it prepares answers, texts and documents, and every action that changes or sends something goes through a confirmation request, valid for 24 hours, which only the person can approve. Evo can make mistakes: its answers must be checked before relying on them.
What data are processed
- the conversations with Evo: the title (written by a model from the first question), the complete history of the messages, of the work steps and of the questions, and a short extract of the last message;
- the files: those uploaded by the person (up to 25 MiB each) and those produced by Evo, such as documents, spreadsheets, presentations, PDFs, images, narrated audio and videos, collected in "My files", with the PDF preview copy of Office documents;
- the content created by Evo (images, narrated audio, videos): the text of the request and the reference images, which remain in the conversation and in "My files"; the job of each content (type, outcome, quantity, cost and a short title, never the whole text of the request); the label and the register of fingerprints described later in this section;
- the sentences that the person speaks with "Talk", kept only as text in the conversation: the audio is not kept;
- the confirmation requests that Evo proposes to the person (for example saving or replacing a file in a library, asking an agent, using a connector or an API, saving a company memory entry), with the necessary data;
- the working context: the libraries, agents, connectors and APIs that the person has pinned or excluded, and the resources that Evo has used (type, identifier and name);
- the personal memory: memory entries (a short sentence, with priority, expiry, source, conversation of origin and last use), nodes (people, companies, projects, with other names and a card), relationships between nodes, revisions of earlier texts, search indexes (numerical representations of the entries) and the choices on the memory;
- the company memories of the space: shared entries and nodes, written with the confirmation of a person, with the name of the author;
- the consumption and activity data: for each call to the models, the person, the conversation, the model, the quantities and the credits, without the text; for each request, when and for how long Evo has worked;
- the audit log: only identifiers and counts of Evo's actions with confirmation, of the switching off of the memory for the space, of the deletion of the whole memory, of the deletion of a conversation or of a file of Evo (without the title or the file name) and of the cleanups, as well as the start, the duration, the number of sentences and the reason for closing of every "Talk" session, never texts or audio.
- Evo editable documents and whiteboards, where active: Evo reads the content of a document or a whiteboard and changes it only when a person of the space asks it to, with the same limits as every other request; what an outside person invited to edit has written on the whiteboard can be read by Evo; comments are not read by Evo as whiteboard text; for conversion and preview the content passes through CodeDesign's conversion service (Hetzner, Germany), which does not keep it beyond the processing; in meetings with a whiteboard Evo listens in real time and acts only on the whiteboard, as described in section 18;
When Evo asks an agent, the question and the answer form a conversation of the agent, in Evo's channel, linked to the conversation with Evo and deleted together with it.
Where and how Evo works
For each person and each space Evo works in an isolated execution environment, a virtual machine of Microsoft's Azure Container Apps Sandboxes service, in the West Europe region. The environment holds the files received and delivered and Evo's work sessions. The environment has a closed network: it reaches only three destinations of the platform (the AI gateway, Evo's tools and the organisation's connectors), with a personal key of 60 minutes that the network adds to the requests and that the code inside the environment does not see; it does not contain the secrets of the connectors; it is suspended after 60 seconds without work and is deleted after 30 days without use. From the environment Evo does not browse the internet: where available, web search and the reading of web pages go through the platform. The measures are described in Annex B to the General Terms of Use, https://evolus.ai/en/security-measures.
The service that governs the environments is hosted on Azure infrastructure in Western Europe and has no database of its own: the conversations, files, memory and the rest of the data are held in the platform's database and file archive, in the same region. The writes that the service cannot deliver to the platform at once stay in a temporary queue for at most 7 days, and its technical logs are kept for 30 days.
To whom the data are sent
All of Evo's requests to the models pass through the Evolus AI gateway, a CodeDesign component that runs on Hetzner infrastructure in Germany. The gateway routes them to the model providers listed on the sub-processors page, https://evolus.ai/en/subprocessors, applying the data rules chosen by the Customer for its space, such as European routing and zero retention where activated. No new providers have been introduced for Evo. The models receive the person's message, the extracts of libraries, documents and tool results needed for the answer and, at most, 8 relevant memory entries.
After each job a small model, the extractor, reads only the text written by the person, not that of third parties, and proposes memory entries. The text of each entry and the search text of each message are sent, for the calculation of the vectors, to the model running on CodeDesign's infrastructure in Germany or, depending on the configuration of the gateway, to OpenRouter (section 8). The title of the conversations is written by a model from the first question.
The organisation's connectors and MCP servers are reached through the platform, which keeps the secrets: tools that only read run at once, those that change or send data go through a confirmation request. These services are recipients chosen by the Customer (section 8).
Evo's memory
Evo remembers what the person tells it that is useful, in order to answer better. The personal memory is on by default: at the first memory entry the person sees a notice that explains it. In "What I remember" the person sees, corrects, archives, deletes and exports the entries, and may switch the memory off whenever they wish: for all conversations, for a single conversation or for a single entry. The administrator of the space may switch it off for the whole space: in that case Evo no longer remembers or writes, but the entries remain with the person, who can read, download and delete them. Switching the memory off does not delete anything.
When Evo writes, and in the company memories, the system refuses to write to memory secrets (such as access keys, passwords, IBANs and card numbers), special categories of data (Articles 9 and 10 GDPR) and evaluations of people who work. The check is deliberately coarse and does not guarantee that every case is recognised. Only in their own personal memory, written by hand, may the person also enter such data, which remain visible only to them.
The company memories collect facts of the organisation, shared according to the access decided by the administrator. A company memory entry is written only with the confirmation of a person, who becomes its author. Whoever reads without managing the memory sees "a colleague" and the date; the managers of the memory see the author and can filter the entries by author. The name of an author never enters Evo's answers.
Images, narrated audio and videos
At the person's request Evo creates images, narrated audio (a text read aloud, delivered as an audio file) and short videos, through specialised external model providers reached through the Evolus AI gateway: for images and videos, the routing provider and the downstream model providers listed on the sub-processors page, https://evolus.ai/en/subprocessors; for narrated audio, the speech synthesis provider listed on the same page. The provider receives the text of the request, the reference images (or the first image of a video) that the person has indicated and, for narrated audio, the text to be read, even when it comes from a document of the person. Some of these providers are in the United States (section 9) and no European route is declared for images and videos: where European routing ("EU only") is active, Evo does not create images or videos and tells the person so, and creates narrated audio only if there is a voice provider that complies with the rule. A low-cost image or narrated audio starts at once; a video, a more expensive content and a content that originates from a text that is not the person's go through a confirmation request, which shows the estimated cost and which only the person can approve.
The contents created are saved in the conversation and in "My files" and follow the periods in section 10. A content being prepared (a video takes a few minutes) is completed even if the person deletes the conversation: the file arrives in "My files" and the credits consumed are charged to the space. If instead the person leaves the space, deletes their account or the space is deleted before delivery, the content is completed at the provider, the credits consumed remain charged and the file is discarded.
"Talk", the voice conversation
"Talk" lets the person converse with Evo by voice in the browser, inside the same written conversation; it is available where Evo is active and only while the person uses it. Speech detection (when a sentence begins and ends) runs in the person's browser. Only the audio of each sentence is sent, through the platform, to an external voice transcription provider that turns it into text; the audio is not kept by CodeDesign or written to the technical logs: only the text of the sentence remains, which becomes a message of the conversation and follows its retention periods (section 10). Evo's answer is read aloud with a voice generated by artificial intelligence: the text of the answer is sent, sentence by sentence, to an external speech synthesis provider, and the audio is not kept. At the start of each session Evo says aloud that it is an artificial intelligence assistant, and the screen reminds the person of it throughout the session. A session has a maximum duration (30 minutes by default) and closes after a period of silence; each person can have only one session open at a time. The two providers are listed on the sub-processors page, https://evolus.ai/en/subprocessors.
Recognisability of generated content
The images, narrated audio and videos created by Evo are content generated by artificial intelligence, and Evolus makes them recognisable, as Article 50 of Regulation (EU) 2024/1689 ("AI Act") requires: (1) every content carries the "AI-generated" label, always visible in the conversation, in the player and in the preview, and in "My files" for videos and narrated audio; (2) if the file already carries a machine-readable marking inserted by the provider of the model, it is kept intact; (3) if it carries none, CodeDesign adds to the data of the file a marking of its own (origin from artificial intelligence, the indication "Evolus Evo" and the date), without altering images and sounds and without including in it people, texts, space or model; this is not possible for every format and every file; (4) for every content delivered, CodeDesign records the fingerprint of the file, the type of content, the type of provider, the outcome of the marking, the technical identifiers of the space and of the conversation, and the date, in order to be able to verify, starting from a file, whether it was generated by Evo. The register contains neither the name of any person nor the content of the files; CodeDesign keeps it as data controller, to comply with the transparency obligation and to ascertain the provenance of the content (Article 6.1.c and 6.1.f GDPR), for 730 days, even when the conversation or the space is deleted, and then deletes it. The markings in the data of the files may be lost when the file is converted, edited, republished by some services or photographed from the screen. The audio of "Talk" is produced and heard in real time and is not a file: it carries no marking, and the person is informed aloud and in writing that they are speaking with an artificial intelligence.
Who can see what
The conversations, files and personal memory of a person are visible only to that person. Neither the administrator of the space nor colleagues read them: the administrator can only switch the memory off for the space, manage the company memories and the access, and remove from a role the permission to use Evo; whoever loses the permission does not lose their data, which follow the periods in section 10. In the activity log of the space the administrator sees who has deleted a conversation or a file of Evo and when, without the title or the file name. CodeDesign personnel who "enter as" another person do not access anything of Evo: all of Evo's functions refuse access on behalf of a user. The authorisations for access to the infrastructure provided for any other data of the platform remain (Annex B, paragraph 14.3). The personal memory is not accessible to the employer, there are no statistics on who writes what in memory and the audit log contains no texts; the only data that links a memory entry to a person is the author of the company memory entries, visible to the managers. A Customer who is an employer complies with Article 4 of Italian Law no. 300 of 20 May 1970 (Annex A, paragraph 8.6).
Retention, rights and deletion of the account
The retention periods of Evo's data are given in section 10, the rights in section 11 and the effects of the deletion of the account in section 15.
14. Payments and purchases through the stores
Payments made from the portal are processed by Stripe, indicated in section 8.
In the Evo Assistant app, the Evo Assistant subscription and the credit top-ups can be purchased exclusively through the App Store (Apple) or Google Play (Google). Apple and Google act as sellers: they manage the payment, issue the receipt and process the payment data and the store account data as independent controllers, according to their own privacy notices. CodeDesign does not receive the payment card data nor the name or email address of the user's Apple or Google account, does not retain the price paid nor the country of the store account and, for these purchases, does not issue an invoice.
At the end of the purchase, the app transmits to the platform servers the transaction signed by Apple or the Google Play purchase token. To activate and manage the purchase, CodeDesign extracts from it and retains: the identifiers of the transactions and of the subscription assigned by the store, the product purchased, the store environment, the dates of the purchase and of the period, the status of the automatic renewal, the events communicated by the store (renewals, cancellations, refunds), the organisation for which the purchase was made and the user who made it. The link with the organisation is obtained by means of a random code generated by the platform servers and transmitted to the store at the time of the purchase. To check the status of the purchases, the platform servers query the Apple and Google services, transmitting the identifiers of the transaction.
The cancellation of, and refund requests for, a purchase made through a store are managed in the store settings.
If the General Conditions of Use have not yet been accepted for the organisation, before the purchase the person who signs for the organisation accepts them from the app, with the recording of the data indicated in section 3.
15. Deletion of the account
The user can delete their Evolus account from the Evo Assistant app, from the "You" section, item "Delete account", or from the portal app.evolus.ai, from the profile page, item "Delete account", with the same effects. Before confirmation, a summary is shown of the organisations that will be deleted, of those the user will leave and of the subscriptions concerned. The deletion is final.
On the platform servers the deletion entails:
- the deletion of the conversations, threads, meetings, daily briefs and answers of the Evo Assistant app awaiting delivery still present, with the related attachments and audio; of memberships, roles, groups and permissions; of personal API keys, notifications and preferences; of join requests; of the personal connections to the catalogue services with the related tokens; of the notification tokens of the devices;
- where Evo is active, the deletion of Evo's personal memory (memory entries, nodes, relationships, search indexes), of Evo's files (except those saved in a library), of the conversations with Evo, including those of the agents that Evo has asked, and of their histories and of Evo's execution environment; the same data are deleted when the user leaves a space, for the data of that space, and when the user's account is deleted by CodeDesign personnel. The entries of the company memories that the user had confirmed remain with the organisation, without the user's name as author. A content that Evo is still preparing is completed, the credits are charged and the file is discarded;
- the anonymisation of the user profile: first name, last name, email address, username, telephone, address, company, language and profile image are removed or replaced;
- the deletion of the organisations of which the user is the sole owner, with the immediate closure, without refund, of the related subscriptions paid through the portal and the switching off of the renewal of Google Play subscriptions. An App Store subscription with automatic renewal active must be cancelled from the store settings before proceeding, and a paid contract managed directly by Evolus must be closed by the Provider at the user's request: while they are active, the deletion cannot be started;
- the deletion of the account from the identity system, as the last step.
The following are retained, because of legal obligations or because they belong to the organisation, and remain linked to the anonymised profile: the evidence of acceptance of the General Conditions of Use and of the clauses, which contains the data indicated in section 3, including name, email address and IP address; the invoices and payments; the audit log, for the period indicated in section 10; the consumption data; the data of the purchases made through the stores described in section 14; the projects of the organisation; the compliance records of the voice configuration; the support reports. The audit log records the deletion with only the counts of the organisations and subscriptions concerned.
On the phone from which the user deletes the account through the app, the databases of all the user's organisations, the attachments, the audio of the meetings, the mail credentials, the scheduled notifications and, if no other user is signed in on the phone, the technical log are deleted. The preferences of the phone, such as the theme and the diagnostics setting, remain. The other phones on which the user had signed in to the app, and all phones when the deletion takes place from the portal, receive a silent notification and, if they do not receive it, check the status of the account at the first sign-in attempt: in both cases they delete the same data. The data of other users present on the same phone are not affected.
Anyone who cannot access their account can request its deletion by writing to privacy@codedesign.it.
16. Amendments to the notice
CodeDesign reserves the right to update this notice to reflect regulatory, technical or organisational changes. The updated version will be published on this page with an indication of the date of last update. You are invited to consult this page periodically.
17. Meta channels: Messenger and Instagram
The Customer may connect its Facebook Page and its Instagram professional account to the platform, through Facebook Login for Business or through Instagram login, so that the messages received on Messenger and on Instagram Direct are answered by its AI assistant, one of its workflows or one of its digital employees. For these data CodeDesign acts as data processor on behalf of the Customer, which is their controller (section 2).
Data processed. The following are processed:
- for the business: identifier and name of the connected Page and Instagram account, username of the Instagram account, identifier and name of the Meta business portfolio, identifier and name of the Meta user who carried out the connection and the permissions granted, access tokens issued by Meta, stored with application-level AES 256-bit encryption in GCM mode;
- for the person who writes to the Page or to the account: the identifier that Meta assigns to them for that Page or account (PSID for Messenger, IGSID for Instagram) and the name, that is first and last name for Messenger or name and username for Instagram, read from Meta only once, at the first message; the profile picture is neither requested nor stored;
- the messages: text, type, date and time, the technical data that Meta sends with each message and the replies sent, including those written directly by the Page's operators. Voice messages are stored and transcribed; for images, videos and files the type and the file name are kept, and the file is downloaded only when the channel is assigned to a digital employee, in whose storage it is saved. When the channel is assigned to an AI assistant, the messages are also recorded in the history of its conversations.
Purposes. The data are used exclusively to receive the messages, have the replies prepared and sent, and show the conversations to the Customer's operators in the portal. They are not used for advertising, profiling or sale to third parties, nor to train artificial intelligence models.
Recipients. To prepare the replies, the text of the messages and the transcripts of the voice messages are sent to the providers of artificial intelligence models and of transcription, in the ways described in sections 7, 8 and 9. Meta Platforms receives the replies to be delivered and is a service chosen by the Customer (section 8).
Retention. The conversations of the Messenger and Instagram channels, with their messages, the stored files and the contacts' names, are deleted once they have had no new messages for the period chosen by the Customer in the "Data retention" page of the portal (from 1 to 730 days; 730 days if no choice is made), and in any case on termination of the contract in accordance with section 10. The Customer may request their earlier deletion. When the Customer deactivates the channel, the assistant stops answering the messages of that Page or account.
Data deletion requests. Anyone who has written to a Customer's Page or Instagram account may request the deletion of their messages and of their profile data by writing to privacy@codedesign.it, indicating the Page or account they wrote to and their name on Facebook or Instagram. Since the Customer is the controller of these data, CodeDesign forwards the request to the Customer in the ways set out in section 11 and carries out the deletion on its instructions, informing the requester. The request may also be addressed directly to the Customer.
18. Evo whiteboards and invited people
This section applies where Evo whiteboards are active. A whiteboard is an Evo document on which the people of the organisation draw and write together; the organisation can share it with outside people and link it to a meeting.
Who is the controller
For the whiteboard and for what guests write, vote and add to it, the data controller is the organisation that shared the whiteboard ("the controller"). CodeDesign S.r.l. provides the platform and processes this data as processor, on behalf of the controller (section 2). The notice that the platform shows guests before they enter is the tool with which the controller informs them. CodeDesign S.r.l. is an independent controller of the security log of entries (IP address, date, time and chosen name) and of the server's technical logs, for security and abuse prevention, on the basis of legitimate interest (art. 6.1.f GDPR).
What data
- Outside people with a link to view: the name they choose, the access (expiry date, entry) and the version and date of acceptance of the notice. They do not give an email.
- Outside people with an invitation to edit: in addition, the email address written by whoever invited them, the confirmation code (only its fingerprint is kept), what they write, vote and add to the whiteboard, and comments.
- Those who ask to edit: the email address they write in the form and, if they wish, a name; only whoever shared the whiteboard sees them.
- Security log of entries and technical logs: chosen name, IP address, date and time, access identifier.
- In meetings with a whiteboard: see below.
Outside people do not have an account and do not talk to Evo; whoever only has the link to view cannot edit or comment.
What it is for and on what basis
The data lets the invited person view or edit the whiteboard, shows who wrote what, checks that the invitation reached the right person and protects access from abuse. The legal basis is determined by the controller (normally performance of a relationship or legitimate interest); for CodeDesign's security log and technical logs it is legitimate interest.
For how long
The access, the session, the confirmation code and the invitation's email address are deleted 30 days after the access expires, even if it was revoked earlier. The address of whoever asks to edit is deleted 30 days after the request has been handled or, if not handled, 30 days after the link expires. The chosen name stays next to comments as long as the whiteboard exists: on request, the controller anonymises it. The security log of entries is kept for 24 months; the server's technical logs, which contain the IP address, for 90 days. Deleting the whiteboard deletes everything, including guests' data. The whiteboard keeps the last 20 saved versions and the last 20 Evo interventions, which are replaced by number and not by days.
Where the data goes and to whom
The whiteboard is kept in the platform's database and file storage, in the European Union. While people work in real time its content travels through a Microsoft service in the European Union, already listed among the sub-processors (section 8). When a person of the controller asks Evo to read the whiteboard, its text and images are sent to the model providers listed in section 8, as for any other request to Evo (section 13): this may include what an outside person wrote. Comments are not read by Evo as whiteboard text.
In meetings with a whiteboard
When a person sends Evo to a meeting with a linked whiteboard, Evo listens to the meeting in real time to recognise commands addressed to it ("Evo, …") and update the whiteboard; it can also show it on screen on request. For this: (a) the audio of each participant is sent in real time to the voice transcription provider listed in section 8, which returns the text; (b) the lines of the live transcript (who speaks, what they say, at which minute) are kept for at most 7 days, are not used for the minutes and are deleted with the meeting if it is deleted earlier; (c) at each command, Evo receives the live transcript up to that moment as context; (d) voice commands act only on the whiteboard and never on mail, calendar, libraries or other data of the person who sent Evo, which are requested from the portal chat; (e) the speaker's name is the one shown in the meeting and is not verified; (f) the whiteboard shown on screen is visible to all participants, including external ones, and can be recorded by the meeting platform. Evo writes in the meeting chat when real-time listening starts, when it starts or stops showing the whiteboard and when it cannot carry out a command. The notice that Evo writes on entering, in the language chosen for the meeting, briefly says who Evo is and on whose behalf it attends, that it records the audio and for how long, how to object and whom to contact; the details are in this section.
Rights and contact
Outside people can ask for access to, correction or deletion of their data, and for their name in comments to be made anonymous, by writing to privacy@codedesign.it: the request is forwarded to the controller within 5 working days and without undue delay (section 11). Anyone who believes the processing violates the law can lodge a complaint with the supervisory authority (in Italy, the Garante per la protezione dei dati personali, www.garanteprivacy.it).
CodeDesign S.r.l., Evolus platform. Registered office: Via Nino Pesce 38, 18018 Taggia (IM), VAT No. IT01739830089. Data protection contact: privacy@codedesign.it. Text of the notice: https://evolus.ai/en/privacy-policy.