POTENTIAConsent-based diligence, explained in one sentence
Strip away the legal framing and the model is simple: instead of a fund or recruiter quietly compiling a founder's public footprint on their own, the founder is sent a request, reads exactly what would be checked, and agrees before anything happens.
From there, they connect the accounts themselves — GitHub, X, a LinkedIn export, a pitch deck, a company website — rather than having someone else scrape or guess at them. The resulting report is built from what they actually shared, not from whatever a search engine happened to index.
The founder can also see what was connected and disconnect it afterward. That single feature — a real "undo" — is something almost no informal OSINT process offers, because informal OSINT processes were never built with the subject's control in mind to begin with.
None of this makes the underlying signal worse. A GitHub commit history connected by its owner is the same commit history a scraper would have found. What's different is that the person it belongs to knew, and said yes.
See how a consent-based check actually works.