Legal

Privacy Policy

What this Memo deployment collects, why it needs it, who else sees it, and how you can get it back or delete it.

Effective 21 November 2026·Version 1.0·Memo · hosted reference deployment

Memo is a small, independently operated memory service. We keep the product deliberately simple, and that shapes the data: there are no advertising networks, no third-party analytics and no tracking pixels.

Plain-language summary: we store your account details and the memories you save, run the service on Vercel and Neon, and never sell your data. You can export everything as JSON and delete it at any time.

01Scope

This Privacy Policy explains how Memo (“Memo”, “we”, “us”) handles personal data in its hosted service, including the dashboard, API, MCP server and capture scripts.

Memo is an independent project. This policy describes only the official hosted deployment at memex-iota.vercel.app.

02Data we collect

We collect the following categories:

  • Account data — your email address, display name and account creation time. For password accounts we store a scrypt hash with a random per-user salt; we never store the password itself. For Google or GitHub sign-in we store the provider, the provider's user identifier and the verified email address returned by the provider.
  • Memory content — the text you add, capture or approve, its category or code type, importance, source and timestamps, and for code memory the repository name and optional key.
  • Recall data — when you search, recall or build a context pack, we store an event containing the query text and the kind of operation, used for usage signals and ranking.
  • Team data — repositories you create, their members and pending invitations, including the invitee's email address.
  • Imports — a ChatGPT or Claude export or pasted transcript you upload is processed in memory to find candidate memories. We do not keep the uploaded file; only the memories you choose to save are stored.
  • Credentials and technical data — MCP token prefixes and hashes, token creation, revocation and last-use times, session token hashes, and short-lived rate-limit counters derived from your IP address. Our hosting provider may also keep standard request logs, which can include IP address and user agent.

03Cookies and local storage

  • memo_session — an httpOnly, SameSite=Lax cookie (Secure in production) valid for 30 days that keeps you signed in. It contains a random session token; the server stores only its SHA-256 hash.
  • memo_oauth_state and memo_oauth_next — short-lived (10 minute) cookies used only to protect the Google or GitHub sign-in flow and to return you to the page you started from.
  • We do not use advertising, analytics or cross-site tracking cookies. The dashboard keeps some interface state in your browser's local storage; it is not sent to us.

04How we use data

  • provide the Service: authenticate you, store and recall memories, build context packs, run imports, resolve duplicates and conflicts, and share code memory with teammates you invite;
  • secure the Service: rate-limit abuse, detect and investigate attacks, and keep tokens and sessions revocable;
  • operate and improve the product: understand usage through recall events and fix defects;
  • communicate: respond to support or legal requests and send service notices;
  • comply with law and enforce our Terms of Service.

06When we share data

We do not sell your data and we do not share it for advertising. We share it only with:

  • Hosting and infrastructure providers — Vercel (hosting and serverless functions) and Neon (PostgreSQL database), which store and process data on our behalf.
  • Identity providers — Google or GitHub, when you choose those sign-in options.
  • Anthropic — only if the operator enables the optional Claude integration. When it is enabled, text submitted for extraction, answers or commit summarisation is sent to Anthropic's API. On this deployment that integration is disabled by default and extraction runs locally.
  • Teammates — members of a repository you share, for that repository's code memory only.
  • Authorities — when required by law or to protect rights, safety or the integrity of the Service. We will tell you unless legally prohibited.

07International transfers

Our providers may process data in countries other than yours. Where required, transfers rely on appropriate safeguards such as standard contractual clauses. You can ask us for details of the safeguards that apply.

08Retention

  • Memories stay until you delete them. Superseded memories are kept as history and excluded from recall; deleting a memory removes it.
  • Pending auto-captures stay in the inbox until you approve or discard them.
  • Sessions expire after 30 days, and expired sessions are removed.
  • Invitations expire after seven days.
  • Rate-limit counters exist only for their short window.
  • Account data is kept while your account exists and deleted after account deletion, except for records we must keep by law.
  • Request logs held by our hosting provider follow their retention schedule.

09Your rights and choices

Depending on where you live, you may have the right to access, correct, export, delete, restrict or object to our processing of your personal data, and to withdraw consent.

You can export everything as JSON and delete all memories from Dashboard → Settings at any time. To delete your account or make another privacy request, contact us; we respond within 30 days, or the period required by law.

You may also complain to your local data-protection authority.

10Security

Passwords are hashed with scrypt and a random salt. Session and MCP tokens are stored only as SHA-256 hashes, and the raw token is shown once. Sessions use httpOnly, SameSite cookies, every query is scoped to your user or to a repository you belong to, and traffic is served over HTTPS. No system is completely secure; if a breach affects your personal data, we will notify you and the authorities as required.

11Automated processing and AI

Embeddings are computed on our servers with openly licensed BGE models; your text is not sent to an embedding provider. Recall and ranking are automated, but they do not produce legal or similarly significant decisions about you. Where the optional Claude integration is enabled, the text you submit for extraction or answers is processed by Anthropic to generate that output.

12Children

The Service is not directed to children under 16, and we do not knowingly collect their personal data. If you believe a child has provided personal data, contact us and we will delete it.

13Changes to this Policy

We may update this policy as the Service changes. The effective date at the top shows the current version, and we will give notice on the website or by email before a material change takes effect.

14Contact

For questions or requests about this policy or your data, contact the maintainer through GitHub. If your request involves personal data, describe the request without posting the data itself.

Questions about this document?
Reach the maintainer through their GitHub profile.
Read the Terms of Service