Shipping daily
Nov 1DATAAll 646 projects re-verified: 6,419 developer claims tested against registers, courts and pressNov 1DATAMalaysia TEDUH and Philippines DHSUD licence checks: expired licences and approved delays foundNov 1DATAThailand ONEP register: 2 condos found selling before environmental approvalNov 1DATAMexico PROFECO contract register checks: one sales registration belonged to a laundryNov 1DATAAbu Dhabi ADREC inspections and RAK RERA permit list added: % built straight from the regulatorNov 1SHIPPEDNew stage filter: completed but still sellingNov 1SHIPPEDPublic database page: verification levels, disclosure distribution, every marketNov 1DATA+212 projects in one day, round 3: USA, Caribbean, Gulf, Africa, Japan, AustraliaNov 1SHIPPEDStage on every case: off-plan or under constructionOct 31SHIPPEDVerification level per check on every case card: registry, independent, developer, contradicted
Changelog →

Kolaboro / Developers / Right of reply

Answer any finding, free

Every project in our database is anonymous. If you build one of them, you can answer what we found with documents: prove the project's domain is yours with one DNS record, attach your licence, permit or land title, and write your reply. A person reviews it, and only then is it published next to the finding. Developers never pay us, and paying is not possible.

Checking what is live…

1Prove the project's domain is yours

No email loop and no account: add one TXT record to the DNS of the domain the project is sold on. Only someone who controls that domain can do it. The record holds a random code made in your browser, so it does not say which Kolaboro project it is for.

2Attach your documents

Licence, building permit, land title, escrow letter, progress report. Your files do not leave your computer. Your browser computes each file's SHA-256 fingerprint and only that, with the size and type, is sent. When we ask for the file (or you add a link to it), the moderator checks it matches the fingerprint byte for byte, and the published reply lists the fingerprints so anyone holding the document can check it is the same one.

Drop files here or choose files (PDF, images; up to 12)

    3Write your reply

    What is public, and when

    Before a reply is approved

    Nothing. The project stays an anonymous id. The TXT record holds a random code, not a project id. Your reply, name, email, domain and fingerprints are visible only to the Kolaboro moderator.

    After a moderator approves it

    Your reply text, the date, the document types and their SHA-256 fingerprints, next to the finding. Your company name and domain only if you ticked the box. Your name and email are never published.

    What the moderator checks

    The TXT record is still there (checked live again), the domain really is the domain of that project in our private records, and each document matches its fingerprint and the issuing register where one exists.

    What we cannot do

    We cannot verify a document we have not seen: a fingerprint proves which file you mean, not that it is genuine. A confirmed document raises the verification level; an unconfirmed one is published as your statement.

    Published developer replies

    Loading…

    No access to the DNS? Send an unverified note instead

    This goes to our inbox, is not published automatically, and we will ask you to prove you speak for the developer before anything changes.

    What happens next

    1. A moderator re-checks the DNS record and confirms the domain belongs to that project.
    2. We check each document against the issuing register or an independent source.
    3. Within 10 working days we update the project: a confirmed document raises its verification level; your reply is published next to the finding either way.

    See what we expect developers to publish in the Off-Plan Disclosure Standard, use the free templates, or compare yourself with your market in the benchmark. Buying and want to share documents privately with your lawyer? Use an encrypted deal room.

    Protect my purchase