ZERO-EGRESS DATA BOUNDARIES

Privacy Policy

Last updated: September 19, 2026 • Effective immediately across all SiftrCode software distributions.

Foundational Commitment: Your Code Never Leaves Your Machine

SiftrCode is architected from the ground up as a 100% offline, local-first AST compressor. We believe intellectual property and codebase confidentiality are non-negotiable. SiftrCode does not upload your files, does not maintain remote telemetry, does not train machine learning models on your syntax, and does not operate network proxies that touch your proprietary code.

1. Source Code Execution & Processing

When you execute siftrcode audit, siftrcode pack, or attach the SiftrCode MCP server to your IDE, all syntax tree analysis, token estimation, and body dissolution occur exclusively on your local device's CPU using SiftrCode's air-gapped local runtime.

Zero Network Sockets: The parsing pipeline opens 0 network connections during code transformation.
Memory-Only Syntheses: Pruned interface skeletons are maintained in volatile RAM or emitted directly across local standard input/output (stdio) pipes to your agent client.
No Remote Parsing Queues: No source files, directory paths, git commits, or AST representations are ever streamed to external cloud servers.

2. Telemetry & Analytics

The SiftrCode Open Source CLI (npx siftrcode) contains no usage tracking, no user telemetry, no analytics beacons, and no crash report uploads. We do not track what repositories you audit, which files you prune, or what AI agents you pair with SiftrCode.

3. Model Context Protocol (MCP) Boundaries

The SiftrCode MCP Server communicates with coding agents (such as Claude Code, Cursor, Windsurf, or Antigravity) strictly over local Unix standard streams (stdio). MCP tool calls (siftr_skeleton, siftr_pack, siftr_audit) execute as direct child processes of your IDE, preserving your IDE's established security boundary.

4. Website & Team Trial Inquiries

When you visit our marketing website (siftrcode.com) or request a Team Pro trial via our activation form, we may collect:

Work Email Address: Provided voluntarily to issue team trial credentials and setup guides.
Team Size & Primary Agent Stack: To provision appropriate team cache resources.
Standard Web Server Logs: Standard IP addresses, timestamps, and browser user-agent headers generated during HTTP requests, retained strictly for server security and rate-limiting.

We never sell, rent, monetize, or trade contact details with third-party advertising networks.

5. Security Disclosures & Inquiries

Because SiftrCode is open source, our AST engine and local daemon are completely transparent and verifiable. If you have questions regarding security or wish to report a vulnerability, contact our engineering team directly at:

[email protected]