Privacy Policy
Last updated: November 14, 2026
Contents · 18 sections
This is a convenience translation. The German version is the legally binding one.
1. Controller
The controller within the meaning of the General Data Protection Regulation (GDPR) is:
Narveno
Owner: Thomas Iovine
c/o flexdienst – #20454
Kurt-Schumacher-Straße 76
67663 Kaiserslautern, Germany
Email: privacy@memexa.ai
No data protection officer has been appointed, as the legal requirements for a mandatory appointment (§ 38 BDSG, Art. 37 GDPR) are not met. We answer privacy requests at privacy@memexa.ai.
2. Principle: your data belongs to you
Memexa is a hosted, model-neutral memory for your AI. Your notes, documents, emails and the resulting knowledge graph are processed solely to provide the service to you. We do not train AI models on your content, do not analyse it for advertising and do not pass it on to third parties for advertising or training purposes. AI services we use (see section 9) process content only to fulfil the respective function (text recognition, embeddings, answer generation, relevance ranking) and not for model training.
Your content (storage, search, graph, document processing) is processed on EU infrastructure operated by European providers. Which AI app reads it is your decision (section 8).
3. What data we process
- Account data: email address and login/session information (one-time code sent by email, no passwords).
- Content data: the notes you create, uploaded documents, emails forwarded to your memory including attachments, and the texts, embeddings and links extracted from them.
- Usage and billing data: consumed pages/volume for limit calculation and, for paid plans, order and subscription status via our payment provider Creem (section 10). We do not store full payment details.
- Technical data: server logs (IP address, timestamp, endpoint) to ensure operation and security. If an error occurs, we process diagnostic data (error type, message, stack trace) via a self-hosted error-reporting service on our own EU infrastructure, without note content and without IP addresses; personal data is removed before transmission. For quality assurance of the AI features we also operate a self-hosted evaluation instance on our own EU infrastructure; no data is shared with third parties here either.
4. Purposes and legal bases
Processing is carried out to perform the user agreement (Art. 6 (1)(b) GDPR), to comply with legal obligations (Art. 6 (1)(c) GDPR, e.g. retention of billing records) and on the basis of our legitimate interest in a secure, functioning service (Art. 6 (1)(f) GDPR, e.g. server logs and abuse prevention). Where consent is required (Art. 6 (1)(a) GDPR), we obtain it; you can withdraw it at any time with effect for the future.
5. Cookies
Memexa only sets technically necessary cookies (session login). Details in the cookie policy. Legal basis: § 25 (2) no. 2 TDDDG, Art. 6 (1)(b) GDPR. The visitor statistics on this website work without cookies (section 5a).
5a. Visitor statistics on this website (Plausible)
On this website (memexa.ai) we count visits with Plausible Analytics. The provider is Plausible Insights OÜ, Tallinn, Estonia; the data is processed in the EU. Plausible acts as our processor (Art. 28 GDPR). This applies to this marketing website only: the Memexa app (brain.memexa.ai) and the Web Clipper have no visitor statistics.
Purpose: we want to know which pages are read and where visitors come from, so we can improve the website. What is recorded: the page viewed, the referring page (referrer), the country and, roughly, the device type, browser and operating system. The result is aggregated statistics; Plausible does not build profiles of individual people.
No cookies, no stored IP address: Plausible sets no cookies and stores nothing on your device. IP addresses are not stored. To count visits, Plausible uses a hash that changes daily, so you are not recognised from one day to the next. The script and the measurement data run through our own domain (memexa.ai/js/…), so your browser does not load anything directly from a third party.
Legal basis: Art. 6 (1)(f) GDPR. Our legitimate interest is privacy-friendly audience measurement to improve the website. § 25 (1) TDDDG does not apply because nothing is stored on your device; we therefore do not ask for consent.
Objection: you can object to this processing at any time (Art. 21 GDPR) by writing informally to privacy@memexa.ai. Because we do not recognise you, you can also prevent the counting yourself by blocking scripts from memexa.ai/js/ in your browser, for example with a content blocker.
6. Email capture: emails forwarded to your memory
You can forward emails to a personal capture address of your account. These emails including attachments are received, processed and stored as content in your memory; related messages are merged into conversations.
In doing so we inevitably also process personal data of third parties, such as the name, email address and message content of senders and other participants in the email thread. This processing takes place exclusively on your behalf and for your private knowledge archive; the content is accessible only to you. Legal bases: Art. 6 (1)(b) GDPR (towards you) and Art. 6 (1)(f) GDPR (with regard to third parties; our and your legitimate interest in the filing of your correspondence initiated by you). You are responsible for only feeding in emails that you have lawfully received and are permitted to store. If you delete a conversation or your account, the associated data is deleted (section 11).
We use a European email service provider (EU, France) as a processor for receiving incoming emails (section 9).
7. Emails from us to you
We send you transactional emails (login codes, “document processed”, billing receipts) and (if enabled) summary digest notifications about your memory. Legal basis: Art. 6 (1)(b) GDPR. You can unsubscribe from digest notifications at any time in the settings. We only send marketing newsletters with your consent.
Cancellation and withdrawal forms: Via “Cancel contracts here” (/en/cancel) and “Withdraw from contract” (/en/withdrawal) you can declare a cancellation or a withdrawal without an account. We process your name, the email address you enter, optionally the contract or order number, for a cancellation its type, the reason and the requested date, for a withdrawal the contract concerned, optionally the date the contract was concluded and your message, plus the time of receipt and the language. Purpose: processing and carrying out your declaration, the legally required confirmation of receipt by email, and proof of receipt. Legal basis: Art. 6 (1)(b) and (c) GDPR in conjunction with §§ 312k, 356a of the German Civil Code (BGB). For a cancellation we send a confirmation link to the email address of the associated account so that nobody cancels someone else's contract; we only store a hash of this link. Recipients are our email delivery service Scaleway Transactional Email (Scaleway SAS, Paris, France; section 9) and (to carry out the cancellation or a refund) Creem (section 10). We process your IP address only transiently in memory to limit abuse (at most one hour) and do not store it. You do not need an account. We keep the declarations for three years from receipt (standard limitation period, § 195 BGB, as proof); after that we delete name, email address, free texts and numbers and keep only a pseudonymous hash of the email address, the time of receipt, the type of declaration and the processing status (for cancellations, the affected subscription ID at Creem).
8. MCP access by your AI apps
You connect your own AI apps (AI clients such as Claude, ChatGPT or local models) to your Memexa account via the Model Context Protocol (MCP). Access is granted via an OAuth token issued per account; an AI app reads and writes exclusively in your own memory.
Important: when your AI app retrieves content, it transmits it to the provider of the model you have chosen, depending on the provider, also outside the EU. What that provider does with the content is governed by its own privacy policy and is outside our control. The choice of AI app is your decision; our own processing scope (storage, search, graph, document processing) remains unaffected within the EU.
The Ask/chat feature in the web interface uses the AI model of a European provider (EU, France; section 9): your question, relevant excerpts from your content and your profile details are passed to the model as context to generate the answer. You are therefore interacting with an AI system; answers may contain errors and are not binding information.
8a. Browser extension “Memexa Web Clipper”
The Memexa Web Clipper is an optional extension for Google Chrome. Its single purpose is to save web pages, text selections, images and videos you choose into your own Memexa account and to let you ask your memory questions from the browser. It only works with a Memexa account.
What the extension processes, and when:
- Current page (when you open the extension): when you click the Memexa icon, the extension reads the address, title, your text selection and the content (HTML) of the active tab to show you a preview. This happens locally in your browser; nothing is transmitted yet.
- Saving a page or selection (only when you click “Save to Memexa” or “Save selection”): the page address, title and either the page content (HTML, up to about 500,000 characters) or the selected text are sent to Memexa. Our server extracts the readable text and stores it as a document in your memory.
- Saving a video (only when you click “Save video”): only the address of the video is sent. Our servers then retrieve the video from the platform and create a transcript (AI services, section 9).
- Saving an image (only via right-click “Save image to Memexa”): the extension reads the image you clicked from the page and uploads it, with its file name and type, to our EU object storage via a time-limited upload link issued by Memexa.
- Questions (only when you send one): the question you type is sent to Memexa and answered as described for the Ask/chat feature in section 8.
- Sign-in data (stored only in your browser): the extension signs in to your Memexa
account via OAuth 2.1 with PKCE in a Memexa sign-in window. The resulting access and refresh
tokens, the extension's client registration and your choice of workspace are stored in the
extension's local browser storage (
chrome.storage.local). The extension does not access your Google account.
The extension does not record your browsing history, has no content scripts that run on pages by
themselves and contains no analytics, tracking or advertising code. It communicates exclusively over
HTTPS with Memexa (brain.memexa.ai) and, for image uploads, with our object storage in
the EU (France).
Purpose and legal basis: the data is processed solely to provide the function you triggered: saving the content into your Memexa account, processing it there (sections 3 and 9) and answering your questions. Legal basis is Art. 6 (1)(b) GDPR. Saved content is processed like all other content in your memory, on EU infrastructure.
No sale, no advertising: we do not sell data from the extension and do not transfer it to third parties, except to the processors listed in section 9 to the extent necessary to provide the function, or where required by law. We do not use it for advertising (including personalised advertising), to determine creditworthiness or for lending purposes, or to train AI models. The use and transfer of information received through the extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Retention and deletion: saved pages, images, videos and the resulting notes remain
in your memory until you delete them or your account (section 11). “Disconnect” in the extension
revokes its access at Memexa and removes the tokens from your browser; uninstalling the extension
(chrome://extensions → “Remove”) deletes all data it stored locally.
Questions about the extension: privacy@memexa.ai.
9. Processors and sub-processors
We use carefully selected service providers under data processing agreements (Art. 28 GDPR) and host and process primarily in the EU with European providers. The overview below lists the categories of recipients (Art. 13 (1)(e) GDPR). Where a provider or its subcontractors process data outside the EU (e.g. edge/log data of our CDN provider or subcontractors of our payment provider), this is safeguarded by appropriate guarantees under Chapter V GDPR, in particular Standard Contractual Clauses (SCC).
| Category | Purpose | Region |
|---|---|---|
| Cloud infrastructure (hosting, database, object storage) | Operating the application (app, MCP endpoint, workers), storing notes, metadata, account and billing status, embeddings and uploaded original files | EU (France) |
| Email delivery service (Scaleway Transactional Email, Scaleway SAS, Paris) | Transactional emails (login codes, notifications, receipts) | EU (France) |
| Email receiving service | Receiving incoming emails (email capture) | EU (France) |
| AI services | Text recognition (OCR), embeddings, link suggestions, answer generation (Ask/chat) and relevance ranking of search results. Context may contain personal data; no model training on your data | OCR, embeddings, distillation, transcription: EU (France). Relevance ranking: EU (Germany, data centre Berlin), see trust page |
| Visitor statistics (Plausible Insights OÜ, Estonia) | Cookieless, aggregated visitor statistics for this marketing website only, not in the app (section 5a) | EU |
| CDN/network provider | DNS, CDN/edge plus WAF and DDoS protection | EU provider; global edge locations, log/request data possibly outside the EU (SCC) |
| Creem (payment provider, Armitage Labs OÜ) | Payment processing and subscription management as merchant of record (paid plans only) | Tallinn, Estonia; US subcontractors under SCCs (see section 10) |
We will provide a list naming the processors currently in use on request at privacy@memexa.ai.
10. Payment processing via Creem
Paid plans are handled by Creem as merchant of record. The provider is Armitage Labs OÜ, Rotermanni tn 14, 10111 Tallinn, Estonia (registry code 16977866). For the purchase, Creem acts as your contractual partner for the payment, processes your payment data under its own data protection responsibility and issues the invoice. Creem uses subprocessors in the US as well; these transfers are safeguarded by EU standard contractual clauses (SCCs). Details and the current list at creem.io/dpa. We do not receive full payment details from Creem, only the order and subscription status information required to activate your plan. Creem's privacy policy applies in addition.
10a. Our profiles on social networks
We run profiles on Instagram, Facebook, TikTok, YouTube, X, Mastodon and Bluesky to inform people about Memexa and to stay in touch with those interested. The links are in the footer of this website.
On this website the network icons are plain links. We do not embed social media plugins, embedded videos or tracking pixels. No data goes to a network until you click a link and open its page.
What the networks process: When you visit one of our profiles, the respective operator processes your data (for example IP address, device and usage data and, if you are logged in, your account data) under its own responsibility and its own privacy policy, often also for advertising. Some operators transfer data to countries outside the EU, in particular the USA, and state that they rely on the EU-US Data Privacy Framework or on standard contractual clauses. We have no influence on this processing. From the networks we only receive aggregated statistics (such as reach, views, broad age groups and countries) that do not let us identify individual people.
What we process: Content you send us there (comments, mentions, direct messages) and your public profile name, so we can reply and manage our profiles. The legal basis is our legitimate interest in informing people about our service and communicating with you (Art. 6(1)(f) GDPR). If it concerns a contract with us or a request about one, the basis is Art. 6(1)(b) GDPR. We delete direct messages once your request is resolved and no statutory retention period applies. Public comments stay visible until you or we delete them. Please do not send us sensitive data via social networks; for questions about your account use support@memexa.ai.
Joint controllership with Meta: For the statistics of our Facebook Page (“Page Insights”) we are joint controllers with Meta Platforms Ireland Limited, Merrion Road, Dublin 4, Ireland (Art. 26 GDPR). In an agreement with us, Meta has taken primary responsibility for this processing, including handling your rights: Page Insights Controller Addendum. Where Instagram or other networks provide us with statistics, joint controllership may also exist; the agreements the respective operator offers for this then apply.
| Network | Operator for users in the EU | Privacy information |
|---|---|---|
| Instagram, Facebook | Meta Platforms Ireland Limited, Ireland | Instagram, Facebook |
| TikTok | TikTok Technology Limited, Ireland | tiktok.com |
| YouTube | Google Ireland Limited, Ireland | policies.google.com |
| X | Twitter International Unlimited Company, Ireland | x.com/privacy |
| Mastodon (mastodon.social) | Mastodon gGmbH, Germany | mastodon.social |
| Bluesky | Bluesky Social, PBC, USA | bsky.social |
Your rights (section 12) can be exercised against us, including for processing by a network; we then forward requests to the operator. They usually take effect fastest directly with the operator, as only it has access to your user data. You can change how a network shows you ads in your account settings there.
10b. Referral programme
Purpose and legal basis. When you enter a referral code or open a referral link, we store the code, the time and the status of the attribution (attributed, paid, rejected) so we can grant the start pack (500 pages) after your first payment (Art. 6(1)(b) GDPR, pre-contractual steps and performance; Art. 6(1)(f) GDPR for abuse prevention such as self-referrals).
No cookie. The referral link sets no cookie and uses no browser storage. The code lives in the address and the form until you sign in.
Your own code. Every user gets a random code. We store it with your account and two counters (sign-ups and paying referrals). We never show you who signed up with your code, only the counters. Your code and status can also be read in your connected AI apps through the Memexa tool “get_referral_info”, your own data only.
Commission via Creem (only if you activate it). If you activate commission we pass your name and email address to our payment provider Creem (section 10) so that Creem can invite you to its affiliate programme (Art. 6(1)(b) GDPR). Creem processes your data as an independent controller (commission accounting, payouts, identity checks, tax documents). Creem decides what its affiliate portal shows you about referrals. We don't pass any data about the friends you refer on to you.
Retention. Attribution and start-pack record: until your account is deleted. On deletion all opt-in and attribution data is removed. The code itself remains as a blocked entry without personal data so it is never reissued. You close your affiliate account at Creem yourself.
The programme rules are in the Referral Programme Terms. Your rights (section 12) apply here too.
11. Retention
We store content and account data for as long as your account exists. After you delete your account, your content is deleted; statutory retention periods (e.g. for billing records, § 147 AO, § 257 HGB) remain unaffected. You can delete individual notes, documents and email conversations yourself at any time. You can export all your content and account data yourself at any time as a ZIP archive (Markdown and JSON, “Settings” → “Export”). This also covers your right to data portability (Art. 20 GDPR).
12. Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection to processing based on legitimate interests (Art. 21). You can withdraw consent you have given at any time with effect for the future. To do so, contact privacy@memexa.ai.
You also have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). Our competent authority: Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Rheinland-Pfalz, Hintere Bleiche 34, 55116 Mainz, Germany.
13. Data security
We implement technical and organisational measures pursuant to Art. 32 GDPR, including transport encryption (TLS), tenant-separated data storage with database-level access controls (row-level security), a per-account token model for MCP access, signature-verified webhooks for payment processing, and least-privilege access keys (automations receive only narrowly scoped tokens; central keys are kept in a managed secret store).
14. Changes to this policy
We update this privacy policy when the legal situation or our processing changes. The version published here applies. We will inform you of significant changes (such as new sub-processors for content data) by email or in the web interface.