START OVER
Logo for PEAT the Prompt Engineering Assistant Tool by Gabriel Cassady | Springfield, Mo

PEAT Privacy Policy

Scroll to Content

Last updated: May 28, 2026 • Applies to PEAT v2.0.2 and later.

PEAT (Prompt Engineering Assistant Tool) is committed to absolute user privacy. The design philosophy is simple: your prompts are yours alone. Because PEAT is built as a local-only tool, it does not send your data to external web services, does not track your behavior, and does not share telemetry of any kind.

1. Core privacy commitments

      • No outbound network calls. PEAT contains zero fetch(), XMLHttpRequest, WebSocket, or other network requests to any external server. You can verify this yourself by reading the source code on GitHub.

      • Local-only storage. All prompt templates, categories, settings, and onboarding state are stored inside your browser’s sandboxed extension storage — on your computer, under your control.

      • Zero webhooks, zero analytics, zero telemetry. Earlier prototype versions of PEAT (pre-2.0) included an optional webhook for community prompt sharing. That entire code path was removed in v2.0.0 and is not present in any released v2.x build.

      • No tracking of your AI usage. PEAT does not collect or log how many templates you create, which AI assistants you visit, or what you type into them.

    2. What permissions PEAT requests, and why

    PEAT uses only the minimum browser-extension APIs required to do its job. There are exactly two:

    storage — used to save and retrieve your prompt templates, categories, and settings. The data handled includes your prompts, category tags, your choice between local and synced storage, and a flag indicating whether you’ve completed the first-run walkthrough. By default everything is saved on your local machine. If you enable the optional sync toggle in Settings, your library is synced across your signed-in browser profiles using your browser’s built-in sync service — your prompts still never touch any server controlled by PEAT or by me.

    activeTab — used to inject your filled-in prompt into the active ChatGPT, Claude, or Gemini composer when you click “Insert into Composer.” Only a single text string is written into a single text field. PEAT does not read the rest of the page, does not log what’s there, and does not send anything anywhere.

    PEAT’s host permissions are scoped to exactly three domains: chatgpt.com, claude.ai, and gemini.google.com. It cannot run on any other website.

    3. Your control over your data

        • Export. You can export your entire prompt library as a standard JSON file at any time from the Preferences panel.

        • Import. You can import a previously exported JSON file to restore or merge templates.

        • Delete. Deleting a prompt in the My Library view removes it from your storage immediately. Removing the extension or clearing your browser’s extension data wipes the entire PEAT library. 

      4. Changes to this policy

      PEAT is open source. Any future change that could affect this privacy posture will be documented in the public CHANGELOG and reflected here.

      5. Contact

      Questions or concerns about this privacy policy? Email gabriel@2oddballs.com.