How to use this guide: AffiliateDataset provides the factual program terms and evidence metadata used in examples. Privacy Affiliates independently produces the workflow, judgments, and conclusions. This is not a promise of earnings or a product endorsement.
Build two scorecards
Keep product-security evaluation separate from affiliate economics. The product scorecard should cover threat model, ownership, jurisdiction, logging claims, protocol choices, incident history, and independent audits. The commercial scorecard can cover commission, cookie, and payout rules. Never let the second change the first.
Design for hostile reading
Assume a skeptical reader will inspect every claim. Link primary evidence, state what you did not test, name material limitations, and timestamp the review. Put the commercial disclosure before the recommendation and explain whether compensation changes with plan length or order value.
Use a correction protocol
Security products and ownership structures change. Provide a corrections route, keep a review log, and schedule re-checks for both product claims and affiliate terms. If a source becomes unavailable or the program stops accepting applicants, downgrade or remove the listing rather than preserving an attractive historical rate.
Working checklist
- Product and commercial scores separated
- Threat model stated
- Ownership and audit claims sourced
- Compensation disclosed before recommendation
- Correction and re-review dates published