ModeesWho writes it
Modees Learn is written and edited by the Modees team. The byline is the team because these guides are maintained collectively, not published under a borrowed expert name. When an article has a named author, that person's role appears with it.
We do not publish paid placements, affiliate reviews or invented client stories. If a product is mentioned, it is because it is part of the workflow being described, not because someone paid for the mention.
How claims are checked
Technical statements are checked against the primary documentation: the RFCs for SPF, DKIM and DMARC; Google, Microsoft and Yahoo's published sender guidance; the ICO's direct-marketing guidance and the text of PECR and the UK GDPR. Where a provider's behaviour is described, the provider's own documentation is the source.
Numbers are treated carefully. A figure from a provider is named as theirs. A scenario used to explain a point is labelled as an illustration, not a benchmark. We do not present a made-up statistic as a result.
The consent and PECR articles describe a practical process, not legal advice. Rules differ in Scotland and outside the UK, and guidance changes; have the process reviewed before it carries material revenue.
What we publish, and what we do not
One article answers one question. If two ideas need separate outlines, they become two articles. We would rather publish four useful pieces a week than fifty thin pages that repeat each other; search engines treat scaled, low-value content as a liability, and so do readers.
The opening half of every guide is free to read. Joining the mailing list opens the rest and every new guide: one confirmation email, no account and no card. A signed-out reader and a search engine are shown the same page, because hiding an answer while telling a crawler it is there is not a strategy we would defend.
Corrections
If something here is wrong, reply to any Modees email with the article URL and the sentence. We will check it against the source, correct the article, and move its updated date. Substantive corrections are described in the article rather than quietly rewritten.
Last updated 25 October 2026.
Primary sources we use
- RFC 7208 — Sender Policy Framework
- RFC 6376 — DomainKeys Identified Mail
- RFC 7489 — DMARC
- Google Workspace email sender guidelines
- ICO direct marketing guidance
- The Privacy and Electronic Communications Regulations 2003
- Data Protection Act 2018
- Companies House register