Contact
Contact
One inbox for everything: questions, data corrections, trademark requests.
Last updated: October 25, 2026
Prefer a subject line that says what the message is about — it routes faster:Data correction, General question,Trademark request or Privacy request.
We answer by email rather than a web form so that every correction keeps a traceable thread with its sources — the same evidence trail we publish on data pages.
Report a data error
This is the channel we care most about. A wrong field is worse than a missing one, and community reports are how we catch what daily probes miss.Corrections backed by a source are acknowledged within 48 hours and applied as soon as they are verified — usually within that same window. If we cannot verify a report, we reply with what we found instead of silently changing the value.
Open a pre-filled correction email, or send the same details in any form:
Field that is wrong: … (e.g. iOS client listed as Official)
What the page says: …
What it should say: …
Source: … (official docs, repository, or store listing URL)
A source URL is what makes a correction fast. Without one we have to reproduce the finding before we can act on it.
Response times
| Topic | Where | Target |
|---|---|---|
| Data corrections | [email protected] | Acknowledged within 48 hours; verified fixes applied promptly |
| Trademark / takedown requests | [email protected] | Response within 48 hours; see the naming policy on Methodology |
| Privacy requests (access, deletion, opt-out) | [email protected] | Handled per the Privacy Policy |
| General questions | [email protected] | Within a few business days |
What we can't help with
We are a comparison and data site, not a support desk for the projects we cover. For installation and troubleshooting questions, the fastest route is always the project's own community — its GitHub issues, forum or chat. Our Methodologypage explains what our data does and does not tell you.
Business & partnerships
We do not sell sponsored content, paid placements or links, and we do not accept payment in exchange for coverage — so we will politely decline offers of that kind. Genuine data partnerships and corrections from maintainers, on the other hand, are always welcome.