1. Permission, identity and recipient expectations
- Send only to recipients for whom you have the required permission or other lawful basis. Keep evidence of consent where applicable.
- Identify yourself and your organization accurately. Use only sender IDs approved for your account and the relevant route.
- Honor unsubscribe, opt-out, suppression and do-not-contact requests promptly, and maintain current recipient lists.
- Keep messages relevant to the purpose for which a recipient supplied their details. Do not use OTP or transactional messaging as a way to bypass consent requirements for marketing.
2. Prohibited activity
You must not use GLOBE SMS to send or facilitate:
- Unsolicited, deceptive, fraudulent or unlawful messages, including phishing, impersonation or attempts to obtain credentials or payment details.
- Threats, harassment, abusive content, unlawful discrimination, or content that violates another person’s rights.
- Malware, malicious links, scams, prohibited goods/services, or instructions intended to cause harm or evade safeguards.
- Messages to purchased, scraped or otherwise improperly obtained lists, or repeated messages after a recipient has opted out.
- Traffic designed to evade rate limits, sender-ID checks, account controls, provider rules or applicable law.
3. API, credentials and service protection
Keep passwords, SMS API keys and OTP API keys confidential. Use keys only for their intended scope, store them on trusted servers, rotate exposed keys, and revoke credentials no longer needed. Do not probe, disrupt, overload, reverse engineer or attempt unauthorized access to the platform or another account.
Do not attempt to circumvent service limits by distributing traffic across accounts, phone numbers, API keys or source addresses. Use the dedicated OTP API for OTP workflows and follow its cooldown, verification and billing rules. See Developer Docs for integration guidance.
4. Customer responsibilities
You are responsible for your campaign content, recipient data, consent records, customer disclosures, required notices, retention practices and compliance obligations. Secure any personal data uploaded or accessed through your integration and restrict it to personnel who need it.
Test integrations with authorized test data and avoid repeated production requests. A provider acceptance response is not proof of delivery, and uncertain requests should be checked before retrying to avoid duplicates.
5. Reporting, review and enforcement
Report suspected abuse, compromised credentials or privacy concerns to support@globe.bd. When contacting us, include a relevant account, request or transaction reference where available, but do not include passwords, API secrets, OTP values or unnecessary recipient data.
We may review activity and apply proportionate restrictions, suspend sender IDs or API keys, pause traffic, or disable an account when reasonably necessary to investigate reports, protect recipients or the service, meet provider requirements, comply with law, or address a violation. Where practical, we will provide an explanation and a route to contact support. This policy may be updated; the latest published version is shown on this page.