Developer Privacy Framework
Last Updated: May 31, 2026.
1. 100% Local Sandbox Model
ContextCove V1 operates entirely inside your local browser runtime. All content scripts, heuristic parser executions, and clipped documentation pages are stored inside your browser's chrome.storage.local database using developer-unlimited disk boundaries. We do not operate backend servers that caching your clips, URLs, code sections, or indices. Your curated data is strictly yours.
2. Zero PII or URL Tracking
We do not collect or monitor your browsing history. The extension requests the <all_urls> permission solely to enable link discovery and local background fetching of public documentation pages. We never log, analyze, or upload your documentation URLs or your research objective goals.
3. Waitlist & Loops.so Storage
When you enter your email to join our waitlist, your email address is transferred securely via HTTPS to our developer-friendly CRM partner, **Loops.so**. Loops handles our waitlist data securely. We will only use your email address to update you about ContextCove's launch, features, or roadmap releases. We do not sell, rent, or trade your email address with third parties.
4. Opt-In Feature Telemetry
We use strict, completely opt-in-only telemetry for basic feature event tracking (for example, "Export Markdown Button Clicked"). This helps us understand what features our developer community uses most. It carries zero context contents, URLs, code blocks, or PII. You can toggle telemetry off instantly in the extension settings panel at any time.
5. Your Rights
Since your curation database lives on your local disk, you can completely erase all clipped pages, session histories, and objectives at any time by simply clicking **"Clear Session"** inside the extension sidebar, or by uninstalling the extension.