SakiAgentSSH Privacy Policy

Last Updated: 2026-02-28

“Your compute power is yours. Your data is yours. We only care that the stream remains uninterrupted.”

Saki Studio understands the gravity of the wasteland. The standard outputs (stdout) and standard errors (stderr) generated during cross-machine automation and AI Agent operations often contain highly classified data—API keys, environment variables, and proprietary algorithms. Therefore, we have established the following strict privacy protocols.

1. Strictly Local & Peer-to-Point (P2P)

The design philosophy of SakiAgentSSH is the decentralized bridging of isolated nodes.

  • Zero Intermediary Servers: All connections are established directly between your saki-ssh-client and the target machine’s saki-ssh-daemon (Peer-to-Point).
  • Zero Cloud Dependency: We do not operate signaling servers, nor do we employ proxy relays. The flow of data is entirely dictated by your own network topology.

2. Zero Telemetry

In an era where every piece of corporate software greedily siphons user behavior data, we choose to refuse.

  • No Tracking Pixels.
  • No Google Analytics or third-party telemetry SDKs.
  • We will absolutely never transmit your usage statistics, executed commands, or stack traces back to Saki Studio or any external entity.

3. Log & Data Retention

All logs generated by SakiAgentSSH belong solely to you.

  • Local Storage: Any error logs or execution records from the Daemon and Client exist only on your local machine—either dumped directly to /dev/stdout or written to a log file path you explicitly define.
  • Burn After Reading: When the gRPC bidirectional stream concludes, or when a process is terminated via CancelRequest, the memory buffers are instantly purged. We do not covertly write residual command data to hidden cache files.

4. Perimeter Defense (Permissions & ACL)

SakiAgentSSH is a powerful proxy, so we hand you the keys to the vault.

  • CIDR Whitelist (ACL): Via the allowed_cidrs parameter, only IP subnets you explicitly authorize can access the Daemon. This ensures that even if your node is exposed, unauthorized IPs cannot establish a connection, thereby safeguarding your system’s privacy.
  • Records of rejected network requests are kept strictly in your local terminal logs, serving purely as telemetry for your own perimeter defense.

5. Protocol Amendments

Given the stateless and entirely local nature of SakiAgentSSH, this privacy policy will rarely require amendments. However, should we introduce new mechanisms that necessitate local configuration storage in the future, we will update this log. Our core directive—“Do not disturb, do not collect”—will remain absolute.

If you detect any privacy anomalies, transmit an inquiry to: [email protected]