Trust & transparency
Editorial Policy
Tempmail’s engineering blog is written by the people who build and test our disposable inbox, API, and QA tooling. This page explains how we source, review, update, and correct that work.
Last reviewed:
Named teams
Every byline identifies the engineering, QA, security, or privacy team responsible for the article.
Sources listed
Guides link to the standards, documentation, and research behind their claims.
Dates visible
Published and materially updated dates appear on the page and in the article schema.
Corrections welcome
Send the URL and the correction to our contact page. Substantive fixes update the article date.
1. Who writes our articles
Articles are published under team bylines — for example, Testmail Security Research, the QA Engineering Group, or the Privacy Architecture Team. Each byline identifies the group responsible for the article and its updates. We do not invent individual authors or credentials to make a guide look more authoritative.
The author box on every article includes the team’s role and a short description of the work it does. If a guide was written by a different team in the future, the byline and author box will change with it.
2. How we research and test
Our starting points are primary sources: RFCs, NIST publications, browser and framework documentation, and official vendor guidance. When a claim can be tested against a running system, we prefer a hands-on test over a paraphrase of someone else’s blog post.
Code samples are executed where practical. If a snippet is illustrative rather than a complete, runnable example, the surrounding text says so. We also distinguish between behavior we have observed in Tempmail and behavior that depends on a third-party provider.
3. Sources and further reading
Each article ends with a Sources & further reading list. The list is not a bibliography of everything we read; it is the set of documents a reader can use to check the article’s most important claims. Links open in a new tab and point to the original publisher.
A source appearing in the list does not mean the publisher endorses Tempmail. It means we relied on that document for a specific point. If you believe a source is outdated or has been misread, tell us.
4. AI assistance and editorial responsibility
We use AI-assisted tooling for drafting, editing, and validation. The team named in the byline is responsible for the published claims and for keeping the article current. AI output is treated as a draft, not as evidence.
We do not use AI to fabricate test results, citations, author identities, or customer stories. Where an article includes a measurement or a code sample, the source or test method should be visible to the reader.
5. Independence and disclosure
Tempmail is the product built by the team behind this blog. Articles may link to Tempmail features, the API, or the disposable inbox because that is the system we know best. We disclose that relationship here rather than pretending the blog is independent of the product.
Articles are not paid placements. If we ever publish sponsored content, it will be labeled clearly and kept separate from editorial recommendations.
6. Corrections and updates
We correct substantive errors — wrong technical claims, broken code, outdated standards, or misleading framing — and update the article’s modified date when we do. Small copy edits may be made without changing the date.
To report a problem, use the contact page and include the article URL, the passage you are questioning, and the source or test that supports your correction. We aim to acknowledge reproducible corrections and to explain any change we make.
Questions about our standards?
Send the article URL and the detail you want us to check. For privacy or data-handling questions, start with the privacy policy.