For government & public institutions
Public decisions get examined. Whoever examines them will ask where the numbers came from, who was actually asked, and whether anything changed after collection — and a procurement process will ask before the study even starts.
Most collection vendors can hand over a spreadsheet. Very few can show who accessed it, when, and that it has not been edited since.
When evidence supports an unpopular decision, the method is what gets attacked. An unverifiable dataset is indefensible regardless of how carefully it was collected.
Any study that only reaches people with smartphones and data plans has already excluded the populations most affected by public services.
An audit trail over the dataset, not just the report drawn from it.
Each dataset carries a SHA-256 fingerprint anchored to a public ledger outside our control, so the date it was sealed can be confirmed without trusting the platform that produced it.
Web, Telegram, video responses, and offline field collection through ODK Collect or KoboCollect — one study, one dataset, regardless of how people answered.
A facial liveness check confirms a unique real person. No ID document is collected, and results carry wallet addresses rather than names — verification without building an identity database.
Enterprise agreements can specify where data is stored, alongside SSO, role-based access and audit-ready exports.
27 languages, so a national study reaches citizens in the language they actually use.
Read live from the platform, not written into this page.
Stated plainly for the record: a seal proves integrity and timing, not representativeness. Sampling frame and weighting remain methodological choices, and we would rather document them openly with your team than let a verification badge imply something it does not cover.
Check any dataset's fingerprint yourself →Who you need to hear from, roughly how many responses, and where. You will hear back from someone who can actually answer it.
