Permitted Use
Truncus supports two traffic types: transactional and outreach. Each type must use a separate sending domain.
Transactional email
Permitted transactional use cases include:
- Order confirmations and purchase receipts
- Password resets and account security notifications
- Account activity alerts and system notifications
- Invoices and billing confirmations
- Shipping and delivery notifications
- User-triggered workflow notifications (e.g., “your export is ready”)
Transactional emails must be sent to recipients who provided their email address directly to you and have an existing relationship with your service.
Outreach email (isolated streams)
Truncus supports personalized outreach via isolated streams. Outreach must meet all of the following conditions:
- Sent from a dedicated outreach domain, separate from your transactional domain
- Individually addressed and personalized — no bulk broadcasts
- Compliant with CAN-SPAM, GDPR, and applicable anti-spam laws
- Includes a working unsubscribe mechanism
- Uses the
x-truncus-traffic-type: outreach header
Outreach streams that exceed bounce or complaint thresholds (see Review Triggers below) will be automatically throttled or paused to protect your sending reputation.
Prohibited Use — Zero Tolerance
The following result in immediate account suspension without warning or refund:
- Spam or unsolicited bulk email of any kind
- Bulk unsolicited marketing, newsletters, or promotional broadcasts
- Purchased, rented, or scraped email lists
- Phishing, spoofing, or impersonation of any entity
- Malware, ransomware, or malicious content
- Email to harvested or guessed addresses
- Circumventing unsubscribe mechanisms
- Using Truncus to relay email on behalf of unlicensed third parties
Review Triggers
The following patterns trigger automated review and may result in throttling or suspension:
- Spam complaint rate exceeding 2% in any 7-day window
- Bounce rate exceeding 10% in any 7-day window
- Volume spike exceeding 10× your normal daily baseline
- Sending to role addresses at scale (info@, admin@, support@, etc.)
- High rate of “user unknown” or “mailbox full” bounces
Automated systems act first. Human review follows. This order is intentional — reputational damage to shared infrastructure happens faster than any manual process can respond.
Your Responsibilities
- Maintain suppression lists: remove hard bounces immediately, soft bounces after 3 failures
- Honor unsubscribe requests within 10 business days
- Ensure you have a legal basis (consent or legitimate interest) to email each recipient
- Keep sending volume within your plan limits
- Secure your API keys — you are responsible for all activity under your account
- Comply with CAN-SPAM, GDPR, and all applicable email regulations in your jurisdiction
Enforcement
- Monitoring runs continuously. Threshold breaches trigger automated action.
- Suspension is applied first; review follows. This is not reversible for zero-tolerance violations.
- Appeals for non-zero-tolerance suspensions: email support@truncus.co within 14 days of suspension.
- Truncus is the sole arbiter of AUP violations. Our decision is final.
Why This Exists
Truncus uses shared sending infrastructure. When one sender spams, complaint rates rise across the entire platform, affecting the deliverability of every customer. These rules protect your deliverability as much as they protect ours. We enforce them without exception because there is no other way to maintain a platform that works reliably for legitimate senders.