> ## Documentation Index
> Fetch the complete documentation index at: https://docs.firstrespondershub.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Unsubscribe and compliance

> How unsubscribe links work, the public unsubscribe page, and what's required before you can send.

Every campaign sent from Contacts is CAN-SPAM compliant by default: every recipient gets a unique unsubscribe link, and your organization's physical address is rendered in the footer. This page explains how it works and what you need to have set up.

## What's attached to every email

Every email sent via the Contacts composer includes, automatically:

* Your organization's **name**
* Your organization's **physical address** (street, city, state, zip)
* A per-recipient **unsubscribe link** with a secure token
* A short CAN-SPAM footer identifying the email as being from your organization

You cannot remove these. If your organization address is not set, sends will fail — add it in organization settings before sending.

## The unsubscribe link

Each email's unsubscribe link includes a per-recipient token. When a contact clicks it:

1. They land on a public unsubscribe page at `firstrespondershub.com/unsubscribe`.
2. The page shows your organization name and confirms what they're opting out of.
3. They click **Unsubscribe** to confirm — one-click confirmation.
4. The contact's email status flips to `Unsubscribed` immediately.

Unsubscribe is per-organization: a contact who unsubscribes from Org A is still reachable by Org B if they exist in both orgs' contact lists.

## Who is excluded from sends

Contacts with email status **Unsubscribed** or **Bounced** are automatically excluded at send time. This happens at the recipient-count step (so the number you see in the composer is already post-exclusion) and is enforced again when the background job dispatches each message.

You cannot re-subscribe a contact from the dashboard. If they want back in, they must sign up again through your public information request form or checkout.

## Bounces

When the email provider reports a hard bounce (mailbox doesn't exist, domain rejects mail), the contact is automatically marked **Bounced** and excluded from all future sends. This protects your sender reputation and keeps your domain deliverable for the contacts who do want to hear from you.

Soft bounces (temporary failures like mailbox full) are not marked — they're retried by the provider.

## What you need before sending

To send any contact campaign, your organization must have:

* **Email address** for the sender (set in organization settings) — used in the CAN-SPAM footer and as a reply-to.
* **Physical address** — street, city, state, zip. Required by CAN-SPAM.
* **Email campaigns feature enabled** on your plan — see [Plan tiers and limits](/plans-and-billing/plan-tiers-and-limits).
* **Monthly email quota remaining** — the composer blocks sends that would exceed your plan's cap.

## What you're responsible for

The platform handles infrastructure — headers, tokens, footer, bounce handling. You are responsible for:

* Having permission to email the contacts you import or add manually.
* The content of your emails (honest subject lines, no deceptive routing).
* Reasonable sending cadence — even within your plan's quota, repeatedly emailing an unengaged list harms deliverability for the whole platform.