SakiMCP Privacy Protocol

> ARCHITECTURE: ZERO_KNOWLEDGE | TELEMETRY: DISABLED

Effective Date: February 24, 2026

“Your data is sovereign. Our architecture is silent.”

In an era of surveillance capitalism, SakiMCP is built on a radical premise: What happens on your machine, stays on your machine.

I. The Zero-Telemetry Mandate

SakiMCP operates under a strict Zero-Telemetry Policy. We do not track your usage. We do not profile your code. We do not upload your file indices.

The application logic executes entirely within the localhost environment of your macOS device. Whether you are indexing a private crypto repo or writing personal journals, Saki Studio has zero visibility into your operations.

II. Local-First Data Architecture

All application states, including:

  • Project File Indices
  • Vector Embeddings (if generated)
  • User Preferences
  • MCP Connection Configs

Are stored exclusively on your local SSD, typically within ~/Library/Application Support/SakiMCP/. This data never leaves your physical hardware unless you explicitly transfer it.

III. Network Activity Transparency

SakiMCP is air-gapped by design, with controlled exceptions initiated solely by the operator:

  1. Localhost MCP Server: The HTTP Server (Port 3456) operates on the loopback interface exclusively. No external ingress permitted.
  2. LAN Agent Relay (Optional): When you explicitly configure list_mcp_clients and call_remote_tool, SakiMCP can communicate with other MCP servers within your local area network (LAN) only. No WAN-facing ports are opened. All inter-node data remains within your network perimeter and never transits Saki Studio infrastructure.
  3. SSH Tunnel / Tailscale (Optional, Experimental Professional Feature): If you manually configure SSH tunneling or Tailscale connectivity, SakiMCP will communicate through your own encrypted channels. Saki Studio does not relay, intercept, or possess any connection credentials or transmitted content. You hold the keys.
  4. Web Search Tool (Optional): If (and only if) you enable the web_search MCP tool and provide your own Brave Search API Key, the application will make outbound HTTPS requests to Brave Software’s endpoints. This interaction is subject to Brave’s privacy policy, but Saki Studio remains out of the loop.

IV. Commitment to Data Sovereignty

We believe that the toolmaker should not own the craftsman’s work. SakiMCP is a tool for your agency, not a platform for our data mining.

For privacy inquiries or technical audits:

© 2026 Saki Studio. All rights reserved.