How it works
Transparent verification without continuous surveillance.
Metric ID enables precise, time-bound location verification for organizations that value human agency and data privacy.
The logic of consent
Nothing happens until the user says yes.
Opening a request reveals its details. Authenticated consent is the separate action that can begin verification.
-
01
Request is created
An organization defines the address, purpose, recipient, and one-to-four-day verification window.
-
02
Scope is reviewed
The user signs in to see the requesting organization, duration, data scope, and reason.
-
03
Consent is recorded
Only an explicit yes issues the one-time tracking credential. A no immediately rejects the request.
Opening is not tracking
A universal link loads request details only. Tracking never begins without authenticated, explicit consent.
For organizations
Set the purpose, place, and time.
Create a request from the organization portal or API. Every query remains scoped to the current organization, and live and test credentials stay separate.
-
Create the request
Enter an email and address, choose the verification duration, and send a secure invitation.
-
Monitor clear states
Follow pending, accepted, rejected, active, and completed requests without exposing unrelated user data.
-
Review the result
Use an audit-ready summary and idempotent event history for operational decisions.
Command center
Active verifications
Ada O.
Permanent address verification
Jordan K.
Permanent address verification
Sam L.
Permanent address verification
Consent screen
Northstar Finance
is requesting address verification
- Purpose
- Account opening
- Duration
- 2 days
- Shared
- Verification result
For end users
See every detail before sharing anything.
Users receive a secure invitation, authenticate, review the scope, and decide. They cannot extend an organization’s chosen duration, and they can decline without generating a tracking credential.
Receive: open a UUID-based secure link.
Review: understand requester, purpose, and time window.
Consent: explicitly accept or reject the request.
Build trust by design
Ready to prioritize privacy?
Give organizations reliable evidence and users meaningful control.