Recipient-first sending policy

Acceptable Use Policy

These rules protect recipients, customer domains, provider relationships, and the shared infrastructure NoticeAPI runs on.

Last updated: July 28, 2026
  • Consent-based sending
  • Working unsubscribe paths
  • Truthful sender identity
7Policy sections23Policy statementsJuly 28, 2026Last updated

Permission and recipient choice

Consent comes first. Opt-outs stay final.

These sections define when a message belongs on the platform and how recipient choice must be carried through every sending path.

01Section 1

Consent-Only Sending

Marketing, newsletter, broadcast, lifecycle, and automation email through NoticeAPI must be sent only to recipients who gave valid consent for that specific category of email, including documented implied or soft opt-in consent where the law that applies to you permits it.

You must be able to explain and, when asked, provide evidence for how each audience was collected, including source, timing, message category, and any re-opt-in after unsubscribe, bounce, complaint, or suppression.

Transactional email must be tied to a real product, service, account, purchase, security event, legal notice, or user action. Do not disguise marketing, lead generation, or re-engagement campaigns as transactional messages.

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.

SMS consent must be specific to the end business, messaging program, purpose, and phone number. Marketing SMS requires an affirmative written record of the exact disclosure; consent may not be bundled with a purchase, hidden in general terms, transferred from an unrelated party, or inferred from email consent.

02Section 2

Unsubscribe and Suppression Rules

Every marketing, promotional, newsletter, broadcast, automation, lifecycle, or subscribed message must carry a visible working unsubscribe path. Broadcasts and automations include List-Unsubscribe headers, and if you do not include the unsubscribe merge tag, NoticeAPI will append a footer automatically.

You may not use REST, SMTP, templates, batch sending, or another transactional path to avoid marketing unsubscribe controls.

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 for non-promotional transactional or relationship messages whose primary purpose is account, purchase, security, legal, or service delivery.

You are responsible for honoring opt-outs across your own systems, including imports, API calls, backups, segment rebuilds, and tools outside NoticeAPI.

For SMS, you must treat standard keywords and any other reasonable request to stop as revocation. You may not insist on one exclusive opt-out channel, move a suppressed recipient to another sender number, or send promotional content in an opt-out confirmation.

Prohibited uses and product boundaries

The platform has a clear edge.

These sections name prohibited content, deceptive conduct, enforcement evasion, and workflows NoticeAPI is not built to support.

03Section 3

Prohibited Content and Conduct

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.

You may not send content that collects sensitive information by deception, violates intellectual property rights, evades another provider's enforcement, uses cloaking or link shorteners to hide destination or identity, or causes unreasonable load, complaints, blocks, or reputation risk.

High-risk regulated or deceptive offers, including unlawful gambling, counterfeit goods, unsafe medical claims, debt-relief scams, investment scams, or similar schemes are not allowed.

During the SMS private beta, lead generation, purchased lists, political messaging, sweepstakes or giveaways, work-from-home offers, auto-warranty offers, short-term health-insurance offers, and debt or interest-rate reduction campaigns are not supported, even if another provider would review them.

04Section 4

Platform Boundaries

NoticeAPI is for transactional email, consent-based broadcasts, API-based email receiving, and approved first-party SMS programs. It is not a CRM, mailbox host, cold outreach platform, list broker, lead-generation platform, 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.

Do not use inbound receiving, webhooks, tracking, or the simulator to collect data unlawfully, harass recipients, test phishing flows, or build a mailbox, shared inbox, CRM, or cold outreach workflow.

Sender health and enforcement

Shared infrastructure comes with operating controls.

These sections cover platform monitoring, verified sender identity, remediation, and the actions NoticeAPI may take when risk crosses a threshold.

05Section 5

Deliverability and Abuse Controls

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.

SMS is subject to verified sender and program review, low initial recipient limits, recipient-local marketing windows, consent and suppression checks, STOP and carrier-failure circuit breakers, content checks, wallet limits, and immediate operator holds. You may not split traffic across numbers or projects to avoid those controls.

Free accounts without a completed Stripe payment-method setup are limited to simulator testing. Production sending requires a card on file, a verified domain, and may be warmed up through daily caps. These controls protect everyone using shared provider capacity.

You must maintain accurate authentication and sender records, keep complaint rates low, remove bad addresses, avoid spam traps and list bombing, and follow mailbox-provider requirements that apply to your traffic.

06Section 6

Domain and Sender Requirements

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.

Your messages must use truthful routing information, accurate sender identity, and legally required sender contact information. Subject lines, preview text, links, and attachments must not be deceptive.

Shared provider capacity is used for scale, not reputation tiering. Plan upgrades must not be used to avoid reputation, review, or abuse controls.

07Section 7

Enforcement

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, consent evidence, message examples, recent complaint or bounce context, and remediation plan.

Related legal pages

The Terms, Privacy Policy, and Acceptable Use Policy work together as the published rules for using NoticeAPI.