Data handling and identifier protection - Numpay Docs

How an identifier is verified

Numpay never checks your mobile number or email itself. Verification is done by Web3Auth: The Numpay server trusts an identifier only when it comes from a valid ID token signed by Web3Auth for the Numpay app. An identifier typed into a request body is never treated as proof of who you are.

How identifiers are stored

Mobile numbers are stored in E.164 format with spaces and dashes removed (for example +919876543210).
Emails are stored lowercased.
Each mobile number and email is unique: one identifier maps to exactly one wallet.
Identifiers are kept in Numpay’s PostgreSQL database. They are not written to the blockchain.

What other people can see

Lookup	What’s returned
By mobile number	The user’s ID, name, mobile number, wallet address, country code and status. No email.
By email	The user’s ID, name, email, wallet address, country code and status. No mobile number, so an email can’t be used to discover a mobile number.
Inside a payment or request	The other party’s ID, name, mobile number or email, and wallet address only

Encrypted keys for claimable wallets are never included in any API response.

What’s on-chain

Only wallet addresses, amounts and timestamps of transfers appear on Base. Your mobile number and email never do. See Payment privacy and on-chain transparency.