Land like a human: why we built MailDignity.

For years, the conversation about cold email was a conversation about infrastructure. Authenticate your domain. Configure SPF, DKIM and DMARC. Warm up the inbox. Keep volume under control. Avoid the spam folder. All of that still matters. None of it answers the question that follows delivery: what does the person who receives this email feel compelled to do?

Technical deliverability decides whether a message can reach an inbox. Human reputation is what happens once it arrives: a reply, a quiet deletion, an unsubscribe, or a spam report. Mailbox providers can observe those reactions. Authentication is not immunity from the consequences of repeatedly making people feel used.

MailDignity is not a replacement for your deliverability stack. It is the missing check between a draft and a send: not “will this reach a human?” but “does this treat that human as a peer?”

A useful introduction can still start a valuable relationship. A stranger can have a relevant offer, a specific observation or something worth reading. The problem is not that an email is commercial. The problem is the assumption that the reader already owes the sender attention, effort or time.

When generating another personalised email costs almost nothing, it becomes easy to ask thousands of people for “just 15 minutes”. The sender spends seconds; the recipients collectively spend hours sorting, deciding, declining and recovering their attention. A request can be polite in wording and still unequal in what it demands.

Earn the next step before asking for it. State the professional reason, make the first response cheap, and leave room for an honest no. A meeting is a reasonable outcome of mutual interest; it is not an entitlement created by sending an email.

What readers call “cringe” is often more concrete than taste. Silence is framed as a debt. A fake Re: line borrows the appearance of a conversation. An unsolicited audit announces that a stranger’s work is broken. A flattering opening could have been sent to anyone. A vague subject disguises a sales pitch.

These are recognisable boundary crossings, not a list of forbidden words. MailDignity names ten of them and points to the actual language responsible. That makes a verdict actionable: you can see what the draft takes from the recipient and change that part without throwing away your offer.

The same sentence can mean something different in a different relationship. “Can we talk for 15 minutes tomorrow?” is ordinary coordination after someone has asked for your help. As a first message to a stranger, a fixed time demand can put the calendar decision ahead of any demonstrated relevance. A friendly invitation is not automatically a failure just because it mentions a call.

“I think you’re great” may be warm and sincere between people who know each other. In a cold campaign, unspecific praise repeated across prospects can read as a placeholder. Likewise, “following up on our conversation” is useful context if that conversation happened; inventing it to get an open crosses a different boundary.

A requested website review is a service. An uninvited declaration that a stranger is losing customers is a diagnosis they did not ask for. Referencing a public product launch can explain professional relevance. Referencing a pregnancy, health condition or family event to open a pitch intrudes on private life.

Cold outreach is the default lens. Personal Mode, available as Everyday email, relaxes stranger-specific expectations for ordinary correspondence. The checker works with the draft and the context you supply; it cannot independently establish a relationship, verify a claimed conversation or know every fact behind the message. Context changes the interpretation, not the obligation to be honest.

An email draft may contain customer names, commercial terms and information that was never meant to become a training example or a permanent audit record. Our product should not need to accumulate those drafts in order to work.

Email bodies are processed in memory and are not stored at rest by MailDignity. Signed-in audit records retain metadata only: verdict, short summary, issue types and their severity, and word count. Feedback contains no email snippets. API keys are stored as one-way hashes, rather than readable credentials.

Short-lived repeat-check caching is memory-only, not a saved copy in your history. This zero-retention design describes MailDignity’s storage: content still has to be processed by the AI service to perform an audit. It is not a claim that no other system in your own sending workflow ever holds the email.

AI gives senders leverage. A dignity gate puts some of that leverage to work for the recipient: less invented familiarity, fewer obligatory meetings, less homework and a clearer reason to care.

We do not want to outlaw selling, erase personality or turn every message into the same bland template. We want a sender to make a real offer without pretending a relationship already exists. Keep the facts. Keep the voice. Repair the boundary crossing.

The writer generates. MailDignity checks. Your workflow decides what to send. Technical infrastructure gets you to the inbox; treating the reader like a human gives you a reason to remain welcome there.