1. Who this policy covers
This Policy applies to customers, their users, developers, integrations, and other parties accessing Neopolis SMS or Neopolis Connect. You are responsible for the activity you authorize through your account, API credentials, and connected devices.
Use must comply with applicable law, our Terms of Service, our Messaging Policy, and the requirements of messaging providers and carriers. A technically successful request does not establish that the activity is permitted.
2. Prohibited conduct
You must not use the Service to:
- Send spam, unsolicited bulk messages, phishing links, fraudulent offers, impersonation, or deceptive communications.
- Harass, threaten, exploit, discriminate unlawfully, or promote violence or abuse.
- Transmit unlawful sexual content, child exploitation material, malware, ransomware, or instructions intended to compromise another system.
- Infringe intellectual property, privacy, confidentiality, or other rights, including through unauthorized images or contact lists.
- Collect passwords, authentication codes, payment credentials, or sensitive identifiers through deception.
- Misrepresent your business, campaign purpose, recipient consent, sender identity, or provider registration information.
- Continue ordinary messaging after a recipient opts out, or use another account or number to evade the request.
3. Messaging and content restrictions
Carrier and provider restrictions can be stricter than what local law permits. Consent does not make prohibited content acceptable, and a registered campaign is not approval for unrelated content.
Neopolis does not permit messaging for adult entertainment or pornography, illegal or federally controlled drug promotion, or fraudulent financial offers. Other high-risk categories—including lending advertisements, credit repair, debt relief or collection, affiliate lead generation, and deceptive earnings schemes—require advance written authorization where provider rules allow them. Age-restricted goods require an approved channel, safeguards, and provider authorization. If a category is not supported, you must not send it.
Check with us before starting a restricted or uncertain use case. Current provider requirements are available in Bandwidth’s messaging content policies; applicable carrier restrictions also apply.
4. Data and account protection
Collect and upload only information you are authorized to use. Purchased, rented, scraped, or shared lists are not proof of recipient consent. Do not disclose another person’s confidential information without a lawful basis.
Do not upload credentials, full payment card details, or highly sensitive information unsuitable for ordinary text messaging. Do not use the Service for regulated sensitive workflows that require contractual or technical protections we have not expressly agreed to provide.
Keep API keys private, authorize only trusted devices, and promptly report compromised access. Do not create accounts or alter identity information to avoid a restriction imposed on another account.
5. Network integrity
Do not probe accounts you do not own, attempt unauthorized access, bypass rate or size limits, disable opt-out protections, or disrupt infrastructure. Do not conduct penetration testing, vulnerability scanning, denial-of-service testing, or load testing against the Service without prior written authorization.
Use API and webhook endpoints only as documented. Validate your integrations and avoid retry loops, duplicate sends, misleading callbacks, and traffic that places unreasonable load on the platform. Do not deliberately obscure message destinations, attachment types, or the source of traffic to evade checks.
6. Reviews and enforcement
We may request consent evidence, campaign descriptions, example messages, identity information, and corrective action when investigating an issue. You must cooperate with reasonable compliance and security requests and pause disputed traffic when directed.
We may reject messages, restrict features, revoke credentials, suspend accounts, or terminate access to address violations, legal requirements, or provider restrictions. Urgent threats may require immediate action. Where appropriate, we will provide a way to explain or correct the issue; reopening service remains subject to applicable requirements.
We may preserve relevant records and disclose information when lawful and necessary for an investigation. Enforcement does not waive charges already incurred or other remedies available under the Terms or applicable law.
7. Reporting abuse
Report suspected abuse using the contact information below. Include the sender number, date and time, message text or a screenshot, and any relevant message identifier. Avoid sending unnecessary sensitive information.
If you are a recipient, you can also reply STOP to the sending number or contact the business directly. If a communication presents an immediate threat to someone’s safety, contact the appropriate emergency or law-enforcement service rather than relying on this platform.
Contact
For questions about this policy, contact support@neopolis.net. Include the relevant account or message reference, but do not email passwords, API keys, or payment card details.
Service operator: Neopolis SMS