Aerod should correct errors clearly and quickly. Privacy, VPN, proxy, and defensive security content can become outdated as providers change, browsers update, policies shift, and tools behave differently.
What may be corrected
Corrections may cover:
- Incorrect technical explanations.
- Outdated provider details.
- Broken affiliate or source links.
- Incorrect pricing or feature descriptions.
- Content-transfer errors.
- Missing disclosures.
- Incorrect publication or review dates.
- Methodology language that no longer matches app behavior.
Minor edits
Small grammar, formatting, accessibility, or clarity edits may be made without a correction note when they do not change meaning.
Material corrections
A correction is material when it changes a recommendation, risk explanation, provider description, methodology claim, privacy statement, or user decision. Material corrections should be reflected in a correction note or changelog entry and followed by a fresh review.
The correction note should identify what changed without repeating private correspondence or unnecessary personal information. If the original wording could have led to an unsafe or materially different decision, the replacement should be clear enough that a returning reader can understand the new conclusion.
Provider update requests
Providers may request corrections. Aerod should review the request against source material and observed behavior. Provider requests should not be accepted automatically because of affiliate status or business pressure.
Requests that concern changing prices, plan names, limits, ownership, policies, or technical capabilities should include a current primary source. Marketing preference alone is not evidence that accurate critical wording should be removed.
How reports are reviewed
Aerod should first verify the affected URL and exact claim, then compare the report with the page's cited evidence, the current product or browser behavior, and any relevant first-party documentation. A correction can be declined when the report does not identify an error, lacks supporting evidence, or asks for promotional wording rather than factual accuracy.
There is no guaranteed publication outcome or response time. Security vulnerabilities should be sent through the separate Responsible Disclosure process rather than a general editorial correction request.
Transferred-content issues
If an article is missing source text, screenshots, tables, metadata, disclosures, or dates, Aerod should hold the page for review instead of filling gaps with generic replacements.
Contact
Send correction requests through the Aerod correction form. Include the page URL, the disputed text, the proposed correction, and supporting source material.