Questions, answered.

Because mailbox providers fingerprint email CONTENT independently of sender reputation. Other warmup tools build sender reputation by sending synthetic small-talk (no links, no CTAs, no dollar claims) — that body content is what's been getting placed in inboxes. The first time your real campaign goes out — with links, sales language, a {{firstName}} merge — it's a new content fingerprint with zero history. So it goes to spam, even though your sender looks pristine. NeverSpam fixes this by warming your actual template, so the reputation is on the content that matters.

Copy your campaign subject and body straight out of Instantly (or wherever you draft cold email). Paste them into NeverSpam. We warm exactly that — same merge fields, same links, same CTAs — against the seed pool. When you launch the real campaign a week or two later, mailbox providers have already seen and rated that exact content.

Your subscription begins automatically at the tier you selected. You can cancel anytime from the Stripe customer portal.

Warmup stops, but your account stays open and you can view your history. No prorated refunds.

Warmup pauses until the card is updated. Your account stays open — login keeps working — and a banner prompts you to update payment.

For Gmail: a refresh token via OAuth, scoped to "https://mail.google.com/" so we can send and check folders. For SMTP: just the credentials you give us, encrypted at rest with AES-256-GCM. We never read inboxes beyond what we need for bounce + inbox-placement detection.

So the Gmail consent screen carries your name, and so your Workspace admin can trust your app without trusting a shared multi-tenant OAuth client. We walk you through the 5-minute setup.

Yes. 100K+ real mailboxes across Gmail, Outlook, Yahoo, iCloud, and other major providers. We do not run synthetic engagement; what you send is what gets opened.

We use natural send cadences (10-30 min spacing, randomized per-account start time, 9 AM-5 PM ET window). The seeds open, read, and occasionally reply just like real recipients do. There's no header or signal that distinguishes a warmup send from a normal one — because, from the provider's perspective, it isn't one.

Heroku US East (Virginia). Postgres backups daily. Customer credentials (SMTP / IMAP / OAuth / Instantly API key) encrypted at rest with AES-256-GCM. No analytics on sender content.