Acceptable Use Policy

1. Consent: every recipient, every time

Every Recipient on every list you upload to the Service must have given you their email address with a clear understanding that you would send them email of the kind you intend to send. Specifically:

• Marketing lists must be double-opt-in. A user enters their address and then confirms via a click-through email. Single-opt-in is not acceptable for marketing on the Service. This is non-negotiable; we will require evidence of double-opt-in if a list shows abnormal complaint rates.
• Transactional sends (password reset, receipt, account notification) may use the contractual relationship as the basis. Marketing content may not be embedded in transactional templates.
• You must keep evidence of consent — timestamp, source, IP address of opt-in, the exact text of the consent prompt — for at least the lifetime of the subscription plus 24 months. We may ask for it.

2. Prohibited list sources

You may not send to any list that includes addresses obtained from:

• purchase, rental, lease, or barter from any third party;
• scraping websites, social networks, WHOIS, or directories;
• append services, "data enrichment" providers, or co-registration networks where the Recipient did not specifically opt in to your sending;
• contests, sweepstakes, or content gates where the email field was not the explicit signup;
• old lists that have not received a Message in more than 12 months ("re-engagement-after-cold-storage" requires re-permissioning, not just a "we miss you" blast).

3. Required content

Every commercial Message sent through the Service must include:

• a working unsubscribe link, prominent and reachable in one click without login, that processes the request within ten (10) business days (we recommend within minutes);
• a valid physical postal address of the sender (CAN-SPAM §316.5; see also our Privacy Policy on data residency);
• a non-deceptive From, Reply-To, and Subject — no false header information, no subject lines that misrepresent the content;
• a List-Unsubscribe header (RFC 2369) and, where supported, the List-Unsubscribe-Post one-click variant (RFC 8058).

4. Suppression-list compliance

The Service maintains a per-account suppression list of addresses that have hard-bounced, complained (FBL), or unsubscribed. You agree:

• not to attempt to circumvent the suppression list — including by re-uploading a previously-suppressed address, by spoofing capitalization, or by routing the same Recipient through a different sub-account;
• to honor manual unsubscribe requests received outside the Service (e.g. by reply email) within ten (10) business days, and to add them to the suppression list;
• that "list washing" — sending only to engaged segments after stripping out non-engagers — is not the same as cleaning a list and does not justify keeping non-consenting addresses in storage.

5. Deliverability thresholds and auto-suspend

The Service applies automatic protective limits. These are floors, not ceilings of "acceptable" performance — well-run senders are far below.

6. Authentication and infrastructure

• You must publish SPF and DMARC records for every sending domain. We will publish DKIM keys for you and require DMARC p=none at minimum during ramp-up, moving to quarantine or reject as soon as practical.
• You may not use a sending domain you do not control. We verify domain ownership via DNS TXT record before activation.
• You may not use the Service as a relay for outbound traffic that did not originate in your application logic (no "open SMTP" for arbitrary clients).

7. Content prohibitions

You may not send Messages whose primary purpose or content is:

• phishing, credential harvesting, or impersonation of a brand, person, or institution;
• malware, ransomware, drive-by exploits, or links to such content;
• "pump and dump" stock promotion, unregistered securities solicitation, or pyramid/MLM-style recruitment;
• controlled substances or prescription pharmaceuticals offered without lawful authority;
• sexual content involving minors, in any form, ever;
• incitement to violence against a person or identifiable group;
• content that violates the law in the jurisdiction of either the sender or the Recipient.

8. Reporting abuse

If you have received email sent through the Service that violates this AUP, please report it to abuse@splitsoft.com with full headers. We acknowledge within one business day and act on confirmed reports within five.

9. Consequences of violation

Violations are handled under Section 5 of the Terms. We strongly prefer to work with you to fix problems; we will use the suspend-without-notice option only when reputation, legal exposure, or Recipient harm leaves no alternative.