Privacy Policy
1. Who the controller is
Forsnaps AI - Soluções Tecnológicas, Unipessoal Lda (VAT no. 518932494), with registered office at Rua da Igreja Nº99, Varziela, 4650-722 Felgueiras, provides the Recato service, available at recato.ai. It is the controller of the account registration, balance top-up, billing, technical log and usage measurement data and, for individual accounts, of all the account data. Where the account belongs to a company, entity or professional, the controller of the conversations, files, documents, tasks and emails processed in the service is that customer, and Forsnaps AI - Soluções Tecnológicas, Unipessoal Lda processes them on its behalf, as processor. If your data appears in that content (for example, you are a client of someone who uses Recato), please address your requests to whoever uses the service; if you contact us, we will forward the request. Contact for data protection matters: info@recato.ai.
2. What data we process and why
| Data | Purpose | Legal basis | Retention |
|---|---|---|---|
| Name, email and, if you provide them, VAT number, company and telephone (account, top-ups and contact) | Creating and managing the account; service communications | Performance of the contract | For as long as the account exists, plus 12 months |
| Conversations, attached files, derived memories | Providing the AI assistant service | Performance of the contract | A period set by the customer (configurable retention); by default, for as long as the account exists |
| Document library: files the user keeps for reuse, with the name, type, client and notes they give them and, for templates, the summary and the fields identified by the assistant | Providing the AI assistant service | Performance of the contract | Until the user deletes them or the account is deleted; not subject to the conversation retention period |
| Tasks and scheduled tasks: the request, the steps, the result and the files produced; record of the emails sent by the assistant (recipients, subject, text and attachments) | Doing what the user asked and showing them what the assistant did on their behalf | Performance of the contract | Tasks: the retention period set by the customer, counted from the last change (by default, for as long as the account exists), or until the user deletes all their conversations; a task in progress is never deleted midway; the request of a scheduled task remains until the user deletes it. Sent emails: the content is deleted with the conversation or task it came from, and only the date and status of each one remain |
| Technical logs (IP, date, browser agent) | Security, abuse detection, usage limits | Legitimate interest | 90 days |
| Billing data | Billing and tax obligations | Legal obligation | 10 years |
| AI consumption (tokens, costs) | Accounting for credits and limits | Performance of the contract | For as long as the account exists; in the former no-account trial space (until 25 October 2026), no time limit |
| Usage measurement: the step reached (wrote a first message, created an account, paid, hit a limit), whether the account has ever topped up, date and time, country, type of browser and a technical identifier of the space which, on its own, does not identify the customer. In accounts, no conversation content, no name and no email. In the former no-account trial space (until 25 October 2026), also an identifier of the guest and the text of each message sent to the assistant | Understanding at which step people stop being able to use the service, and fixing what blocks them | Legitimate interest | 12 months |
| Connected mailbox (optional): access credentials issued by the mail provider or, for IMAP/SMTP mailboxes, an encrypted username and password; the address and name of the account; the content of emails searched, read or sent by the assistant; if the user turns on inbox triage, the sender, subject, start of the text and arrival date of the most recent emails and, for each one, the category and short reason assigned to it | Reading and sending mail on the user's behalf, when they ask the assistant to, within a task or within a scheduled task; sorting the emails in the inbox into «For today», «Can wait» and «Noise», if the user turns on triage | Performance of the contract, upon voluntary connection by a user holding an account | The credentials for as long as the mailbox is connected; the content of emails read remains only in the conversation where it was used, and that of emails sent in that conversation's record of sent emails, both under the retention period for conversations; for triage, only each email's identifier, arrival date, category and reason, for up to 30 days after the email arrives, or less if the user turns off triage or the mailbox or the account is deleted (the sender's address, the subject and the text are not kept) |
| Former trial space, without an account (until 25 October 2026): conversations and files | Understanding what people asked the assistant and improving the service | Legitimate interest | No time limit |
For company and professional accounts, the purposes and legal bases for conversations, files, documents, tasks and emails are the customer's; the table describes the processing we carry out on its behalf.
The former trial space. Until 25 October 2026 the assistant could be tried without an account, in a shared space, with no name and no email. That is no longer possible: an account is needed to use the assistant. The conversations and files left there are still kept on our systems, with no time limit, and we may read them to understand what people asked the assistant and to improve the service. The cookies that space left in the browser are no longer used and expire on their own.
Account and balance. To create the account we ask for your name, email and a password, and we confirm the address by email. The account has its own space and conversations are kept for the retention period you set, whether or not the account has balance, with the same commitments: processing in the European Union and no model training. Balance top-ups are paid on the secure page of a payment service provider, which processes the payment data; we receive only the confirmation, the amount and, for the invoice, the name, email and VAT number you provide.
Creating an account or signing in with Google, Apple or Microsoft. If you use the «Continue with Google», «Continue with Apple» or «Continue with Microsoft» button, we receive your name and email from that company and use them to create your account or to sign you in. We do not receive the password of your account with that company, and we do not send you a confirmation email, because that company has already confirmed the address.
Private chat. In accounts, the private chat (in the Recato app for Android and Apple, in the «Recato — Private chat» browser extension and on the privada.recato.ai page) is encrypted on your phone or in your browser and is only decrypted inside a secure enclave, an isolated environment where the language model reads it and replies; before sending, the app, the extension or the page confirms that the enclave is genuine. Our servers only pass on the encrypted text: we cannot read it. If you close the app, the extension or the page in the middle of a response, the response carries on: we keep it encrypted, just as it arrives and without being able to read it, until you come back, and delete it as soon as you receive it or, at the latest, after 7 days; the key that opens it stays only on your phone or in your browser, also encrypted. If the assistant needs to search the web, it asks for your permission first, for each search or, if you choose, once for that conversation; only the search phrases you allow (or the addresses of the pages to open) pass through our servers to the search service, which returns the results, and they are neither stored nor logged. On the privada.recato.ai page, only the extension can confirm that the page is the published version of the code. To deduct it from the AI balance, we record for each request only sizes, the number of tokens and the model that answered (the one for text or the one for images). If you choose to keep your private chats, we store them encrypted with a key we do not have: the key stays in your phone's security chip or in your browser, where it cannot be copied, and on another device only your recovery code opens them. We do not have that code and cannot recover it: without it, and without the device where you opened them, saved private chats are lost. They follow the retention period of your other conversations.
Browser extension. The «Recato — Private chat» extension only works on recato.ai pages. It keeps, in your browser only, the session of the private chat that is open, which is deleted when you close the tab or the browser, what is needed to carry on a response left unfinished when you closed the tab (the chat and the key that opens the response, encrypted, until the response appears and for 7 days at most), the result of the check of the privada.recato.ai page and the list of published versions of the code, which it fetches from that code's public repository without sending any data from your account. It does not collect your browsing history or read other sites. The use of data handled by the extension complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
3. Where the data lives
Data is hosted and processed exclusively in data centres within the European Union. Language model inference is carried out by European sub-processors, on servers in the European Union, with no retention of requests once answered and no use of the data to train models. There are no transfers outside the European Economic Area.
If you connect your mailbox, the assistant communicates with your mail provider (Microsoft 365, or the IMAP/SMTP server you specify) through that provider's official interfaces. That provider was chosen and contracted by you and handles your emails under its own terms, including as to where its servers are located; Recato does not control it. Outside that connection, everything above continues to apply.
4. Sub-processors
We engage sub-processors for hosting in the European Union, model inference in the European Union, transactional email delivery and payment processing. All are bound by contract to the same confidentiality and security obligations.
5. We do not train models on your data
Your conversations, files and account data are never used, by us or by our sub-processors, to train, fine-tune or evaluate artificial intelligence models.
6. Retention controlled by the customer
The account owner can set a retention period (in days) after which all users' conversations, together with attached files, derived memories and finished tasks, are deleted automatically; of sent emails, only the date and status remain. They can also request complete deletion of the account. Each user can delete their own conversations at any time; the account owner neither sees nor deletes other users' conversations.
Documents kept in the library are not subject to this period: they remain until the person who saved them deletes them (for documents shared with the team, the account owner can too) or until the account is deleted. Each document is private to whoever saved it, unless they share it with the team; if that user is archived, the account owner can see and delete their documents, including private ones, for as long as that user remains archived. If that user is reactivated, they receive an email telling them so, with the names of the documents the account owner deleted.
To delete the account, follow the steps at recato.ai/eliminar-conta.
Deleted data ceases to be included in backups within a maximum of 90 days, unless a legal obligation requires it to be kept.
We do not analyse conversations with abuse classifiers, nor do we retain content or scores on that basis. Deleting a conversation also deletes the content of the emails the assistant sent from it: only the date and status of each one remain. «Delete all my conversations» also deletes finished tasks, with their files and steps; those still in progress carry on and are deleted later, under the retention period. All that remains are any documents you saved to the library and, for 30 days, a technical marker with no content that stops the deleted conversation from reappearing. Emails that were sent remain in your mailbox, like any email you send.
7. Your rights
You have the right of access, rectification, erasure, restriction, portability and objection, under the GDPR.
Portability is immediate and does not depend on us: in «My account», the «Export my data» button delivers, there and then, a file with your conversations — as data, usable by another system, and in a readable format —, the files you attached, the documents you saved in the library, the assistant's memory, the tasks and the emails the assistant wrote on your behalf. The account owner also exports the account data — users and balance, with the top-ups —, but not the other users' conversations or files. When a company's contract ends, the data of anyone who can no longer export it may be delivered to that company, at the request of its representative. You may do it as often as you wish, at no cost and without asking us first. Passwords and mailbox credentials are not part of the export: they are secrets kept on the server, not data to be returned.
To exercise the remaining rights, write to info@recato.ai. We reply within one month. You may lodge a complaint with the Portuguese data protection authority (CNPD) or with the supervisory authority of the EU country where you live or work, or where the infringement took place.
8. Connected mailbox
Connecting a mailbox is done by the user themselves, in their own account. We request from the provider only the access needed to read, organise and send mail. Organising — marking an email as read or unread, moving it to the trash, restoring it or deleting it forever from the trash — only happens when the user does it on the email screen; opening an email there marks it as read in the mailbox itself, as in any email program. For mailboxes connected with email and password, Recato keeps a copy of the emails it sends in the mailbox's own sent folder. The assistant reads only what the question or the task requires, except for inbox triage, which is off by default and which the user turns on and off in the inbox itself. With triage on, whenever the user opens the inbox, and while it stays open, the most recent emails not yet sorted first go through automatic rules (mailing lists, automatic replies, bounce notices, emails already replied to and, in Outlook, the «Other» folder). Only those the rules do not settle go to the language model, which receives only the sender, the subject, the start of the text and how long ago each email arrived, and sorts them into «For today», «Can wait» and «Noise». Only the classification is kept, that is, the category and a short reason, with the email's identifier and arrival date; never the sender's address, the subject or the text. It is kept for up to 30 days after each email arrives, and turning off triage or the mailbox deletes it immediately. Triage only reads: it does not mark emails as read, move them or delete them. It counts towards the AI balance. The assistant sends an email only after the user approves it, unless they have authorised free sending within a task or a scheduled task. Scheduled tasks run on their own, at the time and frequency the user chose, without the user being present: on each run, the assistant may search and read the connected mailbox to the extent the saved request requires and, if the user asked for it, sends them the result from their own mailbox. Authorisation to send other emails without asking is given when creating or editing the scheduled task, applies while it is active and covers only the recipients named in the request or the sender of the email being replied to. Pausing or deleting the scheduled task, or disconnecting the mailbox, stops these reads and sends immediately. Access credentials never appear in the interface; passwords for IMAP/SMTP mailboxes are encrypted with a key that exists only on the server. Disconnecting the mailbox deletes the credentials immediately. Emails that are read do not enter the assistant's memory, unless the user expressly asks for it.
9. Security
Encryption in transit (TLS) and at rest, isolation per customer (each customer, individual or company, has their own database), strong password authentication and optional two-factor authentication, encrypted backups in the European Union, access logging and rate limiting.
10. Cookies
We use only strictly necessary cookies: the session cookie (which, for accounts, lasts 30 days from the last use); the form-protection cookie; and, for accounts, one that stores only the address of your workspace, for one year, so that the site takes you straight there, and which is deleted when you sign out. We use no advertising cookies and no third-party tracking cookies.
11. Usage measurement
We measure use of the service to understand at which step people stop being able to use it — for example, how many arrive, how many get as far as writing a first message, how many create an account and how many are stopped by a limit of ours. This measurement covers the site and each customer's space.
For each step we record only: the step itself, whether the account has ever topped up, the date and time, the country and type of browser (derived from the IP address and browser agent, which are not stored), and a technical identifier of the space which, on its own, does not identify the customer or the user. Inside the application we also record which screens are opened and when: only the area and the screen, never the record shown there nor who opened it. In accounts, with or without balance, we never record the content of conversations, files, names, email addresses, tax identification numbers or any text written by the user. Until 25 October 2026, in the no-account trial space, we also recorded a technical identifier of the guest and the text of each message sent to the assistant; those records follow the retention period in the table (12 months).
Measurement is carried out by a system hosted on our own servers, in the European Union; nothing is sent to third-party analytics services. It uses no cookies and no other marker stored on the device. The basis is our legitimate interest in maintaining and improving the service, and the records are kept for 12 months. You may object to this measurement using the contact given in point 1.
12. Changes
Material changes to this policy are notified by email 30 days in advance. The version in force is always at recato.ai/privacidade.