01Email
Plain email is fine for most things. Use PGP below if what you're sending is sensitive — an unpublished incident, a document, or anything you'd rather not send in the clear.
02PGP
Public key: pgp.txt
Verify the fingerprint before trusting a key you fetched from anywhere else — including this page.
03If you run a listed service
Disputes are welcome and they get read. What makes one work:
- Point at the specific field. "Your custody model is wrong" is actionable; "your grade is unfair" isn't. Every grade here is built from named criteria — say which one is wrong.
- Send evidence, not assertions. Documentation, a public policy page, a transaction, an audit. We already treat a service's own marketing as a claim rather than a fact, so more of it doesn't move a grade.
- Expect the correction to be public. If you're right, the fix is published with the date and reasoning — that's the point of the corrections log. We don't quietly edit grades, in either direction.
04Tips & incidents
If a service froze your funds, demanded KYC unexpectedly, or behaved differently from what its own terms say, that's worth sending. Include what you can show: order IDs, screenshots, dates, support replies.
Unverified reports don't become grades on their own. Where an allegation is credible but unproven, it's recorded as exactly that — an allegation, marked unproven, with its source — so a reader can weigh it themselves.
05What happens to your message
Mail is read and kept only as long as it's useful for the correction it concerns. Nothing is forwarded to the service you're reporting on, and nothing identifying is published without asking first. If you'd rather not be named in a correction entry, say so — attribution is optional.