Terms of Service

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

These Terms of Service ("these Terms") govern the conditions of use of the self-commitment monitoring application "NoSurf" (product code: no-surf; "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 iOS's Network Extension (NEPacketTunnelProvider) to run a local VPN and detect — at the DNS query level — access attempts from the user's device to websites (domains) the user has registered in advance. The Service does not physically prevent browsing of registered domains; DNS responses are passed through unchanged, and at the moment of detection the Service displays a push notification and a full-screen alert to the user ("NoSurf is active. Stay disciplined."), supporting the user's own self-control.
2. The main features of the Service are as follows:
   1. Detection of access attempts (DNS queries) to registered domains
   2. A push notification at detection and, when the user taps through, a full-screen alert
   3. Charging under the charged-on-failure model for each registered URL (see Article 4)
   4. In-app display of the registered domain list and the current month's failure status
3. The Service is designed as a "device for calling upon the user's self-control" and does not coerce the user. Browsing a registered domain remains technically possible at all times. A clean exit path is always available.

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. The UUID is stored in the iOS Keychain; iCloud Keychain sync is not recommended.
3. Users may optionally set a nickname (1–20 characters), 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, loss, or complete deletion of the app (including the iOS Keychain), previously registered domains, history, and registered URL lists cannot be recovered (see Article 6). This is a deliberate design trade-off in exchange for anonymity, and users are informed of this during onboarding.
6. Important notification policy: Because the Service is designed not to collect email addresses, all important notices — including fee changes, cancellations, card expiry, payment failures, and Terms changes — are delivered exclusively via in-app banners and push notifications. No email notifications of any kind will be sent. Stripe receipt emails are also suppressed. Users acknowledge that they may miss important notices if the app is not opened for an extended period.

Article 4 — Fees and Payment

The Service operates on a two-tier structure: a charged-on-failure model for each registered URL (free in months you succeed; charged only in months with an access attempt, based on the sum of self-commitment amounts for each failed URL) and a Pro subscription that primarily unlocks the ability to register more than five URLs.

1. URL Limit and Pro Subscription
   1. The Service allows up to 5 URLs to be registered free of charge. Registering a 6th URL or beyond requires an active Pro subscription.
   2. The Pro subscription fee is ¥980 per month (Japan) or $10 per month (outside Japan).
   3. The Pro subscription renews automatically on a monthly basis via Stripe's subscription feature. Cancellation takes effect at the end of the current billing cycle.
   4. If the Pro subscription is cancelled, any registered URLs beyond the 5th will be deactivated (excluded from detection). They will be reactivated if the subscription is reinstated.
   5. The Service's reward mechanism is structured as "real-world commitment enforcement via the charged-on-failure model" and does not use App Store In-App Purchases (IAP).
2. Setting the Self-Commitment Amount
   1. When registering a URL, the user must select a self-commitment amount for that URL.
   2. Self-commitment amounts are selected from the following options: In US dollars (USD): $50, $100, $200, $300, $400, or $500. In Japanese yen (JPY): ¥5,000, ¥10,000, ¥20,000, ¥30,000, ¥40,000, or ¥50,000.
   3. The default self-commitment amount is $100 (or ¥10,000).
   4. In the first version of the Service, only US dollars (USD) and Japanese yen (JPY) are supported. The currency is automatically selected based on the device locale or the billing currency of the registered credit card.
3. Definition of "Failure" and Month-End Settlement
   1. A "failure" for a given URL in a given month is confirmed at the moment a DNS query for that URL occurs within the configured time window. The web page does not need to have finished loading in the browser.
   2. Multiple access attempts to the same URL 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 URL 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).
   5. We apply the sum of self-commitment amounts for failed URLs to cover operating costs for our escrow function.
4. Disputes
   1. Users may submit a dispute regarding a monthly failure flag at any time up to the 1st day of the following month.
   2. In v1.0, disputes are processed as automatic cancellations with a single tap. If abuse is observed, we reserve the right to restrict the dispute feature in the future (e.g., by introducing a No-Excuses mode).
5. Changing the Self-Commitment Amount, Time Window, and Registered URLs
   1. Increases to the self-commitment amount, extensions of the time window, and additions of new URLs take effect immediately.
   2. Decreases to the self-commitment amount, reductions of the time window, and deletion of registered URLs take effect at noon the following day (device local time). This delay exists to prevent impulsive changes.
6. 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, off-session) is executed against the stored card only if failures occurred during the month.
   4. Pro subscription payments are processed automatically on a monthly basis via Stripe's subscription feature.
7. Receipts and Invoices
   1. Because the Service is designed for personal use, we do not issue receipts or qualified invoices (see Article 8).
   2. Failure history and billing history can be viewed only through the in-app dashboard.

Article 5 — Cancellation, Withdrawal, and Uninstallation

Consistent with the Service's philosophy of respecting user self-control, a clean exit path is always available. The following methods are provided. In all cases, no charge will be incurred if there are no failures during the month.

1. Deletion of Individual Registered URLs
   1. Users may delete a registered URL from the settings screen. Deletion takes effect at noon the following day after the request is submitted (an asymmetric delay to prevent impulsive removal).
   2. During the period before deletion takes effect, the URL remains active for detection purposes; any access attempt during this period will trigger a failure flag and be subject to month-end billing.
2. Cancellation Flow
   1. Users may submit a cancellation request from within the app or via the web.
   2. Cancellation takes effect 7 days after the request is submitted. The detection feature remains active until the effective date, and any access 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, the month's failure flags are settled (charged if failures occurred, no charge if not), and the account, registered URLs, history, and Stripe Customer data are all deleted.
3. 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. After a set period following the cessation (approximately 3–5 days), the month's failure flags are settled, and the account, registered URLs, history, and Stripe Customer data are all deleted.
   3. Removal via this path is immediate and irreversible.
4. Pro Subscription Cancellation
   1. The Pro subscription may be cancelled independently, returning the user to free access for up to 5 URLs. This is governed by Article 4, Clause 1.

Article 6 — Device Changes and Lost Devices

1. The Service does not provide an account transfer feature. This is to preserve the anonymity design — which does not collect email addresses or passwords — and to ensure the effectiveness of the billing and cancellation mechanisms described in Articles 4 and 5.
2. In the event of a device change, damage, loss, or complete deletion of the app (including the iOS Keychain), the user must create a new account on the new device and re-register registered URLs and self-commitment amount settings.
3. The old device's account will be automatically deleted through either the cancellation flow or the uninstallation detection process. The month's failure flags are settled upon deletion, and no double-charging will occur.
4. For users planning a device change, the recommended approach is to first create a new account and re-register URLs on the new device, then initiate the cancellation flow on the old device.

Article 7 — Scope of Detection

1. The Service detects access to registered domains that route through the device's standard DNS resolution. Specifically, access attempts via Safari (including Private Browsing), SFSafariViewController (in-app Safari in third-party apps), and other browsers and apps that use the iOS standard DNS are subject to detection.
2. The following types of access are outside the scope of detection. We will not detect or charge for access made via these means:
   1. Access from a browser with DNS over HTTPS (DoH) or DNS over TLS (DoT) enabled (e.g., Brave, Firefox, or Chrome with the Secure DNS feature turned on)
   2. Access via anonymizing networks such as Tor
   3. Access using a VPN other than the Service (multi-layered VPN)
   4. Viewing content of a registered domain within a native app (e.g., X/Instagram/Facebook or news apps) — because it is technically impossible at the DNS level to distinguish background network traffic from active browsing within a native app, such access is excluded from detection
   5. Access from a device other than the user's own (public Wi-Fi, another person's device, etc.)
3. The Service does not guarantee complete detection of all access to registered domains. We accept no liability for any consequences arising from access made via the out-of-scope means described above.

Article 8 — Personal Use Restriction

1. The Service is designed exclusively for personal use. Use by corporations or organizations, use for business purposes, use for expense reimbursement purposes, and management of multiple accounts 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 (a corporate plan is under consideration for v1.x and later).

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 domain or third-party social media profile 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 confirmation of a failure flag, month-end settlement, or payment processing 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 the iOS local VPN (NEPacketTunnelProvider) and DNS query observation, the following limitations exist:
   1. If the user disables the VPN profile from the OS Settings, the Service's detection feature will cease to function.
   2. Access via the out-of-scope means listed in Article 7, Clause 2 cannot be detected by the Service.
   3. Detection operates at the domain level. Detection of a specific path — such as "only a specific user's profile on a specific social network" — is outside the scope of the Service's functionality.
   4. Background network traffic from advertising SDKs, WebViews, or similar may trigger a DNS query to a registered domain, causing a false positive. Because the per-month, per-URL cap prevents overcharging, the financial impact is limited to a single self-commitment amount; false positives may be cancelled via the dispute feature.
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 via in-app notification.
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 URLs, 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)