Privacy Policy
Last updated: 2025-08-03
Deepdeep is committed to protecting your privacy. This policy explains what data we collect and how we use it.
1. Data We Don't Collect
Deepdeep does not collect, store, or transmit any personal data to our servers. We have no servers. The extension runs entirely in your browser.
- No analytics — no usage tracking
- No telemetry — no crash reports or performance data
- No accounts — no login or registration system
2. Data Stored Locally
The following data is stored in your browser's local storage (chrome.storage.local) and never leaves your device unless you actively send it to your chosen AI provider:
| Data | Storage | Purpose |
|---|---|---|
| API settings (Base URL, key, model) | storage.local | Connect to your AI provider |
| System prompt, Temperature | storage.local | Customize AI behavior |
| Active conversations | storage.session | Persist chats between sidebar sessions (cleared on browser restart) |
3. Data Sent to Third-Party AI Providers
Deepdeep is a BYOK (Bring Your Own Key) extension. When you send messages or use features, the following data is sent directly from your browser to your configured AI API provider (such as DeepSeek, OpenAI, Anthropic, MiMo):
- Your input messages
- Selected text from webpages (when using text selection popup or right-click menu)
- Page content (when using page summary, translation, or explanation; limited to ~12,000 chars)
- Tab content (when using
@tabreferences, up to ~8,000 chars per tab) - Your system prompt and temperature settings
This data is governed by your AI provider's privacy policy, not ours. We cannot access this data.
4. Permissions
| Permission | Why Needed |
|---|---|
| storage | Save API settings and active conversations |
| sidePanel | Display chat sidebar |
| contextMenus | Right-click "Explain / Translate / Summarize" on selected text |
| activeTab | Get current tab content for page actions |
| scripting | Read page content for summary and @tab context |
| tabs | List open tabs for @tab references |
| <all_urls> | Content script runs on all pages to support text selection popup |
5. API Key Security
Your API key is stored in chrome.storage.local and only sent to your configured AI provider via Authorization: Bearer header when you make a request. It is never logged, shared, or transmitted anywhere else.
6. Third-Party Libraries
| Library | License | Purpose |
|---|---|---|
| marked | MIT | Markdown rendering |
| DOMPurify | Apache-2.0/MPL-2.0 | HTML sanitization |
| Lucide | ISC | Icons |
7. Policy Changes
As the extension evolves, we may update this policy. Any changes will be posted on this page.
8. Contact Us
For privacy concerns: deepdeep@nopress.net