Privacy policy

Last updated: 2026-05-19

Short version. Slashprompt is a local-first browser extension. Your prompts are stored only in your browser's IndexedDB and never transmitted to us or to anyone else. We don't run any backend, don't collect any analytics, don't use any third-party scripts, and don't have an account system. The only time prompt data leaves your machine is when you click Export JSON.

What data the extension stores

• Prompts and folders — title, body, tags, folder name, timestamps, and a per-prompt use counter. Stored in your browser's IndexedDB under the extension's origin.
• Local settings — UI preferences and (in a future version) license state. Stored in chrome.storage.local.

What data the extension does not collect

• No account, no email, no signup, no login.
• No analytics, telemetry, crash reports, or usage pings.
• No third-party scripts, fingerprinting, or trackers.
• No reading or transmitting of host-page content.
• No syncing of your prompts across devices unless you manually export and re-import them.

Permissions the extension requests

Slashprompt is published on the Chrome Web Store with the minimum permissions it needs to function:

• storage — to read and write local settings via chrome.storage.local.
• activeTab — to send the chosen prompt to the active tab when you trigger it.
• https://*/* content-script match — so the slash command works in any text box on any site. The content script watches for the / trigger and renders a UI; it does not read or transmit page contents.

Network traffic

Slashprompt makes no network requests of its own. The extension package contains no fetch, XHR, WebSocket, or chrome.tabs.executeScript calls to external endpoints. You can verify this by inspecting the source on GitHub or by opening the browser's Network tab with the extension active.

If a paid tier ships

A future Pro license check will use a third-party payment processor (ExtensionPay or LemonSqueezy). When that lands, this page will be updated to disclose exactly what data the payment flow sees (typically: your email + a license key) and how it's stored. The payment processor will operate under their own privacy policy.

Changes to this policy

If this policy changes materially, the date at the top of this page will be updated and prior versions will be retained in the project's Git history.

Contact

Questions or concerns: hello@slashprompt.app.

← Back to home