Policy
Acceptable use and anti-spam policy.
Meisa sends product email to people who asked for it: onboarding, lifecycle and transactional email, and newsletters people subscribed to. It is not a tool for cold email.
Last updated: November 4, 2026
Opt-in only
Every recipient asked to hear from you.
No bought lists
No purchased, rented or scraped addresses.
One-click unsubscribe
In every marketing email, honoured at once.
Limits that are enforced
High bounces or complaints pause sending.
1.Who this applies to
Every Meisa account, on every plan, whether Meisa sends for you or you connect your own provider such as Amazon SES. It applies to every email sent through Meisa: sequences, triggers, broadcasts, newsletters and API sends. It is part of our Terms of Service.
The Service, meaning Meisa's website, apps, API, connectors and any related service, is operated by Ertiqah LLC ("we", "us", "our"). If you use the Service on behalf of a company or a client, you also agree to this Policy on their behalf and you are responsible for how they use it.
2.Consent
You may only email people who gave you their address themselves and expect to hear from you. That means:
- Users who signed up for your product, for email about that product.
- Customers, for receipts, account notices and other transactional email.
- Subscribers who joined your newsletter or list through your own form.
Keep a record of how and when each contact opted in. We can ask to see it, and for a sample of your signup flow, at any time.
3.What is not allowed
- Cold outreach of any kind: sales prospecting, lead generation or any email to people who have not opted in.
- Purchased, rented, traded or scraped lists, and addresses taken from websites, directories or social profiles.
- Lists from a third party, a partner or another product, unless those people agreed to hear from you by name.
- Emailing people who unsubscribed, bounced or marked you as spam.
- Misleading sender names, subject lines or headers, and hiding who the email is from.
- Phishing, malware, scams, and content that is illegal where you or your recipients are.
- Splitting sends across accounts, domains or products to get around limits or a suspension.
4.What every email needs
- A sending domain you own and have verified with SPF, DKIM and DMARC.
- A From name and address that clearly identify you or your product.
- A working unsubscribe link in every marketing and newsletter email. Meisa adds the link and the one-click unsubscribe header, and you may not remove or hide them.
- A valid postal address for your business where the law requires one.
Unsubscribes take effect immediately. Meisa stops sending to anyone who unsubscribes, hard bounces or files a spam complaint, and you may not add them back unless they opt in again.
5.Bounce and complaint limits
Low bounce and complaint rates are the sign of a list that wants your email. We measure both over the last 30 days of sending.
At the warning level your dashboard shows the problem and how to fix it. At the pause level we stop your sending until the cause is found and fixed, usually a stale or badly sourced list.
6.Security and system integrity
Unless we have given you written permission, you must not:
- scan, probe or test the Service for vulnerabilities, including with automated vulnerability scanners;
- fuzz any page, form, endpoint or API;
- run load, stress or performance tests, or send traffic meant to slow down or overload the Service;
- bypass, or try to bypass, sign-in, permissions, rate limits, usage limits, plan limits or any other security or access control;
- access, or try to access, another user's account or data, or any data that is not yours;
- interfere with, disrupt or damage the Service, its servers or the networks connected to it.
"Written permission" means an email from us that confirms the scope, the dates and where the testing will come from. Research that follows our Responsible Disclosure Policy is permitted within the limits of that policy (see section 12).
7.Scraping and automated access
You must not scrape, crawl, harvest or mine data from the Service with bots, scripts or other automated means, except through the official API, integrations and connectors we provide, and only within their documented limits. You must not create accounts by automated means, or use the Service to collect other people's personal information without their consent.
8.Malware and harmful code
You must not upload, send or link to viruses, malware, ransomware, spyware or any other code meant to damage, disable or gain unauthorized access to a system, device or data.
9.Illegal and harmful content
You must not use the Service to create, store or share content that:
- is illegal, or that encourages or helps illegal activity;
- infringes anyone's copyright, trademark, privacy or other rights;
- sexually exploits or endangers children;
- threatens or promotes violence against any person or group.
10.Reselling and sharing access
You must not sell, resell, rent, sublicense or share access to the Service or to your account, or offer the Service as part of your own product, unless we have agreed to it in writing. Serving your own clients through features we provide for that purpose, such as team or agency workspaces, is allowed.
11.What we do when a rule is broken
- We can review any account, sender or list before or after sending starts, and ask how the contacts opted in.
- We can pause a broadcast, a sequence or all sending on an account while we look into a report or a spike in bounces or complaints.
- Sending cold email, or using a purchased or scraped list, ends the account. We do not issue warnings for it.
- We cooperate with mailbox providers, our sending providers and the authorities when they report abuse.
If we believe you have broken this Policy, we may remove content and limit, suspend or terminate your access to the Service, with or without notice. We may report the activity to law enforcement, hosting providers or other affected parties, keep the related logs as evidence, and pursue any legal remedies available to us, including claims for damages and court orders.
Security testing that does not follow our Responsible Disclosure Policy is unauthorized access to our systems.
12.Good-faith security research
We want to hear about security problems, and we would much rather fix them with you than read about them in public. If you find a vulnerability, report it to us privately and follow our Responsible Disclosure Policy. If you do:
- we will treat your research as authorized under this Policy;
- we will not take legal action against you or ask law enforcement to investigate you because of it;
- we will not suspend or close your account because of it.
This safe harbor only applies to research that follows that policy, including reporting the issue to us first and keeping it private until it is fixed or 90 days have passed. If you are not sure whether something is allowed, ask us at [email protected] before you start.
13.Report abuse
Got an email sent through Meisa that you did not ask for? Forward it to [email protected] with the full message headers if you can. A person reads every report. To report a breach of this Policy, email the same address. To report a security vulnerability, see our Responsible Disclosure Policy.