// legal

last updated September 8, 2026

Acceptable Use Policy

This policy sets out what you may and may not do with mailQA, operated by KAPTIVA SOLUTIONS LLC ("we", "us"). It is part of the Terms of Service, and every user of the Service — every member of an organization, and every application using its credentials — is bound by it.

What mailQA is for

mailQA captures email sent by an application that you control, or that you are authorised to test, so that you can inspect that mail and assert on it. Every legitimate use of the Service fits that description. Nothing that reaches mailQA is delivered to anyone.

What you may not do

Deliver or relay mail. mailQA delivers nothing, and you may not attempt to make it. Do not use the SMTP sink, a mailQA address or the API as part of any path that sends mail to a real recipient, and do not present a mailQA address to anyone as a way of reaching a person.

Capture mail you are not entitled to. Direct mail to mailQA only where you have the right to receive it. Do not point another party's mail at mailQA without their permission, and do not use mailQA addresses to sign up for third-party services in a way that breaks their rules — bulk registrations, trial abuse, sockpuppet accounts or evading a ban. Testing your own signup flow is what the Service is for; testing someone else's is not.

Use it as disposable or anonymous email. mailQA inboxes are test fixtures for your organization, not throwaway addresses for concealing your identity from other services.

Store or distribute prohibited content. Do not send to mailQA, or keep in it, content that is illegal, that infringes someone's intellectual property or privacy, that sexually exploits minors, or that contains malware, and do not use attachments captured in mailQA to distribute any of those.

Attack, probe or overload the Service. Do not scan, penetration-test or load-test the Service without our written permission. Do not circumvent rate limits, plan limits or the verification gate on public addresses, create accounts by automation, or share credentials or sessions to exceed the seats on your plan.

Interfere with other users. Do not attempt to access another organization's inboxes, messages or credentials, or to interfere with anyone else's use of the Service.

Impersonate. Do not choose an organization name, subdomain or inbox name in order to impersonate a person, company or brand, or to suggest an affiliation that does not exist.

Break the law. Do not use the Service in violation of any law that applies to you, including privacy and data-protection law, anti-spam law, and United States export-control and sanctions law.

Resell. Do not offer the Service to third parties as your own product without a written agreement with us. Using mailQA in a product you build for a client is fine; rebranding mailQA and selling access to it is not.

Mail addressed to real people

The SMTP sink captures whatever your application hands it. If you point a staging or production environment at it, mail addressed to real users — with their names, addresses, password-reset links and whatever else your application writes — lands in your inboxes, where every member of your organization can read it. That is your organization's decision to make, and your organization is responsible for the notice and lawful basis it requires. Prefer test accounts and synthetic data. Do not route mail carrying sensitive personal data through mailQA unless you have assessed that doing so is appropriate.

Enforcement

We may investigate any suspected breach of this policy, and while we do we may suspend access to the Service or refuse mail at the SMTP level. Where we find a breach we may remove content, suspend or terminate the organization and its accounts, and, where the law requires or the conduct warrants it, report it to law enforcement. We will tell you what happened where doing so is practical and lawful.

Reporting abuse

To report abuse of the Service, email abuse@mailqa.io. Include the mailQA address or subdomain involved, the time and any message headers you have, and a description of what happened. We investigate every report.

Questions about this document? Write to legal@mailqa.io.