LLMnesia

Privacy Policy

Last updated: 30 September 2026

Overview

LLMnesia is a browser extension and optional local desktop MCP integration that indexes your AI conversations locally on your device. Vault is a separate, optional paid feature that adds an encrypted server backup, sync, and restore. Current Vault subscribers may also use an installable Vault web app beta to search and ask questions over an existing synced Vault. LLMnesia is built with a local-first, privacy-by-design architecture.

Your AI conversation content, conversation titles, conversation URLs, prompts, responses, search queries, extension settings, and searchable index are stored locally on your device using the Chrome Storage API (chrome.storage.local), unless you choose to opt in to Vault, an optional encrypted backup and sync feature described below. If you enable the desktop MCP integration, LLMnesia also stores a local copy of that corpus in your user profile so desktop AI apps can search it.

LLMnesia uses limited product analytics through PostHog to understand feature usage, diagnose problems, and improve the extension and the Vault web app. LLMnesia does not send AI conversation content, conversation titles, conversation URLs, prompts, responses, search queries, cookies, authentication tokens, or local index data to PostHog or any other external analytics service.

Information processed locally by the extension

LLMnesia processes the following data locally on your device to provide its core search functionality:

  • Conversation metadata such as titles, URLs, and timestamps from supported AI chat platforms, used to build your searchable conversation index.
  • Conversation content such as text from your AI conversations on supported platforms, indexed locally to enable full-text search.
  • Search queries entered into LLMnesia, used locally to search your on-device index.
  • Extension settings such as your preferences and configuration, stored locally in your browser.

This data is processed and stored on your device using the Chrome Storage API (chrome.storage.local). It is not transmitted to LLMnesia servers, PostHog, or other third parties, unless you opt in to Vault, described below.

Desktop MCP and local browser bridge

If you choose to connect LLMnesia to a supported desktop AI app, LLMnesia creates a second local conversation corpus in your operating-system user profile (by default under ~/.llmnesia/corpus). The browser extension sends conversation records to a native messaging helper running on the same computer, and the local MCP server reads and writes that corpus when the desktop AI app uses a LLMnesia tool.

The native messaging helper and MCP server do not upload conversation content, titles, URLs, prompts, responses, MCP search queries, cookies, authentication tokens, or local index data to LLMnesia, PostHog, or other third parties. The MCP server makes no analytics or advertising requests.

Desktop MCP and automatic browser sync are optional. Chrome asks you to approve native messaging access when you click Enable automatic sync in LLMnesia Settings. The local helper setup also configures the supported desktop AI apps you choose to use.

Product analytics

LLMnesia uses PostHog to collect limited product analytics from the browser extension and from the Vault web app beta. This helps us understand which features are used, diagnose errors, improve reliability, and make better product decisions.

Analytics events may include limited technical and usage information such as:

  • Extension version
  • Browser type and operating system
  • Supported AI platform name, such as ChatGPT, Claude, Gemini, or Perplexity
  • Feature interactions, such as opening the extension, starting indexing, completing indexing, or using a settings control
  • Error categories or failure states
  • Aggregate counts, such as the number of conversations indexed
  • An anonymous extension install identifier used to understand product usage without requiring an account
  • Web app usage events, such as opens, sign-ins and unlocks (recorded by method only), lock and sign-out, searches (query length and result count, never the query text), Ask submissions (question length, never the question text), and transcript opens
  • An anonymous web app identifier: a random ID kept in the browser's localStorage on the vault.llmnesia.com origin, never an email address or account identifier

LLMnesia does not send any of the following to PostHog or any other external analytics service:

  • AI conversation content
  • Conversation titles
  • Conversation URLs
  • Prompts or responses
  • Search queries
  • Conversation snippets or page text
  • Cookies or authentication tokens
  • Your local search index
  • Your name, email address, or AI platform account details

PostHog analytics are used only to operate, debug, and improve LLMnesia. They are not sold, used for advertising, transferred to data brokers, or used to determine creditworthiness or for lending purposes.

How your data is stored

All AI conversation data created or processed by LLMnesia, including your conversation index, conversation metadata, search data, and extension settings, is stored locally in your browser using the Chrome Storage API (chrome.storage.local). If you enable desktop MCP, a second local corpus is stored in your operating-system user profile so desktop AI apps can access it.

You can view, export, or delete your locally stored LLMnesia data at any time through the extension's settings.

Data handling

When you visit a supported AI chat platform, LLMnesia reads conversation titles and content from the page and saves them to a local index on your device. When you search, the extension queries this local index and displays results in your browser.

AI conversation content, conversation titles, conversation URLs, prompts, responses, search queries, extension settings, and local index data are not sent to LLMnesia servers, PostHog, or other third parties, unless you opt in to Vault, described below.

Limited product analytics are sent to PostHog as described in the Product analytics section above.

If desktop MCP is enabled, searches and tool calls run against the local filesystem corpus. They do not send the query or result to LLMnesia servers or analytics services.

Vault (optional paid encrypted backup and sync)

Vault is an optional paid feature that lets you back up your conversation index and keep it in sync across your own devices. It is off unless you deliberately create a Vault. Setup requires an account, authenticated with your email address and a one-time code, plus a private passphrase and an active subscription.

If you turn Vault on, your conversation content is encrypted on your device (AES-256-GCM, with a key derived from a passphrase only you know) before it ever leaves your device. The encrypted data is then synced to LLMnesia's sync backend, hosted on Supabase, so it can be restored to your other devices.

LLMnesia's servers store encrypted conversation and memory payloads, a wrapped copy of the Vault key, record identifiers, sync versions and timestamps, deletion markers, account and sign-in information, and subscription status. Record identifiers reveal which supported AI platform a record came from. We do not have access to your passphrase or unwrapped encryption key, and cannot read or decrypt conversation text, titles, URLs, previews, saved-memory text, or search queries stored in Vault.

Because the browser extension is built to support Vault for every installation, the extension requests permission to communicate with its Supabase sync backend (https://tkgvwpaxycliwqsrufxe.supabase.co) regardless of whether you have Vault turned on. This permission is not used, and no data is sent to that backend, unless you opt in to Vault.

Every remote Vault operation—upload, download, metadata and key retrieval, sync, and restore—requires an active subscription and is enforced by the server. If the subscription lapses, conversations already stored on each device stay there and remain searchable. The encrypted server copy is not deleted, but it cannot be synced or restored until you renew.

Payments are handled by Stripe. Stripe receives the payment and billing information you enter there; LLMnesia receives the billing email address, Stripe customer/subscription identifiers, plan and status, and relevant subscription dates. LLMnesia never receives or stores your full card details.

You can sign out of Vault at any time from the extension's settings, which removes the Vault key from that device. To have your encrypted backup deleted from LLMnesia's servers entirely, or to close the Vault account, email hello@llmnesia.com from the address on the account. There is currently no self-service whole-Vault deletion button.

Vault web app beta and Ask

Current Vault subscribers may optionally use the installable Vault web app beta at vault.llmnesia.com. The web app is a reader for an existing Vault and cannot create a person's first Vault.

The web app downloads encrypted Vault records from Supabase, then decrypts and indexes them inside the browser. The readable local corpus is stored in the web app origin's IndexedDB so the device does not need to restore the complete Vault on every visit. Lock removes readable content from the page and destroys the live Vault key, but it does not erase that local corpus. Sign out offers a choice to keep the corpus for the same account's next visit or remove the web app's local corpus and caches.

The web app may store an account session, a biometric convenience-unlock record, and a provider API key on the device. These records are encrypted with device-local, non-extractable WebCrypto keys. This protects them from a copied storage dump, but it does not protect them from malicious code already running on the Vault web app origin. Signing out removes the saved provider credential and biometric record. The user can also forget a provider key from Ask settings.

Search, filtering, and transcript reading happen locally. When the user taps Ask, the web app starts a bounded Ask session using the provider and model selected in Ask settings. It sends the question and bounded relevant context directly from the browser to that provider, currently OpenAI, Anthropic, Google, or OpenRouter, using the user's own API key. Ask does not send the whole Vault. The request does not pass through LLMnesia. The selected provider receives the request content and ordinary network metadata under its own privacy and data-retention terms. The completed answer links back to supporting source conversations.

The Vault web app includes the same kind of anonymous PostHog product analytics as the extension, described in the Product analytics section above. It has no crash-reporting SDK. Vercel hosts and delivers the app's static files and receives ordinary web request metadata such as IP address, user agent, and request time.

Browser permissions

LLMnesia requests the following browser permissions, each used solely to provide core functionality:

  • Storage saves your conversation index and extension settings locally in your browser.
  • Unlimited storage allows a large local conversation index to remain available without the browser's small default extension-storage quota.
  • Tabs opens the correct conversation when you click a search result.
  • Active Tab detects which supported AI platform you are currently visiting.
  • Scripting injects the search overlay and indexing scripts into supported AI chat pages.
  • Offscreen runs local background work that needs a document context, including semantic search processing and Vault encryption/decryption.
  • Alarms schedules bounded background maintenance, including indexing checks, Vault sync, and subscription-status refreshes.
  • Native messaging, requested only when you enable automatic sync, connects the extension to LLMnesia's local helper on the same computer so desktop AI apps can use the local corpus.

Host permissions

LLMnesia requests host permissions for supported AI platforms:

  • ChatGPT (chatgpt.com, chat.openai.com)
  • Claude (claude.ai)
  • Gemini and Bard (gemini.google.com, bard.google.com)
  • Google AI Mode (google.com, enabled as an optional site permission)
  • Perplexity (perplexity.ai)
  • Microsoft Copilot (copilot.microsoft.com)
  • Meta AI (meta.ai)
  • DeepSeek (deepseek.com, chat.deepseek.com)
  • Grok and X/Twitter (grok.com, x.com, twitter.com)
  • Mistral (chat.mistral.ai, lechat.mistral.ai, mistral.ai)
  • Kimi (kimi.com, kimi.ai)
  • Qwen (qwen.ai, chat.qwen.ai)
  • Google AI Studio and its legacy hosts (aistudio.google.com, makersuite.google.com, studio.google.com)
  • Character.AI (character.ai)
  • Z.ai (chat.z.ai)

These permissions are used to index supported AI conversation content locally on your device and to provide LLMnesia's search functionality. LLMnesia does not use these permissions to transmit AI conversation content, search queries, cookies, authentication tokens, or local index data to external servers.

Google AI Mode is optional. New access to google.com and www.google.com is requested only when you enable Google AI Mode in Settings and approve Chrome's permission prompt. If you approved Google access in an earlier version, Chrome may retain that grant and Settings will show the integration as enabled. Chrome grants access at the domain level because extension host permissions cannot be limited to a URL query parameter. LLMnesia limits its content script to Google Search URLs and activates conversation extraction only for full-page AI Mode results (/search with udm=50). Ordinary Google searches are not indexed. Disabling Google AI Mode removes the optional permission without deleting conversations already saved.

LLMnesia also requests a host permission for its own sync backend, hosted on Supabase (tkgvwpaxycliwqsrufxe.supabase.co), used only by Vault, the optional encrypted backup and sync feature described above.

The llmnesia.com host permission is used for the optional email-updates form and the extension's own account, pricing, support, changelog, and local-viewer handoff pages.

Third-party services

LLMnesia uses PostHog for limited product analytics as described above. PostHog may receive limited technical and product usage events, but it does not receive AI conversation content, conversation titles, conversation URLs, prompts, responses, search queries, cookies, authentication tokens, or local index data.

LLMnesia uses Supabase to host the Vault sync backend described above. If you opt in to Vault, your encrypted conversation data and Vault account information are stored on Supabase's infrastructure. Supabase does not have access to the encryption key needed to read the encrypted payloads.

LLMnesia uses Stripe for Vault subscriptions. Payment details are entered and handled by Stripe; LLMnesia receives the identifiers and subscription state needed to grant or pause Vault access.

Vercel hosts and delivers the optional Vault web app beta. It receives ordinary web request metadata and the web app's anonymous usage events described above, but does not receive readable Vault content, the passphrase, Vault key, search or Ask text, or provider API keys from the application.

When a user taps Ask, the selected provider, currently OpenAI, Anthropic, Google, or OpenRouter, receives the current question, bounded relevant context selected for that Ask session, the user's API key, and ordinary request metadata. Ask does not send the whole Vault. The request goes directly from the browser to the provider and is governed by that provider's own terms.

The optional desktop MCP server and native messaging helper run locally and do not send conversation content or MCP queries to a third-party service.

LLMnesia does not use third-party advertising networks, data brokers, or information resellers.

Data sharing

We do not sell user data. We do not share user data with advertisers, data brokers, or information resellers.

Limited product analytics are processed by PostHog only to help us operate, debug, and improve LLMnesia. AI conversation content and local index data are not shared with PostHog. If you opt in to Vault, encrypted conversation payloads and the associated account and sync metadata described above are processed by Supabase solely to provide Vault.

Chrome Web Store Limited Use disclosure

LLMnesia's use of information received from Chrome APIs and supported AI chat pages is limited to providing and improving its single purpose: local indexing and search of the user's AI conversations, including the optional Vault backup and sync feature described above.

LLMnesia does not sell user data, does not use user data for advertising, does not transfer user data to data brokers or information resellers, and does not use user data to determine creditworthiness or for lending purposes.

Human access to AI conversation content is not possible through LLMnesia because AI conversation content and the searchable index are stored locally on the user's device and are not transmitted to LLMnesia servers, PostHog, or other third parties. If you opt in to Vault, your conversation content is encrypted on your device before it is stored on LLMnesia's servers, so it remains unreadable to LLMnesia there as well.

Data security

AI conversation content, conversation metadata, search queries, extension settings, and local index data are stored locally on your device. This data is protected by your device's own security measures and your browser's extension storage protections.

Unless you enable Vault, AI conversation content and local index data are not transmitted to LLMnesia's servers. Data you deliberately back up via Vault is encrypted on your device before it is sent, so its content remains unreadable to LLMnesia and Supabase.

Data retention and deletion

AI conversation content, conversation metadata, search queries, extension settings, and local index data are stored locally on your device for as long as the extension is installed, unless you delete them earlier.

If you enable desktop MCP, its filesystem corpus remains on the device until you delete it. Uninstalling the local helper deliberately leaves that corpus intact so removing an integration cannot accidentally destroy your history.

If you use the Vault web app beta, its local readable corpus remains in that web origin's IndexedDB after Lock. Signing out lets you keep it for the same account's next visit or remove the corpus and PWA-owned caches. Signing out always removes the saved provider credential and biometric unlock record.

You can delete your locally stored LLMnesia data at any time by:

  • Using the export/delete controls within the extension's settings
  • Uninstalling the extension, which removes the extension's local storage
  • Clearing your browser's extension storage

To remove the desktop MCP copy as well, run the LLMnesia MCP uninstall command and delete the corpus path it prints (normally ~/.llmnesia/corpus).

If you opt in to Vault, encrypted records are retained until you delete them while remote access is active, ask us to delete the whole Vault, or close the account. They are not deleted merely because a subscription lapses; during a lapse they cannot be synced or restored unless you renew. Deleting a conversation locally while access is paused does not remove the remote encrypted record until Vault is renewed and the deletion can sync. See the Vault section above for how to sign out or request deletion of the complete Vault.

Limited analytics data processed by PostHog may be retained for product analytics, debugging, and improvement purposes. This analytics data does not include AI conversation content, conversation titles, conversation URLs, prompts, responses, search queries, cookies, authentication tokens, or local index data.

Children's privacy

LLMnesia is not directed to children under 13. LLMnesia does not knowingly collect personal information from children under 13.

The extension processes supported AI conversation data locally on the user's device solely to provide indexing and search. It never sends conversation content, prompts, responses, search queries, or local index data to PostHog. Vault remains optional; if deliberately enabled, it transmits only the encrypted payloads and associated account and sync metadata described above.

Changes to this policy

If we update this privacy policy, we will revise the "Last updated" date at the top of this page. Continued use of the extension or website after changes constitutes acceptance of the updated policy.

Support requests

When you email hello@llmnesia.com or use our contact form, we use the details and message you provide to respond to your request. We also keep basic ticket details, including the sender name and email address, date received, subject, and status, to track it. Our email and support record providers process this information for us.

We keep support email for 12 months after the request is closed and remove resolved ticket records after 180 days. You can request deletion by emailing hello@llmnesia.com.

Contact

If you have questions about this privacy policy, please contact us at hello@llmnesia.com or via the contact form on our website.