Our guarantee

Your users can prove facts from any third-party account to your application. Our servers never see the credentials, the verified data, or anything else on their account. The verified data is delivered straight from the user's device to your application's callbacks, only for the facts they chose to share. This isn't a policy promise — it's enforced by cryptography and hardware.

What is Reclaim Protocol

Reclaim Protocol turns any logged-in account into a source of cryptographically verifiable facts. The user signs into the source site (a bank, an exchange, a ride-share app, a social network, a KYC provider) on their own device. A proof of one specific fact about that account (an exact balance, a credit score, a transaction history, a verified identity, a follower count) is generated locally, then delivered to your application. Your application verifies the proof itself, without ever calling the source site. You can read the whitepaper here.

Our commitment

The promise above breaks down into three specific guarantees. Each one is enforced by a different mechanism, and you can verify each one on this page.

  • Credentials never reach us. The user signs in on their own device, or inside a TEE-hosted client where even our own team can't see the session. Either way, the credentials never touch our servers. How →

  • Verifications can't be tampered with by anyone. Not by the user. Not by us. Not by any man-in-the-middle. Each verification is cryptographically bound to its data by a zero-knowledge proof. Change the value, and the proof falls apart. How →

  • The code is the truth. Every verification service is open-source. TEE attestations prove cryptographically that the exact code you can read on GitHub is what generated your verification. You don't have to take our word for any of it. How →

Automated verification runs

Every check on this page runs automatically on a schedule: hourly (uptime), daily (supply-chain, license, TEE), weekly (PII, security, compliance), monthly (whitepaper).

Duration: 1sSections verified: 1

What this run covers

Every hour·Sections: uptime

See also: Daily Run (Every day · 10:00 IST)·Weekly Run (Every Friday · 10:00 IST)·Monthly Run (1st of month · 10:00 IST)

Duration: 1sSections verified: 1

What this run covers

Every hour·Sections: uptime

See also: Daily Run (Every day · 10:00 IST)·Weekly Run (Every Friday · 10:00 IST)·Monthly Run (1st of month · 10:00 IST)

Duration: 1sSections verified: 1

What this run covers

Every hour·Sections: uptime

See also: Daily Run (Every day · 10:00 IST)·Weekly Run (Every Friday · 10:00 IST)·Monthly Run (1st of month · 10:00 IST)

Duration: 1sSections verified: 1

What this run covers

Every hour·Sections: uptime

See also: Daily Run (Every day · 10:00 IST)·Weekly Run (Every Friday · 10:00 IST)·Monthly Run (1st of month · 10:00 IST)

Duration: 1sSections verified: 1

What this run covers

Every hour·Sections: uptime

See also: Daily Run (Every day · 10:00 IST)·Weekly Run (Every Friday · 10:00 IST)·Monthly Run (1st of month · 10:00 IST)

Duration: 1m 41sSections verified: 2

What this run covers

Every Friday · 10:00 IST·Sections: pii, compliance, security

See also: Daily Run (Every day · 10:00 IST)·Monthly Run (1st of month · 10:00 IST)

Showing last 8 runsResults are written directly to this page — no manual review

Subprocessors

View all
aws

Amazon Web Services·Cloud infrastructure (compute, storage, databases)

Google Cloud Platform·TEE confidential compute. Both TEE_K and TEE_A run as attested Docker images.

Firebase (Google)·Admin authentication (Google OAuth)

A

Anthropic·AI analysis for PII, security, and whitepaper checks