Acceptable use
Geo SMS Hub delivers transactional messages that the recipient is expecting — verification codes, sign-in codes, and password resets — through a phone number and sender name we operate. Because every message is sent under our own sender identity and through our own provider account, misuse affects every other customer. These rules exist to keep the service available to everyone using it honestly.
What you may send
- One-time codes and verification messages your own users have requested.
- Messages triggered by an action the recipient took in your application.
- Messages to recipients who gave you their number for this purpose.
What you may not send
- Marketing, promotional, or bulk campaign messages of any kind.
- Anything claiming to come from a bank, government body, delivery service, or any organisation you are not.
- Messages designed to obtain passwords, card details, or personal data from the recipient.
- Messages to people who did not give you their number, or who asked you to stop.
- Content that is unlawful under Georgian law, or that harasses or threatens the recipient.
How we enforce this
Free accounts send from a fixed set of built-in templates, and message variables are checked automatically: values containing links, web addresses, or phone numbers are refused. This is deliberate. It makes the most common form of SMS fraud impractical rather than merely forbidden.
We may suspend a project immediately, without notice, if we believe it is sending prohibited traffic. Suspension stops delivery at once; you keep access to your message history. Where a suspension is a mistake, contact us and we will restore the project.
Limits and credits
Free accounts receive a fixed allowance of message credits and a daily sending limit. Credits are consumed per SMS segment, which is what our delivery provider charges for: longer messages, and messages in Georgian, use more than one segment each. Credits have no cash value and are not refundable.
What we promise, and what we do not
We do not guarantee delivery, delivery time, or availability. Mobile delivery depends on
networks and handsets outside our control. We report status honestly: submitted
means our provider accepted the message, and delivered is used only after a real
delivery confirmation. We never fabricate a delivery receipt.
The service is in private beta. Features may change, and we may end the beta with reasonable notice.
Your responsibilities
- Keep your API keys secret. Anyone holding a key can send as your project.
- Have a lawful basis for messaging every recipient you send to.
- Tell us promptly if a key is exposed, so we can revoke it.
Contact
Questions, suspensions, and abuse reports: jemal@leansystems.ge.