01 Who is the controller
The data controller is Adianny Ramírez Armenteros, sole trader (Spanish NIE Y0470333C), based in Madrid, 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).
- 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.
- 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).
- 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.
This is the same for everyone. There is no different privacy deal depending on what you pay. Who hears your voice depends on the device: on Mac, iPhone and Android it is processed by ElevenLabs, which is who hears you and who speaks to you. On Apple Watch the audio goes to Amazon (Transcribe), in the EU: it leaves the watch for our European infrastructure and not to Google. The earlier path, which did pass through Google, we removed on 9 August 2026. And what Saelyx reads aloud to you is synthesised by Amazon (Polly), in the EU. When you share your screen or open the camera, Saelyx reads the text on your own device and only that text travels to the voice engines. Video is never streamed, not in Meeting Mode either. But when you ask Saelyx to look at what is in front of you, the image does leave your device: this happens when you ask it to recognise what it sees through the camera, when you save a photo to visual memory, and when you use remote desktop, which sends the full screenshot. In those cases the photo is uploaded to our storage inside your account's own space and sent to the model that describes it, which runs in the European Union (Ireland). Those images are reachable only from your account, do not expire on their own, and are deleted when you delete them or when you delete your account.
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
| Processing | Legal basis (GDPR) |
|---|---|
| Account, access and service delivery | Performance of a contract (Art. 6(1)(b)) |
| Memory, documents, panel, skills | Performance of a contract (core product function) |
| Face recognition (biometrics) | Explicit consent (Art. 9(2)(a)) |
| Meeting recording and summary | Recording consent; you act as controller towards participants (Art. 6, 14) |
| Connection with Claude: what Claude reads from your Saelyx | Consent (Art. 6(1)(a)), which you give when connecting and withdraw at any time by revoking the connection. Where other people’s data is involved (meeting voice), see section 4. |
| Learned skills (profiling) | Legitimate interest (Art. 6(1)(f)); disclosed, and they can be listed and deleted at any time, all of them or one by one. There is no way to stop them being derived again. |
| Billing | Legal obligation (Art. 6(1)(c)) |
| Logs and security / anti-abuse (including the connectors’ access history) | Legitimate interest (Art. 6(1)(f)) |
06 Sub-processors (who is involved)
To operate Saelyx we rely on the following providers, each under a data processing agreement (DPA):
| Provider | For what | Note |
|---|---|---|
| Calendar: reading your events, if you connect your Google account. | Calendar only if you connect the account, and read-only. Servers outside the EEA, under the safeguards in section 07. | |
| Amazon Web Services (incl. Bedrock) | Infrastructure (databases, storage, authentication), memory-extraction and vision models, synthesising the voice Saelyx reads aloud with, transcribing Apple Watch voice and the images you save to visual memory | Storage and databases in the Ireland region. Reasoning goes through an EU inference profile that spreads across European regions by load —Ireland, Frankfurt, Paris, Milan, Stockholm and Spain—. |
| Stripe | Payment processing | Only if you subscribe to a paid plan. |
| Twilio / SendGrid | Transactional email delivery (reminders, sign-in links) | Only your email address and the reminder content. |
| ElevenLabs | Real-time voice: the conversation audio in both directions | It receives both your microphone and the voice Saelyx answers with: it is who hears you and who speaks to you. Servers in the US, under SCCs. Their service does not store the audio: it is processed in real time and discarded. The transcript is kept for at most 30 days and is then deleted automatically. Applies to Mac, iPhone and Android. |
| Microsoft (Graph) | Reading your calendar when you connect your account | Only if you connect the account, and only the permissions you grant when connecting it. |
| Tavily and Brave Search | Web search when you ask for it | They receive the query being searched, not your identity or the rest of the conversation. |
| Apple (APNs) | Push notifications to your devices | For the reminders you schedule. |
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. 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).
- 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).
- 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.
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 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 or in Claude Code) 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.
In this connection Anthropic is not a processor for Saelyx: it is the recipient you choose. What Claude receives from Saelyx becomes part of your relationship with Anthropic and is governed by its terms, its privacy policy and your Claude plan, not by this policy. Anthropic may process that data outside the EEA.
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.