Terms

Use the platform responsibly, pay for what you enable, and do not turn the network against itself.

These terms describe the operating rules for access to Li9ht. They cover who can use the service, what customers are responsible for, how paid plans work, and the boundaries around misuse, abuse, and unlawful activity.

Updated March 29, 2026Public legal surfaceProduct-integrated trust

Access

Eligibility and account responsibility

You are responsible for maintaining the confidentiality of account credentials, controlling workspace access, and ensuring that authorized users act within your internal policies.

If you create accounts on behalf of a business, you represent that you have authority to bind that organization to these terms.

Acceptable use

What you cannot do with Li9ht

Do not use the service to break the law, attack other systems, interfere with network operations, or exfiltrate data without authorization. Do not attempt to bypass rate limits, abuse payment flows, or compromise the integrity of the platform.

If a workflow requires high-trust access, operator approval, or security review, do not automate around those gates or attempt to impersonate other users, workspaces, or services.

  • No malicious scanning, credential abuse, fraud, or unauthorized access attempts.
  • No resale, sublicensing, or misuse of the service outside the scope of your plan and agreement.
  • No reverse engineering or interference with platform integrity controls except where prohibited by law.

Commercials

Billing, renewals, and plan changes

Paid plans renew according to the billing cadence presented at purchase unless canceled in line with the applicable agreement. Taxes, provider fees, and other charges may apply depending on your region and purchasing channel.

If payment fails or your account falls materially out of compliance with billing obligations, Li9ht may suspend access to paid features until the issue is resolved.

Operations

Service changes and availability

Li9ht may update, improve, or retire parts of the service over time. We aim to avoid breaking core workflows without notice, but platform evolution is part of operating a live product.

Availability can be affected by maintenance, incidents, third-party failures, abuse mitigation, or customer environment issues. Public status communication belongs on the status surface, not hidden inside support threads.

Liability

Warranty and liability baseline

Except where the law does not allow it, the service is provided on an as-available basis without guarantees that it will be uninterrupted or error-free in every environment.

To the maximum extent permitted by law, Li9ht is not liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits, revenues, or data arising from use of the service.