Security and privacy
Protecting your data is our priority. We use industry-standard safeguards to keep your information secure throughout every verification workflow.
Files are uploaded over HTTPS and stored securely.
We use your data only to verify email addresses.
Access is limited to authorized systems and personnel.
Bulk-verification data follows the retention periods configured in the deployed service.
Download or delete your verification data when needed.
Name, email, organization, and authentication details.
File name, job status, counts, and timestamps.
Email outcome and verification details.
Invoices, payment references, and usage statistics.
Bulk-verification data becomes eligible for deletion according to the configured lifecycle. Cleanup runs asynchronously.
Export verification results whenever needed.
Delete individual jobs or remove stored data.
Create, revoke, and rotate credentials.
We believe in clear communication about how we handle your data. Contact us whenever you have a security or privacy question.
Contact securityIf you believe you have found a security issue, please let us know immediately. We typically respond within 24 hours.
No. Uploaded addresses are processed only to provide the verification service and are never sold.
Yes. Authorized account users can delete individual verification jobs and their associated data.
By default, source uploads and row-level verification items are scheduled for deletion after 7 days, result exports after 30 days, and abandoned uploads after 24 hours. Bulk-job metadata is assigned a 365-day expiry. These are deployment settings, and deletion occurs asynchronously when scheduled cleanup handles the expired data.
Data is processed using controlled infrastructure with access restrictions, monitoring, and secure storage practices.
Uploads are protected with HTTPS in transit and stored using encryption at rest.
Access is limited to authorized users on your account and authorized systems or personnel required to operate the service.
Powerful email verification supported by security-first data practices.
