Privacy policy.

01 Who is the controller

The data controller is Adianny Ramírez Armenteros, sole trader (Spanish NIE Y0470333C), based in Ares (A Coruña), Spain, reachable at info@saelyx.ai. Saelyx is the product's commercial brand. For special-category data (facial biometrics) you can use the same contact, which acts as our data protection point of reference.

02 What data we actually store

Saelyx is an agent with memory. So that it can remember what you ask, we do persist certain data tied to your account (identified by your email). Transparently:

• Account: email, name, plan and, if you pay, your customer identifier at the payment provider. If you sign in with your Apple or Google account, we receive from them your email and the name you share. Your password never reaches us.
• Memories. Durable facts you choose for Saelyx to remember (routines, preferences, context). May include personal information.
• Faces. If you enable "remember faces", we store the cropped face image and the derived features to recognize it later. This is special-category biometric data (see section 4).
• Scenes. Frames of objects/places you ask to recognize, with their description.
• Meetings. If you use Meeting Mode (a paid feature), we store the meeting transcript (including the voice and content of participants) for 30 days, and a distilled summary durably. It requires your recording consent (see section 4). If you connect Microsoft 365, the minutes can be copied to your OneDrive or SharePoint and sent through Outlook or the meeting’s Teams chat (see section 14).
• Learned skills. Patterns of how you work that Saelyx automatically derives from your conversations (profiling) to help you better. They make no automated decisions with legal effect. You can delete them anytime.
• Documents. The files you upload to your knowledge bases and the ones Saelyx generates for you.
• Conversation panel. The feed of your most recent conversation (text), so you can resume it across devices.
• Scheduled reminders, personal dictionary and usage metrics.
• Reports. If you report one of Saelyx’s answers from the app, we store the text of that answer and the reason you give, together with the platform and the app version, so we can review it. If the answer quoted something from your Microsoft, that text goes in the report.
• Connections with Claude. If you connect Saelyx to your Claude account, we store which connections you have and with which permissions, and a history of every access, without its content (see section 13).
• Connection with Microsoft 365. If you connect your Microsoft account, we store which account it is and with which permissions, an encrypted token to renew access, your copy preferences and the state of each copy. Actions still waiting for your confirmation are stored for a few minutes, with their content. What you import is stored in your account (see section 14).
• Technical data and logs from the app and website (version, OS, crashes, access) to diagnose and detect abuse. In logs, your email is stored pseudonymised (not in clear text).

03 What is processed on the fly (and the nuance)

Live audio is streamed in real time to the voice engine. The camera and the screen are not: Saelyx reads them on your own device, and what travels is the text it has read. Saelyx does not store them in its own systems.

In other words: the ephemerality of audio/screen in our systems is real, and at the voice engine provider we have configured it ourselves: it does not store the audio, and the transcript is deleted after 30 days. Even so, we do not enable its zero-retention mode, so we do not promise you a universal "zero retention": we tell you exactly what is kept and for how long.

04 Faces, meetings and consents

The remember-faces feature processes biometric data, which the GDPR classifies as special category (Art. 9). Therefore:

• It is off by default and is enabled only with your explicit consent, which you can withdraw at any time from the app.explicit consent, which you can withdraw at any time from the app.
• When you withdraw consent we immediately delete all remembered faces: the image, the derived features and its recognition index. (Deleting a single face does the same for that face.)
• Without that consent we do not create biometric templates or a recognition index, and Saelyx does not identify anyone, even with the camera active. That is different from storing a photo: images you upload, or that Saelyx captures at your request, may contain people and are stored in your account like any other photo, without being analysed to identify anyone.
• You are responsible for presenting to the camera only faces for which you have a legitimate basis; remember to inform those people where appropriate.

Meeting Mode records and summarises your meetings, which involves processing the voice and content of the other participants. It therefore also requires your explicit recording consent before the first meeting. When you enable it:

• You act as the controller of the participants' data: it is your responsibility to inform them and, where applicable, obtain their permission; Saelyx acts as a processor handling the meeting on your behalf (Art. 14).
• The raw transcript is kept for 30 days; the summary, durably until you delete it or close your account.

We keep a record of your consents (what you consented to, when, and with which version of the text), which you can review in your data export. We carry out a data protection impact assessment (DPIA) for these processing activities given their sensitive nature.

05 Legal bases

06 Sub-processors (who is involved)

To operate Saelyx we rely on the following providers, each under a data processing agreement (DPA):

Anthropic (Claude) is not listed in this table because, in the connector, it does not process data on Saelyx’s behalf: it is the recipient you decide to send it to (section 13).

We do not sell your data to anyone.

07 International transfers

Saelyx infrastructure is hosted in the European Union (AWS, Ireland region). Everything goes through it. Some providers (Google, Stripe, Apple, ElevenLabs, Microsoft, Tavily and Brave Search) may process data outside the EEA. In those cases, transfers rely on the mechanisms the GDPR provides —Standard Contractual Clauses (SCC) and/or the EU–US Data Privacy Framework where the provider is certified— together with the corresponding DPA. Entra and Graph, the Microsoft services your connection goes through, are global: Saelyx does not choose the region in which Microsoft processes them. And in voice, what Saelyx reads from your Microsoft to answer you passes through ElevenLabs, in the US (section 14). What you send to Claude through the connector leaves that infrastructure by your decision: Anthropic receives it and may process it outside the EEA under its own terms (section 13).

08 How long we keep data

• Account, memories, faces, scenes, skills, documents, reports: while your account is active. Deleted when you delete the account (cascade deletion).
• Meetings: the raw transcript is kept for 30 days; the summary, while your account is active.
• Conversation panel: up to 90 days from last update (renewed with use).
• Summarised sessions: 90 days. Linked devices: 180 days.
• Application logs: 90 days. Access/authentication logs: 30 days. Email in logs is pseudonymised.
• Connectors: connections, while they are active; the access history, without content, 90 days. What is generated in your account at Claude’s request, such as a document, is kept like the rest of your data (see section 13).
• Microsoft 365: the connection (account, permissions and token), until you disconnect or delete your account. Copy preferences, the state of the copies and the list of what the watched folder brought in, until you delete your account (disconnecting does not delete them). Files you import, until you delete them or delete your account.
• Microsoft actions awaiting confirmation: 10 minutes (5 for sending the minutes). What was read in web chat and in meetings without voice: 24 hours after your last message. Detail in section 14.
• Your account backups: almost all your account data (profile, memories, faces, scenes, skills, meetings, bases, files, conversation and, if you use Microsoft 365, your preferences and the state of the copies): 35 days; they are also deleted when you delete your account.
• Billing: 5 years (Spanish legal obligation).
• Audio and screen: not stored in our systems (see section 3).

09 Your rights and how to exercise them

You have the right to access, rectify, erase, object, restrict processing and data portability. The practical way:

• Export all your data (access + portability): from the app, the export option. It produces a file with all your data categories, including the consent record and —while it exists (30 days)— a link to the raw transcript of your meetings.
• Delete your account (erasure): from the app. It is irreversible and cascades through your data across our databases, files and associated indexes.
• Withdraw biometric consent: turn off "remember faces" in the app (deletes your faces immediately).
• Withdraw meeting consent: turn it off in Settings; we stop accepting new recordings.
• Withdraw consent for a connector: revoke the connection under “Connectors” in your account at saelyx.ai (see section 13).
• Withdraw the Microsoft 365 connection: in Account, “Disconnect Microsoft”. That deletes our token, not the permission in Microsoft: to remove it there, revoke access from your Microsoft account or, if it is a work or school account, ask your administrator to do it in Microsoft Entra (see section 14).
• Delete learned skills or any specific memory, face or meeting: from the app, without deleting the whole account.

You can also write to info@saelyx.ai (we reply within 72 hours) and lodge a complaint with the Spanish DPA, the AEPD.

10 Cookies

We use strictly necessary cookies and, optionally, anonymous analytics. Details in the cookie policy.

11 Minors

Saelyx is not directed at children under 18. If you believe a minor has created an account, write to us and we will delete it.

12 Changes

If we change this policy we will notify you by email before applying it, and we will review the document whenever the processing changes. Previous versions are archived and you can read them: version 8 (24 October – 14 November 2026) and version 7 (16 October – 24 October 2026) and version 6 (12 August – 16 October 2026) and version 5 (5 – 12 August 2026) and version 4 (5 August 2026) and version 3 (3 – 5 August 2026) and version 2 (2 July – 3 August 2026). There is no English version 1 — the English site did not exist yet; the Spanish version 1 (24 May – 2 July 2026) was withdrawn because it was inaccurate, as explained on that page.

This policy is written in Spanish first and translated into English. Both say the same thing — but if you ever find a difference between them, the Spanish text is the original, and we would rather know: write to info@saelyx.ai and we will fix it.

13 Connectors: Saelyx and Claude

You can connect Saelyx to your Claude account (Anthropic’s assistant, for example in claude.ai) so that Claude reads or uses parts of your Saelyx when you ask it to. It is optional, and nothing is connected until you approve it.

What Claude can do depends on the permissions you approve and on your Saelyx plan. In every case, a connection sees only the data of the account that authorised it:

• Read connection. Read your meetings with their summaries, decisions and tasks; your memory, your knowledge base, your notes and your recent conversation with Saelyx; your agenda and your reminders; and the state of your account (plan and usage). It can also put a text question to Saelyx: we answer it as if you had asked it in the app, with the same providers as in section 6 and using the same daily allowance of your plan.
• Odoo and Jira (read only). Only if you have already connected them to Saelyx and you grant that permission in that connection. Your Odoo and Jira keys stay encrypted in Saelyx: they never leave it and we never give them to Claude.
• Never through the connector: your faces and any other biometric data; what your camera and screen see; control of your computer; deleting your memory or your account; exporting or importing your data; your security settings and your billing.

How you give permission:

• Before Claude receives anything, Saelyx shows you its own consent screen: who is asking for access, with which permissions and where it returns to. Nothing is connected without your approval, and we keep that approval (which connection, with which permissions and when).
• Odoo and Jira are only included if you expressly grant them in that connection.

How you withdraw it:

• Under “Connectors”, inside your account at saelyx.ai, you see your connections and when each was last used, and you can revoke them. When you revoke one, Saelyx stops serving that connector within a minute and its renewal permission stops working; to use it again you will have to reconnect it.
• If you only disconnect Saelyx from Claude, you remove access on that side; to cancel the permissions in Saelyx as well, revoke the connection under “Connectors”.
• Revoking does not delete what Claude has already received: that sits in your Claude account and is managed there. If you delete your Saelyx account, your connections are revoked and deleted along with the rest of your data.

What we keep:

• A history of every connector access: which connection, which tool, with which permission, when, how long it took and how big the response was. Without the content: what Claude read or wrote is not copied there. It lets us show you the last use, detect abuse and protect your account, and it is kept for 90 days.
• If a question that Claude puts to Saelyx generates a document, that document is your data like any other.

What Saelyx receives from Claude. From your Claude account, nothing beyond the technical identity of the client that connects: that it is Claude, and the address it returns to after you authorise. We do not receive your conversations with Claude, nor the email or name of your Claude account, nor your Claude projects, files or memory. Only what Claude asks of us in each request, to do what you asked it to, arrives, for example the text of a search or of a question, and we treat it as if you had typed it in the app.

Other people’s data. Your meetings, and what is in your Odoo or your Jira, contain other people’s data: participants, customers, colleagues. If you give that content to Claude, you are the one who decides to send it and who answers to those people, as we already explain for Meeting Mode (section 4). That is why the full transcript of a meeting is not offered through the connector.

14 Microsoft 365

You can connect your Microsoft 365 account (work, school or personal) so that Saelyx reads and uses your email, your calendar, your tasks, your OneNote notebooks, your contacts and your files when you ask it to. It is optional, it is a paid-plan feature and nothing is connected until you approve it on the Microsoft screen. Permissions are requested in blocks and are all delegated: Saelyx acts as you, not on its own account.

These are the blocks and what each one allows. You turn on only the ones you want:

The Files block asks for permission over your whole OneDrive, because Microsoft does not allow that permission to be limited to one folder.

In total that is 16 Microsoft Graph permissions plus 4 basic identity ones (openid, profile, email and offline_access). Blocks marked with an asterisk only work with a work or school account.

When it asks you to confirm:

• With confirmation, in two steps: sending or replying to an email, creating, moving or cancelling an event, posting to a channel and sending the minutes (by email or in the meeting chat). First Saelyx prepares the action and tells you about it; it only goes out in a second step, single-use and with an expiry. There is a cap of 25 a day across emails, channel and chat messages, minutes sent and events with attendees. The server enforces the two steps; whether you said “yes” is judged by the assistant in the conversation, there is no separate check.
• Without prior confirmation: reading email, calendar, contacts, tasks, teams, channels and files; creating and completing tasks, creating the minutes’ tasks and OneNote pages; importing, saving and syncing files.
• Automatic copies: when a meeting ends, Saelyx copies the minutes to your OneDrive or SharePoint without asking. It is on by default once you save your Microsoft settings once (with a paid plan and the files block granted), and you can turn it off. The automatic copy of the transcript and of new files from your Saelyx are off by default.

What it reads from your Microsoft:

• Email. When searching, up to 25 results with sender, subject, date and an excerpt. When opening one, also recipients, body and attachment names (it does not open attachments). At most 6,000 characters of text reach the assistant in each reading, marked as third-party text.
• Calendar. Up to 30 events with title, time, place, organiser and number of attendees. When sending minutes, it looks at the meeting’s attendees to suggest recipients.
• Contacts and people. Name, email, job title and company, up to 15 results per search.
• Tasks, OneNote, teams and channels. For tasks, title, due date, list and status (up to 50). For OneNote, only the names of notebooks and sections, not the content of your pages. For teams and channels, only the names (up to 40). Saelyx has no permission to read the messages in your chats or your channels.
• Files. When browsing or searching, it lists names of folders, files, sites and libraries, with size, date and link. It only opens the content of a file when you import it or, if you have a watched folder, when you sync it.

Import and watched folder:

• Import. You choose a file from OneDrive or SharePoint and Saelyx copies it to your account: to Files (up to 25 MB) or to a knowledge base (text, up to 2 MB).
• Watched folder. You choose a folder and a base. When you press “Sync” (or ask by voice), Saelyx brings in everything new or changed in that folder (text or HTML, up to 2 MB) and removes from the base what you have deleted from it. There is no background sync.
• What stays in Saelyx. The copy, in your account, until you delete it or delete your account (in Files, with its extracted text). If you delete a file from Files or a base, the previous version is kept for 30 days; and your account’s backups, which include what you imported, for up to 35 days. What goes into a base is also restructured by a language model, so it can be searched, and kept as text fragments (up to 1,800 characters each) in the search index. If you use the connector in section 13, the assistant you connect can search your bases, including what was imported from Microsoft; through the connector it cannot read your email, tasks, contacts or Microsoft files, or write or send anything in your account. The exception is the agenda: if you have granted the Agenda block, the assistant you connect can ask for the events in your Outlook calendar (title, time, place, organiser and meeting link), and it can read in your recent conversation whatever Saelyx quoted from your email or calendar (section 13).

What we store:

• The connection. The email of your Microsoft account, the identifier of your organisation and of your account, the permissions granted, the status and the dates. To renew access without asking you to sign in again, an encrypted refresh token. For the calendar we also store a short-lived access token, also encrypted. Your Microsoft password never reaches us.
• Your preferences. Where to copy to (folder, site and library), what is copied automatically, and the watched folder with its base.
• The state of the copies. Meeting title or file name, destination, link, file fingerprint, size, dates and errors; the list of what the watched folder brought in; and the tasks and the OneNote page created from each set of minutes, so they are not duplicated. Not the content of the minutes: that goes to your Microsoft.
• Actions waiting for your confirmation. When preparing an email, an event, a channel message or the sending of the minutes, we store the full action: recipients, subject and body of the email (up to 20,000 characters); title, attendees, place and description of the event; or the channel message. For sending the minutes, recipients, subject and a note of up to 500 characters. It is valid for 10 minutes (5 for sending the minutes) and is deleted when executed or discarded. Otherwise it is marked for deletion 15 or 10 minutes after creation and the database removes it in its automatic purge, which can take up to about 48 hours. The database also keeps recovery copies: an action that has already expired may remain in them until those copies expire.
• Logs and administration. Calls to Microsoft leave codes, counts and statuses in the logs, not the content. Saelyx’s admin panel shows, per user, that a connection exists, its status, the email of the connected account and the dates; it does not show tokens.

What stays in the conversation. What Saelyx reads enters the conversation so it can answer you, and is stored depending on where you talk:

• Web chat and meetings without voice. The conversation thread stores the result of what was read, including the text of an email, for 24 hours after your last message (each new message renews it) and is then removed automatically; the database’s automatic purge can take up to about 48 hours more. Deleting your account does not delete it sooner: it expires on its own.
• Conversation panel. It keeps the text of what you and Saelyx say for 90 days (section 8). If Saelyx quotes or summarises an email or an event when answering you, it stays there.
• Voice. What Saelyx reads goes through ElevenLabs so the voice agent can answer you. ElevenLabs keeps the transcript for up to 30 days (section 6). We have not verified whether it includes the tool results: assume it does.
• Memories and skills. If what was read comes up in a conversation from which Saelyx extracts memories or skills (section 2), they may pick it up: we do not filter Microsoft tools out of that process. You can delete them whenever you like.

Other people’s data. Your email, your calendar and your contacts contain other people’s data: senders, recipients, attendees, organisers and, for your contacts, name, email, job title and company. The minutes copied to your Microsoft contain the meeting’s participants, and the transcript, their voice too. You are the one who decides to ask Saelyx to read, send or copy it, and who answers to them, as we already explained for Meeting Mode (section 4).

Where it is processed. What Saelyx stores is in the Ireland infrastructure (section 7). But the connection goes through Microsoft Entra and Microsoft Graph, global services: Saelyx does not choose the region in which Microsoft processes them, and what is in your account is wherever your organisation is in Microsoft. In voice, the results also pass through ElevenLabs, in the US.

How you withdraw it:

• Disconnect. In Account, “Disconnect Microsoft”. It disconnects everything, not block by block. It deletes the token and the connection data (account, permissions). It does not delete your copy preferences, the state of the copies, what you imported or your bases: those go when you delete your account, and files and bases also when you delete them yourself.
• Disconnecting does not revoke the permission in Microsoft. Saelyx does not tell Microsoft: the permission stays in your Microsoft account until you remove it. To remove it, revoke Saelyx’s access from your Microsoft account or, if it is a work or school account, ask your administrator to do it in Microsoft Entra (Enterprise applications, Saelyx, Properties, Delete; or Permissions, Revoke). If you revoke from Microsoft, Saelyx can no longer renew access and the connection becomes expired; no data is deleted.
• Deleting your Saelyx account. It removes the connection, the preferences, the state of the copies, what was imported, the bases and their indexes, and your account’s backups. The database recovery copies keep their data until they expire (up to 35 days). It does not delete what is in Microsoft or revoke the permission.
• What Saelyx wrote to your Microsoft stays there. Minutes, transcripts, sent emails, events, messages, tasks, OneNote pages and copied files are yours and are in your Microsoft account: we do not delete them when you disconnect or delete your account, and they do not expire on our schedule (the copied transcript is not deleted after the 30 days in section 4). Delete them in Microsoft. If the destination folder already has a file with the same name, Saelyx replaces it without asking; the previous version can only be recovered through the OneDrive or SharePoint version history, if you have it on.
• Export. Your export includes the preferences, the state of the copies, the connection data without tokens and the links to imported files. It does not include the technical list of what the watched folder brought in or the one of the minutes’ tasks.