Skip to content
Yieldo

Editorial Policy

This page answers three questions: by what rules we publish numbers and texts, what happens to a mistake once it is found, and how the project makes money. What follows describes mechanisms that run in the code, not intentions for the future.

What we publish and how

  • The numbers on our pages are collected by our own crawlers straight from public exchange APIs and open sources. Every figure has a source and a polling time, and both are open to checking.
  • A fact is printed only together with the date it was collected. The answer line at the top of a page is built from the real polling time: no timestamp — no block; data older than 24 h — no block either, because the question in the heading is asked in the present tense and yesterday's rate answers it wrongly.
  • A value above 50 % APR never goes into a page title or meta description. An exchange promo rate stays visible in the table as that exchange's own claim, but it does not become ours. A fact that fails this guard is not printed at all — not as a zero, not as a dash, not as a default value: «there is no rate» and «the rate is zero» are different statements.
  • Every article carries a named author and a link to their profile.
  • Some of the text on this site is produced by a language model from our own data, and we do not hide it: that is how the short coin descriptions in the cards, the daily macro reviews and the blog articles are written. The name in an article byline says who is answerable for it, not who typed it.

Sources, polling frequency and calculation rules live on the data methodology page.

The two dates of an article

  • The publication date and the revision date mean different things, and both are visible. The publication date does not depend on text edits at all. The revision date moves only when the body of the article or its questions and answers have been rewritten: editing the title, the description, the URL or any service field does not move it. That exact date is what goes into the machine-readable markup, so what you see and what a machine reads agree by construction.
  • The stamp is set by the article itself on save, not by whoever edits it. It was built this way after a single cosmetic migration shifted the «date modified» of fourteen articles at once: the date stopped telling a rewrite apart from a replaced comma, and therefore stopped meaning anything.
  • Numbers on the data pages are dated by the time they were collected, never by the time of your visit: using render time as the data date is forbidden here and covered by a test.

Errors and corrections

  • A data error is not fixed by editing the number — it is fixed by fixing the collector, and the correction arrives with the next polling cycle. While a source stays silent, the page keeps showing the timestamp of the last successful poll, so the age of the value is visible rather than masked.
  • Once an hour a freshness watchdog checks every exchange on every feed separately and alerts the administrator when a source stops updating. Per exchange precisely: a table-wide check reported «all feeds fresh» for four days while several exchanges were silent and the remaining ones kept the aggregate age looking recent.
  • An error in an article is fixed by editing the text, and such an edit is never silent: it moves the revision date, and with it the date in the markup.

Money and independence

  • The site is free and requires no registration. The data we collect is published as machine-readable feeds under the CC BY 4.0 licence — you may take it, embed it and republish it with attribution.
  • Links to exchanges are partner links. A click goes through our own redirect, the project may earn a commission from it, and it costs you nothing extra. Articles disclose this in a dedicated line.
  • Nothing on this site is financial advice: we show numbers and where they came from, the decision stays with you.

What we do not have

  • There is no fact-checker as a separate role in this project. That is why the markup of our articles carries no «reviewed by» field (reviewedBy): the slot exists and is empty. Filling it with a name that no review stands behind would mean printing a statement that never happened into the machine-readable layer — the very deception every guard above exists to prevent. Once a review happens, the field will appear, with a name and a date at once.
  • We do not yet run a dedicated channel for error reports, and we promise no response times. Publishing an address nobody reads would be exactly the kind of promise this page avoids.
  • We publish no correction notices: the only visible trace of an edited text is the revision date that moved.

Who runs the project — the author page.