Acceptable use that protects serious telecom operators.
ZoikoNex is built for responsible telecom monetization, governed API access, secure integrations, and trusted customer operations. Our Acceptable Use rules define the conduct, content, automation, API activity, and telecom practices that are not permitted on the platform.
security and procurement review faster, not harder.
Telecom abuse can create customer harm, regulatory exposure,
carrier-relationship risk, payment disputes, and brand damage.
API misuse can cause data leakage, billing errors, unauthorized
provisioning, excessive load, and integration instability.
Clear rules protect legitimate customers by separating
responsible operation from high-risk or unlawful behavior.
Transparent boundaries help legal, compliance, security, and
procurement teams complete due diligence faster.
What is not allowed.
A scannable map of prohibited activity. Each card states the rule and why it protects the ecosystem —
examples are illustrative, not exhaustive.
Illegal or harmful use
Facilitating unlawful conduct, exploitation, harassment, threats, scams,
or otherwise harmful activity.
Why: protects customers, partners, end users, and ZoikoNex from
unlawful or unsafe use.
Telecom fraud & network abuse
Robocall abuse, unlawful spoofing, SIM/eSIM fraud, unauthorized
porting, traffic pumping, or bypass fraud.
Why: protects carrier relationships, service integrity, and telecom
compliance posture.
Spam & unauthorized messaging
Bulk unsolicited messaging, deceptive outreach, phishing, credential
harvesting, or unlawful promotional traffic.
Why: protects deliverability, recipients, brand integrity, and partner
networks.
Security abuse
Malware, credential stuffing, vulnerability exploitation, unauthorized
scanning, data exfiltration, or bypassing controls.
Why: protects platform availability, confidentiality, and customer trust.
API & automation misuse
Excessive requests, scraping, token sharing, reverse engineering, rate-
limit evasion, or unsafe bot behavior.
Why: protects service performance, fair access, and integration reliability.
Billing & financial abuse
Payment fraud, chargeback abuse, invoice manipulation, artificial
usage, or manipulating rating or settlement logic.
Why: protects revenue integrity, customer trust, and financial operations.
AI misuse
Using AI features for deceptive content, impersonation, fraud,
discriminatory decisions, unlawful surveillance, or unauthorized
automated actions.
Why: protects governance integrity and prevents unsafe automation.
Policy circumvention
Avoiding restrictions, misrepresenting identity, hiding beneficial
ownership, bypassing jurisdiction controls, or reselling access without
authorization.
Why: protects enforcement, compliance, and commercial fairness.
Responsible platform use.
The operating model for legitimate customers and partners. Follow these and your usage stays
protected.
Accurate identity & authorization
Keep account, organization, developer, partner, and billing information accurate and authorized.
Respect telecom & messaging rules
Use voice, SMS, eSIM, numbers, roaming, and provisioning only for lawful and approved use cases.
Protect credentials & API keys
Use secure storage, rotation, least privilege, and report compromised credentials immediately.
Respect rate limits & boundaries
Design integrations to follow documented API, webhook, event, and sandbox limits.
Maintain consent & legal basis
Handle consent, disclosure, opt-out, and recordkeeping obligations where relevant.
Report suspected abuse promptly
Use the abuse-reporting path for suspected fraud, security issues, misuse, or harmful conduct.
API, developer & sandbox use.
Clear boundaries that keep evaluation easy and the platform reliable.
Sandbox is for testing, evaluation, and integration development only, unless production access is approved.
No production traffic, live personal data, or real customer credentials in sandbox environments.
No unauthorized load testing or undocumented endpoint probing.
API keys, tokens, and webhooks must not be shared or committed to public repositories.
Respect rate limits, idempotency rules, endpoint authorization, and event-subscription boundaries.
Follow documentation constraints; design for deprecation and change notices.
Enforcement & remediation.
Fair, proportionate, and evidence-aware. Most issues start with guidance, not penalties.
continue
abuse report
carrier/partner notice where appropriate
contract & law
decision-authority record
Enforcement is proportionate but not a fixed sequence — severe or unlawful abuse may require immediate action. Actions are subject to your contract and applicable
law.
sensitive credentials.
I agree that ZoikoNex may contact me about this submission and process my details
per the Privacy Notice.
responds faster.
(priority).
operations.
Build on a platform designed for responsible telecom operations.
ZoikoNex gives serious telecom operators clear rules for safe, governed, and commercially
credible platform use. Review the policy, request the enterprise legal pack, or report
suspected abuse through the appropriate route.