Privacy policy
Last updated: 13 October 2026 · Version 2.6
This policy explains which personal data Recall processes, why, how long we keep it and what your rights are. Recall is memory for AI agents: it stores what you or your software send it, so an agent can remember people across conversations.
Who we are
Recall is a trade name of Smidt Beheer, Binnendelta 11M, 1261 WZ Blaricum, the Netherlands (Chamber of Commerce/KvK 99124254, VAT NL004444074B96). In this policy "Recall", "we" and "us" mean Smidt Beheer.
For anything about privacy, email privacy@recallmem.dev, or write to the address above. We have not appointed a data protection officer.
Our two roles
- Controller. We decide how and why we process the data needed to run our business: account, sign-in, billing, usage, website and security data, and our emails with you. This policy is about that data.
- Processor. Our customers send Recall content, usually about their own users: messages, files and the memory Recall builds from them. For that content the customer is the controller, and we process it only on their instructions, under our data processing agreement (DPA).
If you use an app or agent that is built on Recall, the company behind that app decides what happens to your data. Please contact them first. If you contact us, we pass your request on to them.
What we process
| Category | What it includes | Where it comes from |
|---|---|---|
| Account data | The email address of each member of an account, the account name, roles, workspace names, settings, the names and first characters of API keys (never the keys themselves), which version of our terms each member accepted and when, and when we sent the account our getting-started emails or it turned them off. | You |
| Sign-in data | Sign-in links (stored only as a hash), dashboard sessions, and the MCP clients you connect with OAuth. | You and your devices |
| Billing data | Credit balance, top-ups, usage charges, refunds, auto top-up settings, your consent to start each purchase at once (with the version of the terms and the time) and your customer reference at Stripe. Your name, billing address, VAT number and card are entered at Stripe Checkout. We never see your full card number. | You, Stripe |
| Usage data | Number of requests, tokens and charges per task, with timestamps, and when your account first created an API key or connected an app and first stored a message. | Your use of the service |
| Technical and security data | IP address and request details, used to answer requests and enforce rate limits. For the sign-in and welcome-credit limits we store a keyed hash of your network address, never the address itself; for the welcome credit also a keyed hash of your email address. | Your device |
| Communications | Emails with our support, security reports, notices of illegal content, and our replies. | You |
| Customer content (as processor) | Messages, files, names of people (peers), sessions and workspaces, metadata, and what Recall derives from them: facts ("conclusions") with their sources, peer cards, summaries and embeddings. | You or your software |
You need to give an email address to have an account, and billing details to buy credit (tax law requires some of them). Without them we cannot provide those parts of the service.
Why we process it, and on what legal basis
| Purpose | Data | Legal basis (GDPR Art. 6(1)) |
|---|---|---|
| Provide your account, the dashboard, the API and MCP access, and sign you in | Account, sign-in, usage | Performance of our contract with you (b) |
| Charge for usage, take payments, issue invoices and handle refunds | Billing, usage | Contract (b) |
| Keep financial records that Dutch tax law requires | Billing | Legal obligation (c) |
| See where new accounts get stuck while setting up, so we can improve the service: counts of accounts that reached each first step (an API key, a first message, a first answer, a first top-up), seen only by us | Account, usage, billing | Legitimate interest (f): improving the service |
| Keep the service secure and prevent abuse: rate limits, refusing disposable email addresses, one welcome credit per email address and per network | Technical and security, account | Legitimate interest (f): a safe service and fair use of free credit |
| Send service messages: sign-in links, purchase confirmations, payment and auto top-up notices, changes to our terms or sub-processors | Account, billing | Contract (b); legal obligation (c) for purchase confirmations to consumers; legitimate interest (f) in informing customers |
| Help new accounts get started: a welcome email after sign-up, and one reminder if nothing has used the account two days later (no message stored, no app connected, no API key used). At most two emails, never to accounts older than 14 days, and each has a link to turn them off | Account, usage | Legitimate interest (f): helping new customers start using the service they signed up for |
| Record that you accepted our terms and asked us to start purchases at once | Account, billing | Contract (b); legitimate interest (f) in proving the agreement |
| Answer your questions, support requests and security reports | Communications, account | Legitimate interest (f); contract (b) where it concerns your account |
| Handle notices of illegal content and requests from authorities | Communications, account | Legal obligation (c), including the EU Digital Services Act |
| Establish, exercise or defend legal claims | The data relevant to the claim | Legitimate interest (f) |
Where we rely on a legitimate interest, we have weighed it against your interests, and you can object (see your rights).
We do not sell personal data, show ads, use third-party analytics or tracking, or use your content to train AI models. We do not send marketing email: besides service messages, new accounts only get the two getting-started emails above, which you can turn off in each of them. If that changes, we will only do it as the law allows, and you can always opt out.
Content you send
Recall stores the messages and files you send and builds memory from them. All of it is stored in our database in Frankfurt (EU). To read messages, build memory and answer questions, Recall sends text to AI models through OpenRouter (see who receives data). We look at customer content only when that is needed to give support you ask for, to investigate abuse or a security incident, or when the law requires it.
For this content you are the controller and we are your processor, under the DPA. You need a lawful basis for it and must tell the people it is about.
Plugins and integrations
The Recall plugins and integrations (for example for Claude Code, Codex, OpenClaw and Hermes) send your prompts and the agent's replies to Recall so it can learn, and load what Recall knows at the start of a session. They send this only to the Recall server you configure (api.recallmem.dev by default). Your API key stays on your computer: Claude Code keeps it in your system's credential store, and the other integrations read it from an environment variable or a configuration file you control. The plugins have a setting to turn recording off, and you can delete stored data at any time.
Who receives personal data
These service providers process data for us:
- Vercel Inc. (USA) hosts the website, the dashboard and the API. The API and dashboard run in Frankfurt (EU); the website is served from Vercel's worldwide network.
- Neon (USA) runs our database, in Frankfurt (EU).
- OpenRouter, Inc. (USA) passes our requests to AI models. The model providers it uses process the text to build memory and answer questions: currently OpenAI (USA), which also computes embeddings, and Anthropic (USA).
- Resend sends sign-in links and account emails. It receives your email address and the email, not your content.
- Stripe Payments Europe, Ltd. (Ireland) handles payments, invoices and tax calculation. Stripe also processes some payment data as a controller in its own right, for example to prevent fraud; see Stripe's privacy policy.
- Cloudflare provides DNS for our domains. It does not receive the content of your requests.
We also share personal data, where needed, with our email provider (for messages to support@recallmem.dev), our accountant or tax adviser (billing data, for our bookkeeping), authorities and courts when the law requires it, and a buyer or successor of Recall's business, who must respect this policy.
International transfers
Our database and the servers that run the API and dashboard are in the EU. Some providers are based in, or process data in, the United States: OpenRouter and the model providers it uses (such as OpenAI), and, depending on the service, Vercel, Neon, Resend and companies of the Stripe group.
The European Commission has decided that the United States protects personal data adequately only for companies certified under the EU-US Data Privacy Framework. For each transfer we rely on that certification where the provider has it, and otherwise on the European Commission's Standard Contractual Clauses, with additional measures where needed. You can ask us for a copy of these safeguards at support@recallmem.dev.
How long we keep data
| Data | How long |
|---|---|
| Customer content and memory | Until you delete it or your account. Deleting a person (peer) or your account removes the data from our database at once. Deleting a session or a workspace removes it in the background, usually within minutes. A single fact you delete is removed from our database at once. Facts the background consolidation merges or replaces stop being used at once but stay in the database, marked as replaced, until the session, person, workspace or account they belong to is deleted. |
| Account data and usage records | While your account exists. Deleted when you delete the account. |
| Credit balance and credit history | While your account exists. Deleted when you delete the account (ask for any refund first). |
| Invoices and payment records | 7 years, as Dutch tax law requires, also after you delete your account. They are kept in our Stripe account and our bookkeeping. When you delete your account we also delete your customer record at Stripe, including saved cards. |
| Record of processed payment events | Kept with our financial records. It holds only Stripe's event reference, the event type and your account's internal id. |
| Sign-in links | Valid for 15 minutes and usable once. The record (email address and hashed network address) is deleted after one day. |
| Dashboard sessions | Up to 30 days. Deleted one day after they expire or you sign out. |
| MCP connections (OAuth) | Access tokens are short-lived. Expired or used tokens are deleted after one day, revoked connections after 30 days. |
| Welcome-credit check | Keyed hashes of the network address and of the email address (with aliases of one mailbox counted as one), not linked to your account. The network hash is deleted after 35 days, the email hash after one year, so that deleting an account and signing up again does not give a second credit. |
| Background job records | Deleted one day after a job finishes, or 30 days after it fails. |
| Emails with us, security reports and notices | As long as needed to handle them and up to two years after the last message, or longer if we need them for a dispute or the law requires it. |
| Hosting logs | Kept by our hosting provider for a short period, for operations and security. |
Your rights
Under the GDPR you have the right to:
- access the personal data we hold about you and get a copy;
- rectification of data that is wrong or incomplete;
- erasure of your data;
- restriction of processing, for example while we check a complaint;
- data portability: receive your data in a machine-readable format, or have it sent to another provider;
- object to processing based on our legitimate interest;
- withdraw consent where we rely on it, without affecting processing before you withdrew.
Much of this is built in. Account owners and admins can download everything an account stores as a JSON file in the dashboard (Settings), and the owner can delete the whole account there. The API, SDKs and CLI can erase a person (DELETE /v3/workspaces/{workspace}/peers/{peer}), a session or a workspace. For anything else, email support@recallmem.dev. We answer within one month. If a request is complex, we may take two more months and will tell you why. We may ask you to confirm your identity first.
You can also complain to the Dutch Data Protection Authority, the Autoriteit Persoonsgegevens, or to the authority in the EU country where you live or work.
Automated decisions
We do not make decisions about you that have legal or similarly significant effects based solely on automated processing. Some abuse checks run automatically, such as refusing sign-up with a disposable email address or not giving welcome credit to a network that received it recently or to an email address that already received it. You can still buy credit and use Recall, and you can ask a person to review the decision at support@recallmem.dev.
Cookies
The website (recallmem.dev) sets no cookies and loads no analytics, tracking or third-party scripts or fonts.
The dashboard (app.recallmem.dev) sets two cookies that are strictly necessary for it to work. They need no consent and are never used for tracking.
| Cookie | Purpose | Lifetime |
|---|---|---|
__Host-recall_session | Keeps you signed in. It holds a random, signed token. | Until you sign out, at most 30 days |
__Host-recall_csrf | Protects the sign-in forms against cross-site request forgery. Set only while you are signed out. | 24 hours |
Both are first-party, HttpOnly and Secure. Payment pages are run by Stripe (at pay.recallmem.dev or checkout.stripe.com) and set Stripe's own cookies, for example to prevent fraud; see Stripe's cookie policy.
Security
We protect data with measures that suit the risk, such as encryption in transit, hashed keys and tokens, and strict separation between accounts. See our security page for details and for how to report a vulnerability.
Children
Recall is a service for businesses and developers. It is not meant for anyone under 16, and we do not knowingly collect their data as a controller. Customers who process data about children through Recall must meet the GDPR's rules on children's consent.
Changes
We update this policy when our processing changes, and change the date and version at the top. We announce material changes to account owners by email before they take effect. Earlier versions are available on request.
Contact
Smidt Beheer, trading as Recall · Binnendelta 11M, 1261 WZ Blaricum, the Netherlands · support@recallmem.dev