Data protection.
How Renor applies the Lei Geral de Proteção de Dados: what we process, where it is stored, how transfers work, what you can ask us for, and the places where Renor is still behind the strongest reading of the law. Every claim names its source.
Sumário em português: a Renor opera no Brasil sob a LGPD. Dados de memória ficam em nuvem própria na Google Cloud (us-central1, EUA); autenticação na Supabase e login com o Google; pagamento na Paddle, revendedora e responsável pela cobrança (assinaturas anteriores seguem na Stripe); site e painel e nomes de domínio na Cloudflare, que também conta as visualizações de página; análise de uso na PostHog, que recebe o e-mail e o nome da conta junto com os eventos de uso do produto, para entender como as pessoas usam a Renor; relatórios de erro na Sentry; e-mails de confirmação de cadastro, de redefinição de senha e de login, enviados pela Supabase, na Brevo, que registra se o e-mail foi aberto e se o link foi clicado (o link passa pelo redirecionador da Brevo; é um rastreamento de entrega que a Brevo aplica e que não podemos desativar, e a Renor não o usa para marketing); e-mails de boas-vindas, de acesso liberado, de cobrança e de novidades na Resend; correio enviado a endereços renor.cloud, pela ImprovMX; documentação na Mintlify, que conta visualizações de página. Hoje, todo espaço de trabalho envia à Google Vertex AI (gemini-embedding-001) os trechos de memória e as consultas de que a busca por significado precisa, e uma pequena amostra das memórias de cada tema ao Gemini na Google Vertex AI, em sua multirregião dos EUA, para dar nome aos temas do mapa de memórias do painel; o motor da Renor também pode ser configurado para enviá-los à Voyage AI, que nenhum espaço de trabalho ativo usa, ou ao Ollama Cloud, possível provedor de extração de evidências, desligado salvo se uma implantação o configurar, e nenhum espaço de trabalho tem modelo de extração de evidências configurado. Resumos escritos no momento da gravação são um terceiro envio, desligado por padrão e ativado por implantação: onde estiver ativo, cada nota salva é enviada (até 20.000 caracteres) à Fireworks AI (EUA), em seu endpoint exclusivo dos EUA, para que um modelo escreva uma única vez um resumo datado da nota; pelos termos da Fireworks AI, o conteúdo não é retido além da resposta nem usado para treinar modelos. Números de uso anônimos são enviados à Renor por padrão, em toda instalação própria e todo espaço hospedado, para melhorar a Renor para todos. A base legal para os números de uso anônimos enviados por padrão é o legítimo interesse (art. 7º, IX), porque os dados são anônimos, mínimos e podem ser desligados a qualquer momento: escreva para privacy@renor.cloud em um espaço hospedado ou execute renor-engine telemetry off em uma instalação própria. Uma instalação própria avisa em uma linha antes de enviar qualquer coisa: na primeira resposta que dá ao seu agente e no log de um serviço executado em segundo plano; um espaço hospedado não mostra aviso separado, e esta página e a Política de Privacidade são o aviso. O nível padrão, signals, envia só números anônimos rotulados: um registro da instalação (id aleatório, versão e commit do motor, versão principal do Node, família e arquitetura do sistema, se roda em CI e o modo de conexão); um sinal diário (nome e versão do cliente de IA, embedding, reranker e índice em uso, tamanho da memória em faixas, e por ferramenta contagem de chamadas, faixas de latência e classes de erro sanitizadas); as etapas de primeiros passos, cada uma com sua hora, sob um id aleatório criado a cada execução; uma contagem de desativações sem nenhum id; e números calculados dentro da sua própria pasta de dados a partir do registro de aprendizado: resultados de recuperação e uso posterior, resultados de gravação e totais e tempos de sessão agrupados. Cada sinal também informa, a partir de uma lista fixa, de que tipo de configuração veio: hospedada ou própria, a versão da Renor, a família do app de IA (por exemplo Claude Code ou Cursor), o conjunto de ferramentas e o provedor de embeddings e, nas instalações próprias, a família do sistema operacional e a versão principal do Node.js. Todos os campos estão em “Every field sent”, na página de telemetria do motor, com link em Security and your data. Ao receber os números, a Renor deriva da conexão só o código de duas letras do país e guarda só esse código. Nunca guardamos seu endereço IP junto com seus dados. Para impedir abusos, um código embaralhado e de mão única dele é mantido por no máximo 2 dias, separadamente, e depois apagado. Não envia texto de memória, consultas, ids de memória, chaves, nomes, nomes de arquivo nem caminhos. Para desligar os números em uma instalação própria, execute renor-engine telemetry off, peça ao seu agente ou, no ambiente dela, ative o Do Not Track ou desligue a configuração de compartilhamento da Renor (Security and your data nomeia as duas); em um espaço hospedado, escreva para privacy@renor.cloud. O nível data acrescenta a consulta que originou uma recuperação, o texto das memórias retornadas e as declarações salvas, e nunca é ligado por padrão: texto só é compartilhado depois de um sim explícito seu, em um terminal na instalação própria ou na opção “Improve Renor for everyone” do painel de um espaço hospedado; a Renor pode usar esses exemplos para treinar, avaliar e melhorar seus próprios modelos. Os dados compartilhados são mantidos pelo tempo em que ajudarem a melhorar a Renor, sem prazo fixo, e são apagados quando você pedir ou desligar a opção de texto. Não usamos seu conteúdo para treinar modelos, a menos que você opte pelo nível data, e não vendemos dados. Você pode mudar ou retirar essa escolha a qualquer momento: em um espaço hospedado, desligue “Improve Renor for everyone” no painel para parar o envio de texto, ou escreva para privacy@renor.cloud para parar também os números; em uma instalação própria, execute renor-engine telemetry off, que interrompe o compartilhamento imediatamente e pede à Renor que exclua tudo o que mantém para a instalação. Para pedir exclusão sem mudar o nível, execute renor-engine telemetry delete ou escreva para privacy@renor.cloud. Se a Renor não puder ser alcançada, o pedido fica guardado e é repetido; backups podem manter uma cópia por até mais 7 dias. Um ajuste de ranking já calculado com as linhas não pode ser desfeito, mas o próximo cálculo deixa suas linhas de fora. Você tem direito de acesso, correção, portabilidade e exclusão — escreva para privacy@renor.cloud. Somos agente de tratamento de pequeno porte (Res. ANPD 2/2022): o encarregado é dispensado pelo art. 11 e mantemos canal aberto com titulares e ANPD. Você pode excluir sua conta em Configurações, no painel, onde a opção estiver disponível (ou por e-mail); a exclusão ainda não foi verificada de ponta a ponta em produção e não apaga eventos já enviados a provedores de análise, de erros e de e-mail; os backups são automáticos, com retenção de 7 dias, e a validação de restaurar e depois excluir ainda não foi feita — preferimos dizer isso agora. Quando você chega por um link, registramos a tag de campanha e o domínio do site de origem (nunca o endereço completo) e os guardamos com a sua conta, para saber quais canais trazem pessoas à Renor. A Renor usa três pequenos cookies próprios, gravados em renor.cloud e legíveis por todos os seus subdomínios: um lembra se a barra lateral do painel está aberta, um guarda as tags de campanha e o site de origem da sua primeira visita por 90 dias, apagado quando você sai da conta, e um guarda as tags de campanha e o domínio do site de origem da sua primeira visita por 30 dias, desde a primeira visita, mesmo que você nunca crie uma conta, até você criar uma conta, quando passam a ficar com a sua conta. Nenhum dos cookies de campanha é gravado quando o seu navegador envia Global Privacy Control ou Do Not Track. A Renor não usa cookies de publicidade. Se você conectar o Claude Code ou o Codex com a linha de comando da Renor, a Renor também guarda, no seu espaço de trabalho, cada prompt que você envia (até 8 KB) e um registro curto de cada uso de ferramenta (o nome da ferramenta, um resumo curto da entrada e os nomes dos arquivos, nunca a saída nem o conteúdo dos arquivos). Texto que parece um segredo é removido antes, os registros expiram após 90 dias e você pode desligar isso com renor capture observe off.
1. Scope: what we claim, and what we do not
Renor is operated from Brazil and processes personal data under the Lei Geral de Proteção de Dados (Law 13.709/2018); this is about the operator, not about where the data is stored — that is in section 4. This page states how we apply the law, and names the source of every claim so you can check it rather than take our word for it.
We do not describe Renor as “LGPD compliant”, “certified” or “audited”. Compliance is a documented and auditable state; a badge is not evidence. Where Renor falls short of the strongest reading of the law today, this page says so in the section where it belongs — see sections 6 and 8.
Renor is designed for developers and teams building AI agents, and it is not intended for unlawful use. It is for people 18 and over, or the age of majority where they live if it is higher, and it is not directed at children. We do not knowingly create accounts for anyone younger than that. We do not verify age when an account is created.
2. Who we are: controller, operator, and who you contact
For your account data — the email address, authentication state, billing record and connection metadata listed in section 3 — Renor acts as the controller: we decide why and how that data is processed, and the purposes are the ones on this page and in our Privacy Policy.
For the memory content itself the position depends on what you are doing, and we do not describe it with one word. When you store content for your own workspace and Renor only stores, indexes and retrieves it on your request as part of the service, Renor is the controller of that processing. When you connect a workspace to your own AI client and instruct it, or store content on behalf of your own end users, you remain the controller of that content and Renor acts as your operator, processing it only on your instructions.
Renor is operated from Brazil by Patrick Passos Agostinho (see our Terms of Service, section 11). We are a small-size processing agent under Resolution CD/ANPD 2/2022, art. 2, I.
We have not appointed an encarregado (data protection officer). Small-size agents are not required to appoint one (Res. 2/2022, art. 11), provided they keep a communication channel open to data subjects and to the ANPD — we do, at privacy@renor.cloud. The rules on the role itself are set by Resolution CD/ANPD 18/2024.
Resolution CD/ANPD 2/2022 · Resolution CD/ANPD 18/2024
3. What data we process, and why
The categories are the ones in our Privacy Policy, section 2, and they are listed here as well so this page stands on its own: account data — including, when you choose Google sign-in, the account identifier, email address, profile name and OAuth tokens Google provides; workspace data, including usage and activity metadata (counts, the names of the AI clients you connect, monthly call totals), and connection tokens; the memory content you store; the email address and referral details (the site you came from, as its scheme and host only) if you ask for access when sign-up is full; billing metadata; product analytics that never carries memory text, prompts or queries, tied to a random identifier kept in your browser or, once you sign in, to your account identifier, when PostHog also receives your account email and name together with product usage events, to understand how people use Renor; error-reporting metadata — the operation that failed, the error name and stack traces; our error reporter is never passed memory text, prompts or queries; the content of each message — the sign-up, password-reset and sign-in email our authentication provider sends you, and the welcome, access and billing email we send you; your email address, unsubscribe choice and the product-update messages we send to account holders; the mail you send us and our replies (your address and whatever you write); and the server logs (IP address and request metadata) produced when the site and dashboard are served, and the page views that Cloudflare Web Analytics counts there and that Mintlify counts on the documentation site.
The legal bases are performance of a contract and your requests before entering one (LGPD art. 7, V) for the account, the workspace and the memory service; consent (art. 7, I) for an access request when sign-up is full, and for marketing email where you opted in — a consent you can withdraw at any time; compliance with a legal obligation (art. 7, II) for billing and tax records; and our legitimate interest (art. 7, IX) in keeping the service secure and working, limited to product analytics and error reporting. Sharing memory text with Renor (the data level) rests on consent (art. 7, I), which you can withdraw at any time. We do not use your memory content to train models unless you opt in to the data level, and we do not sell it.
Anonymous usage numbers are on by default, on every self-hosted install and hosted workspace, to improve Renor for everyone. The legal basis for the default anonymous usage numbers is legitimate interest (LGPD art. 7, IX), because the data is anonymous, minimal and can be switched off at any time: write to privacy@renor.cloud for a hosted workspace or run renor-engine telemetry off for a self-hosted install. A self-hosted install tells you in a one-line notice before anything is sent: in the first reply it gives your agent, and in the log of a service you run in the background. A hosted workspace shows no separate notice; this page and the Privacy Policy are how it tells you. The default level, signals, sends only anonymous labelled numbers: an install record (a random install id, the engine version and commit, the Node major version, the operating-system family and architecture, whether it runs in CI, and how it is connected); a daily heartbeat (the AI client’s name and version, which embedding, reranker and index are in use, the memory store’s size in buckets, and per-tool call counts, latency buckets and sanitized error classes); the steps of getting started, each with its hour, under a random id made for each run; a count of opt-outs that carries no id; and numbers worked out inside your own data folder from the learning log: retrieval results and whether returned memories were later opened, cited, updated or retired; save outcomes; and session totals and timing, with counts, scores, token sizes and times bucketed or rounded. Each signal also says, from a fixed list, what kind of setup it came from: hosted or self-hosted, the Renor version, the family of AI app (for example Claude Code or Cursor), the tool set and embedding provider, and for self-hosted installs the operating system family and Node.js major version. Every field is listed under “Every field sent” on the engine’s telemetry page, linked from Security and your data. When the numbers arrive, Renor works out the two-letter country code from the connection and stores only that code. We never store your IP address with your data. To stop abuse, a scrambled one-way code of it is kept for at most 2 days, separately, and then deleted. It sends no memory text, queries, memory ids, keys, names, file names or paths. To turn the numbers off on a self-hosted install, run renor-engine telemetry off, tell your agent, or turn on Do Not Track or set Renor’s sharing setting to off in its environment (Security and your data names both settings); for a hosted workspace, write to privacy@renor.cloud. The data level sends those signals plus the query behind a retrieval, the text of the memories it returned, and the statements you saved. It is never on by default: text is shared only after you explicitly say yes, at a terminal on a self-hosted install or with the “Improve Renor for everyone” switch in a hosted workspace’s dashboard. At that level, Renor may use those examples to train, evaluate and improve its own models. Shared data is kept for as long as it helps improve Renor, with no fixed period, and is deleted when you ask or when you turn the text switch off.
Memory content is never sent to analytics, and connection tokens are stored hashed, never in raw form. Workspaces created before 9 October 2026 were given a public web address containing a name derived from the part of the account email before "@". Those addresses appear in public certificate logs, which cannot be deleted. Since 9 October 2026, new workspaces get a name that does not come from your email.
4. Where your data is stored, and international transfers
Your memory content is stored on Renor-controlled infrastructure hosted on Google Cloud, currently in the us-central1 region (United States). Account records live in Supabase; signing in with Google is handled by Google, whose sign-in script also loads on our sign-in and sign-up pages before you choose it; the site and dashboard are served by Cloudflare, which also handles domain names and counts page views; the documentation site is hosted by Mintlify, which counts page views there; payments are handled by Paddle, our merchant of record (subscriptions started before Paddle stay with Stripe); error reporting is Sentry; the sign-up, password-reset and sign-in email our authentication provider sends goes through Brevo, and the welcome, access, billing and product-update email through Resend; mail sent to renor.cloud addresses passes through ImprovMX on its way to Renor, and replies to our emails go to a Gmail mailbox. Our Privacy Policy, section 3, keeps this list current.
When cloud embedding or model features are enabled for a workspace, the relevant provider receives the memory excerpts and queries needed to perform retrieval or evidence extraction. That hop is configured per deployment: on the hosted service today, every workspace sends the memory excerpts and queries needed for search by meaning to Google Vertex AI (gemini-embedding-001), and a short sample of each topic’s memories to Gemini on Google Vertex AI, in its United States multi-region, to name the topics of the dashboard’s memory map. The engine can also be configured to send them to Voyage AI — named here so that provider cannot be reached without disclosure, and used by no live workspace today. It can also be configured to send them to Ollama Cloud, a possible evidence-extraction provider that is off unless a deployment configures it. No workspace has an evidence-extraction model configured.
Write-time digests are a third hop, switched off by default and switched on per deployment. Where the feature is on, each saved note is sent (up to 20,000 characters of it) to Fireworks AI (United States), through its US-only endpoint, so that a model can write once a short dated summary of the note; search then reads the summary without calling a model. Under its terms of service Fireworks AI does not retain that content beyond delivering the response and does not train on it. A deployment where the feature is off sends nothing to Fireworks AI. We have not yet confirmed that the executed agreement with Fireworks AI carries the standard contractual clauses of Resolution CD/ANPD 19/2024: its data-processing addendum, as published, has none for Brazil.
Because your data is processed outside Brazil, we rely on the transfer mechanisms that the LGPD provides for. The European Union is recognised by the ANPD as providing an adequate level of protection (Res. 32/2026). The United States is not covered by that recognition, so the transfer mechanism the law provides for those hops is the standard contractual clauses of Resolution CD/ANPD 19/2024, alongside any specific contractual clauses and the processors’ own transfer terms.
Art. 2, sole paragraph, of that resolution gave arrangements already in place 12 months from 23 August 2024 to incorporate those standard contractual clauses. That transition window closed on 23 August 2025, so the clauses are the mechanism these transfers require today rather than an incorporation still in progress. We do not assert that each executed agreement carries them: the agreements are the only evidence, they are not published here, and our internal posture record keeps that verification on its open list instead of describing it as complete.
Resolution CD/ANPD 19/2024 · Resolution CD/ANPD 32/2026
5. Security measures
Traffic to Renor’s public endpoints is protected with HTTPS/TLS. The engines are not reachable from the internet: each one listens on the host’s loopback interface only, behind the one proxy that terminates TLS, and the host is administered over SSH with a key rather than a password. Connection tokens are stored hashed and are revocable by you at any time from the dashboard; each workspace’s memory is kept in a separate per-workspace store and resolved per request by the gateway, with no shared fallback. Tenant processes run under per-workspace resource limits.
One limit belongs in this section rather than in a footnote: the engines are still reached over one shared operator credential (the gateway secret, the same value in the gateway and in every workspace engine) rather than per-workspace ones. Each workspace is kept separate, and its files cannot be read by another workspace’s process; the shared credential means isolation between workspaces still rests partly on the gateway and engines refusing requests, so it is not yet a complete privilege boundary. Per-workspace credentials are the fix, and they are not in place yet.
We do not maintain a simplified information-security policy yet. We are writing one, proportionate to our size and risk, as Resolution CD/ANPD 2/2022 (art. 13) provides for, and we will publish it here once it exists. No system is perfectly secure, and we do not claim otherwise; section 7 covers what we do if something goes wrong.
6. Your rights, and how to exercise them
Under LGPD art. 18 you may request confirmation that we process your data, access to it, correction of incomplete or inaccurate data, anonymisation, blocking or deletion of unnecessary or excessive data, portability of the data you provided, and information about who we share it with. Where processing rests on consent, you may withdraw it (art. 8, §5) and we will stop that processing.
Write to privacy@renor.cloud from your account address. We answer within 15 days for the simplified declaration under art. 19, I (Res. 2/2022, art. 15) and within 30 days for access and correction requests — 15 days under LGPD art. 19, II, doubled for small-size agents by Res. 2/2022 (art. 14, I). If we cannot meet a deadline, we will tell you why and when we will.
You can revoke connection tokens yourself at any time from the dashboard, which immediately stops clients from reaching your memories. You can delete your account yourself from the dashboard’s Settings, where it is offered: it cancels any paid plan, revokes every key and agent sign-in, erases the workspace and the account, and confirms by email. Otherwise the operator handles a request sent by email and confirms to you when it is complete. Both paths have been tested only on local stand-ins: the production path has not yet been run end to end on a test workspace, which our data-deletion runbook requires before the procedure is treated as operationally verified.
7. Security incidents
If a security incident may create relevant risk or harm to you, we will communicate it to you and to the ANPD, in the form and with the content that Resolution CD/ANPD 15/2024 requires, and we will publish notice where the law requires broad disclosure. We aim to notify in under three business days, within the window that resolution sets (art. 6); small-size agents have additional time under Res. 2/2022, art. 14, II, and we do not intend to use it unless we must. That path is untested as well: we have not rehearsed a notification against the clock, and the incident-response runbook that governs it is not published yet.
When we notify, we record the incident, its scope and the measures taken, keeping that record in the simplified form Res. 2/2022 (art. 9) allows — the same simplified form section 9 uses for the processing record itself.
Resolution CD/ANPD 15/2024 · Resolution CD/ANPD 2/2022
8. How long we keep data, and where this page is still incomplete
We keep your data while your account is active. Account and control-plane records are deleted on request; billing metadata is kept for the accounting and tax periods the law requires (LGPD art. 16, I) — references only, never memory content. Events already sent to our analytics, error-reporting and email providers stay in their logs for their own retention periods; deleting your account does not erase them. Paddle, our merchant of record, keeps its own payment records as the law requires; deleting an account cancels the subscription but does not erase those records.
You can change or withdraw sharing at any time. For a hosted workspace, turn off “Improve Renor for everyone” in the dashboard to stop sharing memory text, or write to privacy@renor.cloud to stop the usage numbers as well; for a self-hosted install, run renor-engine telemetry off: sharing stops at once and Renor is asked to delete everything it holds for that workspace or install. A self-hosted user can instead run renor-engine telemetry delete to ask for deletion without changing the level; anyone can contact privacy@renor.cloud. If Renor cannot be reached, the request is kept and retried, and backups can hold a copy for up to 7 more days. A ranking setting already fitted from shared rows cannot be recalled, but the next fit leaves your rows out.
Three things Renor does not have yet, stated plainly:
- Self-service deletion is new and not yet verified in production. Settings offers Delete account where it is switched on; otherwise a request goes to the operator by email, and the operator confirms completion.
- We do not yet validate restore-then-delete. Backups are scheduled: our engine host is covered by a daily snapshot policy that keeps each snapshot for 7 days and keeps it even if the disk is deleted. A restored backup could still in principle re-expose data that was deleted after the backup was taken, so deletion is not asserted for the backup copies — and, as section 6 says, the procedure itself has not been run end to end yet, so it is not validated for the live records either.
- Product updates to account holders rest on a basis we have not settled. We send occasional product updates to account holders, and every message carries a one-click unsubscribe. The consent we record covers the people who asked for updates; for account holders who never did, we are establishing the basis before sending further. Nothing in the product stops a send in the meantime — the shipped default still mails every account holder who has not unsubscribed — so until the basis is settled this page describes the mechanism and does not claim a basis for it.
We would rather say this here than let you discover it in an incident review or a procurement questionnaire. Our data-deletion runbook is published in the product repository and says the same thing.
9. Assessment, records, and how this changes
We keep a simplified record of our processing operations (LGPD art. 37) as Res. 2/2022 (art. 9) allows, and we reassess our processing when we add a new data category, a new processor, a new region, or a feature that changes the risk — a high-risk activity such as systematic profiling or large-scale sensitive-data processing would move us out of the small-size-agent regime, and that is a decision we would take deliberately and document here.
The ANPD may require us to prove that we qualify as a small-size agent, and may require us to comply with obligations this regime waives; we keep the evidence for that in section 2 (Res. 2/2022, arts. 5 and 16).
We will update this page when a mechanism changes — for example, when self-service deletion has been run end to end in production, when a restore-then-delete test has passed on a disposable workspace, when the simplified information-security policy in section 5 exists, and when an age check exists at signup. We publish what is true at the time of writing and date it, rather than promising a state we are not in yet.
Effective date: 17 November 2026.
Questions or requests: privacy@renor.cloud — see also our Privacy Policy and Terms of Service.
Renor home Durable memory for AI. Your agents stop starting from zero.
Product How it works Docs Research Culture Press Install Blog Pricing Status
Account Get started Sign in
Legal Security Privacy Data protection Terms Refunds Support
© 2026 Renor