tnl.dev :: legal
privacy policy
how tnl handles personal data, cookies, and privacy requests.
effective .
who operates tnl
Adams Array LLC d/b/a tnl operates tnl.dev and the hosted tnl service. Our mailing address is 4500 South Lakeshore Drive, Suite 595, Tempe, AZ 85282, United States. Contact privacy@tnl.dev about personal data or hi@tnl.dev for support.
This notice covers our website, accounts, hosted service, support, and CLI telemetry received by us. It also covers information about team invitees and visitors to hosted public URLs. A business-use account does not remove an individual's privacy rights.
We are the controller for personal data used to run accounts, secure the service, handle support, and understand service use: we decide why and how that data is used. When we process personal data on a customer's instructions to carry their application traffic, our role may instead be a processor. The customer is responsible for its application's privacy information and lawful processing. This notice is not a customer data processing agreement.
A self-hosted server has its own operator and data practices. CLI telemetry can still reach us when you use a self-hosted server unless you turn it off.
information we collect
| Information | Source and use |
|---|---|
| Account and authentication information | GitHub provides your account identifier, login, name, avatar, email, and email-verification information. We store authentication records, provider credentials, session information, IP addresses, user agents, and timestamps to sign you in and secure access. We do not receive your GitHub password. |
| Team, invitation, and domain information | You and other team members provide team names, roles, member slugs, invitation email addresses, and domains. We keep verification, membership, and invitation history to manage access and ownership. |
| Public URL information | Your client sends public hostnames, local targets, IP policies and allowed address ranges, and publish-run information. We use these to configure and operate the service. |
| Connection and usage information | The infrastructure processes source and destination addresses, requested hostnames, connection timing, traffic volume, failures, and usage measurements to carry traffic, enforce policy, troubleshoot, and manage capacity. |
| Website and CLI measurements | The systems below record page views, selected interactions, command events, and bounded technical information to understand and improve the product. |
| Communications and security records | We receive messages, attachments, abuse reports, and other information you or a reporter sends us. We also retain administrative and security events to support users, investigate problems, and protect the service. |
Account, authentication, and configuration information is needed to provide the associated features. If you do not provide it, you may be unable to sign in, join a team, claim a domain, or publish an application. Optional telemetry and marketing are not prerequisites for using the hosted service.
application traffic
During normal forwarding, visitor TLS passes through ingress and a relay and
ends at the local tnl process. HTTP paths, headers, bodies, and responses remain
encrypted in that path. Ingress and relays still process connection metadata,
including visitor addresses, the requested hostname, timing, and volume.
Usage reports contain counts, traffic measurements, and an approximate count of visitor networks. The network estimate uses a public-URL-specific secret that changes daily and a statistical sketch, rather than a list of source addresses. This does not mean the infrastructure never processes IP addresses.
Encryption does not remove every trust boundary. An operator controlling DNS and certificate issuance could impersonate an endpoint. Read the security explanation for the full boundary. Do not send secrets or sensitive application content in support or abuse reports.
website analytics and cli telemetry
Vercel Web Analytics measures visits to the homepage and documentation. Its browser requests are separate from the first-party interaction events below. These measurements run automatically when you use the relevant pages and features. See Vercel's analytics privacy information for its collection and processing details.
Our first-party website events record selected sign-in and quickstart clicks and installation-command copies. Those records contain an event category, page category, optional package-manager choice, and receipt time. The event table does not store an account identifier, IP address, or copied text. Hosting and security systems can separately process IP addresses and request metadata.
CLI telemetry records an installation identifier, invocation identifier, command and event, version, operating system, architecture, CI status, and sometimes a coarse framework or hosted/self-hosted classification. Failures use bounded stages and diagnostic codes, not raw error messages. These identifiers make the reports pseudonymous, not identifier-free.
Disable CLI telemetry with tnl telemetry off. This does not disable website
analytics or hosted-service usage records. See the
CLI reference for more controls.
cookies and browser storage
We use cookies to keep you signed in, protect your account, and remember documentation preferences. Your browser also stores account data and invitation information to support those features.
Sign-in cookies generally last up to seven days and may renew while you use the service. Documentation preferences can last a year. Local account data can remain until it is cleared. You can clear browser storage or block cookies through your browser settings, though some features may stop working. Website analytics is described above.
purposes and legal bases
Where the GDPR applies, we use the following bases for our own processing:
- Providing a contract: account access, publishing, and support where the individual is a party to the service contract and the processing is necessary to perform it or take requested steps before entering it.
- Legitimate interests: operating business customer accounts, coordinating teams and invitations, maintaining reliable infrastructure, preventing fraud and abuse, handling support, and understanding product use. We consider the effect on individuals and their rights; this basis does not replace consent where consent is required for a particular technology or communication.
- Legal obligations: responding to binding legal requirements and maintaining records that applicable law requires.
- Consent: optional processing or communications for which applicable law requires consent. Consent can be withdrawn without affecting earlier lawful use.
We use account and contact information for necessary service and security messages. We may use your email address to send occasional news, feature announcements, and offers about tnl, where permitted by applicable law. You can opt out at any time using the unsubscribe instructions in those emails or by contacting hi@tnl.dev. Opting out of promotional emails does not affect necessary account, security, or service messages.
We do not sell personal data, use it for advertising or cross-service tracking, or use account, support, or tunnel data to train AI models. We do not use profiling to make solely automated decisions with legal or similarly significant effects on individuals. Automated technical checks still enforce authentication, IP policies, and capacity limits.
who receives information
We use infrastructure, database, email, analytics, and status-page providers. Our providers page explains their roles. Providers may use their own service providers. GitHub and certificate authorities also process information for their own purposes under their policies.
Team information is shared according to team roles. Other members can see membership information, and people managing invitations can see invitation details, including recipient restrictions. Public DNS records and names in publicly trusted certificates can be visible outside your team; certificate transparency logs are public and are not erased by deleting a tnl account.
Within tnl, production and support-mail access is currently limited to the operator. Provider personnel may have access under their service arrangements. We may disclose relevant information to professional advisers or authorities where necessary to meet legal obligations, investigate abuse, or establish, exercise, or defend legal claims. Any transfer connected to a business sale or reorganization must remain subject to applicable data-protection requirements.
international processing
Adams Array LLC is based in the United States. The hosted application, databases, and tunnel infrastructure are configured to use US regions. Providers can also process information in other countries for delivery, support, and security. The service does not offer EU-only data residency.
Provider data-processing terms include contractual protections for covered transfers, such as standard contractual clauses. Contact privacy@tnl.dev for information about the safeguards applicable to your information and how to obtain a copy.
how long we keep information
| Record | Current cleanup target |
|---|---|
| Minute-resolution public URL usage | One day. |
| Hour-resolution public URL usage | 365 days. |
| CLI telemetry | 365 days. |
| First-party website interaction events | 365 days. |
Cleanup runs periodically in bounded batches, so these are targets rather than guaranteed deletion at an exact instant. These periods do not describe Vercel's analytics records or every infrastructure log and backup.
We keep account and configuration information while needed to provide the service. After closure, we remove information no longer needed, while retaining limited records where necessary for legal obligations, security investigations, or legal claims. Team membership, invitation, and domain history can remain relevant to other team members and ownership decisions. Support and abuse records are kept as needed to resolve the matter and handle related disputes. We assess retention using the record's purpose, sensitivity, legal requirements, and whether an investigation or claim remains open.
Our current routine database backup schedule retains backups for two days. Other operational records and copies needed for an investigation or legal obligation follow the retention criteria above. Signing out, revoking a session, or stopping a tunnel is not the same as deleting an account or all associated records.
your rights and account closure
Email privacy@tnl.dev to request access, correction, deletion, restriction, or portability of personal data, or to object to processing based on legitimate interests. Rights depend on the processing and applicable law. You may withdraw consent at any time, and may always object to direct marketing.
We handle requests and account closure manually. We may ask for proportionate information to verify your identity and protect other people on a team. We respond without undue delay and, where the GDPR applies, within one month. If complexity or the number of requests requires an extension of up to two further months, we explain the extension within the first month. Requests are normally free; any exception must be permitted by applicable law. If we cannot fulfill a request, we explain the reason and available remedies.
You can complain to a supervisory authority, including in the EU/EEA country where you live, work, or believe an infringement occurred. See the European Data Protection Board's authority directory. You do not have to contact us first, and you retain your right to a judicial remedy.
If your request concerns a customer's application, contact that customer too. Where we act as its processor, we assist or direct the request to that customer.
security and changes
We use access controls, protected authentication cookies, encrypted provider credentials, and authenticated service connections. No system can guarantee perfect security. Report vulnerabilities to security@tnl.dev and abuse to abuse@tnl.dev.
The service is for adult business users and is not directed to children. If you believe a child has provided account information, contact us so we can address it.
We will update this notice when practices change, identify its revision date, and provide appropriate notice of material changes before new processing where required. A changed notice does not replace consent when consent is required.