Terms of Service

1. Your responsibility as the sender

You control the gateways, recipient lists, message content, sending times, and mobile network account. You must have a lawful reason to contact every recipient and follow applicable privacy, direct-marketing, telecommunications, consumer-protection, and carrier rules.

2. Marketing and opt-outs

Do not send unsolicited marketing. Obtain the specific consent required in the recipient's jurisdiction, identify the sender, provide a valid way to stop messages, record withdrawals promptly, and screen every new list against a maintained do-not-text list. A purchased, scraped, or publicly visible number is not proof of consent.

3. Prohibited use

• Fraud, impersonation, phishing, harassment, threats, illegal content, or evading recipient blocks.
• Emergency, life-safety, medical, or other delivery-critical messaging where delayed or duplicate SMS could cause harm.
• Bypassing carrier controls, Android security, platform permissions, rate limits, or service restrictions.
• Uploading recipient data you are not authorised to process.

4. Service and device limitations

SMS delivery is not guaranteed. Phones may be offline, Android may restrict background work, carriers may reject or delay messages, and delivery reports may be absent. Keep a human-visible queue, review failures, and avoid blind retries when the outcome is uncertain. The current direct-distribution Android build has documented platform limitations and is not represented as Play-ready or as an uninterrupted 24/7 service.

5. Costs and third parties

You are responsible for carrier charges, phone plans, taxes, hosting, and third-party services. Stripe-hosted billing terms apply when a paid plan is enabled. Keep carrier and Stripe account information current.

6. Security and operations

Use unique secrets, HTTPS, least-privilege access, signed release artifacts, protected backups, and supported software. Rotate credentials after suspected exposure. Do not share pairing codes, device tokens, recipient lists, message bodies, or production logs with unauthorised people.

7. Suspension and account deletion

An operator may block abusive or unsafe workspaces. Account deletion removes active workspace data from primary storage, subject to billing reconciliation, security records that must be retained, and normal backup expiry.