Corrections Policy
Last updated: August 2026
Our Commitment
We are committed to accuracy. If we publish information that is factually incorrect, outdated, or misleading, we want to know about it so we can correct it promptly.
This subject area goes stale faster than most. Projects are discontinued, release channels move, patches stop targeting a version, and a fix that worked last year quietly stops working. A page can be written carefully and still be wrong six months later through no fault of anyone. Reader reports are the main way we find out.
How to Report an Error
If you identify an error in our content, please provide:
- The URL of the page containing the error
- A description of what is incorrect
- If possible, a source or reference for the correct information
Send it to contact@vancedapp.io. The source is the most useful part, and a link to a project's repository, release notes, or announcement carries the most weight. You do not need to identify yourself, and we do not publish the names of people who report errors.
What Counts as an Error
Anything checkable that we got wrong: a feature described that does not exist, a step that no longer works, a project listed as active when development has stopped, a link pointing somewhere it should not, a version number or date that does not match the source. Broken instructions count too, even where the original wording was accurate when written.
Disagreement about a recommendation is a different thing, and we treat it differently. If a comparison page reaches a conclusion you would not, that is not necessarily an error, though it is often a sign that the page failed to explain a trade-off properly. Those messages are read and frequently lead to edits, just not under this policy.
How We Handle Corrections
- Minor corrections (typos, formatting): Fixed within 24 hours without a public note
- Factual corrections (incorrect claims, outdated status): Fixed promptly with a note on the affected page
- Significant corrections (major factual errors): Fixed immediately with a prominent correction notice
Every report is checked against a primary source before anything changes, which occasionally means a report is correct about the problem but not about the fix. Where a claim turns out to be unverifiable in either direction, the page is rewritten to state the general case instead of the disputed specific.
Where the same claim appears on more than one page, the correction is applied across all of them. The English pages are the source of record for the translated versions, so a correction there is what triggers the corresponding change in the other languages.
What We Will Not Change on Request
Some messages ask for edits that would make a page less accurate, and those are declined. We will not describe YouTube Vanced as current or maintained, because it was discontinued in March 2022 and 17.03.38 was its final release. We will not add links to APK mirrors or aggregator sites in place of a project's own release channel. We will not remove a documented risk or limitation because it makes an app look worse, and we will not add a claim about testing, scanning, or certification that we did not perform. Our editorial policy explains why those lines exist.
Transparency
All significant corrections will be noted on the affected page with the date of correction and a brief explanation of what was changed. Pages also carry a last-updated date, and we do not advance that date unless the content actually changed.