Privacy Policy

Plain-language summary: your memories are yours. We collect the minimum needed to run the service, never send memory content to analytics, and do not train on your memory content unless you opt in to the data sharing level.

1. What Renor is

Renor provides durable memory for AI tools and agents. You connect your AI clients to Renor over MCP, and the memories you (or your agents) store can be recalled by those clients in later sessions.

Renor is for people 18 and over, or the age of majority where you live if it is higher. It is not directed at children.

2. Data we collect

Account data: your email address and authentication identifiers, processed by our authentication provider (Supabase) when you sign up or sign in.

Sign-in with Google: on the sign-in and sign-up pages your browser loads Google's sign-in script, so Google sees that visit (your IP address and browser type) before you choose anything. If you choose Google sign-in, Google provides your account identifier, email address and profile name, and Renor receives the OAuth tokens that authenticate you. The session state is held by our authentication provider (Supabase).

Workspace data: your workspace name, membership role, instance metadata, and the connection tokens you create. Connection tokens are credentials — treat them like passwords. Tokens are hashed at rest and are not stored in raw form. We also keep usage and activity metadata: a log of saves and reads (the kind of event, the tool, the client it came through, the counts afterwards and the time), the names of the AI clients you connect, your monthly call totals and how much Markdown your workspace stores. None of it contains memory text. 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.

Memory content: the memories stored through your connected clients. Memory content is stored on Renor infrastructure (currently hosted on Google Cloud, in the us-central1 region in the United States) and is used to provide the service to you. We do not use your memory content to train models unless you opt in to the data level described below, and we do not sell it. If you want your memory never to leave your own computer, you can run Renor's open-source engine yourself instead of the hosted service; see Security and your data. If you connect Claude Code or Codex with the Renor command line, Renor also stores each prompt you send (up to 8 KB) and a short record of each tool use (the tool's name, a short summary of its input and the file names, never its output or file contents) in your workspace. Text that looks like a secret is removed first, the records expire after 90 days, and you can turn this off with renor capture observe off.

Sharing with Renor: 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 policy is 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: how retrievals performed 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. Signals 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 text of the examples: 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. If you choose data, Renor may use that text 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.

Waitlist and access requests: your email address and attribution metadata, if you request access: the campaign tags of the link you followed and the site you came from, stored as its scheme and host only, never its path or query string.

Billing data: paid plans are sold by Paddle, our payment processor and merchant of record (the reseller of every order). Pressing Upgrade starts the checkout: before you pay, we send Paddle your account email, so it can find or create your customer record there, and your Renor account identifier, which is attached to the checkout so the payment is matched to your account. When you buy, Paddle receives your name, email address, billing address and payment details; it processes and keeps them under its own privacy policy, and they never touch Renor servers. Renor stores only limited billing metadata: your Paddle customer and subscription references, plan/price reference, subscription status, renewal period, and cancellation state. A subscription started before Paddle stays billed by Stripe, which holds the same kind of data for it, and for it we keep the same metadata with its Stripe references.

Product analytics: product usage events (for example "client connected", "checkout started"). Once you sign in, PostHog receives your account email and name together with these product usage events, to understand how people use Renor. Events describe actions, not content: our analytics helper rejects property names that could carry sensitive material, and we do not send memory text, prompts, or queries to analytics providers. To see which posts and links bring people to Renor, your first visit's campaign tags (the utm_ values in the link) and the site you came from, as its host name only, are kept in your browser and added to your sign-up and first-use events. Each page view of the Renor site also carries your browser's language (for example pt-BR) and the country code (for example BR) that PostHog derives from your IP address; the IP address, city, region and coordinates are discarded and not stored. When you arrive from a link, we note the campaign tag and the referring website's domain (never the full address) and keep it with your account to learn which channels bring people to Renor.

Browser storage: the Renor site and dashboard keep your sign-in session, a random analytics identifier and, if you use Import, the ids of your last import (so you can undo it) in your browser's local storage, and a timestamp the dashboard uses to reload itself at most once a minute after an update in its session storage. Once you sign in, product events are linked to your account identifier instead of the random one, and PostHog joins the random one to your account. Renor uses three small first-party cookies, set on renor.cloud and readable by all its subdomains: one remembers whether the dashboard sidebar is open, one keeps your first visit's campaign tags and referring site for 90 days, removed when you sign out, and one keeps your first visit's campaign tags and the referring site's domain for 30 days, from your first visit, even if you never sign up, until you create an account, when they are kept with your account. Neither campaign cookie is set when your browser sends Global Privacy Control or Do Not Track. Renor sets no advertising cookies.

Error reporting: when something breaks, our error-reporting processor (Sentry) receives the operation that failed, the error name, stack traces, and the IP address the report was sent from, which Sentry records with it. We never pass memory text, prompts or queries to it. If your browser sends the Global Privacy Control or Do Not Track signal, product analytics and error reporting are both turned off for that browser: no event is sent and the error reporter is not loaded.

Account email: the messages our authentication provider (Supabase) sends you, such as the sign-up confirmation, a password reset or a sign-in link or code, are sent through Brevo, which receives your email address and the content of each message, including its one-time link. Brevo records whether a sign-in or other account email was opened and whether its link was clicked, and the link in the email passes through Brevo's redirect; this is delivery tracking that Brevo applies to all transactional mail and that we cannot turn off, and Renor does not use it for marketing. Welcome, access-approved, billing-notification and product-update messages are sent through Resend, which receives your email address and the content of the message.

Product updates: we send occasional product updates to account holders, and to people who asked to receive them. They go through Resend, which receives your email address and the content of the message. Every message carries a one-click unsubscribe link; we store your unsubscribe choice and the token that link uses so the choice is honoured. You can withdraw at any time, and withdrawing does not affect messages we must send to run your account.

Mail to Renor: mail you send to a renor.cloud address passes through ImprovMX, a mail-forwarding service, which receives the message and forwards it to Renor. Replies to our emails go to Renor's own mailbox, hosted by Google (Gmail), which our automated support agent reads. These messages hold your address and whatever you write.

Hosting and delivery logs: serving the site and the dashboard produces server logs containing IP address and request metadata, kept for as long as the processor retains them. Both also load Cloudflare Web Analytics, which counts page views. The documentation site is hosted by Mintlify, which counts page views there.

3. Third-party processors

We rely on: Supabase (authentication and control-plane database), Cloudflare (domain names, website and dashboard hosting, page-view counts), Google Cloud (hosting of the memory service), Google (sign-in authentication, and Gmail for replies to our emails), Paddle (payments, as merchant of record), Stripe (payments for subscriptions started before Paddle), PostHog (product analytics: your account email and name together with product usage events, to understand how people use Renor), Sentry (error reporting), Brevo (sign-up, sign-in and password-reset email), Resend (welcome, access, billing and product-update email), ImprovMX (forwarding of mail sent to Renor), and Mintlify (documentation hosting and page counts).

External AI features: when cloud-based embedding or model features are enabled for your workspace, the relevant provider may receive memory excerpts and queries necessary to perform retrieval or evidence extraction. Which providers are used depends on deployment and configuration: today every workspace sends the memory excerpts and queries needed for search by meaning to Google Vertex AI (gemini-embedding-001), in the us-central1 region (United States), and, to name the topics of the dashboard’s memory map, a short sample of each topic’s memories to Gemini on Google Vertex AI, in its United States multi-region; the engine can also be configured to send them to Voyage AI, which no live workspace uses, or to Ollama Cloud (ollama.com), a possible evidence-extraction provider that is off unless a deployment configures it. No workspace has an evidence-extraction model configured. We keep this list current as the configuration changes.

The AI clients you connect: when ChatGPT, Claude or another AI client you chose calls a Renor tool, the memory text the tool returns goes to that client and to the company that runs it (for example OpenAI for ChatGPT, Anthropic for Claude), and from then on it is governed by that company's terms and privacy policy, not ours.

Write-time digests: a feature that is switched off by default and switched on per deployment. Where it is on, each note you save is sent (up to 20,000 characters of it) to Fireworks AI, a US company, so that a model can write once a short dated summary of what the note says, and search can then read that summary without calling a model. We use Fireworks AI's US-only endpoint. Under its terms of service Fireworks AI does not retain the content it processes beyond delivering the response and does not use it to train models. A deployment where write-time digests are off sends nothing to Fireworks AI. The summaries are kept next to your workspace's other data and are removed when the note they describe changes or is forgotten, and with the workspace on deletion.

4. What we do not do

We do not sell your data. We do not use your memory content to train models unless you opt in to the data level. We do not read your memories for advertising or profiling. We do not share your memories with other users.

5. Retention and deletion

We keep your data while your account is active. You can revoke connection tokens at any time from the dashboard, which stops clients from accessing your memories.

To delete your account and the memories associated with it, use Delete account in the dashboard’s Settings, where it is offered: you confirm with your workspace’s name, and we cancel any paid plan, revoke every connection key and agent sign-in, erase your workspace and its memories, delete the account and email you a confirmation. You can also email privacy@renor.cloud from your account address; we then process the deletion by hand and confirm to you once it is complete.

Our analytics, error-reporting and email providers keep their own logs for their own retention periods; deleting your account does not erase events already sent to 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 your sharing choice 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. Turning sharing off stops it at once and asks Renor to delete everything it holds for that workspace or install. You can also ask for deletion without changing the level by running renor-engine telemetry delete on a self-hosted install or by contacting privacy@renor.cloud. If Renor cannot be reached, the request is kept and retried; 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.

6. Your rights

Depending on where you live (for example under the Brazilian LGPD or the EU GDPR), you have rights of access, correction, portability, and deletion of your personal data. To exercise them, email privacy@renor.cloud from your account address and we will respond.

7. Security

Traffic between your clients and 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 hashed at rest and revocable. No system is perfectly secure: if a breach affects your data, we will notify you and the relevant authorities as required by law.

8. Who operates Renor

Renor is operated by Patrick Passos Agostinho, Brazil. Contact: privacy@renor.cloud.

9. Changes and contact

We will post any changes to this policy on this page. Questions or requests: privacy@renor.cloud.

Effective date: November 17, 2026.

See also Security and your data, how Renor applies the Brazilian LGPD, and our 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