Corrections
Last updated 16 July 2026
We will get things wrong. This page is how you tell us, what we treat as an error, and how a correction shows up on the page once we have made it.
CryptRing does not yet have a registered legal entity, so the publisher responsible for these corrections cannot be named — [COMPANY LEGAL NAME] S.R.L. is a placeholder. The process below is the one we already follow; this page stops being a draft when there is a company named behind it.
Contents
1. How to report an error
Email hello@cryptring.com with “Correction” in the subject. There is no form and no ticket queue — a person reads it.
What makes a report actionable in one pass:
- The link. The exact article or token report page, not the section it lives in.
- The sentence or number you believe is wrong, quoted.
- What it should say, and how you know — a transaction signature, a mint address, a block explorer link or a primary source beats an assertion.
You don’t need an account, and you don’t need to be the project involved. Anyone can report anything.
2. What we correct
We correct anything that is factually wrong, including:
- A wrong number, name, mint address, date or figure.
- A misread on-chain fact — an authority reported as revoked when it isn’t, liquidity called locked when it isn’t.
- A claim the data doesn’t support, or a sentence that reads as advice. Both are errors under our Editorial Policy.
- A broken or mis-targeted link, and a missing or wrong attribution.
- A defect in the scoring engine itself. That one gets fixed in the engine, and every affected report changes with it — not just the article that quoted it.
What we don’t change on request: a factually accurate piece a project dislikes, and a RingScore. The score is what our engine measured; if you believe the measurement is wrong, that is a data or engine report and we treat it as one.
3. A score that moved is not an error
RingScores are timestamped measurements. Liquidity gets locked or pulled, authorities get revoked, holders concentrate or disperse — and the score follows. An article quoting a score of 41 last week is still accurate today even if the token now scores 63, because the article reports what was true when it was measured.
The live number is always the one on the token report page, and every score we publish links to it. If an article and a report disagree, the report is current and the article is dated — that is the design, not a contradiction.
What is a correction: an article that quotes a score the engine never produced, states a measurement date wrongly, or presents an old snapshot as the current position.
4. How a correction appears on the page
Corrections are visible, dated, and specific. When we fix a substantive error, the article carries a note saying what was wrong, what it now says, and when we changed it. We don’t silently rewrite a claim and leave the page looking untouched.
- Substantive error — a wrong number, a wrong fact, a claim withdrawn: dated correction note on the article, permanently.
- Headline or standfirst change that alters the meaning: noted the same way.
- Typo, broken link, formatting — fixed without a note. A missing comma is not a correction.
We fix a verified error as soon as it is verified, not on a publishing schedule. If a claim is serious and we can’t verify it quickly, we say so on the piece rather than leaving it standing unqualified.
5. Takedowns, legal complaints and right of reply
We don’t remove accurate reporting because it is unwelcome, and removal is never for sale. Where a piece is materially wrong about a project, the correction is the remedy — and if the project wants to respond, we will publish a short, on-the-record response alongside it.
Legal notices, personal-data requests under GDPR and copyright complaints go to privacy@cryptring.com and are handled under our Privacy Policy and Terms, not under this page.