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.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.
The Services are intended for legitimate business email, including:
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:
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.
You must not use the Services to send, transmit, host or link to:
You must not:
You must not:
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.
You must, at all times:
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.
| Metric | Target | Warning | Enforcement |
| Spam complaint rate | Below 0.10% | 0.10% - 0.30% | At or above 0.30% — throttling or suspension |
| Hard bounce rate | Below 0.5% per send | 0.5% - 2% | Above 2% — sending halted pending list validation |
| Soft bounce rate | Below 3% | 3% - 8% | Above 8% — review of list quality and cadence |
| Spam trap hits | Zero | Any pristine trap hit | Any confirmed trap hit — immediate review |
| Unsubscribe rate | 0.1% - 0.5% | Above 1% | Sustained above 2% — content and consent review |
| Authentication pass rate | 99% or above | 95% - 99% | Below 95% — sending suspended until corrected |
| Blocklist listings | None | Any listing on a minor list | Any major listing (e.g. Spamhaus SBL/CSS) — immediate action |
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.1 The following result in immediate termination without notice and without refund, and are not subject to the enforcement ladder in section 10:
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.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.
| Severity | Examples | Our response | Notice given |
| Tier 1 — Advisory | Metrics entering the warning band; minor configuration faults; a single soft bounce spike | Written notice, guidance, and a request for a remediation plan | Notice first; you have 5 business days to respond |
| Tier 2 — Restriction | Thresholds breached; repeated Tier 1 issues; a minor blocklist listing | Rate limiting, stream-level blocking, or volume rollback to a prior warm-up step | Notice at or before the restriction takes effect |
| Tier 3 — Suspension | Sustained threshold breach; major blocklist listing; unverifiable consent; failure to respond to a Tier 2 notice | Account suspended, queued mail held, IP allocation frozen | Notice as soon as reasonably practicable; suspension may precede it |
| Tier 4 — Termination | Any Zero-Tolerance Violation under section 9; repeat suspensions; deliberate circumvention | Immediate termination without refund, IP withdrawal, and reporting to third parties where appropriate | None required |
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.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.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.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.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.
 |
