HOW AYA WORKS
From an unknown number to an evidence-aware recommendation.
Aya is designed to show the path from input to decision, including cost, provider attempts, conflicts, confidence, and limitations.
STEP BY STEP
The standard lookup path
1. Confirm the purpose
The user acknowledges a lawful, permissible reason and the server validates the phone format.
2. Check fresh stored results
A valid cached result can reduce provider cost and latency while respecting configured retention.
3. Select a source
Standard mode avoids calling every provider. Comparison mode uses selected configured sources for a higher fixed credit cost.
4. Separate the evidence
Identity, caller label, carrier, line type, abuse indicators, and provider conflicts remain distinct.
5. Explain the decision
Aya assigns evidence confidence and scam risk separately, then shows reasons, limitations, and safer next actions.
6. Record the charge atomically
Credits are deducted with concurrency protection and idempotency so retries cannot intentionally double-charge a completed request.
PRIVACY BY WORKFLOW
Controls exist before and after a lookup.
- Account identity comes from a verified authentication token, not a caller-supplied email address.
- Sensitive routes require authorization and rate limits.
- Lookup results are saved as contacts only when the user chooses.
- Users can export or delete their account-linked information.
- Correction and suppression requests require appropriate verification before records are changed.
- Raw provider storage is disabled by default. Lookup history and saved contacts are capped at 250 items each and remain until the user clears them or deletes the account.
LANGUAGE ARCHITECTURE
English and Spanish today, with a manifest-driven path for more.
The application loads language resources by locale code and falls back to English when a future translation is incomplete. Public marketing pages use the same paired-locale model with separate crawlable URLs, reciprocal language annotations, and localized titles and descriptions.
FAQ
Frequently asked questions
Why does a provider comparison cost more?
It calls more configured sources and performs conflict analysis, increasing provider expense and processing work.
Are credits deducted safely?
The backend uses atomic credit checks and idempotency records designed to prevent negative balances and duplicate charges.
Can more languages be added?
Yes. App and marketing language registries keep locale codes, translations, and paired URLs separate from core business logic.
Check the evidence before you trust the caller.
Open Aya to investigate a phone number, suspicious message, or voicemail. Every paid product has a fixed allowance—there is no free or unlimited plan.