Acceptable use.Acceptable use.

01Use systems you are authorized to expose

Use trqsh for legitimate development, previews, webhook delivery, testing, or other lawful connectivity. You must have permission to publish the service, use any configured domain, and transmit the content going through it.

Keep sensitive development interfaces behind appropriate authentication. A difficult-to-guess hostname is not a security control. Follow the security guide when exposing local services.

02Prohibited activity

• Phishing pages, credential theft, impersonation intended to deceive, or fraud.
• Malware distribution, botnet control, exploitation of other people’s systems, or unauthorized collection of their data.
• Spam, denial-of-service traffic, abusive scanning, or attempts to disrupt other users or networks.
• Publishing illegal content, violating intellectual-property or privacy rights, or sharing personal data without the necessary authorization.
• Bypassing quotas, rate limits, account restrictions, domain verification, or security controls.
• Stealing or sharing account credentials, API keys, or pairing links without authorization.

Security testing must be limited to systems for which you have explicit authorization and must avoid disrupting other users or collecting their private information.

03How we respond

We may investigate reports, restrict a hostname or tunnel, revoke access, or suspend an account when activity violates this policy, threatens others, or creates a legal or security risk. Serious issues may require immediate action.

Enforcement does not mean that every request or hostname has been reviewed or that abuse will always be detected automatically. You remain responsible for your application and the activity you permit through it. If you believe an action was mistaken, contact hello@trqsh.uz with the affected account and hostname.

04Report abuse or a security issue

Send reports to hello@trqsh.uz. Include the full tunnel hostname or URL, the date and time with time zone, what you observed, and relevant evidence. For a vulnerability, include the affected component and version, impact, and safe reproduction steps.

Do not put active credentials, private captured traffic, or an exploitable security issue in a public GitHub issue. If you include screenshots or logs, remove unrelated personal data and secrets. Sending a report does not require you to interact further with a suspicious service.

05Related policies

This policy forms part of the Terms of service. The Privacy policy explains how account and connection records are handled. Contact hello@trqsh.uz if a planned use is unclear.