What we publish
Our public pages explain product behavior, email data concepts, verification workflows, pricing rules, integrations, security boundaries, and result limitations. We prioritize questions that help a reader make a decision or use the product safely.
How pages are prepared
- We start from the current product implementation, provider contract, or a clearly identified public source.
- We separate observed product behavior from general protocol context and opinion.
- We state the population, date, method, or limitation when a claim depends on measurement.
- We link related explanations so a reader can inspect the evidence and the boundary.
What we do not do
We do not invent accuracy percentages, certifications, testimonials, customer results, rankings, deliverability guarantees, or security claims. Unknown results remain unknown. A demonstration is labeled as a demonstration and is not presented as a live mailbox test.
Updates and corrections
Pages show a last-updated date when the subject depends on product behavior or a changing source. If you find a factual error, contact Refresh List support with the page URL, the specific statement, and the evidence that should be reviewed.
Sources and responsibility
Product pages describe the current Refresh List workflow. Educational pages should be read with their linked standards, provider documentation, and limitations. Refresh List is responsible for the accuracy of its product descriptions; it does not control third-party provider behavior or receiving-system decisions.
