FAQ
Common questions
What is this, in one sentence?
A live demo of a phone + identity check that only runs after a real device proves it's present — the same trust gate that can stand in for a one-time code, a 2FA prompt, or a CAPTCHA.
Why scan a code first?
It proves a real phone is present before anything runs. Without it, the form is just text anyone could type — the scan is the difference between "a number was entered" and "the device answered."
How does the trust gate actually work?
You scan the QR code with the Pulse app on your phone. The app answers for that browser session and returns a short-lived result the page can check. Only then does the lookup unlock. No account, no password — the scan is the proof.
What does the check return?
For the number itself: whether it's valid, the carrier, and the line type (mobile, VoIP, landline). It also returns an SMS-fraud risk score. If you add a name and address, it returns an identity match — a per-field verdict (first name, last name, address, city, state, ZIP, date of birth) and an overall score.
Do you store my number, name, or results?
No. Numbers, names, addresses, dates of birth, and results are used to perform the check and then discarded. We keep no lookup history and build no profile. See the Privacy page.
Is this tracking the phone?
No. The check asks the carrier about the number for this single lookup. There's no location trail, no following the device, and nothing kept afterward.
Where does the data come from?
From the mobile carrier's own records, reached through our lookup provider (Twilio). The identity match compares what you enter against the carrier's account-holder record — not a copied or third-party database.
Is the name and address required?
No — the identity section is optional. The number check stands on its own. If you do add a name, the first and last name are required for the match to be meaningful; address and date of birth are optional and each one you add strengthens the result.
What makes the identity check strong?
It compares your input against the carrier's own account-holder record. The more fields that line up (name, address, date of birth), the higher the confidence — a perfect match across all fields returns a top score.
What does "SMS-fraud risk" mean?
It's a carrier-derived signal (0–100) for how likely a number is tied to SMS abuse — bulk one-time-code farming and similar. Low is good; higher means treat verification codes to that number with more care.
Is a match proof of identity?
No. A match is a strong signal that the number, name, and address line up with carrier records — not a guarantee of identity on its own. It's meant to be one input to a decision, not the decision.
Can it detect a SIM swap or a ported number?
Those carrier packages exist, but they aren't enabled on this demo account yet, so they aren't part of the result today. The line-type, carrier, fraud-risk, and identity-match signals are.
How is this different from 2FA, OTP, or CAPTCHA?
A one-time code proves someone can read a text; a 2FA push proves a tap; a CAPTCHA proves you're not a simple bot. None of them prove a real, present device — let alone who's behind it. Pulse checks for the present device first, then lets you read what the carrier knows about the number.
Does it work outside the US?
The number and carrier checks work worldwide. The identity match is strongest in the US, where carrier account-holder coverage is best.
Is this a credit check?
No. Nothing here is a credit decision, credit offer, or consumer report. See the Terms.
What happens if a lookup fails?
Transient network blips are retried automatically on our side, so most never reach you. If a check still can't complete, you'll see a quiet "try again" — no scary errors, and nothing is stored.