NEXI SMS Bot Terms v1.2

Effective Date: February 17, 2026 (KST) | Last Updated: February 17, 2026

Article 1 (Purpose and Scope)

These Terms of Service ("Terms") govern the conditions of use, billing rules, rights and obligations, and liabilities for the paid digital SMS verification service provided by NEXI SMS Bot ("Service") on Discord.

These Terms apply specifically to the SMS bot service. If any conflict exists with other bot/site terms, these Terms prevail for SMS-related matters.

The interpretation priority among related documents is (1) these Terms, (2) notices on payment/service screens, and (3) operational policy documents; applicable mandatory law prevails where required.

Article 2 (Definitions)

The terms used herein have the following meanings:

• User: An individual or entity using the Service
• Server (Guild): The Discord guild unit that uses the Service
• Credit: Paid usage unit consumed for Discord/Gmail/Microsoft issuance
• Others (uses): Usage model for non-Discord/Gmail/Microsoft platforms, managed as server-specific uses (service code ot, country code 16)
• Automatic Recovery (20 minutes): Policy restoring deducted usage when number issuance fails or code is not received within 20 minutes, based on original SMS API status
• Manual Deposit Verification: Manual top-up process after operator verifies bank transfer payment
• Server-bound / Non-transferable: Credits and uses belong to the specific server and cannot be transferred, assigned, or merged across servers (feature not provided)
• Platform Auto-Disable (Protection): Temporary automatic suspension of issuance on a platform when API errors accumulate
• Order ID: Identifier used for request tracking under server-level policy

Article 3 (Formation of Agreement and Eligibility)

1. The service agreement is formed when a user adds the bot and accepts these Terms.
2. Use may be restricted based on Discord policy, including age/account restrictions.
3. Users must provide accurate information. False information or impersonation may result in termination.

Article 4 (Paid Service, Billing, and Top-Up)

4.1 Paid Service Principle

SMS verification is a paid digital service. Use is unavailable without sufficient credits or active uses.

4.2 Platform Billing Rules

• Discord / Gmail / Microsoft: 1 successful number issuance = 1 credit deduction
• Others: No regular guild credit deduction; only server-specific uses are deducted/restored

For Others, one use is deducted only after successful number issuance through the standard /setup flow, and Others is disabled for that guild when remaining uses reach zero.

Detailed thresholds and exceptions for Others may be defined in operational policy documents or notices.

4.3 Server-bound Allocation and Transfer Restriction

Credits and uses are bound to the specific server. The Service does not support transfer, assignment, collateralization, merge, or cash-out across servers.

4.4 Payment Method and Manual Top-Up

1. Payment is made via bank transfer to the account announced in the support server.
2. Top-up is processed manually after operator verification, typically within one business day.
3. Processing may be delayed due to the following reasons (examples): bank maintenance, depositor mismatch/unidentifiable transfer, high request volume, internal maintenance, or force majeure.
4. If delay is expected or occurs, the Service may provide status guidance through notice channels, DM, or support responses.

4.5 Status of Order IDs

Order ID policy (format, issuance, usage permissions) is determined by each server administrator. The Service is not the contracting party to each server's own payment policy or transactions.

Order IDs are management identifiers for request tracking and may not be recognized as definitive proof of payment completion or payment amount in individual disputes.

The Service may process order IDs only for request identification, error handling, and security/audit purposes.

Article 5 (Service Provision and Operations)

5.1 Supported Platforms

The Service supports Discord, Gmail, Microsoft, and Others platforms.

Others is operated as disabled-by-default and can be enabled only through administrator-level procedures (e.g., /admin others or other operator-announced activation procedures).

Others may be exposed only in the standard /setup panel and may be excluded from admin instant-issuance panels.

5.2 Administrative Features

The Service may provide operational commands including /admin lookup, /admin reset, /admin export, /admin integrity, /admin health, /admin diagnose, /admin maintenance, /admin blocklist, /admin unblock, /admin others, and related controls.

5.3 Platform Protection

If API failures accumulate or abnormal states are detected, the Service may automatically disable issuance on the affected platform for stability protection.

Article 6 (Automatic Recovery Policy)

6.1 Common Recovery Standard

1. Deductions are recoverable when number issuance fails.
2. Deductions are recoverable when verification code does not arrive within 20 minutes after issuance.
3. "Original API basis" means the original SMS API status values, request/response timeline, and operator verification logs.
4. No recovery applies where normal issuance and normal code arrival are confirmed under the above basis.

6.2 Others (uses) Recovery Triggers

For Others, one use is restored when timeout, STATUS_CANCEL, or set_status_ready failure occurs.

When Others is disabled, the Service may provide administrator-contact guidance to general users and activation guidance to server administrators.

6.3 Abuse Prevention and Restriction Criteria

If induced failures, abusive automation, or abnormal traffic is suspected, the Service may hold recovery or restrict use based on reasonable indicators (examples) including:

• Multiple repeated failures in a short period for the same user/order/server (e.g., 3 or more within 24 hours, including timeout/STATUS_CANCEL/set_status_ready failure)
• Automation-like access, excessive repeated calls, or circumvention attempts
• Blocklist evasion or abnormal cross-use patterns across accounts/orders/servers

Where needed, the Service may apply measures without prior notice, including recovery hold (up to 72 hours), temporary restriction, or permanent restriction. Users may submit explanatory materials and request reconsideration.

6.4 Record Retention and Objection Process

1. Evidence records for recovery decisions (API statuses, processing timeline, operator verification logs) may be retained for at least 90 days.
2. Users may file an objection within 7 days from notice of a recovery decision and must provide at least verifiable identifiers such as server ID, order ID (if any), and request timestamp.
3. The Service aims to provide a first response within 7 business days from receipt; where additional verification is required, reasons and expected schedule may be notified.
4. The Service may reject objections where evidence is insufficient or abuse indicators are confirmed.

Article 7 (Refund and Cancellation)

7.1 Principle

To the extent permitted by applicable law, purchased credits and uses are non-refundable by default.

Where mandatory law grants refund or withdrawal rights, such law prevails.

7.2 Exceptions

Only the following cases may qualify for exceptional refund/adjustment, to the extent permitted by applicable law:

• Where refund is legally required
• Where a material operator fault is proven (e.g., duplicate charge, obvious mischarge)

7.3 Commencement of Use

"Commencement of use" under these Terms means the point when a user's first issuance request results in an actual credit deduction or Others uses deduction.

7.4 Withdrawal Restriction for Digital Service

1. Credits and uses are digital usage entitlements intended for immediate use.
2. By completing payment/top-up, users agree to immediate supply commencement, and withdrawal may be restricted after commencement of use.
3. To the extent permitted by applicable law, even where statutory withdrawal applies, used quantity, restored/adjusted quantity, and free/promotional grants may be excluded from settlement.

7.5 Request Procedure (Minimal)

1. Exception requests must be submitted with evidence within 14 days from awareness of the cause.
2. Required materials are minimized in principle and limited to payment date/time, depositor name, server ID, refund reason, and verifiable records.
3. The Service may request additional materials only to the minimum extent necessary for verification.
4. If approved, settlement method and schedule will be provided individually.

7.6 Non-Refundable Exclusions

To the extent permitted by applicable law, the following are excluded from refund eligibility:

• Free grants, event/promotional bonuses, and discretionary administrative adjustments
• Balances on accounts/servers restricted for Terms or policy violations
• Internal transaction disputes under each server administrator's own policy

Article 8 (User Obligations and Prohibited Conduct)

• No spam, raid, illegal activity, or rights infringement using the Service/API
• No intentional failure induction or abuse of recovery rules
• No impersonation, malicious false reports, or payment identity misuse
• Compliance with Discord policies, applicable laws, and these Terms

Article 9 (Logs, Security, and Data Processing)

9.1 Logging Framework

• Guild log channels (server-configured): admin command logs, security events, restart notices
• Global log channels: partitioned logs for bot, run.sh, web
• Local logs: application logs and logs/audit.log

9.2 Storage Principle

The Service may process necessary metadata for operations, audits, and security; however, message raw content is not stored.

9.3 Blocklist Management

The Service may operate user restriction/unblock policies using user_blocks to prevent abuse.

Article 10 (Restrictions, Suspension, and Termination)

10.1 Restrictions

1. Use may be restricted for Terms violations, security threats, legal requests, or urgent operational reasons.
2. Restrictions may include warning, temporary suspension, or permanent ban; serious cases may be permanently restricted immediately.
3. Users may submit explanations within 14 days from notice.

10.2 Service Suspension/Termination and Remaining Balance

1. The Service may suspend or terminate all or part of features for operational reasons and, where feasible, will provide at least 14 days prior notice.
2. To the extent permitted by applicable law, settlement at termination is limited to objectively verifiable unused paid credits.
3. Free grants, event/promotional grants, and balances on restricted accounts/servers may be excluded from settlement.
4. Termination-related settlement must be requested within a separately announced period or within 30 days from termination date; late requests may be limited.
5. Settlement method (e.g., bank refund) and schedule will be determined by termination notice or individual guidance.

Article 11 (Limitation of Liability)

11.1 Functional Distinction

Free informational features and paid SMS issuance differ in nature. Paid-feature consideration and liability scope are governed by this Article.

11.2 Disclaimer and Exceptions

To the extent permitted by applicable law, limitations in this Article do not apply to damages caused by intent or gross negligence, damages to life or bodily injury, or other losses that cannot be limited/excluded by law.

To the extent permitted by applicable law, liability may be limited for force majeure, external API failures, and user-attributable causes.

To the extent permitted by applicable law, special, indirect, incidental, punitive, business-interruption, and loss-of-profit damages are excluded from compensation scope.

11.3 Liability Cap

To the extent permitted by applicable law, the aggregate liability cap is the total actual payments made by the relevant server in the six months immediately preceding the incident.

To the extent permitted by applicable law, this cap applies and may be adjusted by mandatory law, special statutory liability including personal-information law, intent/gross negligence, or final court determination.

11.4 Claim Period and Duty to Mitigate

To the extent permitted by applicable law, users must provide written notice within 3 months from knowledge of damage and file claims within 1 year from occurrence.

Users must take reasonable steps to mitigate damage; avoidable expanded damages may be excluded from compensation.

Article 12 (Intellectual Property)

Rights to service code, architecture, marks, UI, and operational logic belong to the operator or legitimate rights holders. Users shall not copy, distribute, or reverse-engineer beyond permitted service use.

Article 13 (Notices and Amendments)

1. Notices may be made through website announcements, Discord support server, DM, or email.
2. General changes to Terms or operational policy will be announced at least 7 days before effectiveness.
3. Material user-disadvantageous changes (including price increase or unfavorable changes to deduction/recovery/refund rules) will, where feasible, be announced at least 14 days before effectiveness.
4. For urgent legal/security needs, immediate application without prior notice is allowed, with prompt post-notice.
5. Continued use after the effective date of changes is deemed acceptance of revised Terms. Users who do not agree may discontinue use.

Article 14 (Governing Law and Jurisdiction)

These Terms are governed by the laws of the Republic of Korea. Parties shall first attempt good-faith consultation for disputes.

Where users are non-consumers, or to the extent permitted by applicable law, the Seoul Central District Court shall be the court of first instance. Where users are consumers, jurisdiction follows applicable civil-procedure and consumer-protection laws.

Article 15 (Supplementary Provisions)

1. Version 1.2 takes effect on February 17, 2026 (KST).
2. Users who continue to use the Service after the effective date are deemed to have accepted these Terms.
3. If interpretation conflicts arise between Korean and English texts, the Korean version prevails.

v1.2 Change History

• Reorganized non-refundable and withdrawal-restriction clauses with legal-priority structure and clear definition of "commencement of use"
• Simplified exception refund/settlement process around minimal required materials while keeping 14-day request window
• Clarified "original API basis" for 20-minute automatic recovery using status values, request/response timeline, and operator verification logs
• Maintained 7-day objection window and added first-response target within 7 business days
• Toned down abuse restriction triggers as examples and added explanation/reconsideration path while keeping up to 72-hour hold framework
• Refined termination settlement clause for unused paid credits with 30-day request window and individually guided settlement method
• Stabilized liability clause by placing intent/gross negligence and life/bodily injury carve-outs first and adding legal-limit qualifiers
• Added delay-notice channel for manual top-up SLA and clarified that order IDs may not serve as definitive payment proof