Contact Registration Risk Index
Send the page, passage and current evidence to the appropriate publication channel. Keep personal identity records, passwords and API keys out of the inquiry.
Corrections to product facts, scores, sources or the comparison.
- Send the page URL and the passage or criterion in question.
- Include current product documentation, pricing and the relevant date.
- To suggest a tool, explain its registration-risk scope and link to public evidence.
Research collaboration and useful educational resources for software buyers.
- Describe the intended audience and the proposed work.
- Keep commercial terms separate from factual corrections.
- A commercial inquiry cannot buy a score, review slot or ranking position.
Questions about this site or information supplied in an editorial inquiry.
- Identify the page, interaction and approximate date.
- Do not send passwords, API keys or payment details.
- Direct product-account or demo-data requests to the relevant vendor.
Questions about a vendor link, referral parameter or commercial disclosure.
- Include this site’s page URL and the destination link.
- Explain the tracking, attribution or wording you want checked.
- Use the editorial channel for a disputed product fact.
Questions about the ranking, methodology or new account fraud prevention category.
- Include your publication, topic and deadline.
- Link to the score or figure you want to discuss.
- Start with the methodology and source directory for reusable context.
Before writing
Read Methodology, Sources and About for editorial context. These contacts concern the publication, not vendor product support.