Acceptable use and deliverability

SendLit cloud shares sending infrastructure, domains and provider standing across its customers, so one abusive account can hurt everyone. These rules and controls apply to SendLit cloud. Self-hosted OSS installations run their own infrastructure and none of the controls below apply to them.

What you may send

Send only to people who asked to hear from you, and make it easy for them to stop. You may not use SendLit for:

• purchased, rented, scraped or harvested lists, or lists of people who never opted in;
• phishing, credential harvesting, malware, or links that hide where they go;
• impersonating another person, company or brand;
• deceptive offers, scams, illegal goods, or content that is illegal where it is sent or received;
• getting around these controls, for example by spreading sends over several accounts.

SendLit may review accounts, imports and email content for these purposes, hold emails for review, pause a team's sending, and suspend or close organizations that break these rules, with or without notice. If we pause something by mistake, reply to our email and a person will look at it.

Signing up

Accounts are created with a one-time code sent to the email address, so every account owns its mailbox. In addition, cloud signup:

• rejects disposable and temporary email domains;
• may flag accounts on free mail providers (Gmail, Outlook, ...) for review;
• limits how many accounts can be created from one network per day.

Checks before sending

Before a broadcast or sequence starts, before a test is sent, and when a running sequence's email is edited, SendLit checks the email for phishing, malware and spam patterns (link text that hides the real destination, account-verification lures, executable downloads, link shorteners, and similar), optionally with an AI classifier.

• Held for review: the email can't be sent until a SendLit operator approves it, usually within a business day. You get an email.
• Blocked: clear phishing or malware. Sending for the team is paused while an operator reviews it.

Once approved, the same content isn't checked again.

Large imports

Importing a large list in a short time, especially on a new account, alerts SendLit's operators. On accounts younger than 30 days, campaigns can't start until the import has been reviewed. Imports are recorded in the organization's activity log.

New accounts send gradually

For an organization's first 30 days, marketing mail is paced:

• the daily marketing allowance ramps up: 200 a day at first, then 1,000, then 10,000, rising as the account stays free of bounce and complaint problems (the steps need 3, 4 and 7 clean days);
• each day's allowance is spread over about 12 hours, so a broadcast goes out over the day instead of in one burst. The broadcast page shows the pace and when it should finish.

Emails beyond the pace wait for the next hour or day; nothing fails. A SendLit operator can lift pacing early for a vetted organization. Transactional mail is not paced. Each plan also has a monthly email allowance; see Pricing and billing.

Reputation windows

After a team has at least 500 accepted messages in a rolling seven-day window, SendLit evaluates bounce and complaint rates from the outbound ledger. Retries and duplicate provider events count once.

all_paused does not auto-recover. A SendLit operator must review the list and release the team, which starts at warned.

Domain verification

Cloud sending requires a verified organization owner email. After about 100 accepted lifetime messages, the From domain must be verified with a DNS TXT record at _sendlit-verification.<domain>. Plain SMTP can be used for tests but cannot unlock volume without a healthy bounce/complaint feedback connection.