Maker and review policies
Listing and developer confirmation establish provenance. Reviews describe the available evidence.
Listing guidelines
Listings must describe a real, publicly available software product using accurate public HTTPS sources. We reject malware, deceptive products, illegal content, impersonation, unsupported claims, undisclosed affiliate manipulation, and attempts to buy trust. Binary uploads and private evidence are not accepted.
Moderation, corrections, and appeals
We aim to respond within 10 business days. Reviewers may request clarification, reject a request with a rationale, or prepare an approved change for the next editorial catalogue deployment. Appeals may be submitted within 30 days with new public evidence. Rejected operational requests are retained for 90 days, except where law or abuse prevention requires longer retention.
Developer confirmation
Accepted proof methods are a matching domain email, a DNS TXT challenge, or a token published on the product website. Confirmation proves that an account represents the product; it does not confirm every privacy statement and cannot be purchased.
Review methodology
Reviews record a date, defined scope, evidence, limitations, and per-check results of pass, partial, fail, or Not confirmed. Checks may cover availability, ownership, privacy policy, source code, account requirements, local processing, self-hosting, tracking, deletion, and export documentation. Thryve does not issue a universal privacy score.