PRIVACY POLICY

Last Updated: July 4, 2026

1. Local-First Sandboxed Workspace

PromptLock Workspace is designed under a strict local-first paradigm. Your API keys, conversation threads, documents, settings, and folder structures remain fully enclosed inside your local Chrome browser storage (`chrome.storage.local` and IndexedDB). No remote cloud database logs, caches, or profiles your prompt data.

2. Zero Telemetry & Tracking

We do not inject tracking analytics, telemetry scripts, or event loggers. We have no insights into your prompts, which models you configure, or the content of the files you attach. The workspace is fully auditable.

3. Local Credentials Cryptography

Your keys are securely encrypted client-side using authenticated **AES-256-GCM** encryption before writing to disk. Key derivation is handled locally via **PBKDF2** using a high-iteration hash derived from your master password. Decryption happens purely in transient service worker memory scopes and is never leaked.

4. Outgoing Requests Isolation

All requests made to provider completion APIs (OpenAI, Anthropic, Gemini, etc.) occur directly from your browser origin. To safeguard your system, CORS-bypass request headers are dynamically bound via Declarative Net Request rules, restricted exclusively to the active PromptLock extension runtime ID.

5. Third-Party Payments

License checkouts are processed securely via Stripe. We do not collect, process, or store credit card numbers. Your checkout email is used solely to generate and mail the asymmetric Ed25519 license verification token.