Using Notilify
Notilify provides transactional SMS infrastructure for product and engineering teams. Customers are responsible for using the service only for lawful messaging, maintaining accurate account information, protecting dashboard credentials, and making sure their own application workflows comply with the rules that apply to their users and destination markets.
You may not use Notilify to send abusive, deceptive, unsolicited, or illegal messages. Messaging programs should clearly support the product experience your users expect, including account access, verification, service alerts, delivery notifications, and other operational communication.
Account and billing
Account owners are responsible for invited users, API keys, sender configuration, message activity, and charges generated from their workspace. Pricing can vary by destination, route, sender setup, and provider costs, so teams should review current pricing before sending production traffic.
If payment fails or account activity creates operational risk, Notilify may limit, suspend, or disable access while the issue is reviewed. We will try to keep customers informed when a billing or policy issue affects service access.
Service responsibilities
Delivery receipts, provider statuses, and webhook events are operational signals from messaging infrastructure and carriers. They help teams debug sending behavior, but they are not a guarantee that a human recipient saw a message.
Customers are responsible for the content they send, the phone numbers they collect, consent where required, and any fallback or support process needed when a critical message cannot be completed.
Questions about these terms?
Contact Notilify support before sending production SMS traffic if your team needs account, billing, or data-handling clarification.