TomatoTerm does not hand your server connections to a third-party relay before executing actions for you. It is a local-first, local-storage, direct-connection desktop tool. It only contacts TomatoTerm servers for necessary scenarios such as licensing, activation, and limited event analytics.
SSH, SFTP, port forwarding, workflow execution, and the core links behind cloud-assisted features all connect from your device to the target resource directly, without relaying through TomatoTerm servers.
That means your remote access path is not “platform first, server second”, which reduces the trust burden of platform-held connections.
Connection settings, configuration data, and business data are stored on your local device by default instead of relying on cloud hosting.
Local data is encrypted with a combination of device context and application mechanisms, aiming to make it hard to reuse outside the current device and current software environment.
Sensitive data such as passwords, SSH private keys, and API keys is not left in plain text across ordinary config files.
These secrets are encrypted and stored in the credential store provided by the operating system, so access is handled by system-level security capabilities.
Logs are essential for troubleshooting, but they can easily become another leak source. TomatoTerm masks log data where possible to avoid direct exposure of passwords, keys, tokens, and other secrets.
Even during issue investigation, the goal is to balance useful diagnostics with minimal data exposure.
Communication with official TomatoTerm servers is intentionally limited to required cases such as licensing, activation, and a small amount of event analytics.
In daily operations, the core admin workflow does not depend on continuously sending your server actions to the platform.
Many users worry less about their servers and more about whether the management tool takes one more privilege, keeps one more copy of data, or adds one more hidden network hop.
TomatoTerm aims to lower that concern so you can use batch management, workflows, and automation without taking unnecessary platform-side risk.
In one sentence: your connections are established directly by your computer whenever possible, your data stays on your computer whenever possible, and your sensitive credentials are protected by your operating system instead of an invisible middle layer.