Terms of Service

Last updated: 2026-06-11 / Established by XTV LLC

These Terms of Service ("these Terms") govern the conditions of use of the outgoing-call blocking application "NoDial" ("the Service") provided by XTV LLC ("we" or "the Company"). By using the Service, you are deemed to have agreed to all provisions of these Terms.

Article 1 — Scope of Application

1. These Terms apply to all matters relating to the use of the Service between us and the user.
2. If you do not agree to these Terms, you may not use the Service.
3. Any individual rules, guidelines, or other policies posted by us in connection with the Service ("Supplemental Rules") shall form part of these Terms. In the event of any conflict between these Terms and Supplemental Rules, the Supplemental Rules shall prevail.

Article 2 — Service Description

1. The Service is an application that uses Android OS's Telecom Framework to technically block outgoing calls to phone numbers that the user registers in advance.
2. The main features of the Service are as follows:
   1. Blocking of outgoing calls to registered numbers (via CallRedirectionService.cancelCall)
   2. A billing model in which you are charged only in a month you attempt a call (see Article 4)
   3. In-app display of the call attempt history for registered numbers
3. The Service is designed as a "tool that respects the user's willpower" and does not coerce the user.

Article 3 — Account and Authentication

1. To use the Service, users must install the Service's application on their device and create an account.
2. We do not collect personal information such as email addresses, passwords, names, phone numbers, or home addresses when creating an account. The account identifier is a unique identifier (UUID) generated on the user's device.
3. Users may optionally set a nickname, which is used for display purposes only.
4. Possession of a device on which the Service application is installed shall be deemed sufficient evidence of identity. We may treat any operations performed from that device as operations by the account holder.
5. The Service does not provide an account transfer feature. If access to an account is lost due to a device change, damage, or loss, previously registered numbers, history, and other data cannot be recovered (see Article 6).

Article 4 — Fees and Payment

The Service operates on a billing model in which you are charged only in a month you attempt a call (no charge in months with no attempts; a charge applies only in months when an attempt occurs).

1. Setting the Self-Commitment Amount
   1. When registering a phone number to block, the user must select a self-commitment amount for that number.
   2. Self-commitment amounts are selected from the following options: In Japanese yen (JPY): ¥10,000, ¥20,000, ¥30,000, ¥40,000, ¥50,000, or ¥100,000. In US dollars (USD): $100, $200, $300, $400, $500, or $1,000.
   3. The default self-commitment amount is ¥10,000 (or $100 USD).
   4. In the first version of the Service, only Japanese yen (JPY) and US dollars (USD) are supported. The currency is automatically selected based on the device locale or the billing currency of the registered credit card.
2. Definition of "Failure" and Month-End Settlement
   1. A "failure" for a given number in a given month is confirmed at the moment a call attempt to a registered number triggers the CallRedirectionService.onPlaceCall function. An actual connected call is not required.
   2. Multiple call attempts to the same number within the same month are settled as a single self-commitment amount (there is no uncapped accumulation).
   3. At month-end settlement, the total of the self-commitment amounts for each number that incurred a failure during the month is charged to the user's credit card.
   4. If there are no failures in a given month, no charge is made (the amount billed is zero).
3. Changing the Self-Commitment Amount
   1. Increases to the self-commitment amount take effect immediately.
   2. Decreases to the self-commitment amount take effect at month-end. If a call attempt to the relevant number occurs during the month while a decrease request is pending, the settlement will be calculated using the amount in effect before the change.
4. Payment Method
   1. The only accepted payment method is credit card payment processed via Stripe, Inc.
   2. At account registration, only card authorization and storage are performed (Stripe SetupIntent); no amount is charged at this stage.
   3. At month-end settlement, an actual charge (Stripe PaymentIntent) is executed against the stored card only if failures occurred during the month.
5. Receipts and Invoices
   1. Because the Service is designed for personal use, we do not issue receipts or qualified invoices (see Article 8).
   2. Billing history can be viewed only through the in-app dashboard.

Article 5 — Cancellation, Withdrawal, and Uninstallation

The Service does not provide a UI for deleting registered numbers within the app. Registered numbers cannot be removed from within the app; only the following two methods are available for removal. In either case, no charge will be incurred if there are no failures during the month.

1. Cancellation Flow (standard path)
   1. Users may submit a cancellation request from within the app or via the web.
   2. Cancellation takes effect at the end of the month in which the request is made. The blocking feature remains active until the effective date, and any call attempts during this period are counted as "failures" as normal.
   3. Users may cancel their cancellation request while it is still pending before the effective date.
   4. At the effective date, if failures occurred during the month, the total of the self-commitment amounts for those numbers will be charged; if there were no failures, no charge is made. Simultaneously with the effective date, the account, registered numbers, history, and Stripe Customer data are all deleted.
2. Uninstallation (emergency path)
   1. If the user deletes the Service application from their device, our server will detect the cessation of the periodic heartbeat signal from the application.
   2. Two days after the heartbeat ceases, a warning notification will be sent via Firebase Cloud Messaging.
   3. If there is no response for three days after the warning notification (five days total from the cessation of heartbeat), the uninstallation is confirmed. The month's settlement is executed (charge if failures occurred, no charge if not), and the account, registered numbers, history, and Stripe Customer data are all deleted.
   4. Removal via this path is immediate and irreversible.

Article 6 — Device Changes and Lost Devices

1. The Service does not provide an account transfer feature. This is because providing a transfer feature would undermine the effectiveness of the billing and removal mechanisms described in Articles 4 and 5.
2. In the event of a device change, damage, or loss, the user must create a new account on the new device and re-register the numbers to block.
3. The old device's account will be automatically deleted either through the cancellation flow or by the 5-day uninstallation detection process. The month's settlement will be executed upon deletion.
4. For users planning a device change, the recommended approach is to first create a new account and re-register numbers on the new device, then initiate the cancellation flow on the old device.

Article 7 — Emergency Numbers

1. The Service is designed so that major emergency numbers in various countries — including 110, 119, 118, 911, 112, and 999 — cannot be registered by the user and, even if somehow registered, are automatically excluded from blocking.
2. In the unlikely event that an emergency call is blocked by the Service, we accept no liability whatsoever for any damage arising from such an event.
3. Users should use alternative means of communication (public phones, another person's device, etc.) in emergencies and must not rely solely on the Service.

Article 8 — Personal Use Restriction

1. The Service is designed exclusively for personal use. Use by corporations or organizations, use for business purposes, and use for expense reimbursement purposes are outside the intended scope of the Service.
2. We do not issue receipts, qualified invoices, or invoices of any kind.
3. If you wish to use the Service on a corporate basis, please contact us separately.

Article 9 — Prohibited Conduct

Users must not engage in any of the following conduct when using the Service:

1. Any act that violates laws, these Terms, or public order and morals
2. Any act that infringes the rights of other users, third parties, or the Company
3. Registering a third party's phone number for the purpose of harassment, stalking, or any other improper purpose
4. Any act that damages the reputation, honor, or brand of the Company
5. Reverse engineering, modifying, copying, or redistributing the Service
6. Exploiting vulnerabilities in the Service
7. Evading payment through unauthorized means
8. Any other conduct that the Company deems inappropriate

Article 10 — Intellectual Property Rights

1. All intellectual property rights in the content, software, trademarks, logos, and other materials displayed in connection with the Service belong to us or to third parties who have licensed such rights to us.
2. Users must not infringe these intellectual property rights when using the Service.

Article 11 — Disclaimer and Scope of Warranty

1. We make no warranty of any kind regarding the completeness, accuracy, usefulness, or fitness for a particular purpose of the Service.
2. Because the Service operates via Android's telephony control API (Telecom Framework), the following limitations exist:
   1. Customizations by device OEMs or battery optimization settings may prevent the Service from launching or limit its functionality.
   2. Internet-based calls such as LINE calls and WhatsApp calls are not covered.
   3. Calls made from a different device, a public phone, or another person's device cannot be blocked.
   4. The Service normalizes numbers to E.164 format where possible to handle variations such as withholding caller ID or formatting differences (e.g., +81 format vs. leading-zero format), but cannot guarantee complete matching in all cases.
3. We accept no liability for any damage arising from the limitations described above or from the use or inability to use the Service.
4. Our liability shall in no event exceed the total amount paid by the user to us during the 12 months immediately preceding the event giving rise to the liability.

Article 12 — Service Changes and Termination

1. We may change the content of the Service or discontinue providing it, provided that we give users advance notice.
2. If we discontinue the Service, we will notify users before the termination date, execute the month's settlement on the termination date, and then delete all user accounts, registered numbers, history, and related data.

Article 13 — Changes to These Terms

1. We may amend these Terms.
2. When amendments are made, we will notify users of the content and effective date through in-app notifications. For changes to fundamental matters such as the billing structure or methods of withdrawal, we will obtain renewed consent from users.

Article 14 — Mail-Order Sales and Right of Withdrawal

1. The Service constitutes mail-order sales as defined under the Act on Specified Commercial Transactions (Japan).
2. Because use of the Service begins immediately upon completion of registration, the Service is not subject to the statutory right of withdrawal (cooling-off period).
3. Withdrawal from and cancellation of the Service shall be effected through the cancellation flow or uninstallation, and the method and effect thereof shall be governed by Article 5.

Article 15 — Minors

1. If a user is a minor (under 18 years of age), the use of the Service requires the consent of a parent or legal guardian.
2. If it becomes apparent that a minor has used the Service without the consent of a parent or legal guardian, we may accept a request for cancellation of the contract from the minor or the parent or legal guardian.

Article 16 — Governing Law and Jurisdiction

1. These Terms are governed by the laws of Japan.
2. All disputes arising from or in connection with the Service or these Terms shall be subject to the exclusive jurisdiction of the Tokyo District Court as the court of first instance.

Article 17 — Company Information / Disclosure under the Act on Specified Commercial Transactions (Japan)