AI can forge any document. Have you upgraded your verification pipeline?

Reclaim Protocol generates cryptographic proof directly from source - the university, the employer, the airline, the bank. Nothing to upload, nothing to forge.

Try it yourself!

See how trivial it is to generate a fake document

Change the value of
0/140

How Reclaim Protocol works : 30 seconds. 3 steps.

3M verifications. 0 forged.

1

The user logs in

Your user logs into the source website - their university, employer, airline, bank etc. Reclaim Protocol never sees any credentials.

2

The fact is extracted

Only the specific data you requested is selected, like name, enrollment status, tier, age. Everything else stays on the user's device. Nothing more is ever shared.

3

The proof is generated

A cryptographic proof is created, verifying the data came from the claimed source and hasn't been altered. Unforgeable. Akin to a digital notary.

One protocol. Every verification problem.

If fraud is a problem, Reclaim Protocol is the solution. Globally.

Status Match

Instant loyalty tier verification. 100+ airline and hotel programs. No screenshots.

Education Verification

Verify enrollment from 29,000+ universities. Not just a .edu email — actual academic data.

Employment Verification

Verify employment and income from any employer in any country. From today's payroll, not from stale databases.

ID Verification

Verify age, identity, and citizenship from official sources. 200+ countries. No ID uploads. No privacy laws violations.

Nobody likes a binder full of documents. That's why we built Reclaim Protocol.

We have all uploaded a photograph of our driver's license or a paystub PDF from our employer in the last 6 months. It sucks. It's a privacy problem we're all forced to accept. Users don't want to give away all their details, outside of what is strictly required as part of the verification. Furthermore, no one wants private information sitting around on a server, waiting to be leaked.

But privacy isn't even the biggest problem. Documents can now be trivially forged with AI. Businesses that need to verify information cannot rely on document uploads, as they can be trivially forged with AI.

That's why we started this research in 2022, and published papers utilizing zero knowledge proofs - a break through cryptography - to verify user's information directly from source. You know it hasn't been tampered with. Not even one byte.

We think the internet becomes unusable if AI makes it impossible to tell truth from fiction. We're here to make sure AI gives the internet superpowers, not destroys its very foundation.

If you would like to upgrade your verification process and make the internet a tiny bit future proof - we would be honored to help. Feel free to reach out!

Madhavan (Maddy) Malolan

Cofounder & CEO, Reclaim Protocol

madhavan@reclaimprotocol.org

We've processed over 3 million verifications with zero fraud across identity, student, employment, and loyalty verification.

Top student discount platform verifies enrollment in hard-to-verify geographies

1000 students per university per day

Conversion went from 7% (Document verification) to 44% (Reclaim Protocol)

Available in all countries including Bangladesh, Indonesia, India

Europe's top Airlines verifies status instantly for a status-match

1000+ status match per day, instantly.

Verification cost slashed by 90%+

200+ per day fraud caught intercepted

Leading lending company verifies identity and credit scores

Instant credit check, around the world

No hard-to-verify document uploads needed

$3M processed, protected by Reclaim Protocol verifications

Don't trust. Verify

(That's kind of our whole thing)

Zero credential storage · End-to-end TLS · Zero data retention

10 lines of code for integration

We have support for SDKs in React, React Native, Flutter, Python, Kotlin and Swift. No matter what your product architecture is, integration takes less than an hour.

import { ReclaimProofRequest } from '@reclaimprotocol/js-sdk';

const reclaimProofRequest = await ReclaimProofRequest.init(
    'APP_ID',
    'APP_SECRET',
    'PROVIDER_ID'
);

await reclaimProofRequest.triggerReclaimFlow();

Every document can be forged. See what can't be.