Acceptable Use Policy

1. Introduction

This Acceptable Use Policy defines the permitted and prohibited uses of the NepalOTP platform. It exists to maintain the integrity, reliability, and deliverability of the verification infrastructure we provide.

NepalOTP is designed to enable secure, predictable, and controlled messaging for user verification. Our commitment is to provide a platform that developers can rely on, and that carriers and recipients can trust.

By using NepalOTP, you agree to comply with this policy. Responsible use ensures high delivery rates, protects end users from unwanted messages, and maintains the reputation of the platform for all users.

2. Intended Use

NepalOTP is an OTP-first verification platform. The primary purpose of this service is to generate, deliver, and verify one-time passwords via SMS for user authentication.

Primary use case

OTP-based user verification for login, signup, password reset, and two-factor authentication flows.

Secondary use case

Approved transactional SMS notifications using pre-reviewed templates. This feature is available for operational messages only and is subject to template approval.

NepalOTP is not a bulk messaging platform, a marketing SMS service, or a free-text messaging API. The platform is purpose-built for verification and controlled transactional communication.

3. Allowed Use

The following use cases are permitted on the NepalOTP platform:

OTP verification

Login and signup verification codes
Password reset verification codes
Two-factor authentication codes
Phone number verification during account creation
Transaction authorization codes

Approved transactional messages

Order confirmations and shipping updates
Payment receipts and transaction notifications
Appointment reminders and schedule confirmations
Account security alerts
Service status notifications

All transactional messages must use pre-approved templates. Ad-hoc or free-text messaging is not supported.

4. Prohibited Use

The following uses of NepalOTP are strictly prohibited:

Marketing and promotional content

Advertising, promotions, or special offers
Discount codes or sales announcements
Product launches or feature announcements
Newsletter content or marketing campaigns

Bulk and uncontrolled messaging

Mass messaging or broadcast campaigns
Free-text or user-generated message content
Messages composed dynamically without approved templates
Unsolicited messages to recipients who have not requested them

Harmful or deceptive content

Misleading, deceptive, or fraudulent messages
Phishing attempts or impersonation
Content that violates applicable laws or regulations
Spam or repetitive unwanted messages

Restricted content types

Messages containing URLs or clickable links
Call-to-action content encouraging purchases or signups
Content promoting gambling, adult services, or controlled substances
Political campaign messages

5. Template Requirements

All transactional SMS sent through NepalOTP must use pre-approved templates. This requirement ensures message quality, regulatory compliance, and delivery reliability.

Template rules

1

Submission required

All non-OTP message templates must be submitted for review before use. Templates are reviewed within 24-48 hours.

2

No post-approval modifications

Once a template is approved, its content cannot be modified. To change a template, submit a new version for review.

3

Approved variables only

Only designated variable placeholders may be substituted at send time. Variables are defined during template submission.

4

Content restrictions apply

Templates must comply with all content restrictions outlined in this policy. Templates containing prohibited content will be rejected.

OTP messages use a system-managed template and do not require individual template submission.

6. Sender Identity Rules

Sender identity is a critical factor in SMS deliverability and recipient trust. NepalOTP enforces sender identity rules to maintain platform reputation and carrier relationships.

Approved sender IDs

Messages are sent using sender IDs approved for your account. Sender IDs are configured during account setup.

Change restrictions

Sender ID changes require review and approval. Frequent changes are not permitted to maintain delivery consistency.

Consistent sender identity helps carriers recognize legitimate traffic and improves delivery rates across all Nepali networks.

7. Rate Limits and Fair Use

Rate limits protect the quality of the delivery infrastructure, prevent abuse, and ensure fair access for all platform users.

Limit type	Threshold
OTPs per phone number (hourly)	5 requests
OTPs per phone number (daily)	10 requests
API requests per minute	100 requests
Verification attempts per OTP	3 attempts

Bypass attempts are prohibited

Attempts to circumvent rate limits through multiple accounts, key rotation, or other means are a violation of this policy.

If your use case requires higher limits, contact support to discuss your requirements.

8. Data and Privacy Expectations

You are responsible for ensuring that your use of NepalOTP complies with applicable data protection and privacy requirements.

Lawful consent

You must have appropriate consent or legal basis to send messages to recipients. OTPs should only be sent in response to user-initiated actions.

Legitimate data collection

Phone numbers must be collected through legitimate means. You must not use scraped, purchased, or harvested phone number lists.

Data security

You are responsible for securing API keys and any phone number data in your systems. Do not expose credentials in client-side code.

9. Enforcement

NepalOTP monitors platform usage to ensure compliance with this policy. When violations are identified, we take appropriate action to protect the platform and its users.

Possible enforcement actions

1

Template deactivation

Specific templates that violate policy may be disabled.

2

Temporary suspension

API access may be suspended while a violation is investigated.

3

Account termination

Serious or repeated violations may result in permanent account termination.

Enforcement decisions are made to maintain platform reliability and protect the delivery infrastructure that all users depend on. We aim to communicate clearly about any issues and provide opportunity for resolution where appropriate.

10. Changes to This Policy

This Acceptable Use Policy may be updated as the NepalOTP platform evolves, as regulations change, or as we identify new requirements to maintain service quality.

We will indicate the date of the most recent update at the top of this page. Continued use of NepalOTP after policy updates constitutes acceptance of the revised terms.

For significant changes that affect your use of the platform, we will provide notice through your registered email or the developer dashboard.