01Who this policy covers
trqsh is a tunneling project created and maintained by Otabek Hamroqulov. This policy describes the trqsh website, hosted Control API, dashboard, and the trqsh CLI and desktop app when connected to the hosted service. Contact hello@trqsh.uz about this policy.
If you connect to a self-hosted installation, its operator controls the server-side data and infrastructure. Ask that operator for its privacy terms. Websites and services published through a tunnel have their own operators and privacy practices.
02Information we process
| Information | What it includes and why |
|---|---|
| Account and profile | Email address, display name, avatar URL, sign-in provider, account identifier, and creation date. These identify your account and display your profile. |
| Workspace and access | Organization membership and roles; API-key name, identifier, prefix, hash, creation, last-use and revocation records; reserved subdomains and custom-domain verification records. |
| Tunnel and usage history | Public address, tunnel type and identifier, edge/region, connection start and end times, status, transferred bytes, and request counts. These power history, usage views, and plan limits. |
| Connection information | The agent’s public IP address and, when location resolution is configured, approximate country or city. Servers and network proxies also process connection data to route requests and control abuse. |
| Plan and support records | Your plan, activation or expiry details, and the information you send us when requesting an upgrade, support, or a privacy action. An installation using optional Stripe billing also keeps billing customer and subscription identifiers, status, and usage records. |
We use these records to authenticate accounts, authorize tunnels, enforce quotas, troubleshoot faults, and respond to misuse. You can browse the public documentation without creating an account; operating hosted tunnels requires credentials.
03Tunnel traffic and local captures
For normal HTTP tunnels, public HTTPS ends at the edge, which handles the request before forwarding it to the agent over encrypted transport. This is not end-to-end encryption between the visitor and your local app. The ordinary local HTTP destination is reached over plain HTTP; an application carried through a raw TCP tunnel can provide its own encryption.
The local HTTP inspector records request and response headers, paths, timing, status, and bounded bodies. The standard agent holds up to 256 exchanges in memory, with up to 64 KiB per request body and per response body. Captures can include cookies, authorization headers, and private payloads.
Older captures are replaced when the buffer fills. Clearing the recorder or stopping its agent removes those in-memory captures. Turning off the inspector’s browser listener does not turn off the core recorder. Normal local inspection does not automatically upload these bodies to a cloud capture archive; the dashboard’s cloud-inspector integration is not currently implemented.
Usage counters and tunnel history are separate from capture bodies. Network proxies and your exposed app can process or log requests under their own configuration. Read the inspector guide and security guide for the boundaries.
04Local configuration and logs
The CLI saves configuration, saved tunnel definitions, and its working API key on your computer, normally in ~/.trqsh/trqsh.yml. Runtime files can include the local control token and daemon.log. These files are separate from the in-memory HTTP capture buffer and can remain after the agent stops.
Protect this directory and review logs before sharing them. Client removal and local-data removal are separate operations; the installation guide explains /uninstall yes and package-manager removal. Neither action deletes your hosted account. See Installation and Configuration.
05QR remote-control sessions
Using /qr sends recent console transcript lines and a tunnel-state snapshot through the hosted relay to paired viewers. The relay retains up to 200 recent lines and the last state snapshot in the API process. Pairings expire after 30 minutes and do not survive an API restart; you can end a pairing with /qr stop.
Anyone holding an active pairing link or code can view the shared information and issue allowed console commands without a separate viewer login. Treat that link like a temporary credential. See QR remote control.
06Other services involved
If you choose a configured GitHub or Google sign-in option, that provider handles your sign-in and returns profile information to trqsh. Its privacy policy also applies. The website’s upgrade flow sends you to Telegram; Telegram processes messages you choose to send there.
The backend supports optional Stripe billing. If that integration is enabled for your installation and you use it, payment details are entered on Stripe’s hosted pages; trqsh receives the billing identifiers and subscription information needed to manage the plan. The current public website’s upgrade flow is manual rather than a card checkout.
Hosting, database, DNS, and network-proxy operators can process the information needed to deliver their part of the service. A deployment using Cloudflare routes requests through Cloudflare. If an external IP-location lookup is enabled, the configured provider receives the public IP being resolved; the code also supports location from a trusted proxy header without that external lookup.
Provider choices and physical storage locations depend on the deployment. Contact hello@trqsh.uz for current hosting and processing-location details, including before sending data that must remain in a particular country. The service does not promise a specific data-residency region.
Information may also need to be disclosed to comply with applicable law or investigate abuse. Public issues and release discussions are visible to others; use email for personal account information.
07Cookies, browser storage, and retention
The dashboard uses authentication cookies, and sign-in can use short-lived security cookies. The public website saves your chosen light or dark theme in local storage. The website source does not embed advertising or third-party analytics scripts. See Cookies & storage for details and controls.
Account, domain, tunnel-history, and usage records persist in server storage. There is no published fixed deletion schedule for those records, and the current product does not automatically erase an account when you sign out or uninstall the client. We assess deletion requests against the information needed to operate the account, resolve disputes, investigate abuse, and meet applicable recordkeeping obligations.
Local captures and remote pairings have the limits described above. Browser theme preferences remain until you replace them or clear site storage. Backup and infrastructure-log retention depends on the operator’s configuration; contact us for details rather than assuming immediate deletion from every copy.
08Your choices and data requests
Contact hello@trqsh.uz to request access to, correction of, or deletion of your personal account information. Include the email associated with your account and what you need. We may need to verify ownership before acting. The dashboard currently has no complete self-service account export or deletion flow.
You can revoke API keys, stop tunnels, clear local captures, end QR pairings, and clear browser storage. Revoking a key prevents it from being used for later authentication; stop active tunnels separately when you need to end exposure. Uninstalling a client does not delete server-side account records.
Depending on the law that applies to you, you may also have rights to restrict or object to processing, receive a portable copy, or complain to a data-protection authority. Tell us where you are located when relevant to your request.
09Keeping this policy current
We update this page when the described practices change and revise the date above. Software release notes are available in the changelog. Questions about a change can be sent to hello@trqsh.uz.