terms of service

[ who provides the service ]

These terms are between you and Adams Array LLC d/b/a tnl ("tnl", "we", or "us"), an Arizona company. Our mailing address is 4500 South Lakeshore Drive, Suite 595, Tempe, AZ 85282, United States.

Contact hi@tnl.dev for support or legal@tnl.dev for legal notices.

These terms cover the tnl.dev hosted service, including accounts, public URLs, and related APIs. By creating an account or using the hosted service, you agree to these terms. Open-source software is licensed under its accompanying licenses; these terms do not replace those licenses or govern a separately operated self-hosted server. The privacy policy explains our data practices. The acceptable use policy forms part of these terms.

[ eligibility and accounts ]

The hosted service is for professional or business use, including use by sole traders and freelancers. You must be at least 18, able to enter a binding agreement, and authorized to act for any organization you represent. If you use the service for an organization, "you" includes that organization.

Keep account details accurate, protect your GitHub account and tnl credentials, and notify us promptly about unauthorized access. You are responsible for your use and for access you authorize. Team administrators are responsible for membership and permissions; removing a person from a team does not necessarily remove records needed by the rest of the team.

[ using public urls ]

tnl gives local applications public HTTPS URLs for development and preview work. You control the application, its content, access settings, and the people or systems allowed to visit it. You must have authority to use any application, domain, or data you publish.

Keep your application secure, choose suitable IP policies, and maintain your own copies of configuration and application data. A public hostname, HTTPS, or an IP allowlist is not a substitute for application authentication or your own security controls. DNS records and names in publicly trusted certificates can become public.

Follow the acceptable use policy and applicable law. The service is not designed to support sensitive or regulated-data workloads, such as health records, special-category personal data, or payment-card processing. Do not use it for activities that require safeguards or agreements we have not provided.

When you process personal data through an application, you are responsible for your lawful basis, notices, permissions, and instructions. A required data processing agreement must be in place before the relevant processing; these terms and the privacy policy are not a substitute for one. Contact privacy@tnl.dev about those requirements.

[ ownership and permissions ]

You retain ownership of your applications and content. You authorize us and our service providers to carry traffic, manage DNS and certificates, and process configuration and related data as necessary to provide, secure, and support the service. This permission does not grant ownership of your content or a right to use it for advertising or AI training.

We and our licensors retain rights in the hosted service and branding. Your use does not grant rights to tnl trademarks beyond identifying the service truthfully. Third-party and open-source components remain subject to their own terms.

[ free plans and usage ]

The hosted service is currently free. Teams have a soft allowance of 50 GiB of transfer per month across their public URLs, counting traffic in both directions. An allowance is not a reservation of network capacity.

Teams created during the free period, including the personal team created with an account, remain eligible for a usable free plan if paid options arrive, for as long as we operate the hosted service. This eligibility belongs to the team; an early account does not extend it to teams created after the free period.

Free-plan features and reasonable usage limits may evolve. We will provide advance notice of material reductions as described below. Free-plan eligibility does not excuse abuse or remove the suspension and termination provisions.

For ordinary usage above the soft allowance, we will contact you and give you a reasonable opportunity to reduce usage or discuss options before imposing usage restrictions. Urgent security, abuse, infrastructure-protection, or legal needs may require immediate action. We will explain that action when reasonably possible and legally permitted.

Exceeding an allowance does not create an automatic charge. A paid service requires an affirmative choice and disclosure of the applicable price and terms before purchase.

[ availability and support ]

The service may change, experience interruptions, or be unavailable because of maintenance, capacity, network conditions, or failures. We do not provide an uptime service-level agreement or a guaranteed support response time. Do not rely on it for safety-critical or uninterrupted operation.

To the extent permitted by law, the service is provided "as is" and "as available", without warranties of uninterrupted or error-free operation, merchantability, fitness for a particular purpose, or non-infringement. This does not exclude a warranty or obligation that applicable law does not allow us to exclude.

[ restrictions and termination ]

We may restrict or suspend a public URL, publisher connection, team, or account where reasonably necessary to address a breach of these terms, fraud, abuse, security risks, interference with the service, or a legal requirement. We aim to make the action proportionate to the issue. Serious or repeated violations may result in termination.

For a remediable, non-urgent breach, we will ordinarily explain the issue and give you a reasonable opportunity to correct it. Credible phishing, scams, malware, compromised credentials, or urgent legal obligations can require immediate action without prior notice. Notice may be limited where law prohibits it or where it would undermine security or an investigation.

Request review at abuse@tnl.dev, identifying the affected account or public URL and why you believe the action was mistaken. We will consider relevant information; a review does not guarantee restoration.

You may stop using the service at any time and request account closure at privacy@tnl.dev. Arrange any needed transfer of team administration first. Closure can stop public URLs and access. Information is handled as described in the privacy policy, rather than automatically erased when a tunnel stops.

[ liability ]

To the extent permitted by law, we are not liable for indirect, incidental, special, consequential, or punitive losses, including lost profits, lost business opportunities, or loss of goodwill arising from the service.

Our total aggregate liability arising out of or relating to the service or these terms is limited to the greater of USD 100 or the fees you paid us for the service in the 12 months preceding the event giving rise to the claim.

Neither the exclusions nor the cap applies to our fraud, willful misconduct, gross negligence, or any liability that applicable law does not permit us to exclude or limit. Nothing in these terms removes mandatory statutory rights, including applicable data-protection rights or remedies.

[ changes and service closure ]

We will ordinarily give at least 30 days' notice of materially adverse changes to these terms, material reductions in a free plan, or planned closure of the hosted service. We will use an account email or a prominent service notice appropriate to the change. Urgent security, abuse, or legal requirements, or circumstances that make advance notice impracticable, may require shorter notice; we will give as much notice as reasonably possible.

Changes will identify their effective date and will not retroactively change accrued claims. You may stop using the service if you do not accept a change. Where law requires affirmative agreement, we will obtain it rather than rely only on continued use. Free-plan eligibility does not require us to operate the service indefinitely.

[ law and disputes ]

Arizona law governs these terms, excluding its conflict-of-laws rules, except where mandatory applicable law requires otherwise. Subject to mandatory jurisdiction rules, disputes are to be brought in the appropriate state or federal courts in Maricopa County, Arizona, and the parties submit to those courts.

This provision does not restrict a person's right to complain to a data-protection authority or use another forum or remedy that mandatory law provides. Please contact legal@tnl.dev if you want to discuss a dispute.

If a provision is unenforceable, the remaining provisions continue to apply to the extent lawful. A delay in enforcing a term is not a waiver. Provisions that by their nature need to survive termination, including ownership, accrued obligations, liability limits, and dispute provisions, survive to that extent.