Anti-spam and reports

Anti-Spam Policy

LoftBox supports verified-domain transactional and operational email for AI agent workflows. We do not allow spam, purchased-list sending, deceptive campaigns, or reputation-hiding relay behavior.

Last updated: May 31, 2026

Allowed email

LoftBox is intended for service, transactional, and operational messages sent by or on behalf of configured agents. Examples include support replies, workflow notifications, account or service updates, monitored follow-ups, and other recipient-expected operational communication.

Sender requirements

  • Sending must use domains the user owns or is authorized to operate.
  • Domains must complete ownership verification and sender alignment before outbound use.
  • Agent identities, display names, and message content must not mislead recipients.
  • Users must maintain appropriate consent, contractual basis, or other lawful basis for the messages they send.

Prohibited sending

  • Unsolicited bulk email, purchased lists, scraped addresses, harvested contacts, or cold campaign blasts.
  • Phishing, impersonation, malware, credential theft, fraud, deceptive routing, or evasion of delivery controls.
  • Messages that hide the sender, falsify headers, misrepresent the reason for contact, or bypass opt-out obligations.
  • Use as an open relay, shared reputation tunnel, or fallback sender for blocked traffic.

Controls and enforcement

LoftBox may apply rate limits, verified-domain requirements, delivery review, message holds, manual review, delivery monitoring, bounce handling, complaint handling, and account restrictions.

We may suspend or terminate sending for domains, mailboxes, agents, workspaces, or accounts that create misuse risk, deliverability harm, delivery-policy violations, security risk, or repeated recipient complaints.

Bounces, complaints, and opt-out

Users must handle recipient complaints, unsubscribe or opt-out requests, and compliance requests promptly. High bounce rates, high complaint rates, blocklist signals, or delivery warnings may result in throttling, review, or suspension.

Report a message

Send user reports to [email protected]. Include the full message headers, sending address, recipient address, approximate time received, and a short description of the issue when possible.