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 / Database / Buyer reports

Signed buyer reports

People who bought into a tracked project can report what happened: delays, payment problems, or a good experience. Each report is signed with a passkey on the buyer's own device. Proof of purchase stays private: your browser computes a fingerprint of your contract or receipt and only that fingerprint is sent. A person reads every report before anything is published, without names.

Checking whether buyer reports are open…

File a report

Proof of purchase, kept on your device

Pick your contract, booking form, receipt or bank transfer confirmation. The file is not uploaded: this page computes its SHA-256 fingerprint in your browser and sends only those 64 characters.

Published reports

Loading…

How a report is checked

  1. Signed on your device. When you send, your phone or computer asks for Face ID, a fingerprint or your screen lock and creates a passkey for kolaboro.com. It signs the exact report (project, text, dates and the document fingerprint). The private key never leaves the device. Our server checks the signature before storing anything.
  2. One report per passkey per project. We store only a SHA-256 of the passkey's public key, so a second report from the same passkey on the same project is refused. Five reports an hour per connection, and daily caps in the database.
  3. Proof of purchase without handing it over. We keep the 64-character fingerprint of your document, never the document. If you want the moderator to see it, email the same file to [email protected] with your report number. The moderator checks it gives the same fingerprint, notes "document seen" and deletes the email.
  4. A person approves it. Nothing is public until a moderator approves it. The moderator may shorten the text to remove anything that could identify you. Published reports show the project, the kind of report, the year you bought, the month it was sent and whether a moderator saw the document.

What this does not prove

  • A passkey proves the same device signed the report, and that a person unlocked it. It does not prove who you are, and one person can create more than one passkey. That is why every report is read by a moderator and why the rate limits exist.
  • A fingerprint on file proves nothing until a moderator has seen the matching document. Each report says which of the two it is.
  • We never publish the document fingerprint. A developer holds the same contract and could otherwise match it to you.
  • A report is one buyer's account. It sits next to the project's public record; it does not change the project's checks or score.
Protect my purchase