Clear operating terms for SmartRoute DNS.

These Terms describe the basic rules for accessing DiBelok.In, maintaining an account, and using SmartRoute DNS responsibly during this early product phase.

Using the service

DiBelok.In provides SmartRoute DNS as a hosted software service. You may use the service only in accordance with applicable law, these Terms, and any plan or account limits presented during signup or billing.

Accounts and responsibility

You are responsible for maintaining the confidentiality of your login credentials and for the activity that occurs under your account. Please provide accurate information and notify us promptly if you believe your account has been accessed without authorization.

Billing and subscriptions

Paid plans renew according to the billing cycle you choose unless you cancel before the next renewal date. Fees are generally non-refundable except where required by law or explicitly stated in a separate written agreement.

Acceptable use

You may not use the service to violate laws, interfere with network operations, abuse third-party systems, or attempt to disrupt the reliability or security of the platform. We may suspend or terminate access if usage creates risk for the service, other customers, or our providers.

Availability and changes

We work to keep SmartRoute DNS available and useful, but the service may change over time. We may update features, pricing, infrastructure, or policies as the product evolves, and we may suspend access for maintenance, operational, or legal reasons when necessary.

Limitation of liability

To the maximum extent permitted by law, DiBelok.In is not liable for indirect, incidental, special, consequential, or punitive damages arising from your use of the service. Our total liability for claims related to the service will not exceed the amount you paid us for the applicable subscription period giving rise to the claim.

Questions about these terms

If you have questions about commercial use, billing, or account access, please contact DiBelok.In before relying on the service for a specific operational requirement.

Effective date: April 13, 2026