Verified identity claims without exposing identity

Pelican acts as a verification guarantor for emails and phone numbers, allowing applications to trust claims without storing sensitive data.

Pelican verifies and cryptographically binds identity claims such as email addresses and phone numbers to a user's vault. Applications receive verification guarantees with verification information.

Claim Types

Email Address

Verification: One-time verification and cryptographic binding

Exposure: Optional

Phone Number

Verification: SMS-based verification and device binding

Exposure: Optional

Core Features

Verification Guarantee

Pelican guarantees that a claim has been verified and is controlled by the authenticated user.

Selective Disclosure

Applications can request emails and phone numbers with verification information trusting that the claim is verified.

How It Works

1

User verifies email or phone once in Pelican

2

Claim is cryptographically bound to the vault

3

Application requests the claim

4

Pelican returns the claim with verification information

Use Cases

Account recovery flows
Fraud prevention and trust scoring
Communication enablement
Compliance-sensitive applications

Frequently Asked Questions

Does my app need to store emails or phone numbers?

No. Applications can rely on Pelican's verification guarantees without storing personal data.

Can users hide their email or phone number?

Yes. Claim disclosure is optional and controlled by the user.

What happens if a phone number changes?

The previous claim is invalidated and a new verification is required.

Ready to verify identities securely?

Start verifying users without compromising their privacy.

Verify with Pelican