SakiClip Privacy Policy

Last Updated: 2026-02-28

“Your clipboard should not be an open display case for corporate telemetry.”

When designing SakiClip, we made an extreme but necessary decision: we completely excised all OS-level background clipboard polling mechanisms. We know that clipboards hold the lifeblood of developers and the secrets of enterprise systems. The following is our privacy commitment to you.

1. Zero-Monitoring Protocol

  • No Covert Polling: SakiClip does not periodically call the NSPasteboard or Windows Clipboard APIs in the background.
  • Explicit Sharing: Data transmission is only initiated when you physically click the “Send” button. Without your explicit authorization, SakiClip will absolutely never touch a single byte of your clipboard data.

2. Strictly Local & Subnet Isolated

SakiClip was forged solely to communicate between the Control Plane and Compute Plane. It does not trust the outside world.

  • Zero Cloud Servers: We operate no relays. Data flows strictly peer-to-point (TCP 19283) between your macOS Hub and Windows Client.
  • Built-in Routing Defense: Upon initialization, the application scans your network interfaces. If it detects an attempt to route traffic outward via a ppp (dial-up) or cellular interface, it forcibly aborts the connection. Your data is physically confined to your secure 802.3 or 802.11 LAN.

3. Zero Telemetry & Data Collection

  • No Analytics: We do not embed Google Analytics, Crashlytics, or any form of user behavior tracking.
  • No Payload Inspection: We do not know what code you transmit or what logs you send. Saki Studio has zero interest in the contents of your holotapes.

4. Local Logs Only

  • The “Transmission Log” visible on the SakiClip interface is stored only in the active application memory or your designated local log files.
  • Once the application is terminated, those brief transmissions evaporate like rain on hot asphalt, leaving no trace.

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