Legal
These rules protect recipients, customer domains, provider relationships, and the shared infrastructure NoticeAPI runs on.
Last updated: July 2, 2026
Marketing email through NoticeAPI must be sent only to recipients who gave valid consent to receive that category of email from you. Transactional email must be tied to a real product, service, account, purchase, or user action.
Cold outreach is not allowed. Purchased, rented, borrowed, scraped, guessed, enriched, or third-party lead lists are not allowed, even if another vendor claims they are compliant.
Every broadcast and automation must carry a working unsubscribe path. If you do not include the unsubscribe merge tag, NoticeAPI may append a footer and List-Unsubscribe headers automatically.
You may not bypass, remove, obscure, break, or delay unsubscribe handling. You may not email unsubscribed, bounced, complained, suppressed, or otherwise opted-out recipients except where lawfully required for essential transactional notices.
You may not use NoticeAPI for phishing, malware, credential harvesting, scams, deceptive identity, spoofing, impersonation, illegal goods or services, harassment, hate, threats, exploitation, adult sexual content, or content that violates applicable law.
You may not use NoticeAPI to send mail that misleads recipients about who you are, why they are receiving the message, how to unsubscribe, or what action a link or attachment will perform.
NoticeAPI is for outbound transactional email and consent-based broadcasts. It is not a CRM, mailbox host, inbound email provider, cold outreach platform, list broker, deliverability trick system, or dedicated-IP marketplace.
Do not attempt to evade rate limits, quotas, review gates, ramp limits, domain verification, suppression lists, unsubscribe controls, webhook signing, authentication, or abuse monitoring.
NoticeAPI monitors bounce rates, spam complaints, provider blocks, usage patterns, and recipient outcomes. Sending may be throttled, paused, capped, reviewed, or terminated when risk thresholds are crossed.
Free production sending requires operator activation and a verified domain. New production accounts may be warmed up through daily caps. These controls protect everyone using shared ACS capacity.
You may send only from domains you own or are authorized to use. You must keep DNS records accurate and must not impersonate another organization or person.
ACS pools are capacity shards only. Accounts are not routed to pools by plan tier, and plan upgrades must not be used to avoid reputation, review, or abuse controls.
We may reject mail, suppress recipients, pause domains, pause accounts, revoke API keys, require remediation, or terminate service if we believe this policy has been violated or platform health is at risk.
If your account is paused and you believe it was a mistake, contact [email protected] with the sending domain, audience source, message examples, and remediation plan.