Why Product Nerve AI requires identity verification before you start

If you've gotten partway through signing up for Product Nerve AI and hit the identity verification step, you might be wondering why a startup validation tool needs your government ID. It's a fair question, and we'd rather answer it directly than leave you guessing.

The short answer: we verify identity so that the platform stays honest, for you and for everyone else on it.

Here's the longer version. Product Nerve AI produces real analysis: scores, reports, financial models, investor materials. That analysis is only worth something if the platform is populated by real founders doing real work, not throwaway accounts testing the system, running validation dozens of times to game a score, or using the platform for something it wasn't built for. Identity verification is one of the quiet mechanisms that keeps that from happening. It's the same logic that makes an accelerator's admissions process meaningful, a filter that says this space is for people doing the work.

There's a second, more practical reason. As the platform grows to include investor facing documents, cap tables, and eventually team collaboration and billing, having a verified identity behind every account is a foundation you can't retrofit later. We'd rather build it in from day one than bolt it on after there's a reason to regret not having it.

What you'll need. A government issued ID, a national identity card, driver's license, or passport, that's it. The verification itself takes about two minutes and runs through an automated verification partner. Most people are approved within moments; a small number of cases route to manual review, which can take longer but is rare.

What happens to your document. This is the part we want to be completely unambiguous about: your identity document is stored in a separate, restricted part of our systems from everything else in your workspace. It is never sent to any AI model, never used as context for any generation, and never appears anywhere inside your projects. It exists for exactly one purpose, verifying that you are who you say you are, and nothing else.

What if verification is rejected? It happens occasionally, usually due to image quality or a document type issue rather than anything more serious. Rejected verifications route to a human on our team for manual review rather than leaving you stuck. If you run into trouble, reach out through Support and we'll sort it out directly.

One more thing worth knowing: business verification (KYB) is a separate, optional step that only comes up later, if you use a feature that specifically requires it, like generating a data room or a co-founder agreement. It's reviewed manually by our team, no automated document scanning, and until you need one of those specific tools, you'll never encounter it.