Unibase
    • Memory
    • BitAgent
    • UB Bridge
    • Membase
    • AIP
    • Unibase Pay
    • Unibase DA
    • Explorer
    • Docs
    • GitHub
    • Twitter
    • Telegram
    • Unibase Korea
Unibase

© 2026 Unibase

Products
MemoryBitAgentUB Bridge
Developer
MembaseAIPUnibase PayUnibase DAExplorerDocs
Community
GitHubTwitterTelegramUnibase Korea
Home/Products/Unibase Memory/Privacy Policy

Privacy Policy

Unibase Memory (Chrome Extension)

Last updated: June 9, 2026

Unibase Memory captures your ChatGPT and Claude conversations into a single, private, searchable memory. Everything stays in your browser by default; anything that leaves your device is end-to-end encrypted with a key only you hold.

On this page

  1. 1. Who this policy covers
  2. 2. What the extension handles
  3. 3. Optional encrypted sync
  4. 4. On-device AI tagging
  5. 5. What we do NOT do
  6. 6. Third-party services
  7. 7. Your controls
  8. 8. Children
  9. 9. Changes
  10. 10. Contact

1. Who this policy covers

This policy applies to the "Unibase Memory" Chrome extension (the "Extension") published by Unibase. It does not cover third-party websites you visit (such as ChatGPT or Claude), 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 and Claude chats you view or import, read from the page as it is rendered, plus titles and timestamps.
  • 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 Membase, Unibase's 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. Membase 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. Optional on-device AI tagging

You may optionally enable AI tag suggestions. The model runs entirely locally inside your browser. On first use, the extension downloads the model weights (data files) from Hugging Face and caches them in the browser. Your conversation text is never sent to any server for tagging — all inference happens on your device.

5. What we do NOT do

  • We do not sell or transfer your data to third parties.
  • 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 run analytics, advertising, or tracking on your conversation content, and we do not maintain a server-side copy of your plaintext.

6. Third-party services

  • Privy — handles sign-in (Google / X / email / wallet) and wallet provisioning. Subject to Privy's privacy policy.
  • Membase / Unibase — decentralized storage that holds your end-to-end-encrypted backups (ciphertext only). Encrypted entries can be viewed by you 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.

7. 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.

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 Membase remain associated with your wallet address until removed; because they are decentralized-storage entries, contact us if you need help managing them.

8. Children

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

9. 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://www.unibase.com/memory/privacy.

10. Contact

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

Unibase Memory stores your data locally by default and end-to-end encrypts anything you choose to sync. You own your memory.