Anti-Spam Policy

Email regulation differs by the recipient's jurisdiction, and senders are responsible for compliance wherever their recipients are. The Service is designed so that the strictest common requirements are the default behavior:

• Unsubscribe in every sequence. Every campaign send from a mailbox carries one-click unsubscribe headers (RFC 8058), which the sender cannot switch off. The visible footer link is on by default; a sender may drop it only for mail they would defend as transactional, and the headers still give every recipient a one-click opt-out. Opt-out must not require a login, a fee, or anything beyond the single action.
• Immediate honoring. Unsubscribe requests take effect the moment they are processed — not in 10 days, which the law allows, but at the next send-time check, which is minutes. Remaining sequence steps to that address are cancelled automatically.
• Suppression that outlives the contact. Unsubscribed, bounced, and complained addresses go onto the workspace suppression list, are checked at send time on every future campaign, and survive contact deletion. A workspace owner — not an ordinary member, and not an API key — can remove an entry that landed there in error, behind a typed confirmation and a permanent audit-log record of who removed which address. Entries recorded from a spam complaint are the exception and cannot be removed by anyone in the dashboard.
• Authentication before sending. A domain's SPF and DMARC must resolve, and DKIM must carry real key material wherever the provider publishes a selector we can check, before that domain can send.
• No hidden senders. From-names and reply-to addresses must belong to mailboxes the workspace controls.

• Send only to recipients for whom you have a valid consent basis or a defensible legitimate interest (see the Acceptable Use Policy, Section 2).
• Identify yourself truthfully: real name, real company, and a valid physical postal address in the message footer where the law requires one (CAN-SPAM does; include it by default).
• Never obscure that a message is commercial outreach, and never use misleading subject lines or fake thread markers.
• Honor opt-outs everywhere: if someone unsubscribes from your SendCanyon sequences, do not re-add them through another tool or channel.
• Keep records sufficient to demonstrate your consent or interest basis if a recipient or regulator asks.

1. Complaints reach us through provider feedback loops, recipient reports to abuse@sendcanyon.com, and blocklist-operator notices.
2. The complained-about address is suppressed in the sending workspace immediately.
3. The complaint is attributed to its campaign and counted against the workspace's complaint-rate thresholds (0.1% warning, 0.3% automatic sending pause — see the Acceptable Use Policy).
4. Patterns are reviewed by a human: a workspace whose complaints cluster around one list or one campaign is required to remediate the source, not just the symptom.
5. Recipients who write to us receive a response confirming suppression, and — as the messages are sent by our customers from their own domains — we identify the responsible sender where lawful and appropriate.

Use the unsubscribe mechanism in the message — it takes effect immediately and permanently for that sender. If the message lacked one, deceived you about its origin, or continued after you opted out, forward it with full headers to abuse@sendcanyon.com. We will suppress your address across the offending workspace, investigate the sender under the Acceptable Use Policy, and act on what we find, up to terminating their account. You do not need to be a SendCanyon customer for this to apply.

Email law and provider requirements evolve (the 2024 Gmail/Yahoo bulk-sender rules moved the industry's floor overnight); we update this policy and the platform's enforcement to track them, and material changes are announced to customers with at least 14 days' notice. Questions: legal@sendcanyon.com.