Acceptable Use Policy

Last updated: September 1, 2026

This Acceptable Use Policy sets out what you may and may not do when sending mail through a WarmHawk instance operated by WarmHawk (“we,” “us”). You must accept this Acceptable Use Policy (“AUP”), together with the Terms of Service and Privacy Policy, before your license can be activated, and it applies for as long as you run WarmHawk under a license we issued.

1. Prohibited uses

You may not use WarmHawk, or any instance running under a WarmHawk license, to do any of the following. These four prohibitions are absolute and are not subject to a customer’s own risk tolerance:

1. Purchased, scraped, or otherwise consent-less B2C lists. Sending to consumer (B2C) recipients who did not provide some affirmative basis for contact — including lists that were bought, scraped from the web, or otherwise assembled without the recipient’s knowledge — is prohibited outright, regardless of jurisdiction.
2. Phishing or fraud, of any kind. Any message designed to deceive a recipient into revealing credentials, financial information, or other sensitive data, or designed to induce a fraudulent payment or action, is prohibited.
3. Sender-identity impersonation. Spoofing the identity of another person, brand, or organization — sending as if you were them without authorization — is prohibited.
4. Illegal content. Sending any content that is illegal under applicable law is prohibited.

2. CAN-SPAM compliance

You are the sender of record for mail sent through your own instance, and you are responsible for that mail’s compliance with CAN-SPAM and equivalent laws in the jurisdictions you send to. At minimum, every campaign you run must:

• include a valid, physical mailing address in the message;
• include a functioning, clearly presented unsubscribe mechanism in every commercial message; and
• honor an opt-out or unsubscribe request promptly, and not re-add that recipient to a future send.

3. Suppression lists are a hard floor

WarmHawk’s built-in suppression-list mechanism — which blocks further sends to recipients who have unsubscribed, bounced, or complained — is a hard floor, not a configurable default. You may not disable it, bypass it, or re-import a suppressed recipient back into an active send list.

4. BYOK AI content

Where you enable AI-assisted personalization, you connect your own API key (“BYOK”) for Google Gemini or Anthropic Claude, and that generation happens directly between your instance and your chosen provider. WarmHawk never stores, reviews, or has visibility into the AI-generated copy your instance produces. That relationship, and the content it produces, is between you and your AI provider — you remain responsible for complying with Anthropic’s and Google’s own usage policies for any content you generate through their models, independent of your obligations under this AUP.

5. Team member access

As of this writing, WarmHawk uses a flat permission model: every team member you invite to your instance has full access to mailbox credentials, campaign data, and billing settings. There is no per-role or restricted-access tier available at launch. The account owner is solely responsible for deciding who to invite, and for any action a team member takes with that full access, including a violation of Section 1 of this AUP.

6. Consequences of violation

If we determine, in our discretion, that your use of WarmHawk violates this AUP, we may suspend or terminate your license without notice. Where we find a violation of this policy, we have no obligation to issue a refund of any amount already paid, including under the Tier 1 money-back guarantee described in the Terms of Service.

7. Related documents

This AUP works together with, and does not replace, the Terms of Service and the Data Processing Agreement. Where this AUP is silent, the Terms of Service govern.

8. Contact

To report suspected abuse or a violation of this policy, email security@warmhawk.com. For general questions about this AUP, email support@warmhawk.com.

This policy is governed by the laws of the State of Texas, without regard to its conflict-of-laws principles — the same governing law as the Terms of Service.