Dev.to Reply Drafter
Effective date: 2026-08-01 · Last updated: 2026-08-01
Short version: We collect only what we need to run the service (your email address, usage counts, and optionally your dev.to username for voice generation). We do not sell your data. We do not post anything to dev.to on your behalf. Your API keys and voice profiles never leave your device.
This Privacy Policy describes how Dev.to Reply Drafter (“we,” “our,” or “us”) collects, uses, and protects information when you use the Dev.to Reply Drafter Chrome extension and its associated backend service at devto.nerdsnipe.cc (collectively, the “Service”).
By installing the extension or using the Service, you agree to the practices described below. If you do not agree, please uninstall the extension and discontinue use.
To create an account, you provide your email address. We use it exclusively to send you a magic-link sign-in email and to identify your account. We do not require a password.
If you choose to generate a voice profile from your published articles, you enter your dev.to username in the extension settings. We use that username solely to fetch your public articles from dev.to's API on your behalf and build a voice profile text string. We never access or store your dev.to credentials, password, or tokens.
We record a draft count per account to enforce plan limits. We do not store the content of your drafts, the article text you viewed, or your drafting history beyond what's needed for the cloud-sync feature you opt into.
The extension requests access to dev.to. This permission is used solely to identify the article you're viewing from its URL; the article and comment content itself is fetched from dev.to's own public API, not by reading the page DOM. The extension does not read dev.to pages in the background; it only acts when you click the extension icon.
chrome.storage.local on your device.For privacy questions, data requests, or concerns about this policy, contact us at nerdsnipe.inc@gmail.com.