Editorial Policy

Every article on TempMailKit is written and edited by Achyuth Kumar, the founder and sole operator of TempMailKit, with input from the people who build and run the service day to day. We write about email privacy, disposable addresses, spam, phishing, authentication protocols, data brokers, and digital security because these are the problems we actively work on, not topics we have outsourced or assembled from third-hand sources.

We are practitioners, not generalists. Our technical claims about how SMTP, SPF, DKIM, DMARC, Redis, Cloudflare, and related infrastructure work come from direct operating experience, not from paraphrasing Wikipedia. When an article is reviewed or substantially updated by someone other than the original author, that is noted in the article. Our goal is that you always know a real, named person stands behind what you are reading.

We do not accept guest posts, paid content submissions, or ghostwritten articles on behalf of third-party companies. Every byline on TempMailKit represents genuine in-house authorship.

We base technical claims on primary sources wherever possible. These include:

• Published internet standards (RFCs) for email protocols — SMTP, IMAP, POP3, SPF, DKIM, DMARC, MIME, and related specifications
• Official documentation from Google, Microsoft, Cloudflare, Upstash, Vercel, and other infrastructure providers we use
• Original legislation and regulatory guidance for privacy law topics (GDPR official text, FTC guidance on CAN-SPAM, ICO publications)
• Peer-reviewed security research and CVE disclosures for vulnerability-related topics
• Verified breach data from reputable sources such as Have I Been Pwned for statistics on data breaches
• First-hand testing of services, tools, and configurations described in our articles

When a factual claim in an article depends on a specific external source, we link directly to that source so you can verify it yourself. We do not cite secondary summaries of primary sources when the primary source is accessible.

We do not publish content generated automatically and left unchecked. Drafting tools may be used to produce initial structure or suggest phrasing, but a human reads every factual statement, verifies claims against their sources, rewrites for clarity and accuracy, and takes personal responsibility for the result before it goes live. No article publishes without a final human review.

Before an article is published, it goes through an internal checklist:

• Factual accuracy: Every specific technical claim, statistic, or legal requirement is verified against the source it came from. Claims that cannot be sourced are removed or rewritten as qualified opinion.
• Balance and honesty: We describe the limitations of disposable email honestly. If a tool or approach has real downsides, we explain them clearly. We do not write promotional content dressed up as editorial.
• Practical usefulness: We ask whether the article genuinely helps a reader solve a problem or understand a topic, rather than simply targeting search keywords. If the article would not help someone who arrived with a real question, it is rewritten or not published.
• Internal consistency: Claims in new articles are cross-checked against related articles already published. Where we reference our own related content, those links are to relevant, substantive pages rather than to improve search rankings.
• Currency: Articles about evolving topics (privacy law, platform policies, security tools) are checked to confirm that the information is current at the date of publication.

All articles display a publication date. Articles in areas subject to change — email platform policies, privacy legislation, security tool behaviour, browser capabilities — are revisited on a regular schedule and updated when the information they contain changes materially.

We distinguish between two types of update:

• Minor updates: Corrections to grammar, spelling, broken links, or minor clarifications that do not change the article’s meaning or factual assertions. These are made silently; the publication date is not changed.
• Material updates: Changes to factual claims, the addition of significant new information, or the removal of information that has become incorrect. Material updates are noted in the article with an “Updated” date, and where the change substantially affects the article’s conclusions, a note explaining what changed and why.

We do not revise articles to make past statements appear more accurate than they were at publication. If we got something wrong, we correct it clearly and say so.

If you find a factual error in any article — a misstatement of how a protocol works, an outdated legal reference, an inaccurate statistic — please tell us. We take corrections seriously and respond to every correction report personally.

When a reported error is confirmed, we correct it promptly. For material errors — ones that affect the practical advice in the article — we add a visible correction note to the article explaining what was wrong, what the correct information is, and when the correction was made. We do not silently rewrite articles to remove evidence of errors.

We also accept corrections on style and clarity when a reader found a passage confusing in a way that could lead to misunderstanding. These are evaluated and applied where they genuinely improve the article.

TempMailKit is funded by display advertising through Google AdSense. This is disclosed clearly on the site and in our Privacy Policy.

Advertising income does not influence what we write. Advertisers do not have input into article topics, conclusions, or recommendations. No article is written to promote a product or service in exchange for payment, and no recommendation in any article reflects a paid relationship.

Where we mention third-party services — email alias providers, VPNs, password managers, privacy tools — we do so on editorial merit, based on our own evaluation of the product or on reliable public information about it. We do not participate in affiliate programs or receive commissions for linking to or recommending any product. Links to third-party services are editorial links, not commercial ones.

If this ever changes — for example if we introduce affiliate links to recommended products — we will disclose that clearly at the top of affected articles and in the relevant policy pages. As of the date of this policy, no such arrangement exists.

TempMailKit publishes guides in the following areas:

• Email privacy and security: How email works at a technical level, how it can be abused or compromised, and practical measures to protect yourself.
• Disposable and alias email: When and how to use temporary inboxes, the trade-offs between different approaches, and how disposable email fits into a broader privacy practice.
• Online privacy tools and practices: Password management, two-factor authentication, data broker opt-outs, digital footprint reduction, and related privacy fundamentals.
• Spam, phishing, and email threats: How attacks work, how to recognise them, and how to minimise exposure.
• Developer and QA use cases: Technical guidance for software engineers and QA teams using disposable email in testing pipelines.

We stay within this scope because it is the area where we have genuine expertise and where we can provide more useful information than a general-interest publication would. We do not publish articles outside these topics simply to increase content volume.

For completeness, here is an explicit list of practices we do not engage in:

• We do not publish AI-generated content without human verification and editing
• We do not publish articles whose primary purpose is to rank for a search term rather than to help a reader
• We do not accept payment to include, exclude, or modify the presentation of any product, service, or opinion in our editorial content
• We do not use misleading headlines or titles that misrepresent the content of an article
• We do not republish or paraphrase other publications’ articles without substantially adding original analysis or information
• We do not suppress corrections or modify article history to conceal past errors