Shipping daily
Changelog →

Kolaboro / Editorial policy

Editorial policy

How we choose what to cover, how a fact gets on a page, who is accountable, when pages are reviewed and how we correct mistakes.

Reviewed on . Next scheduled review: .

What we publish

  • Facts about off-plan projects that a developer, its sales agents, a listing, an official register, a court, a regulator or the press made public, each with the address of its source and the date we read it.
  • Where we find nothing, the page says "not published". We do not fill gaps with estimates.
  • Scores computed by published rules, so anyone can recompute them.
  • No verdicts on named companies: we show what is public and what we could check.

How we choose what to cover

  • We cover off-plan projects marketed to buyers, found on developer websites, listing portals and official registers.
  • A project is added when its developer or a sales page publishes it. Nobody can pay to be added, removed or ranked.
  • Projects of companies linked to a Kolaboro founder are never reviewed or ranked. Projects in Sumba appear only in the Sumba transparency ranking.
  • Projects added but not yet read by our researchers are labelled "not yet reviewed".

Independence

How a fact gets on a page

  1. We read the source and keep a dated copy with its SHA-256 fingerprint.
  2. We record the fact with the address of the source and the date we read it.
  3. Where an official register is open, we look the fact up there and record the result.
  4. Scheduled jobs re-read the sources and record what changed.
  5. A person reviews every developer reply and every buyer report before it is published.

Moderation policy · Where our facts come from

Who is accountable

Kolaboro is run by its two founders, as presented on our About and Team pages:

  • Carlos de Ory: CEO, leads product and growth
  • Ignacio Hojas García-Plaza: co-founder, leads data, register integrations, the API and partnerships

Data and method: Ignacio Hojas García-Plaza, co-founder, who leads data and register integrations. Published by Kolaboro, operated by Equinox Investment Group LLC.

Team and method · About Kolaboro

When pages are reviewed

  • Project pages and rankings are recomputed each time a data file changes. Our jobs run every day: see how we work.
  • Guides, method pages and this policy are re-read at least every three months. Each shows the date of its last review and of the next one.
  • The transparency score method has a version number. A change to its points gets a new version, a date and a line in the changelog.

Method version 1.0, in use since ; points unchanged since then. Next method review: . Transparency score method · How we work

Corrections

  • Every project page has a "Report a correction" link. Developers can also reply on their own pages.
  • When a fact is wrong we fix it and log the date, what the page said, what it says now and why.
  • Errors we find ourselves, for example in our accuracy checks, are logged the same way.

Corrections

Reuse of our data

  • Our data and rankings are free to reuse under CC BY 4.0, with the credit "Kolaboro, kolaboro.com".
  • Our CSV and JSON data files carry the licence in their Link header, and the pages that offer them say so.
  • The scoring rules are published as open-source code (MIT licence).
  • We do not collect personal data about private individuals.

How to cite · Data policy · CC BY 4.0

What we do not do

  • No paid placements: developers never pay us.
  • No legal, tax or financial advice: facts, and questions to ask.
  • No reviews or ratings unless they come from verified buyers.
  • No made-up examples: an illustrative example is labelled as fictional on the example itself.
Protect my purchase