Remote access requires authorization
TucDesk is built for legitimate operations work. You are responsible for having permission to access every system, agent, session, recording, and command path you use.
These terms apply to TucDesk Cloud, self-hosted deployments, client applications, agents, installers, dashboard images, and related infrastructure. If your organization has a separate signed agreement with TucDesk, that agreement controls where it conflicts with these public terms.
Use it lawfully
No unauthorized access, malware, surveillance without authorization, or tenant-boundary bypass.
Operate it deliberately
Pairing, operator access, retention, backups, TLS, DNS, and object storage remain operational responsibilities.
Know what is licensed
Open-source infrastructure follows published licenses; proprietary clients and dashboard images require permission to redistribute.
Agreement
Acceptance
By creating an account, using TucDesk Cloud, running TucDesk self-hosted components, installing an agent, or accessing the dashboard Docker image, you agree to these terms.
If you use TucDesk on behalf of an organization, you represent that you have authority to bind that organization and that operators under your account will follow these terms.
Services
TucDesk Cloud is managed infrastructure operated by TucDesk for remote access, agent management, rendezvous signaling, encrypted relay transport, audit, and session recording storage.
Self-hosted TucDesk lets operators run the API, rendezvous, TURN relay, Postgres, Redis, and object storage in their own environment while using TucDesk-distributed clients and dashboard images.
The deployment mode affects who controls infrastructure and data. It does not change the requirement that operators use TucDesk lawfully and maintain appropriate access controls.
Account registration and security
You are responsible for accurate account information, protecting operator credentials, rotating secrets, and controlling access to paired agents.
You must promptly remove access for operators who no longer need it. For self-hosted deployments, you are responsible for TLS, firewall rules, DNS, database backups, SMTP credentials, and object storage permissions.
Acceptable use
Do not use TucDesk for unauthorized access, abusive traffic, malware distribution, credential theft, surveillance without authorization, or activity that violates the rights of others.
Do not attempt to bypass consent gates, audit logging, policy ACLs, rate limits, authentication controls, or tenant boundaries. Research testing must be conducted only against systems you own or have permission to test.
Prohibited activities
You may not use TucDesk to access systems without authorization, hide malicious activity, exfiltrate data, disrupt third-party infrastructure, or impersonate another operator, organization, or service.
You may not disable, weaken, or misrepresent consent prompts, audit trails, session recording, cryptographic protections, tenant boundaries, or security controls that are required by your organization or by law.
You may not copy, scrape, crawl, probe, or stress TucDesk services in a way that harms availability or attempts to discover other tenants, operators, agents, sessions, credentials, or infrastructure details.
Intellectual property
The API, rendezvous, and TURN infrastructure are MIT licensed where published. The dashboard Docker image, iOS app, Android app, signed installers, and hosted dashboard user interface are proprietary unless a separate written license states otherwise.
You may use TucDesk names and marks only to identify the product or integration. You may not imply endorsement, redistribute proprietary images, or white-label TucDesk without written permission.
Service availability
Cloud availability and support commitments depend on plan tier. Maintenance, security releases, abuse mitigation, dependency incidents, and infrastructure provider outages may affect service availability.
Self-hosted uptime is controlled by the operator. TucDesk may provide software artifacts and documentation, but the operator is responsible for capacity planning, monitoring, backups, and disaster recovery.
Billing and cancellation
Paid cloud plans renew until canceled. Fees are billed according to the selected plan, usage, storage, support level, and any enterprise agreement.
Self-hosted infrastructure can be run without TucDesk Cloud billing unless you separately purchase managed hosting, enterprise support, compliance assistance, or a commercial license.
Warranties
TucDesk is provided as-is except where a signed order form, enterprise agreement, or applicable law requires otherwise. We do not guarantee uninterrupted access, error-free operation, or that every network path, NAT environment, relay, or third-party service will work in all circumstances.
You are responsible for validating TucDesk in your own environment before using it with production systems, regulated workloads, privileged credentials, or critical infrastructure.
Self-Hosted license terms
You may run the TucDesk dashboard Docker image for your own organization and connect it to your own TucDesk API, rendezvous, and relay infrastructure.
You may not redistribute, modify, reverse engineer, decompile, resell, or white-label the proprietary dashboard image or client applications without written permission. Open source infrastructure components remain governed by their published open source licenses.
Data and security responsibilities
TucDesk is designed around end-to-end encrypted sessions, signed audit logs, team-scoped runtime configuration, and tenant-isolated cloud storage paths. These controls reduce risk, but they do not replace operational security.
You remain responsible for deciding which agents may be paired, which operators may connect, what commands may run, how long recordings are retained, and what data may be exported.
Connecting into a company
TucDesk may be used to access company-managed systems only when the operator has permission from the organization that owns or controls those systems. Personal accounts must not be used to bypass company access controls or monitoring requirements.
If your organization requires approvals, recording, retention, SSO, device posture, change-management tickets, or other controls, you are responsible for configuring TucDesk and surrounding infrastructure to meet those requirements.
Limitation of liability
TucDesk is provided with the limitations permitted by applicable law. Remote infrastructure tools can affect critical systems, so production use requires appropriate backups, least-privilege access, staged rollout, monitoring, and operational review.
Except where prohibited by law or a separate written agreement, TucDesk is not liable for indirect, incidental, special, consequential, or punitive damages, or for loss of profits, revenue, data, goodwill, or business interruption.
Termination
We may suspend or terminate Cloud access if an account violates these terms, creates security risk, causes platform abuse, fails to pay required fees, or uses TucDesk in a way that could harm other customers or infrastructure.
You may stop using TucDesk Cloud at any time. Self-hosted operators remain responsible for exporting, retaining, or deleting their own databases, object storage, logs, keys, and configuration after termination.
Governing law and contact
These terms are governed by the law stated in your order form or enterprise agreement. If no separate agreement applies, disputes are handled under the governing law selected by TucDesk for cloud service operations.
For legal questions, contact legal@tucdesk.app. For security reports, use security@tucdesk.app instead of legal support channels.