Fact-checking
DoItSwift publishes calculators, converters, and explanatory articles that many people rely on for quick answers. This page describes how we check factual claims before and after publication, and how we publish fixes. For broader rules, see Editorial policy; for research practice, see How we research.
Fact-checking here means verifying statements against evidence we can point to—not brand policing or tone editing. We still edit for clarity, but a sentence does not pass review just because it sounds confident; it passes when the links, numbers, and code behind it line up.
What we verify
We treat as high priority any statement about money, health, privacy, data leaving your device, or legal obligations. Secondary details—historical anecdotes, illustrative rounded numbers—still get a sanity check, but we prioritize claims that could change decisions or safety outcomes if they were wrong.
UI copy is in scope too: if a button says “nothing leaves your device,” that claim is checked against the actual network calls the page makes. If analytics or fonts load from a CDN, we describe that in privacy-facing text rather than implying an air gap that does not exist.
How verification works
Quantitative claims are traced to a primary citation or to the code path in the tool that produces the number. Links, arithmetic, and formulas in tables that summarize regulations or rates are verified against the named source before publication.
Where automated tests apply — for example, deterministic calculator outputs — we add regression fixtures so future changes cannot silently break them. For content pages, sources consulted at publication are noted internally so subsequent reviews can check them against current versions.
Corrections and transparency
When we confirm a material error, we correct the page and note substantive article changes where readers expect to see them. Silent typo fixes may ship without a log. Tool behavior always wins over marketing copy: if the implementation changes, the visible instructions must match.
If we cannot verify a reader report quickly, we may add a temporary caution banner rather than leaving a possibly wrong claim live while we investigate. Removing uncertainty is better than looking perfect on a deadline.
Reports from readers
If something reads wrong, send the URL, the sentence or result you dispute, and a link to a reliable source when you have one. We cannot respond to every email, but we triage safety- and privacy-related reports first.
Screenshots help when the issue is layout or a transient bug, but the strongest reports include repro steps and the environment (browser version, OS, approximate file size). That detail cuts investigation time sharply.
Contact the editorial desk
Reach us at [email protected] for fact-checking and correction requests.