Legal calibration

Acceptable Use Policy

Last updated: October 16, 2026

The boundary

Trueinbox verifies email deliverability. Verify only lists you own or have consent to process. No scraping, no verification of harvested addresses. This rule applies to single checks, CSV uploads, API calls, webhooks, exports, trials, paid accounts, and support-assisted workflows.

Prohibited list sources

Do not upload addresses collected through scraping, crawling, harvesting, password breaches, unauthorized data broker files, deceptive forms, or sources that cannot document consent. Do not use public websites, social networks, code repositories, leaked files, or guessed address patterns to create verification lists.

Prohibited claims and outcomes

Do not use a verification result to claim that a person consented, that an unknown address is certainly valid, or that a catch-all mailbox will receive a message. Verification is a risk signal; it is not proof of ownership, identity, engagement, or permission.

Security and platform abuse

Do not probe, overload, bypass, reverse engineer, or interfere with the service. Do not share activation codes outside licensed seats, use the API to evade rate limits, or submit malicious files. Automated access must stay within the plan’s documented volume and fair-use boundaries.

Customer responsibilities

The customer must maintain suppression lists, honor unsubscribe requests, follow applicable anti-spam and privacy laws, and preserve evidence of consent where required. Teams should separate valid, risky, invalid, and unknown outcomes rather than exporting everything by default.

Reporting and enforcement

Suspected abuse can be reported to ceo@trueinboxapp.com. Trueinbox may request proof of consent, pause processing, delete unauthorized uploads, suspend accounts, or terminate access. Enforcement may occur without refund when the violation creates legal, security, deliverability, or third-party risk.

Good-use examples

Acceptable uses include verifying a customer’s own newsletter subscribers, cleaning a CRM list collected through disclosed forms, re-checking an opt-in customer base, and auditing MX, SPF, or DMARC configuration for domains the customer controls.

Policy relationship

This acceptable use policy supplements the Terms of Service and Privacy Policy. If a conflict exists on list sourcing or harvested addresses, the stricter consent-first requirement controls.

Questions about this policy can be sent to ceo@trueinboxapp.com. Trueinbox is operated from 914 Canyon Dr, Midland, TX 79703-0000.