Terms & Conditions

01 Acceptance of these Terms

By creating an account, purchasing prepaid plans or packages, submitting DLT/header/template documentation, generating an API key, or integrating our APIs into your application, you agree to be bound by these Terms and our Privacy Policy. If you are acting on behalf of a company or organization, you confirm that you hold proper legal authority to bind that entity.

You agree to provide true, accurate, current, and complete information and to use the service solely for lawful software applications and business operations.

02 What NizoraSMS Provides

NizoraSMS is an OTP/SMS developer routing platform operated by Anvex Group. The platform provides REST API access, prepaid plan billing, approved logical template routing, optional dedicated DLT onboarding, delivery receipts (DLR), and developer diagnostic logs.

03 Account Eligibility & Responsibility

• You are strictly responsible for maintaining the confidentiality of your login credentials, API secret keys, and connected server environments.
• You must promptly rotate or delete any API keys that are inadvertently exposed in client-side applications, public repositories, or unsecured environments.
• You are legally and operationally responsible for all activities and API requests originating from your account.
• Business documentation, GST/PAN certificates, and DLT authorization letters submitted to the platform must be genuine and current.
• We reserve the right to request identity verification before activating high-throughput routes or custom enterprise templates.

04 OTP Generation & Verification Logic

Developers generate the one-time passcode (OTP) on their own application server and verify it within their own backend. NizoraSMS receives the OTP value only to insert it into the regulatory-compliant message template and transmit it via telecom routes.

The developer is exclusively responsible for OTP cryptographic entropy, expiry countdowns, attempt-rate throttling, replay prevention, and final verification logic within their application.

05 DLT, Headers & Content Templates

Platform-Managed Shared Route

Certain developer plans utilize pre-approved shared logical templates and pooled sender headers managed by Anvex Group. The platform maintains redundant approved sender headers behind each logical template for failover continuity.

The internal designation “non-DLT” represents a simplified onboarding workflow; it does not waive any TRAI regulations, telecom standards, or carrier rules. All traffic complies with upstream telecom requirements.

Customer-Specific Dedicated DLT Flow

Customers requiring their own enterprise sender header (e.g. MYAPP) must complete the regulatory DLT onboarding workflow, consisting of:

• Dedicated sender headers are account-specific and cannot be shared across unrelated accounts.
• Approval authority rests solely with external telecom operators and DLT registrars, and cannot be guaranteed by Anvex Group.
• Submissions containing false, misleading, or infringing details will be immediately rejected.

06 Custom Template & Header Requests

Customers wishing to register custom sender headers or custom message bodies may submit a request through the console. Unless included in a premium enterprise package or stated otherwise at checkout, the standard operational review fee is ₹2,500.

This fee covers manual compliance vetting, document formatting, telecom liaison, and gateway mapping work. Payment of this operational fee does not guarantee approval if the telecom operator or regulatory body rejects the application due to non-compliant documentation or prohibited keywords.

07 Payments, Prepaid Plans & Packages

All pricing and payable amounts are clearly stated before purchase confirmation. Entitlements and prepaid balances are credited only after server-side webhook verification from the authorized payment processor.

• Prepaid plans provide service balance valid for dispatching OTP messages at the rate tier associated with the purchased plan.
• Eligible higher-value plan upgrades renew or reduce your per-OTP unit rate for the validity duration specified in your plan details.
• Bulk packages credit the explicit OTP message allocation described at checkout upon verified payment.
• Applicable taxes (GST) and payment-gateway fees, where applicable, are transparently presented at checkout.
• Conflicting or delayed payment events are subject to automated bank reconciliation before additional credits are released.

08 Message Delivery, Routing & Continuity

We deploy intelligent multi-route failover designed to maximize delivery speed and uptime. However, SMS delivery depends on third-party mobile networks, subscriber signal coverage, roaming statuses, handset capacity, and national DLT filters outside our direct control.

Where a provider failure is confirmed, our engine automatically re-routes traffic through secondary vetted pipes. Where provider acknowledgment is delayed or ambiguous, the platform reconciles status rather than duplicate-billing the transaction.

09 Acceptable Use Policy

You agree not to use NizoraSMS for any deceptive, harmful, abusive, or unlawful activities. Prohibited conduct includes:

• OTP Bombing & Harassment: Generating repeated, automated, or unsolicited OTP floods to any recipient.
• Phishing & Deception: Impersonating banks, financial institutions, government agencies, or brands without verifiable authority.
• Template Violation: Attempting to transmit promotional, spam, or casino/crypto messaging through transactional OTP routes.
• Fraudulent Identity: Submitting fake GSTIN, PAN, or forged authorization certificates for DLT registration.
• System Exploitation: Reverse engineering the API, attempting DDoS attacks, or evading rate-limiting controls.

Violation of this policy will result in immediate suspension, route termination, and potential reporting to law enforcement authorities.

10 API & Security Keys

All API calls require authentication using your secret API key. Keys must be stored securely on your server (e.g. environment variables) and never hardcoded in client-side code, frontend JavaScript, or mobile apps.

We strongly recommend utilizing unique idempotency keys in your dispatch requests to eliminate accidental duplicate transmissions during network timeouts.

11 Suspension, Restriction & Termination

We reserve the right to suspend or restrict any account, API key, sender header, or route immediately if we detect abusive traffic patterns, payment chargebacks, fraudulent DLT filings, or formal carrier block requests.

Where feasible, we will notify the account holder and offer a reasonable remediation period, except in emergencies involving security breaches or regulatory compliance orders.

12 Cancellations & Refunds

Refunds and cancellations are handled strictly according to our published Refund & Cancellation Policy.

• Verified duplicate charges or failed payments debited by the bank will be refunded or adjusted.
• Prepaid credits or OTP units that have already been dispatched or consumed are non-refundable.
• Operational fees for custom template/DLT processing become non-refundable once external filing has commenced.

13 Data Protection & Privacy

Our collection, processing, and safeguarding of customer and recipient data are detailed in our Privacy Policy. By using the service, you affirm that you possess a lawful basis and necessary recipient permissions to submit phone numbers for SMS transmission.

14 Intellectual Property Rights

All software, API architecture, logos, branding, user interfaces, documentation, and design assets associated with NizoraSMS are the exclusive intellectual property of Anvex Group. No title or ownership rights are transferred to you under these Terms.

You retain full intellectual property rights to your own applications, logos, and custom content submitted for template registration.

15 Third-Party Dependencies

Our platform operates in conjunction with telecom operators, DLT registrars, SMS gateway partners, and payment processors. We are not responsible for unilateral changes in telecom tariffs, regulatory mandates by TRAI, or upstream carrier routing outages.

16 Disclaimers & Limitation of Liability

The service is provided on an “as is” and “as available” basis. While we strive for 99.9% uptime and sub-second OTP routing, we do not warrant that service will be uninterrupted, error-free, or compatible with every mobile device worldwide.

To the maximum extent permitted by Indian law, Anvex Group shall not be liable for any indirect, incidental, punitive, or consequential damages (including loss of business profits or data) arising from mobile network delays, external DLT rejections, or account credential exposure by the customer.

17 Changes to Terms

We may amend these Terms periodically to accommodate new features, security updates, or legal requirements. Updated Terms become effective upon posting with a revised “Last updated” date. Continued use of the platform after updates signifies your acceptance.

18 Governing Law & Jurisdiction

These Terms shall be governed by and construed in accordance with the laws of India. Any legal dispute or claim arising out of or related to these Terms shall be subject to the exclusive jurisdiction of the competent courts in Gujarat, India.

19 Contact & Support

For inquiries regarding these Terms, billing reconciliations, or platform compliance, please reach out to our official desk: