> For the complete documentation index, see [llms.txt](https://unibaseio.gitbook.io/unibase-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://unibaseio.gitbook.io/unibase-docs/unibase-memory.md).

# Unibase Memory

One encrypted, portable memory across your AI chats — a Chrome extension that captures, organizes, and reuses your **ChatGPT**, **Claude**, and **Gemini** conversations (plus web content), so context follows you instead of staying locked inside one chatbot. Built on the Unibase memory stack: memory you can **encrypt, own, and verify**.

### What it does

* **Capture** conversations from supported AI platforms automatically, or import in bulk.
* **Clip** valuable web pages and selections into a personal Library.
* **Organize** everything in one panel — search, tag, star, filter.
* **Reuse** by sending the right memory straight back into your current AI chat.
* **Sync (optional)** to Membase — end-to-end encrypted, portable, and verifiable on Unibase Explorer.

### Why Unibase Memory

| vs. a chatbot's own history               | vs. note-taking apps                     |
| ----------------------------------------- | ---------------------------------------- |
| Works across ChatGPT, Claude & Gemini     | Auto-captured — no copy-paste            |
| You hold the key (end-to-end encrypted)   | Reuse memory back inside the chat        |
| Portable & recoverable, not vendor-locked | On-chain verifiable via Unibase Explorer |

### Encrypt · Own · Verify

* **Encrypt** — memory is encrypted locally on your device before any sync; only ciphertext leaves your machine.
* **Own** — a cross-AI archive you keep and can export; reuse it across supported platforms and devices.
* **Verify** — synced memories carry a verifiable record on Unibase Explorer, without exposing private content.

### Next Steps

* [Getting Started](/unibase-docs/unibase-memory/getting-started.md) — install, sign in, first sync
* [Features](/unibase-docs/unibase-memory/features.md) — capture, Library, search, send-to-chat, tags
* [Architecture](/unibase-docs/unibase-memory/architecture.md) — the capture → encrypt → sync pipeline
* [FAQ](/unibase-docs/unibase-memory/faq.md)

### Resources

* [Chrome Web Store](https://chromewebstore.google.com/detail/edmncknbiihfoakimejbepnaeemaaamf) · [Unibase Explorer](https://hub.membase.unibase.com)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://unibaseio.gitbook.io/unibase-docs/unibase-memory.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.