Policy

AppVeriq Guide verification policy

AppVeriq Guide is not about “fast downloads”; it helps readers separate official paths from pre-installation risk signals.

Core principles

We do not store or redistribute installers.
We point to vendor/developer-controlled paths such as official sites, official stores, and official releases.
Pages show review date, official domain, and verification status.
Hashes and signatures are recorded when they are practically checkable.
Trademarks are used only for identification and the site is not presented as an official vendor site.

Verification stages

Official source

Checks whether the path is controlled by the vendor, developer, official store, or official release channel.

Distribution target

Confirms the actual download or app-access path for Windows, macOS, Linux, mobile, or web apps.

Terms and license

Separates free, open-source, personal-free, commercial, trial, and team-plan implications.

Version and updates

Records release notes, version history, filenames, store updates, or other freshness signals.

Hash/signature

Records official checksums, signatures, or release digests when available and avoids over-claiming when absent.

Verification status labels

Verified

Official page, download path, license/terms, and available hash/signature evidence have been reviewed.

Draft

A likely official URL exists but final OS targets or licensing details still need review.

Manual review required

Automation is not enough because of bot challenges, dynamic downloads, logins, or store-only paths.

How SaaS and cloud apps are reviewed

For products such as Figma, Dropbox, 1Password, or Microsoft 365, official domain, app access, pricing, terms, privacy, team permissions, and data location can matter more than installer hashes.

AppVeriq Guide does not claim official checksums when a vendor does not publish them.

Limits of automated checks

Some official sites require challenges, region redirects, logins, app stores, or JavaScript rendering, so CLI checks alone may be insufficient. In those cases, conservative caveats or manual-review status are used.

Outdated links and rights-holder correction requests are reviewed through the contact page.