Acceptable Use Policy

1. Purpose and Scope

1.1 SMTPCart provides managed email delivery infrastructure, including isolated sending environments and controlled IP allocation. The value of that infrastructure rests entirely on its reputation with mailbox providers, and that reputation is shared — in whole or in part — across the customers who use it.

1.2 A single abusive sender can cause blocklist listings, provider-level filtering and IP range damage that affects every other customer on adjacent infrastructure, and that can take weeks or months to repair. This Policy exists to prevent that, and it is enforced accordingly.

1.3 This Policy applies to BEINCART LLC ("SMTPCart", "we", "us", "our") and to every customer, account holder, reseller, agency, affiliate and end user of the Services ("you", "your", "Customer"). Capitalised terms not defined here have the meaning given in the Terms of Service.

1.4 You are responsible for the conduct of anyone who uses your account or sends through your Sending Environment, including your own clients where you are a reseller or agency. Their violations are treated as yours.

2. The Governing Principle

2.1 There is one principle underlying everything in this Policy: send only to people who have asked to hear from you, send what they expected, and stop the moment they ask you to.

2.2 Any practice that is technically permitted by the rules below but that defeats this principle is a breach of this Policy. Conversely, if you can demonstrate genuine, current, documented permission for every recipient, you will rarely encounter a problem with us.

2.3 We do not interpret this Policy narrowly or literally in your favour. Where conduct is ambiguous, we assess it by its effect on our infrastructure and on the recipients receiving it.

3. What You May Use the Services For

The Services are intended for legitimate business email, including:

• Transactional mail— receipts, order and shipping confirmations, password resets, account and security alerts, invoices, and system notifications triggered by a recipient's own action;
• Lifecycle and product mail— onboarding sequences, usage digests, renewal and billing notices, and service announcements to active users;
• Permission-based marketing— newsletters, campaigns and promotions to recipients who have knowingly opted in to receive them from your identified brand;
• Internal and operational mail— alerts, reports and notifications within your own organisation or to contracted parties;
• Platform and relay traffic— where you are a SaaS platform, hosting provider, agency or reseller sending on behalf of identified end customers who are themselves bound by terms no less strict than this Policy.

4. Consent

4.1 You must hold a lawful, current and demonstrable basis for sending to every recipient. Consent must have been given knowingly, by an affirmative act, to receive mail from the brand that appears in the From line.

4.2 The following do not constitute valid consent for the purposes of this Policy:

• pre-ticked boxes, or consent bundled into acceptance of unrelated terms;
• a business card, conference badge scan or LinkedIn connection, treated as a newsletter signup;
• an address appearing publicly on a website or in a directory;
• consent given to a different brand, including a parent, subsidiary, partner or acquired company, unless you were clearly named at the point of collection;
• consent that has lapsed under applicable law, including implied consent under CASL, which expires 24 months after a transaction and 6 months after an enquiry;
• consent inferred from a recipient's failure to object.

4.3 Confirmed opt-in is required for any address acquired through a channel you do not directly control, including partner forms, co-registration, competitions, offline events and third-party lead generation.

4.4 You must retain records evidencing consent for each address, including the source, timestamp, IP address where captured online, and the exact wording presented at the point of collection. You must produce these records within five (5) business days of a written request to [email protected]. Inability to produce them is itself a breach of this Policy and grounds for suspension.

5. Prohibited Content

You must not use the Services to send, transmit, host or link to:

• unsolicited bulk or commercial email of any kind;
• phishing, credential harvesting, or any message designed to deceive a recipient into disclosing information or making a payment;
• malware, ransomware, spyware, viruses, or links to any of them;
• content that sexualises, endangers or exploits minors — this is reported to the National Center for Missing & Exploited Children and to law enforcement without notice to you;
• fraudulent offers, advance-fee schemes, pyramid or matrix schemes, chain letters, or "get rich quick" programmes;
• counterfeit goods, stolen data, hacked accounts, or credentials of any kind;
• unlicensed pharmaceuticals, controlled substances, or prescription drugs offered without a valid prescription;
• unlicensed gambling, binary options, or unregistered securities and investment offerings;
• content that is defamatory, harassing, threatening, or that incites violence or hatred against any person or group;
• material that infringes copyright, trade mark, or any other intellectual property right;
• cryptocurrency offerings, token sales or trading signals sent to recipients who did not specifically request them.

6. Prohibited Practices

6.1 Identity and deception

You must not:

• use false, forged or misleading header information, sender names, return paths or routing data;
• impersonate any person, brand, organisation or government body, or imply an affiliation you do not have;
• use deceptive subject lines, including false "Re:" or "Fwd:" prefixes, fabricated reply threading, or subjects implying an account, payment or legal problem that does not exist;
• omit a functioning unsubscribe mechanism, a valid physical postal address, or accurate sender identification where these are required by law;
• register domains or accounts designed to obscure the true sender or to evade filtering.

6.2 Technical abuse

You must not:

• attempt to circumvent volume limits, rate limiting, throttling, filtering or suppression lists;
• distribute traffic across multiple accounts, domains or Sending Environments in order to evade thresholds or detection ("snowshoeing");
• operate an open relay, open proxy, or permit third parties to inject mail through your credentials;
• use the Services to send traffic generated by automated warm-up networks, seed-account reply exchanges or other artificial engagement schemes;
• conduct port scanning, penetration testing, denial-of-service activity, or any unauthorised access attempt against our infrastructure or any third party;
• resell, sublicense or relay the Services on behalf of an undisclosed third party without written authorisation.

6.3 List acquisition

You must not use addresses obtained by purchase, rental, licensing, scraping, harvesting, email appending, co-registration without clear disclosure, or from any third party where your brand was not named at the point of collection. Possession of such a list on our infrastructure is a breach whether or not you mail it.

7. Operational Requirements

You must, at all times:

• Honour unsubscribes within two (2) daysand suppress those addresses permanently across all mail streams, regardless of the longer periods permitted by law;
• Implement RFC 8058 one-click unsubscribeheaders on all marketing traffic, with an endpoint that works without a login or preference form;
• Remove hard bounces immediatelyand never re-attempt them;
• Publish and maintain SPF, DKIM and DMARCrecords for every sending domain, with DMARC alignment verified and a policy of at least p=none;
• Keep SPF within the ten-lookup limitand correct it before adding any new sending source;
• Maintain valid forward and reverse DNS (PTR)for all sending IPs;
• Follow any warm-up scheduleagreed with us, and not exceed agreed daily volumes without prior approval;
• Monitor Google Postmaster Tools, Microsoft SNDSand any applicable feedback loops, and act on deterioration without waiting to be told;
• Maintain a suppression listthat persists across platform migrations and campaign changes;
• Designate an abuse contactwho will respond to notifications from us within twenty-four (24) hours.

8. Performance Thresholds

8.1 The following thresholds apply to each Sending Environment. They are assessed over rolling windows rather than per campaign, and per mailbox provider as well as in aggregate.

8.2 These thresholds are minimum standards, not targets to sit against. A sender consistently operating in the warning band should expect closer scrutiny and slower approval for volume increases.

8.3 We may set lower thresholds for a specific Sending Environment where its traffic profile, history or recipient mix warrants it, and will tell you when we do. 8.4 Meeting these thresholds does not by itself mean you comply with this Policy. Consent, content and identity obligations apply independently of your metrics.

9. Zero-Tolerance Violations

9.1 The following result in immediate termination without notice and without refund, and are not subject to the enforcement ladder in section 10:

• content sexualising, endangering or exploiting minors;
• phishing, credential harvesting or the distribution of malware;
• use of a purchased, rented, scraped or harvested list;
• deliberate circumvention of our volume limits, filtering or suspension;
• distribution of traffic across accounts to evade detection;
• supplying false identity or ownership information during verification;
• any activity that causes a listing on a major blocklist through wilful misconduct;
• use of the Services in furtherance of a criminal offence.

9.2 In these cases we may also preserve and disclose account records to law enforcement, blocklist operators and mailbox providers, and pursue recovery of remediation costs under the Terms of Service.

10. Enforcement

10.1 Our response is proportionate to the severity and persistence of the breach, and to the risk it presents to our infrastructure and to other customers.

10.2 Throttling and pacing applied as a routine part of managed delivery — for example per-provider rate limiting during warm-up — is not an enforcement action and does not indicate a breach. Queries about pacing should go to [email protected].

10.3 We may act at any tier without first acting at a lower one where the risk requires it. Nothing in this section obliges us to give notice before protecting our infrastructure.

10.4 Where an Abuse Event is in progress, we may hold queued messages, block a specific mail stream, or freeze IP allocation while we investigate. We will restore service as soon as the risk is resolved.

10.5 We are not liable for any loss arising from enforcement action taken in good faith under this Policy, and no refund or credit is given for periods of suspension resulting from your breach.

11. Suspension, Appeal and Reinstatement

11.1 On suspension we will tell you what triggered it and what is required to resolve it, unless doing so would prejudice an investigation or breach a legal obligation.

11.2 Suspension does not relieve you of payment obligations for the remainder of the Term.

11.3 To seek reinstatement you must: (a) identify the root cause; (b) remove the affected recipients, lists or content; (c) provide consent evidence for the segment involved; and (d) submit a written remediation plan describing what will prevent recurrence.

11.4 Appeals and remediation plans should be sent to [email protected]. We aim to respond within 48 ~ 72 hours.

11.5 Reinstatement is at our discretion and may be conditional on reduced volume, a fresh warm-up, a different IP allocation, or enhanced monitoring. 

11.6 We are not obliged to reinstate an account terminated under section 9, and we may decline to provide the Services to any person associated with such an account.

12. Monitoring

12.1 We monitor traffic patterns, volumes, complaint rates, bounce rates, authentication results, blocklist status and feedback loop reports for the purpose of protecting our infrastructure and detecting abuse. Abuse reports may be sent to us at [email protected].

12.2 We do not routinely inspect the content of your messages, and nothing in this Policy obliges us to do so. We may inspect content where necessary to investigate a specific Abuse Event, to respond to a third-party complaint or legal request, or to verify compliance following a breach.

12.3 Monitoring is a protective measure, not a compliance service. We do not review your lists, consent practices or content in advance, and the absence of an enforcement action is not approval of your practices.

12.4 We may share information about confirmed abuse with mailbox providers, blocklist operators and industry anti-abuse bodies where necessary to protect our infrastructure or to secure a delisting.

13. Reporting Abuse

13.1 If you believe mail sent through SMTPCart infrastructure breaches this Policy, report it to [email protected], or in writing to BEINCART LLC, [email protected]. Include full message headers where possible — they are usually necessary to identify the sender.

13.2 We investigate all credible reports. We do not disclose the outcome of an investigation to the reporting party, but we act on what we find.

13.3 Recipients wishing to stop receiving mail from a particular sender should use the unsubscribe mechanism in the message. Where that mechanism does not work, that is itself a breach of this Policy and should be reported to us.

14. General

14.1 This Policy is not exhaustive. Conduct that harms our infrastructure, our reputation with mailbox providers, or other customers may be treated as a breach even where it is not specifically listed.

14.2 We may update this Policy to reflect changes in law, mailbox provider requirements or abuse patterns. Material changes take effect thirty (30) days after publication; changes required by law, by an upstream provider, or to address an active abuse or security risk take effect immediately.

14.3 This Policy is effective from 09/26/2026 and is governed by the laws of the State of Wyoming, United States, in accordance with the Terms of Service.