This privacy policy covers all tools published by HackLM under the hacklmdev GitHub organization. We do not operate servers that receive, store, or process your personal information.

Chrome Extension

AI Chat Backup

AI Chat Backup lets you save and browse your AI chat history from ChatGPT, Claude, Gemini, Grok, and Perplexity. Your conversations are stored entirely on your own device using the browser's built-in chrome.storage.local API. No data ever leaves your machine through the extension.

Data Stored

When you click Save, the extension reads the current conversation and writes a structured copy to local storage. This includes:

  • Message text (user and assistant turns)
  • Conversation title and timestamps
  • The name of the AI provider (e.g. "chatgpt")
  • File attachments you sent, as text previews extracted by the AI site

This data lives in chrome.storage.local and is never synced to Chrome Sync or any remote server. It stays on the device where the extension is installed.

Permissions Explained

storage / unlimitedStorage
Saves and retrieves conversations from chrome.storage.local. unlimitedStorage removes the default 10 MB cap for power users.
activeTab
Runs the extractor on the currently focused AI chat tab when you click Save.
Host permissions
Limited to chatgpt.com, claude.ai, gemini.google.com, grok.com, and perplexity.ai. Allows content scripts to read the conversation DOM using your existing browser session.

Third-Party Services

When you use the "Restore" feature to continue a conversation, you are pasting text into an AI platform of your choice. That action is subject to that platform's privacy policy, not this extension. The extension does not embed any third-party analytics, advertising, or tracking libraries.

Data Export & Deletion

You can export your entire vault as a JSON file from the Vault Dashboard at any time. You can delete individual conversations or clear all saved data from within the extension. Uninstalling the extension removes all locally stored data.

VS Code Extension

HackLM Memory

Data Stored

HackLM Memory stores project context as plain .md files inside a .memory/ folder in your workspace. All data remains on your local filesystem.

  • Markdown files you create or that Copilot writes to .memory/
  • These files are plain text and live entirely within your workspace directory

HackLM Memory makes no network requests of its own and does not call any HackLM API. The extension reads and writes files on disk and injects their contents into VS Code Copilot's context — entirely within VS Code's local extension host process.

Permissions

The extension requests VS Code filesystem access scoped to your open workspace folders. It does not access files outside the workspace.

All Products

What We Never Collect

  • No data is transmitted to HackLM servers or any third party
  • No analytics, usage metrics, or telemetry
  • No advertising or tracking libraries
  • No data is sold or shared

Children

Our tools are not directed at children under 13. We do not knowingly collect any information from children.

Changes to This Policy

If we make material changes, we will update the "Last updated" date at the top of this page. Continued use of any HackLM tool after changes constitutes acceptance of the revised policy.

Contact

Questions? Open an issue in the relevant repository on github.com/hacklmdev or email privacy@hacklm.dev.