Skip to content
Membase

Privacy Policy

Membase is operated by Unibase. Part 1 covers the Membase service: the web app at app.membase.com, the API and SDKs, and the MCP connectors that AI apps such as Claude and ChatGPT use to reach your memory. Part 2 covers the Membase Chrome extension.

Last updated: November 9, 2026

Part 1 — The Membase service

1. What this part covers

This part applies to the Membase service operated by Unibase: the web app at app.membase.com, the Membase API and the SDKs and command-line tools that call it, and the Membase MCP server at api.app.membase.com/mcp-http that AI apps such as Claude, ChatGPT, Cursor and Codex connect to. The Chrome extension is covered in Part 2. Third-party apps you connect to Membase are governed by their own privacy policies.

2. What we collect

  • Account information — when you sign in with Google, X, email or a crypto wallet through our sign-in provider (Privy), we receive an account identifier and, depending on the method, your email address and wallet address.
  • Content you add — files, documents, notes, web pages, messages and the material of sources you connect (for example a Notion workspace you authorise), plus anything you, your assistant or an app you have allowed to write saves to your memory.
  • Your memory — what Membase learns from that content (facts, summaries and search indexes), and the profile statements about you (name, role, lasting preferences) that you or your apps keep.
  • Connections and credentials — the apps you connect, the Memories and profile access you grant each one, and the developer keys you create.
  • Activity and technical data — a log of calls made with your connections and keys (which tool, when, and whether it succeeded), shown to you in the app, and standard server logs (such as IP address and request times) used to run and secure the service.
  • Payment information — if you buy a plan, we record the plan, the period and the on-chain payment (paying wallet address and transaction). Payments are made in USDC from your own wallet; we never receive card details.

3. How we use it

  • To provide the service: learn your memory from the content you add, answer searches from you and from the apps you connect, and run your assistant.
  • To keep the service secure, prevent abuse and fix problems.
  • To bill plans you choose and provide support when you contact us.

We do not sell your data, do not show ads, and do not use your content to train AI models.

4. AI processing

Learning your memory, searching it and running your assistant use AI models. To do that, the relevant part of your content is sent to the model provider we use (currently OpenAI), through its API, for processing on our behalf. If you add your own model key under AI Setup, the requests that use it go to that provider under your account and its terms. Model calls are made by our platform; model credentials are never placed inside your assistant's environment.

5. AI apps you connect (MCP)

  • You choose what each app can see. When you connect an app such as Claude or ChatGPT, the consent screen lets you pick the Memories it may read and whether it may read your profile. It sees nothing else.
  • Read-only by sign-in. An app connected by signing in (OAuth) can search and read what you granted; it cannot add, change or delete anything. Write access exists only through a developer key you create and configure yourself.
  • What we receive from the app. We receive only the requests the app makes to Membase (for example a search query) — not your conversation with that app.
  • What the app does with results is governed by that app's own privacy policy (for example Anthropic's for Claude, OpenAI's for ChatGPT).
  • Revoke at any time. Narrowing or removing an app's access under Connect takes effect on its next request.

6. Who else processes it

We share data only with these service providers, acting on our behalf:

  • Amazon Web Services — hosting, database and storage.
  • Privy — sign-in and wallet provisioning (Privy's privacy policy).
  • OpenAI — AI model processing, as described in Section 4.
  • Sources you connect (for example Notion) — only to fetch the material you authorised.
  • Payments — plan payments settle on a public blockchain (Base) through an x402 payment facilitator; the paying wallet address and the transaction are public on that chain.

If you choose to sell access to a Memory on the Membase Marketplace, buyers can read what that listing includes. We may also disclose data where the law requires it.

7. Where it is stored and how it is protected

  • Data is stored and processed on Amazon Web Services in Singapore (ap-southeast-1). Model providers may process requests in other countries, including the United States.
  • Each account's data is isolated from every other account, and your memory is kept in storage of its own.
  • The database and the memory store are encrypted at rest.
  • In the browser, your session is held in a secure, HTTP-only cookie that page scripts cannot read.

8. Retention and deletion

We keep your data while your account is active. When you delete an item, a Memory or your whole account (Settings), it is removed from the live service at once, and access already granted to apps and keys stops with it. Copies in our backups expire on a rolling schedule within 35 days.

9. Your controls and rights

  • See, export and delete your content and memory in the app.
  • Change or revoke any connected app or developer key under Connect.
  • Delete your account under Settings.
  • Depending on where you live, you may have further rights (for example to access, correct or object to processing). Contact us and we will respond.

10. Cookies

The web app uses only the session cookie needed to keep you signed in. It uses no advertising or analytics cookies. Our invite pages on membase.com may set a first-party kol_ref cookie used only to credit referrals (see Part 2, Section 5).

11. Children, changes and contact

Membase is not directed to children under 13 (or the minimum age in your jurisdiction) and we do not knowingly collect their data. We will post changes to this policy here with a new "Last updated" date. Questions or requests: support@membase.com.

Part 2 — The Chrome extension

Last updated: August 9, 2026

Membase captures your ChatGPT, Claude, Gemini, DeepSeek, Kimi, and Grok conversations (including Grok on X, at x.com/i/grok) — and web pages you choose to save — into a single, private, searchable memory. Your content stays in your browser by default, and anything you sync leaves your device only as ciphertext encrypted with a key only you hold. We collect a limited amount of anonymous usage data to improve the product — never your conversation or saved-page content.

1. Who this policy covers

This policy applies to the "Membase" Chrome extension (the "Extension") published by Unibase. It does not cover third-party websites you visit (such as ChatGPT, Claude, Gemini, DeepSeek, Kimi, Grok, or X/x.com), which are governed by their own policies.

2. What the extension handles, and where it lives

Stored locally on your device (always)

  • Conversation content — the text of the ChatGPT, Claude, Gemini, DeepSeek, Kimi, and Grok chats (including Grok on X, at x.com/i/grok) you view or import, read from the page as it is rendered, plus titles and timestamps. On X we read only your own Grok conversation, never your timeline, DMs, or other X content.
  • Saved web pages (clips) — when you save a page or a selection to your knowledge base (via the toolbar, right-click menu, or shortcut), the Extension extracts the readable article text and stores it, along with the page URL, title, and the cover-image URL. Cover images are never fetched automatically — the detail view loads one only if you tap to show it. Pages are only ever read when you explicitly trigger a save (the activeTab permission).
  • Your organization data — tags, stars, highlights, saved snippets, and settings.

This data is stored in your browser's local storage (IndexedDB and chrome.storage.local) on your own device. By default it is never transmitted anywhere.

Account & encryption material (only if you sign in)

  • Email address — if you sign in with Google, X, or email via our authentication provider, your email may be stored locally to show which account is active.
  • Wallet address — the public address of the wallet used to derive your encryption key.
  • Wallet signature — a one-time signature over a fixed, app-specific message. It is hashed on your device into an encryption key. The signature is cached locally so you don't have to sign again on every use. It is not a session token and cannot be used to act as your wallet elsewhere.

3. Optional encrypted sync

Sync is off by default. If you turn it on:

  • Your conversations are encrypted on your device (Fernet: AES-128-CBC + HMAC-SHA256) using a key derived from your wallet signature.
  • Only the resulting ciphertext is uploaded to the Membase network, our decentralized storage layer, stored under your own wallet address.
  • The encryption key never leaves your browser. There is no key escrow and no copy of your key on any server. The network and the Unibase Explorer only ever see encrypted blobs — never your plaintext conversations.
  • Signing in with the same identity on another device re-derives the same key, so your data decrypts locally there. Same wallet, same key, your data.

4. On-device AI (tagging and Ask)

Two features use small AI models that run entirely locally inside your browser:

  • AI tag suggestions (optional) — suggest tags for a conversation.
  • Ask your memory — answer your natural-language questions over your own saved memory. Your question and your memory are embedded and matched on your device; the most relevant excerpts are then inserted into your current ChatGPT/Claude chat so your own model writes the answer.

On first use, the extension downloads the model files (data, not code) from Hugging Face and caches them in the browser. Your conversation or saved-page content is never sent to any server for tagging or for Ask — all embedding and retrieval happen on your device.

5. Usage analytics

To understand how the Extension is used and improve it, we collect a limited amount of anonymous product-usage data through Google Analytics 4 (sent directly to Google's Measurement Protocol endpoint; no third-party tracking scripts are loaded).

What we collect

  • Feature-usage events — for example, that the side panel was opened, a question was asked of your memory, or a web page was clipped, along with basic session information (session start/duration).
  • A random installation identifier — a per-install UUID generated on your device to distinguish sessions and approximate active-user counts. It is not your name, email, or wallet address.
  • Google may additionally process standard technical data such as approximate location (derived from IP address) and device/browser type, per Google Analytics' own handling.

What we do NOT collect through analytics

  • We never send your conversation or saved-page content, titles, tags, highlights, email, wallet address, wallet signature, or any backup data to analytics.
  • Analytics events describe that a feature was used, never what was in your conversations.

This usage data is used solely to measure adoption and improve the Extension. See Google's Analytics privacy information for how Google processes it.

Referral attribution (cookie)

When you install the Extension from a partner or creator link, it reads a single first-party cookie named kol_ref set by our own invite pages on membase.com and unibase.com, so the referral can be credited. Both hosts are read because the invite page moved to membase.com while earlier visitors still carry the cookie set on the old one. This is the only cookie the Extension reads. It is used solely for install attribution, is never linked to your conversation or saved-page content, and is never sold or shared with third parties.

6. What we do NOT do

  • We do not sell your data, and we do not transfer your data to third parties except the service providers listed in Section 7, acting on our behalf.
  • We do not use or transfer your data for purposes unrelated to the extension's single purpose.
  • We do not use your data to determine creditworthiness or for lending purposes.
  • We do not send your conversation content, or any backup data, to analytics or any advertising service. We do not show ads.

7. Third-party services

  • Privy — handles sign-in (Google / X / email / wallet) and wallet provisioning. Subject to Privy's privacy policy.
  • Membase network — decentralized storage that holds your end-to-end-encrypted backups (ciphertext only). If you turn on Show hub addresses in the Extension's menu (off by default), each entry gains a link that opens its encrypted record on the Unibase Explorer.
  • Hugging Face — serves the on-device AI model weights (data files) when you enable AI tagging. No conversation content is sent there.
  • Google Analytics — receives the anonymous product-usage events described in Section 5. No conversation content or account identifiers are sent.

8. Data retention and your controls

Export

Download a full JSON copy of your data at any time.

Delete

Remove conversations, tags, or highlights. Uninstalling clears all local data, including the analytics installation identifier.

Disable sync

Turn sync off so nothing leaves your device.

Sign out

Clears the cached signature and derived key from your browser.

Encrypted backups already uploaded to the Membase network remain associated with your wallet address until removed; because they are decentralized-storage entries, contact us if you need help managing them.

9. Children

Membase is not directed to children under 13 (or the minimum age in your jurisdiction) and we do not knowingly collect their data.

10. Changes to this policy

We may update this policy as the extension evolves. Material changes will be reflected here with a new "Last updated" date at https://membase.com/privacy.

11. Contact

Questions about this policy or your data? Contact us at support@membase.com or visit membase.com.

Membase keeps your conversations local by default, end-to-end encrypts anything you choose to sync, and collects only anonymous usage data to improve the product. You own your memory.