Support, data corrections, security disclosures.
| Operator | not published yet |
|---|---|
| not published yet | |
| Jurisdiction | not published yet |
| Account or billing | The email address on the account. Never send a password, a seed phrase or a private key. Nobody here will ever ask you for one, and any message that does is not from us. |
|---|---|
| A number looks wrong | The tab, the card, the value shown, and what you compared it against — a screenshot with the timestamp visible is ideal. Data disagreements are treated as defects, not opinions. |
| Security | What the issue is and how to reproduce it. Please report privately first and allow a reasonable window to fix it before publishing. |
| API or partnership | What you want to build and the request volume you expect. |
This is a small operation: replies are measured in days, not minutes. A security report is read first.
It is worth reporting even when you are not sure which side is wrong. Several of this platform's own corrections started exactly that way — the difference between a real defect and a difference of definition is usually only visible once both are put side by side. Where a figure could not be read at all, the card says so rather than showing a zero; that is a stated absence, not a bug.
Live source status shows which upstream providers are answering right now, and Methodology explains how the figures are built. If a card is blank, those two pages usually explain it faster than an email can.