Ler em portuguêsThis is a translation. The Portuguese version prevails.

This policy explains how ALMA handles your personal data when you use Lex by ALMA ("Lex"). It starts with a summary; the details follow.

0. At a glance

  • Who is responsible: ALMA (Albuquerque de Matos, Unipessoal, Lda) provides Lex and is the controller of your data.
  • What we process: your account details, what you write in Lex (questions, topics, notes and annotations) and some technical data the service needs to work and stay secure.
  • Artificial intelligence: Lex's answers are generated by artificial intelligence (AI) from the official sources Lex finds. To do this, your question and the sources found are processed by AI models on Cloudflare. Cloudflare does not use this data to train models, and neither does ALMA. If Lex ever uses Claude, from Anthropic, it will only do so with your permission.
  • Who receives data: the recipients listed in section 8, including the people you choose to share with.
  • No advertising: we show no ads, we don't track you across other sites and we don't sell personal data.
  • Your rights: you can access, correct and delete your data, object to its processing and complain to the CNPD (the Portuguese data protection authority). You can delete your account in Lex's Settings.

1. Who is responsible

The controller of your data in Lex is:

Albuquerque de Matos, Unipessoal, Lda (ALMA)
NIPC (tax and company number) 516746596
Address: Rua Canto da Maya 1, 8.º, 1070-372 Lisboa, Portugal
Email: legal@alma.dev

ALMA has not appointed a data protection officer. For any privacy matter, write to legal@alma.dev.

What this policy covers. Lex at lex.alma.dev, its server at api.lex.alma.dev and the Lex app for iPhone, iPad and Mac (identifier dev.alma.lex), once it is available. It does not cover Lex installed by a law firm or another organisation in its own Hub: there, that organisation's privacy notice applies and, for the data that reaches ALMA, the Hub privacy policy. It also does not cover the alma.dev website, which has its own general privacy policy.

2. What we process

  • Account: name, email address, password (stored only as a cryptographic hash, never in readable form), whether you confirmed your email and, if you add one, a profile photo.
  • Signed-in devices: IP address, type of device and of browser or app, approximate location derived from the IP address (city and country), how you signed in and when it was last active.
  • Passkeys: if you create one, we store its public key, an identifier, which password manager holds it and when it was created and last used. The private key never leaves your device or your password manager.
  • Notifications: if you allow them, the device's notification token, the device name and model, and the system and app versions.
  • Preferences: for example language, theme, notifications and research options.
  • What you create in Lex: topics (the title is generated from the first question), conversations, questions, answers and cited sources, notes, annotations and the passages you highlighted, the news you follow and have read, and what you share with other people or receive from them.
  • Document requests: the official link of a document you ask us to add to Lex, kept with your account's identifier so we can show you the requests you made.
  • Error reports: when something fails in the app, it sends ALMA a report with the error and where it happened, the page address with sensitive parts removed, your account's identifier and email, the app version and technical details of the device (browser or app version, system, screen size, language, connection type, approximate memory and number of processor cores). When a request to Lex's server fails, the server keeps a log of the error with your account's identifier, the request address and technical details of the error, and may send a similar report to ALMA's error reporting system, with your account's email.
  • Communications with us: what you write to us, for example to ask for support or to exercise your rights, and our replies.
  • Acceptances: the version of the Terms of Use you accepted, the version of this policy you were shown, and when.

Required data. To create an account we need your name, email and a password; without them the account cannot be created. To answer, Lex needs your question. Everything else is optional: notifications, passkeys and sharing only exist if you use them.

3. Why and on what basis

The legal bases are those of Article 6(1) of the General Data Protection Regulation (GDPR). Retention periods are in section 10.

PurposeDataLegal basis
Create and manage your account and sessionsAccount, devices, passkeys, preferencesPerformance of the contract (point (b))
Answer your questions with AI and keep your topics and conversationsQuestions, sources found, answers, topicsPerformance of the contract (point (b))
Compare the quotes in each answer with the stored text of the sourcesAnswers and sourcesPerformance of the contract (point (b))
Annotations, news you follow, sharing and document requestsWhat you create in Lex, requestsPerformance of the contract (point (b))
Service emails: confirm your address, reset your password, tell you about changes to these textsName, emailPerformance of the contract (point (b))
Notices about your account's security, when neededEmail, session dataLegitimate interest in protecting your account (point (f))
Notifications on your device, after you allow them in the systemNotification token, notification contentPerformance of the contract (point (b))
Error reportsAs described in section 2Legitimate interest in finding and fixing faults in the service (point (f))
Security of your account and of the service, and abuse prevention (for example, limiting automated requests)IP address, device, session dataLegitimate interest in keeping the service secure and preventing abuse (point (f); GDPR Recitals 47 and 49)
Answer requests to exercise your rightsThe request and our replyLegal obligation (point (c)): GDPR Articles 12 to 22
Prove what you accepted and establish, exercise or defend legal claimsAcceptance records, communicationsLegitimate interest (point (f))
Payments and invoicing, once there are paid plans (section 12)Purchase identifiers, invoicing dataPerformance of the contract (point (b)) and legal obligation (point (c)): Article 19 of Decree-Law 28/2019 and Article 52 of the Portuguese VAT Code
MarketingWe send no marketing todayOnly with your prior consent (point (a)), which you can withdraw at any time

Sections 5 and 6 explain how we handle data about other people: those you mention in what you write, and those named in the official sources.

We do not use your data for other purposes. We do not use what you write in Lex to train AI models or for advertising. Before we process data for a new purpose, we tell you (section 17).

4. Your questions and AI

Lex's answers are generated by artificial intelligence. When you ask a question, Lex searches its collection of official sources for the relevant passages, and an AI model writes the answer from them. No person writes or reviews the answers. Each answer shows which model wrote it.

Which models.

  • Lex's own models run on Cloudflare's Workers AI service, in ALMA's Cloudflare account where Lex is hosted. They also plan each search and rank the passages found.
  • Claude, from Anthropic: Lex does not use it today. If it offers it in future, it will only use it after asking for your permission, which you will be able to withdraw in Settings, and we will tell you first (section 17).

What is sent. To write each answer, the model receives your question, the passages from the sources found and the earlier messages of the same topic.

What happens to that data.

  • Cloudflare (Workers AI): under Cloudflare's terms, it does not use this data to train models and does not keep it after answering, except in features that keep logs, such as AI Gateway. Processing happens on Cloudflare's network, in data centres in the European Union and in other countries.
  • Anthropic (Claude), if Lex uses it: processes this data on ALMA's behalf. Under Anthropic's commercial terms, it does not use it to train models and normally deletes it within 30 days. There are exceptions: if a request is flagged for a possible breach of Anthropic's usage rules, it may be kept for up to 2 years, and that request's safety classification scores for up to 7 years. The data is stored in the United States and processed in the United States or in other countries.
  • ALMA: keeps your questions and answers in your topics, in your account, until you delete them or your account. It does not use them to train models.

Quote checking. The quotes in each answer are compared automatically with the stored text of the sources, and those that are not found are flagged. The interpretation is not checked. Always check the sources before using an answer.

No automated decisions. Lex does not take decisions about you based solely on automated processing that produce legal effects concerning you or similarly significantly affect you. If we have to suspend an account, the decision is taken or reviewed by a person.

5. Information about other people you type in

In your questions, notes and annotations you may write information about other people, for example clients, parties to a case or witnesses. This section explains how we handle that information, and it is also meant to inform those people.

A request. Don't include names, tax numbers, contact details or anything else that identifies clients or other people. Describe the facts anonymously: Lex doesn't need to know who the people are to find the relevant provisions and decisions. If you are bound by professional secrecy, it is for you to decide what information you may enter.

  • What data: whatever the user writes. It may include, even indirectly, special categories of data (for example about health, racial or ethnic origin, religious or political beliefs, trade union membership or sex life) or data about criminal offences and convictions. We ask users not to include them when they identify someone.
  • What for: only to answer the question, keep the topic in the account of the person who wrote it and, if that person decides to, share it with whoever they choose.
  • Legal basis: the user's legitimate interest in doing their research and ALMA's in providing the service they asked for (GDPR Article 6(1)(f)).
  • Source: the user who wrote it.
  • Who receives it and where: the recipients and on the terms of sections 4, 8 and 9.
  • How long: as long as the topic or note exists in the account of the person who wrote it, or in a share or a shared space (sections 7 and 10).

Why we don't inform each person directly. We don't know who the people mentioned are or how to contact them, and we could only find out by reading the content of accounts, which we don't do (section 14). So we publish this information and apply these safeguards: we ask users not to identify people; we use this information for no other purpose and not to train models; ALMA's staff don't read it except in the cases in section 14; and it is deleted with the topic or the account, except in shares and shared spaces (section 10).

If you are a person mentioned. You can exercise your rights (section 15) by writing to legal@alma.dev. To help us find the information, tell us what you know, for example the email of the user who may have written it. Without that, we may not be able to locate it.

6. People named in the official sources

Lex's collection holds official texts that have already been published (Portuguese and European Union legislation, decisions of courts and other public bodies, legislative initiatives of the Portuguese Parliament) and references to academic works published in open-access repositories. These texts can name people, for example public office holders, authors, legal representatives, judges or parties to a case.

  • What for: making these texts searchable, citable and up to date in Lex.
  • What data: what the texts contain as published, normally names and roles (for example of judges, legal representatives, authors or public office holders) and, in decisions, the facts of the case as the source published them, which may include health data or data on criminal offences where the source did not anonymise them.
  • Legal basis: the legitimate interest of ALMA and of users in accessing and searching official texts that have already been published (GDPR Article 6(1)(f)), balanced against the rights of the people named.
  • Source: the official sources shown on each document, with their link.
  • Who receives it: Lex users, Cloudflare, where the collection is hosted (sections 8 and 9), and organisations that install Lex in their own Hub, which receive a copy of the collection and are responsible for it.
  • Care taken: we reproduce court decisions as the official sources publish them, normally already anonymised by those sources, and we add no personal data to the texts.
  • How long: as long as the official text is part of the collection.

Your rights. If you are named in a text in Lex, you can object to this processing or ask us to delete or hide your data by writing to legal@alma.dev with the document's link. If the request is upheld, we remove or hide that data in the collection ALMA maintains and we tell the organisations that received a copy.

7. Sharing with others

You can send topics and annotations to another person with a Lex account by entering their full email address. Lex doesn't show or search other users: it only finds the account with that exact address. Likewise, anyone who knows your account's full email address and types it in Lex learns that you have a Lex account and sees your name and your profile photo, if you added one.

The recipient of a share sees your name and what you sent, and can import a copy into their own account. The imported copy then belongs to that person and stays with them, even if you later delete the original or your account. Until the share is imported or declined, you can take it back. So that the recipient can import it, we keep a copy of what you sent until the share is declined or taken back; otherwise, until 180 days have passed since it was sent, even after it is imported. After those 180 days the share is deleted in the next automatic clean-up and can no longer be imported.

You can also save topics and annotations as a file (.lex) on your device and send it to anyone you like. That file is outside Lex: what happens to it depends on you and on whoever receives it.

If you use a space shared with other people, that space's members see what you keep in it, according to the role you give them. If you delete your account, what you kept in that space stays in it; if the space is yours, it passes to another member.

Before sharing, make sure you may share the information the topic contains, especially data about clients or other people.

8. Who receives data

This table shows who receives Lex data. The recipients marked as processors handle data on ALMA's behalf and on our instructions; they are all of Lex's processors.

RecipientWhat forWhat dataWhere
Cloudflare, Inc. (processor)Hosting Lex (server, databases, storage), network delivery and protection, Lex's own AI models (Workers AI), sending service emails and ALMA's error reporting systemThe data described in section 2 and the collection of official sources (section 6)Cloudflare's global network, headquartered in the United States. The databases and storage are not pinned to the European Union.
Anthropic Ireland, Limited, with Anthropic, PBC (United States) as its sub-processor (processor, when available)Answers by Claude, if Lex uses it and only after your permissionThe question, the sources found and the topic's earlier messagesStored in the United States; processed in the United States or in other countries
Apple (Apple Push Notification service, APNs)Delivering notifications in the app for iPhone, iPad and Mac, if you allow themThe device's notification token and the notification contentUnited States
Your browser's push service (for example Google, Mozilla, Apple or Microsoft, depending on the browser)Delivering notifications in the browser, if you allow themThe subscription address and the notification, encryptedDepends on the browser
Our email provider (processor)Receiving and keeping the emails you send usWhat you write to usMay be outside the EEA (section 9)
Other Lex usersThe shares you choose to make and the shared spaces you use (section 7)What you share and your name; and, to anyone who types your account's full email address, your name and your profile photo (section 7)In those people's accounts
Organisations that install Lex in their own HubHaving the collection of official sources in their own LexA copy of the collection, with the personal data the official texts contain (section 6); never your account's data or what you write in LexIn each organisation's own infrastructure

Where the law requires it, we may have to disclose data to public authorities or courts. Once there are paid plans, Apple (App Store purchases) and Stripe (web payments) will receive the data described in section 12.

If we change this list, we update this policy and, if the change is significant, tell you in advance (section 17).

9. Transfers outside the EEA

Some recipients are in the United States or process data in other countries outside the European Economic Area (EEA). Lex's data does not stay only in the European Union: Cloudflare and the Workers AI models may process it in data centres outside the European Union.

  • Cloudflare, Inc. (United States): participates in the EU-US Data Privacy Framework, recognised by Commission Implementing Decision (EU) 2023/1795. Cloudflare's data processing agreement provides the European Commission's standard contractual clauses as a fallback.
  • Anthropic (United States and other countries), if Lex uses Claude: standard contractual clauses approved by Commission Implementing Decision (EU) 2021/914, in Anthropic's data processing agreement. Anthropic does not participate in the EU-US Data Privacy Framework.
  • Apple (United States): the safeguards Apple itself describes in its privacy policy.
  • Browser push services and our email provider: those providers' safeguards, about which you can ask us.

You can ask for a copy of the applicable safeguards by writing to legal@alma.dev.

10. How long

DataPeriod
Account, profile and preferencesUntil you delete your account. Deleting it in Settings is immediate; if you ask by email, we do it within 30 days.
Topics, conversations, answers, notes, annotations and news you followUntil you delete them or your account
Database backupsReplaced after 30 days at most
Sessions and signed-in devices (IP address, device, approximate location, how you signed in)A session ends when you sign out or after 7 days without use. The record is deleted when you sign out, when you end the session in Settings (Sign-in & security) or when you delete your account; if the session ends because it was not used, the record may be kept until one of those moments.
Error reports sent to ALMA90 days
Lex server's error logNo fixed period: when the log passes 10,000 entries, the oldest are deleted. It is not deleted when you delete your account.
Notification tokensUntil you sign out on that device, delete your account or the token stops being valid
Copies at Anthropic, if Lex uses ClaudeNormally up to 30 days; up to 2 years if flagged; safety scores up to 7 years
Shares you sendThe copy kept for the recipient stays until the share is declined or taken back; otherwise, until 180 days after it was sent (it is deleted in the next automatic clean-up after that date), even after it is imported. The record of the share (title, summary, note and who it was sent to) is deleted at the same time, unless you take it back sooner.
Document requests (the link and the identifier of the account that made them)No set period; they are kept even after you delete your account
Support messagesAs long as needed to deal with the matter and then up to 3 years
Requests to exercise rights, and our replies3 years
Records of acceptance of the Terms and of consentsWhile the account exists and then for the limitation period of any claims they may concern
Invoicing documents, once there are web sales10 years (Article 19 of Decree-Law 28/2019 and Article 52 of the Portuguese VAT Code)
Personal data in the collection of official sourcesAs long as the official text is part of the collection; removed or hidden if an objection is upheld

When you delete your account, we delete the account and what you created in your personal Lex space. All that remains is:

  • backups, for up to 30 days;
  • copies other people imported from what you sent them;
  • shares you sent that were not declined or taken back, which the recipient can still import up to 180 days after they were sent, and the copy kept for that, even if already imported, until then;
  • what you kept in spaces shared with other people, which stays in those spaces;
  • error reports sent to ALMA, until they are 90 days old, and the entries in the server's error log with your account's identifier, until they are deleted as described above;
  • the document requests you made, with your account's identifier;
  • records the law requires us to keep.

11. Notifications and email

Notifications. You only get them if you allow them on your device or in your browser. In the app for iPhone, iPad and Mac they are delivered by the Apple Push Notification service (APNs), which receives the device's token and the notification content. In a browser they pass, encrypted, through the push service of the browser's maker. Notifications tell you what happened, for example a legislative update you follow or a share you received, and may include the name of the person who shared and the title of what they shared. Tokens are deleted when you sign out on that device or delete your account. You can turn notifications off in Lex's Settings or in your device's settings.

Email. Service emails (confirming your address, resetting your password and, when needed, notices about your account or changes to these texts) are sent from no-reply@lex.alma.dev through Cloudflare's email sending service. We send no marketing.

12. Payments (once there are paid plans)

Lex is free today and we process no payment data. Before we start selling paid plans, we will update this policy and tell you. It will work like this:

  • On the App Store: Apple sells and handles the payment, under its own terms and privacy policy. ALMA receives only purchase and subscription identifiers, to know which plan you have.
  • On the web: payments will be handled by Stripe, acting as our processor and also as an independent controller for some processing, under Stripe's privacy policy. ALMA stores no card data.
  • Invoicing: we keep invoicing documents for 10 years, as the law requires.

13. Cookies and device storage

The cookies and device storage listed in the table below are those strictly necessary to provide the service you ask for. Lex uses no advertising or analytics cookies, and no third-party tools that track your browsing. Error reports also read some data from the device, as explained at the end of this section.

WhatWhat forHow long
Session cookies (lex.alma.dev and api.lex.alma.dev)Keeping you signed in and protecting the sessionUntil you sign out or after 7 days without use
Browser local storageLanguage, theme, preferences and the state of the screen, so Lex opens as you left itUntil you clear your browser data
Service worker and app cache (web only)Loading Lex faster and showing a page when you are offlineUntil it is updated or you clear your browser data
Data the app keeps on the device (iPhone, iPad and Mac)The accounts signed in on the device (server address, name and email), preferences and texts you save to read offlineUntil you remove the account from the app or uninstall it
iCloud, if you are signed in to iCloud (app)The list of Lex servers you signed in to (server address and name, your name and email; never passwords or session keys), so your other Apple devices can offer them at sign-in. Apple keeps it in your iCloud account and ALMA has no access to it.Until you remove the account from the app

Passkeys are kept by your password manager (for example iCloud Passwords), not by Lex.

Error reports. When something fails, the app reads some technical details from the device for the error report (section 2): browser or app version, system, screen size, language, connection type, approximate memory and number of processor cores. We use them only to find and fix the fault.

14. Security and staff access

We use encrypted connections (HTTPS), store passwords only as cryptographic hashes and end sessions left unused. No system is infallible: if there is a personal data breach, we notify the CNPD as the law requires and, where the breach is likely to result in a high risk to your rights, we tell you.

Staff access to your content. ALMA's staff do not read your topics, questions, notes or annotations, except: at your request (for example, to fix a problem you report); where needed for the security of the service or to investigate abuse; or where the law requires it.

15. Your rights

  • Access: know what data we process about you and get a copy.
  • Rectification: correct inaccurate or incomplete data.
  • Erasure: ask us to delete your data, in the cases the law provides for. You can delete your account in Settings (see the support page).
  • Restriction: ask us to pause processing in certain cases, for example while we check whether the data is accurate.
  • Portability: receive the data you gave us in a structured, commonly used and machine-readable format, and pass it to another controller. You can also save your topics and annotations as a .lex file.
  • Objection: see the box below.
  • Withdrawing consent: where processing is based on consent, at any time, without affecting processing already done.

How to exercise them. Write to legal@alma.dev, preferably from your account's email. We reply within one month, which may be extended by two further months if the request is complex or there are many requests; in that case we tell you why within the first month. It is free, unless the request is manifestly unfounded or excessive, in which case we may charge a reasonable fee or refuse it, explaining why. We only ask for information to confirm your identity if we have reasonable doubts about it. When we correct or delete data at your request, we tell anyone who received it from us, unless this is impossible or involves disproportionate effort.

Complaints. You can lodge a complaint with the Comissão Nacional de Proteção de Dados (CNPD), Av. D. Carlos I, 134, 1.º, 1200-651 Lisboa, Portugal, geral@cnpd.pt, www.cnpd.pt, or with the supervisory authority of the Member State where you live, where you work or where the alleged infringement took place. You can also go to court. We would appreciate the chance to sort it out first, but you don't have to contact us before complaining.

16. Minimum age

Lex is for people aged 18 or over. We do not knowingly create accounts for minors. If you know a minor has created an account, tell us at legal@alma.dev and we will delete it.

17. Changes

This is version 1 of this policy, dated 30 October 2026. If we change it, we publish the new version with its date and keep earlier versions available on this page. Before we start processing data for a new purpose, we tell you. If the change is significant (for example a new recipient or a new transfer outside the EEA), we tell you by email or with a notice in Lex, reasonably in advance of the date it takes effect.

Versions: version 1, 30 October 2026 (current).

18. Contact

Privacy and legal matters: legal@alma.dev
Support: support@alma.dev
Albuquerque de Matos, Unipessoal, Lda, Rua Canto da Maya 1, 8.º, 1070-372 Lisboa, Portugal

See also the Lex Terms of Use, the support page and ALMA's legal information.