Contact us
The most useful message you can send us is one pointing out that we got something wrong, or that a figure has gone stale. Those get acted on and logged.
How to reach us
This is the site's only public address. It takes error reports, corrections and general questions. We read everything but do not promise to reply to everything — what gets a reply is anything that requires us to change something, and the change itself shows up in the corrections record.
What is most useful
- Factual errors. A figure copied wrong, a rule described backwards, a source link pointing at the wrong page. Include the page address and the value you believe is correct.
- Stale data. Something marked 2026-08 that the platform has since changed. This is the most valuable kind of message, because we cannot watch every page at every platform.
- Broken links or page faults. A link that does not open, a tool that does not work, a filter button with no effect.
- Ambiguous wording. A passage you read twice and still were not sure about is usually our fault.
What we cannot help with
- Account problems. Withdrawals that have not arrived, rejected verification, frozen accounts — only the platform can handle these, and you must contact them through the official entrance inside your own account. We are not any exchange's support desk and have no access to any platform account.
- "What should I buy" or "is now a good time". This site does not give investment advice; see the disclaimer.
- Sponsored content, partnerships, table placement. Nothing here is for sale; see the disclosure. Messages of this kind are not answered.
One note about impersonation
We never contact you first, never ask for a verification code, password, recovery phrase or remote access, and never ask you to transfer anything for any reason. Anyone claiming to be Speccue and asking for those things is not us. The same logic applies to anyone claiming to be exchange support — support is reached from inside your own account.
Security reports
If you have found a security issue with this site rather than a content error, use the same address and put "security" in the subject. Machine-readable contact details are in /.well-known/security.txt.
For context: this is a purely static site with no server-side logic, no user accounts, no database and no collection of personal data. That narrows the possible surface considerably, though not to zero.