MemoCat Privacy Policy
Overview: MemoCat is built with a local-first, offline-only architecture. MemoCat has no user accounts, no remote backend servers, and no telemetry, analytics, or advertising SDKs. We do not collect, transmit, sell, or share your conversations, folder paths, or usage data.
1. Data Accessed and Stored Locally
- User-Selected Local Folders (Desktop App): MemoCat Desktop does not silently scan unauthorized system directories. In Mac App Store sandboxed builds, folder access is strictly read-only and granted only when you explicitly pick directories via the macOS file dialog (such as Codex, Claude Code, Grok Bot, or Antigravity log directories), persisted locally via macOS Security-Scoped Bookmarks (
com.apple.security.files.user-selected.read-onlyandcom.apple.security.files.bookmarks.app-scope). - Supported AI Web Pages (Browser Extension): Content scripts execute solely on the explicit AI chat origins declared in
manifest.json. When you click Save or enable auto-save for a specific platform, visible conversation text from the active tab is stored locally in browserIndexedDBand preferences inchrome.storage.local. - Local Database: Imported messages, local hash-cached images, sync state, and MCP delivery audit logs are stored exclusively on your device inside local SQLite (
memo.sqlite).
2. Local Loopback Communication
- Optional synchronization between the Chrome Extension and MemoCat Desktop, as well as the local MCP endpoints for local AI clients, operates strictly over the localhost loopback interface (
127.0.0.1) (default port3792). No conversation data leaves your computer. - Extension-to-desktop pairing validates the extension's 32-character ID alongside a locally generated 256-bit random Bearer token; per-client MCP switches and source allowlists remain under your control.
3. Tracking and Third Parties
- MemoCat sets
NSPrivacyTracking = falseand declares zero collected data types inPrivacyInfo.xcprivacy. - No third-party tracking libraries, remote scripts (
script-src 'self'), or external network beacons are used.
4. User Control and Deletion
- You can delete individual conversations or clear the entire archive inside the browser extension at any time, and export portable Markdown or JSON backups.
- On macOS, you can disable any ingestion source, revoke folder access, or delete the local MemoCat data directory to permanently remove all stored data and cached attachments.
- Note: Local
memo.sqlitestorage and exported JSON backups contain plaintext text without additional app-level at-rest encryption; protect your device with macOS FileVault and standard user permissions.
5. Contact
For privacy inquiries or support requests related to store listings, please open an issue in the project repository at GitHub Issues or visit the Support page.