Saved capture
Smart Capture saves a still image and confirms the capture. Camera frames alone are not treated as completed lead records.
How ZeroScanX works
From capture to evidence-backed result.
ZeroScanX separates extraction, operator review, backend authorization, evidence reasoning, and result proof so every stage has one clear responsibility.
The complete path
Six stages. One accountable result.
The app does not skip directly from camera text to a quality claim. Each record moves through a controlled sequence before completed results are shown.
Local extraction
On-device text recognition reads the saved image. Geometry-aware reconstruction groups rows and contact regions before lead candidates are formed.
Operator review
The pre-validation workspace shows captured contact fields, allows correction, and displays the Credit balance and selected validation cost.
Backend authorization
The app submits only validation-ready records. Backend authority verifies identity, wallet state, request shape, and available Credits before validation proceeds.
Evidence reasoning
Available phone, email, address, duplicate, and provider evidence is correlated. Explanations organize backend facts without replacing the backend score.
Result and receipt
A completed result appears only after the backend returns completed status, quality scores, a remaining Credit balance, and receipt creation proof.
Clear authority
The app explains. The backend decides.
Local engines improve capture, grouping, and explanation. They cannot authorize spending, fabricate provider evidence, or overwrite backend-confirmed results.
ZeroScanX can
- Read saved captures on the device.
- Group visible contact fields into reviewable candidates.
- Let the operator correct fields before validation.
- Organize returned evidence and explain reason codes.
- Display completed scores and receipt references.
ZeroScanX does not
- Claim that captured text alone proves a person or owner.
- Treat unavailable evidence as valid or invalid.
- Let local reasoning change backend scores.
- Spend Credits without backend authorization.
- Show an intermediate validation state as a completed result.
Capture intelligence
Fields stay connected to their physical record.
The extraction path uses saved-image text geometry to avoid treating every detected phone number as a separate person.
Lead sheets
Repeated row geometry anchors names, phones, emails, and addresses to the correct row without merging neighboring contacts.
Business cards
Multiple phone numbers, organization, title, email, and address inside one contact region remain attached to one candidate.
Repeated captures
Strong normalized phone, email, and contact evidence can update an existing candidate instead of multiplying the same contact.
Document boundaries
High-confidence government-ID regions are excluded without blocking legitimate contact regions elsewhere in the same image.
Customer-facing truth
Every evidence row says exactly what the check proved.
Quality score does not turn unknown evidence into a positive result. Each field uses only its own completed check.
ValidExplicit positive evidence for that exact item.
InvalidExplicit negative evidence for that exact item.
Could not verifyUnavailable, timed out, incomplete, or inconclusive.
Not providedThe source record did not contain the item.
Privacy architecture
Keep the result. Minimize sensitive artifacts.
The validation receipt is designed around sanitized metadata, reason codes, status, timestamps, score output, and audit references rather than raw capture content.
Local image work
Saved-image OCR and field reconstruction occur in the app capture path before selected records enter backend validation.
Sanitized receipts
Receipt metadata preserves lineage and proof fields while raw OCR text and raw images are excluded from the validation receipt contract.
Honest availability
Missing or failed evidence is represented as unavailable rather than silently converted into a negative or positive customer claim.
Current testing access
See the workflow on your device.
Join the active beta for iPhone, iPad, or Android. Testing access may be limited by account eligibility.
iPhone and iPad
Join the current iOS beta with TestFlight.
Join with TestFlightAndroid
Open the current internal test in Google Play.
