Messaging & Anti-Spam Policy

Effective Date: April 18, 2026

1. SMS & MMS (10DLC/TCPA Compliance)

All SMS traffic must comply with the CTIA Short Code Monitoring Handbook and 10DLC carrier requirements.

Express Written Consent: Customer must have documented, express written consent before sending the first message, meeting the FCC's definition in 47 CFR § 64.1200(f)(9).

Opt-Out (STOP): Inflowence's system automatically handles "STOP" keywords. Customer is prohibited from attempting to bypass these opt-out mechanisms.

Identification: Every message must include the Customer's business name.

2. WhatsApp & Social DMs (Meta Business Policies)

Use of WhatsApp, Facebook, and Instagram DMs is subject to Meta's Business Messaging Policy.

24-Hour Window: Customer acknowledges that DMs may be restricted to a 24-hour response window unless specific "Message Templates" are used.

Prohibited Content: Messages involving high-risk industries (CBD, Gambling, Adult, Lending) are strictly prohibited and will result in immediate account termination.

3. Email (CAN-SPAM Compliance)

All emails sent via Inflowence (via AWS SES) must include:

  • A valid physical postal address of the Customer.
  • A clear, functional "Unsubscribe" link.
  • Accurate "From" and "Subject" lines.

Bounce Rate Threshold: If Customer's bounce rate exceeds 5% or complaint rate exceeds 0.1%, Inflowence reserves the right to suspend email privileges immediately.

Unsubscribe Handling. Unsubscribe requests must be honored within ten (10) business days of receipt, and the unsubscribe mechanism must remain functional for at least thirty (30) days after the message is sent. Customer may not require recipients to log in, provide payment, or supply information beyond an email address to unsubscribe.

List Sourcing. Customer may only send to recipients who have opted in through Customer's own forms, existing customers with a qualifying business relationship, or leads who have affirmatively requested information. Purchased lists, scraped addresses, third-party lists without verified opt-in, and co-registration leads without a clear opt-in to Customer's sending identity are prohibited.

4. Consent Records

Customer must maintain consent documentation for every recipient, including: (i) date and time of consent; (ii) method of consent (web form, verbal, written); (iii) the channel(s) and sender identity the recipient consented to; (iv) the source URL or physical location where consent was captured; (v) the IP address for web-form consent; and (vi) the exact consent language and disclosures shown. Consent records must be retained for no less than four (4) years for SMS/MMS and two (2) years for email, and must be produced to Inflowence within five (5) business days of a compliance request.

5. Abuse Reporting

Violations of this policy may be reported to abuse@inflowence.ai. Inflowence investigates reports within 48 hours of receipt.

Related Policies

Contact Us

For questions about messaging compliance:

Email: compliance@inflowence.ai

By using Inflowence's messaging features, you acknowledge that you have read, understood, and agree to this policy.