Privacy is not a setting. It is the foundation.

Here is exactly what happens to your code. No ambiguity.

What we collect

  • Account email
  • Plan status
  • Token usage count
  • Device count (trial only)
  • Aggregate stats (no PII)

What we never collect

  • Code content
  • File names
  • Project structure
  • Conversation content
  • Keystrokes
  • Screen content

The Data Flow

[Your Prompt]
[Kinetic MCP Bridge]
[API Provider (Claude/Gemini/Groq)]
[Response back]

Prompt travels. Code stays.

[Your Prompt]
[Encrypted by Kinetic]
[SGX Enclave]
[Provider sees tokens only]
[Response]

Encrypted before it leaves.

[Your Prompt]
[Local Model Stack]
[Response]

Zero external calls. Ever.

The Vault

vault.enc
├── Encrypted with: AES-256-GCM
├── Key derived from: BIP-39 16-word passphrase
├── Wrong passphrase attempts: 5 maximum then self-destruct
├── Location: local disk only
└── Cloud sync: hardcoded excluded at 3 separate layers

Cloud Sync Matrix

File TypeCloud SyncNotes
Settings configYesTheme, preferences, non-sensitive config
Pulse archiveYes encryptedSession memory — encrypted in transit
vault.encNEVERHardcoded exclusion — 3 enforcement layers
RAG indexNoToo large — rebuilt locally
API keysNEVERSecretStorage only — never serialized

The Kinetic Developer Promise

  • Your code content will never be stored, logged, or used for training by Kinetic
  • vault.enc will never be transmitted, synced, or readable by any external system
  • If we ever change these commitments, every user will be notified 90 days in advance

M. Abbas Baber, Founder

Kinetic Tech Solution LLC

M. Abbas Baber

March 13, 2026