QwikVerify

Privacy Policy & Acceptable Use

Last updated 2 August 2026

QwikVerify operates a contact-data validation API. Customers send a phone number, email address, IP address, or domain, and receive a structured assessment of whether it is valid, how it is classified, and how risky it is. This page explains what we do with data sent to us, what we retain, and how data we return may be used.

Data customers send us

API requests contain the identifier being validated and nothing more. We do not ask for, and the API has no field for, names, payment details, government identifiers, or account credentials.

Processing. Identifiers are used solely to perform the requested validation and to return the result.
Caching. Validation results are cached against the identifier to reduce cost and latency. Cache lifetimes reflect how quickly the underlying fact changes — from one hour for live network status to thirty days for number type. Cached results are not shared outside the service.
Logging. We record the endpoint called, a request identifier, timestamp, and credits consumed, for billing and abuse prevention. We do not sell, rent, or share request data.
Retention. Operational logs are retained for a rolling period sufficient for billing and dispute resolution, then deleted.

Data we return, and its sources

Results are assembled from datasets we operate and from licensed upstream providers. Every response names its contributing sources in a data_sources field, so the origin of each result is visible rather than implied. Where an upstream is unavailable or not enabled, the affected fields are returned empty rather than estimated.

Acceptable use of returned data

Identity and contact data returned by this API may be used only for identity verification, fraud prevention, and confirming the accuracy of contact records you already hold or have a legitimate reason to contact.

Customers may not use data obtained from QwikVerify:

to make decisions about credit, insurance, employment, housing, or any other purpose governed by the US Fair Credit Reporting Act — this service is not a consumer reporting agency and its output is not a consumer report;
to build or enrich a marketing list for unsolicited contact, or to contact any person who has opted out;
to stalk, harass, locate, or profile an individual, or to determine eligibility for any benefit;
in any way that breaches applicable telemarketing, privacy, or data-protection law in the customer's jurisdiction or the data subject's.

Accounts found using the service for these purposes are terminated without refund. Customers are responsible for having a lawful basis for each lookup they perform.

Individual rights

QwikVerify does not maintain a consumer-facing database and does not originate identity records. Where a record surfaced through this API originates from an upstream provider, requests to access, correct, or delete it are directed to that provider. If you believe information returned about you is inaccurate, contact us and we will identify the source and pass the request on.

Security

All traffic is served over TLS. API keys are stored hashed and can be revoked by the account owner at any time. Upstream credentials are held as encrypted secrets and are never exposed in responses.

Contact

Questions about this policy, or requests relating to a specific record, can be sent to the address listed on our contact page.