Messaging Acceptable Use Policy

1. Customer accountability

The customer is responsible for every message initiated by its users, integrations, automations, and imported data. Carrier acceptance, number registration, or SMSify review does not establish that a message is lawful.

2. Consent and sender transparency

• Obtain and preserve the consent or other lawful basis required for each recipient, purpose, channel, frequency, and jurisdiction before sending.
• Identify the business sender and avoid misleading caller IDs, domains, brands, offers, or relationship claims.
• Provide required disclosures when collecting a number and use it only for the service or appointment purpose disclosed at collection.
• Honor applicable quiet hours, frequency limits, do-not-contact rules, and industry-specific requirements.

3. Opt-out and help controls

Customers must support clear opt-out and help instructions and promptly honor STOP and equivalent requests across all senders. SMSify may maintain platform suppression controls that customers cannot bypass, and may block traffic when consent or suppression state is incomplete.

4. Prohibited traffic

• Marketing, advertising, or promotional messaging of any kind, including offers, discounts, sales announcements, product promotion, upsell or win-back messages, and review or referral solicitation. SMSify carries service, transactional, and appointment messaging only, and enforces this restriction with automated content controls regardless of any consent the customer may hold.
• Illegal, fraudulent, deceptive, threatening, harassing, hateful, exploitative, or privacy-invasive content.
• Phishing, malware, credential theft, impersonation, spoofing, number pumping, artificial traffic, evasion, or traffic intended to manipulate carrier or platform controls.
• Purchased, scraped, harvested, or randomly generated recipient lists without a valid documented basis.
• Content or industries prohibited by law, carrier policy, payment-provider policy, or an approved use-case registration.
• Emergency dispatch, life-safety monitoring, or any use where delay or failure could cause physical harm.

5. Compliance evidence

On request, the customer must provide the opt-in source and timestamp, disclosure shown, message purpose, sender identity, sample messages, opt-out records, and any registration or exemption evidence. SMSify may retain an auditable review record for the approved legal period.

6. Monitoring and enforcement

SMSify may apply automated and human abuse controls, sampling, velocity limits, destination limits, content restrictions, registration checks, and carrier feedback. It may delay, reject, quarantine, or suspend traffic to protect recipients, networks, or the service, and may report activity where legally required.

7. Transactional verification messages

A phone-verification message must be requested by the recipient, limited to authentication or security, identify SMSify or the relevant business, and contain no marketing. Repeated verification attempts remain subject to rate limits and abuse controls.

Fail-closed launch gate

Outbound traffic remains disabled until the business, representative, use case, sender or number registration, service address, consent flow, opt-out behavior, prohibited-content controls, and required US or Canadian carrier approvals pass review. Missing or contradictory evidence results in no send.