Terms of Service

When you use a product labeled "talex-touch" or "Tuff", you agree to the following terms.

Acceptance

By accessing and using Tuff / talex-touch services, you agree to be bound by these Terms of Service. If you do not agree, please do not use the services.

Service description

Tuff is a local-first desktop command center with plugin, automation, and collaboration features. Features may change as the product evolves.

Accounts and security

You are responsible for safeguarding account credentials and for activity under your account. Notify us promptly of unauthorized use.

Signed cloud configuration and optional features

When you are signed in, Tuff may retrieve and apply signed, versioned, and, where appropriate, encrypted declarative configuration packs from Nexus. For supported features, these packs may adjust endpoint paths, provider or model allowlists, safety limits, feature parameters, and rollout or rollback settings without requiring a desktop client reinstall.

Configuration packs contain data only: they do not contain executable scripts, account credentials, or Provider credentials. Tuff accepts a pack only after client-side signature, schema, compatibility, origin, and local safety-limit checks. A pack can configure only behavior already implemented in the installed client; adding a new executable protocol or capability still requires a client update.

Cloud configuration does not override your local choices. Voice input is off by default, starts only after you enable it manually, and captures the microphone only during an active voice-input session. Receiving a voice routing pack never enables voice input or microphone access. While signed out, Tuff does not check, download, or activate cloud-controlled packs. Where supported, Tuff provides status, manual sync, and rollback controls.

By signing in and using a supported cloud-controlled feature, you authorize this delivery mechanism under these Terms. You can opt out by signing out or by keeping the optional feature disabled. A material expansion of the configuration categories or purposes requires updated terms or a separate notice.

Acceptable use

You may not misuse the service, attempt unauthorized access, reverse engineer restricted components, or use the service for unlawful purposes.

Privacy

How we handle personal data is described in the Privacy Policy at /privacy.

Software license

Desktop client licensing terms are described in the Software License at /protocol.

Changes

We may update these terms from time to time. Continued use after changes become effective constitutes acceptance of the updated terms.

Contact

Questions about these terms can be raised through the in-product feedback channels or the project GitHub organization.