acceptable use

[ use tnl responsibly ]

This policy applies to the tnl.dev hosted service provided by Adams Array LLC d/b/a tnl and forms part of the terms of service. It covers accounts, teams, domains, public URLs, and activity carried through the service.

Use the service only for lawful activity that you are authorized to perform. You are responsible for your applications, content, domain rights, and access you grant. An encrypted connection or tnl hostname does not imply that we endorse an application or its claims.

[ prohibited activity ]

Do not use the service to:

• Run scams, commit fraud, or mislead people into providing money, credentials, personal information, or access to their systems.
• Publish phishing pages or impersonate a person, organization, login screen, support service, or brand to deceive visitors.
• Steal credentials, distribute malware, operate malicious command-and-control infrastructure, or deliver exploits without authorization.
• Access, scan, test, or interfere with systems without permission; conduct denial-of-service attacks; or facilitate unauthorized intrusion or data theft.
• Send unsolicited bulk messages, operate deceptive redirects, or distribute unlawful content, including child sexual abuse material.
• Infringe intellectual-property, privacy, or other legal rights; disclose stolen data; or facilitate harassment, threats, or exploitation.
• Circumvent security controls, account restrictions, or usage limits, including by creating replacement accounts or teams to evade enforcement.
• Consume resources in a way that materially disrupts other users or the infrastructure, or resell access to facilitate prohibited activity.

Legitimate testing still requires authorization from the system owner and must stay within that authorization. Permission from a customer does not authorize attacks against tnl or other customers. Report tnl vulnerabilities to security@tnl.dev; do not access other people's data, persist in their systems, or disrupt service while investigating.

[ protect your application ]

Secure the local service you publish, protect your credentials, and configure appropriate access controls. Do not deliberately expose production secrets or private administrative interfaces to unauthorized visitors. If an account or application is compromised, stop the affected publication, revoke compromised credentials, and contact us promptly.

The hosted service is intended for development and preview work. It is not designed for sensitive or regulated-data workloads requiring special safeguards or agreements that we have not provided. See the terms.

[ report abuse ]

Send reports to abuse@tnl.dev. Include:

• The public URL or hostname and any relevant path.
• What happened and why you believe it is abusive or unlawful.
• The approximate time and time zone.
• Relevant screenshots or other evidence, and a way to contact you if we need clarification.

Send only what is needed to explain the report. Remove passwords, access tokens, payment information, and unrelated personal data. Do not send illegal material itself; describe it and identify its location. For a legal notice, use legal@tnl.dev.

We use report information to investigate, respond, and protect the service as described in the privacy policy. We may need to share relevant details with the affected customer, a provider, an adviser, or an authority where appropriate and lawful. We cannot promise confidentiality in every circumstance.

[ how we respond ]

We may investigate reports and act on other credible information about abuse. Depending on the circumstances, we may request information, require remediation, restrict traffic, disable public URLs, suspend accounts or teams, or terminate service. We may retain relevant records or respond to lawful requests where necessary and permitted by law.

We aim to make restrictions proportionate to the issue. Ordinary usage above a soft allowance receives notice and an opportunity to resolve it under the terms. Credible scams, phishing, malware, compromised access, or urgent security or legal needs can require immediate action without prior notice. We explain restrictions when reasonably possible, unless prohibited by law or doing so would undermine security or an investigation.

Normal forwarding does not decrypt visitor HTTP content at ingress or relays. This policy does not mean that we routinely inspect encrypted content or review every application. Reports and other available information can still lead to enforcement. We do not guarantee a response time or a particular outcome.

[ request review ]

If you believe a restriction was mistaken, email abuse@tnl.dev with the affected account or public URL, the notice you received, and relevant context or remediation. We will consider the information and explain the outcome where reasonably possible. Do not evade a restriction while review is pending. This process does not limit remedies available under applicable law.