docs/PRIVACY.md.
Summary
Draftline is a local-first / BYOK writing assistant.
- We do not operate a Draftline cloud account backend in v1.
- We do not sell personal data.
- API keys you enter stay in Chrome local storage on your device.
- When you use a third-party model provider, your prompts are sent directly from your browser to that provider.
Data Draftline stores on your device
Stored via Chrome extension local storage
(chrome.storage.local / WXT storage items):
| Data | Purpose | Leaves your device? |
|---|---|---|
| Settings (theme, default action, selected model, privacy mode) | Configure the extension | No (unless you export a backup file yourself) |
| Custom prompts, folders, system prompts | Writing shortcuts | No (unless you export a backup) |
| Personas (name, tone rules, do/don’t, samples) | Voice/tone memory | No (unless you export a backup) |
| Active persona id / entitlement tier (local free/paid flag) | Local feature gating | No |
| Onboarding completed flag | First-run UX | No |
| API keys (OpenAI, Anthropic, Google, OpenRouter, custom) | BYOK generation | Never included in backups; sent only to the provider you choose when generating |
Data sent off-device
1) BYOK model providers (only when you generate)
If you choose a cloud model and have configured a key, generation requests are sent directly from the extension to the selected provider endpoint, for example:
- OpenAI (
api.openai.com) - Anthropic (
api.anthropic.com) - Google Gemini (
generativelanguage.googleapis.com) - OpenRouter (
openrouter.ai) - Your custom OpenAI-compatible base URL
Typical request contents:
- model id
- system/user/assistant messages built from your action
- optional selected text
- optional persona tone rules / samples
- optional page context (title, URL, redacted text excerpt)
Draftline does not proxy these through a Draftline server in v1.
2) On-device Gemini Nano (when available)
If you use the free on-device path, text may be processed locally by Chrome’s on-device model APIs when available. Availability depends on your Chrome build/device.
3) Page context chat
When you use page chat, Draftline may include:
- page title
- page URL
- a text excerpt from the page body (capped, currently ~8000 characters)
- basic secret-shaped redaction before send (API-key-like patterns, etc.)
Draftline does not upload full HTML, cookies, or passwords as a dedicated feature.
What Draftline does not do (v1)
- No Draftline cloud account login
- No Draftline-hosted generation backend
- No analytics/telemetry backend in this codebase
- No ad network integrations
- No team/workspace sharing
- No automatic multi-device sync of personas/prompts
- No inclusion of API keys in backup export files
Backups
Export/import backup is optional and user-initiated.
- Backup files include prompts, personas, folders, system prompts, and settings.
- Backup files are designed to exclude API keys.
- Import also rejects payloads that appear to contain keys.
Permissions (why they exist)
| Permission / access | Why |
|---|---|
storage |
Save settings, prompts, personas, local keys |
activeTab |
Interact with the active tab (e.g. open modal from popup/commands) |
contextMenus |
“Ask Draftline” on selected text |
Host access (<all_urls> content script) |
Show selection toolbar / modal on pages where you write |
commands (Alt+W) |
Keyboard shortcut to open Draftline |
Draftline does not request broad unused permissions such as
alarms or scripting.
Third-party services
If you use BYOK providers, their privacy policies apply to the content you send them. Review the provider you choose (OpenAI, Anthropic, Google, OpenRouter, or any custom endpoint you configure).
Children
Draftline is not directed at children under 13.
Changes
If data practices change (for example, adding a hosted cloud tier), this policy must be updated before shipping that change.
Contact
For privacy questions, use the contact details on the Support page or the publisher email listed on the Chrome Web Store listing once published.