1. Platform and Sender Roles
IRIS Systems LLC operates ForgeSystems and provides messaging software and provider connections. The organization identified in a message is generally the sender and is responsible for the campaign, recipients, content, timing, and legal basis. IRIS Systems LLC is the sender only for communications sent on its own behalf.
Multi-tenant rule: A client organization must use its own accurate sender identity, compliance profile, brand, campaign, contact information, and consent language. It may not identify IRIS Systems LLC or ForgeSystems as the sender merely because the platform transmitted the message.
2. Registration and Accurate Information
Before sending application-to-person SMS, an organization must complete the provider, carrier, brand, campaign, number, and use-case registration required for its traffic. Information supplied for registration must be complete, current, and consistent with public business information.
3. Consent and Recipient Expectations
- Send only to recipients for whom the sender can document an applicable permission or other lawful basis.
- Marketing consent must be clear, conspicuous, and specific to the identified sender and messaging purpose.
- Consent for one organization, purpose, or channel may not be treated as blanket consent for unrelated organizations, purposes, or channels.
- Maintain the opt-in source, disclosure shown, timestamp, recipient, campaign, and any later revocation.
- Do not condition a purchase on marketing-text consent where prohibited.
4. Required SMS Disclosure Elements
An SMS opt-in disclosure should identify the sender and program, describe expected content and frequency, state that message and data rates may apply, explain how to obtain help and stop messages, link to applicable privacy terms, and disclose that consent is not a condition of purchase when applicable.
5. STOP, HELP, and Revocation
Senders must honor recognized opt-out requests promptly across the relevant program and must not resume messages without a new valid basis. HELP responses should provide accurate sender and support information. A recipient may revoke consent through any reasonable method required by applicable law or provider policy; keyword automation is not the only possible revocation channel.
6. Email Requirements
Commercial email must use accurate routing and subject information, identify the sender, include a working opt-out method and required postal information, and honor opt-outs within the applicable period. Senders must authenticate domains and follow provider requirements when ForgeSystems makes those controls available.
7. Prohibited Messaging
Do not send unsolicited bulk traffic, purchased-list traffic, phishing, fraud, unlawful content, misleading sender identity, prohibited carrier content, or messages that evade filtering, throughput, registration, or opt-out controls. The Acceptable Use Policy also applies.
8. One-Time and Recurring Notifications
A one-time requested alert and a recurring notification program must be described accurately. Recurring programs need an understandable frequency and an ongoing way to stop. A one-time request must not silently enroll the recipient in continuing messages.
9. Monitoring and Suspension
ForgeSystems may retain consent and delivery evidence, process provider status events, and suspend sending when registration, consent, complaint, opt-out, fraud, or deliverability signals indicate material risk. Provider approval does not guarantee that any message or campaign complies with law.
10. Contact
Messaging compliance questions and abuse reports: support@forgesystems.io. Identify the sending organization and campaign without including unnecessary message content or personal data.
Operational publication prepared for licensed-attorney review. This status does not represent attorney approval or legal advice.