Effective 2026-11-21
Acceptable Use and Anti-Spam Policy
This policy is part of our Terms of Service. It applies to everything you send through Customer.lite, whether you, your application, or an AI assistant acting for you set it up.
1. Consent-based lists only
- Send only to people who signed up for or use your product, or who otherwise agreed to receive your email, as the law where they live requires.
- Never use purchased, rented, shared, scraped, or harvested lists, or addresses you collected for another purpose.
- Keep a record of how and when each recipient agreed, and give it to us if we ask.
- Send from domains you control and that we have verified for your workspace, and identify yourself as the sender, with a valid postal address where the law requires one.
- Do not disguise the sender, the subject, or the purpose of a message.
2. Unsubscribes
- Every marketing message carries a one-click unsubscribe (RFC 8058) that we add for you. Do not remove, hide, or break it.
- An unsubscribe takes effect for all later mail; we check it again just before each send. Do not re-add an address that unsubscribed unless the person subscribes again.
- Honour opt-out requests you receive by other means without delay.
3. Bounces and complaints
- A hard bounce or a spam complaint suppresses the address for your project. Do not try to send to a suppressed address again through another project, workspace, or account.
- Keep your lists clean: remove addresses that no longer engage, and do not send to addresses you have not mailed for a long time without confirming them first.
4. Bounce and complaint limits
We will measure bounce and complaint rates for each workspace and each kind of mail, once enough mail has been sent for the rates to be meaningful. These are the limits we hold every sender to:
| Rate | We may warn you at | We may pause sending at |
|---|---|---|
| Bounce rate | 2% | 4% |
| Complaint rate | 0.05% | 0.08% |
A paused workspace sends nothing until we have reviewed the cause with you and the list or content is fixed. If our email provider pauses a workspace's sending, it stays paused until the provider lifts the pause.
5. A person approves before sending
A workflow that sends email goes live only after a person approves it. Activating it mails a one-time approval link to the workspace's approvers; the approval covers that exact version of the workflow, including its content, trigger, and timing. Any change, and any reactivation, needs a new approval. An API key or an AI assistant cannot approve. Approvers must check that the recipients have agreed to the mail before approving.
6. Prohibited content and uses
You may not use the Service to send or link to:
- unsolicited bulk or commercial email, or email to recipients who have not agreed to it;
- phishing, malware, or content that tries to obtain passwords, payment details, or other credentials;
- deceptive offers, get-rich-quick or pyramid schemes, or fake invoices, notices, or prizes;
- illegal goods or services, or content that is unlawful where it is sent or received;
- content that harasses, threatens, or incites violence or hatred against people;
- sexual content involving minors, or sexually explicit content sent without the recipient's explicit request;
- content that infringes others' intellectual property or privacy.
You may also not:
- use link shorteners or redirects to hide where a link leads;
- probe, overload, or work around the Service's limits, approvals, or security controls;
- resell the Service, or send for third parties as an agency, without our written agreement.
7. Enforcement
If we believe this policy is breached, we may pause sending, remove a sending domain, or suspend the account, with notice where practical. Serious or repeated breaches lead to termination under the Terms of Service.
8. Reporting abuse
Report unwanted email or any other abuse to stg-placeholder@example.com, with the full message and its headers. See Contact and abuse for what to include.