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 nevercollect

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

The Secure Bridge — Data Flow

[Your Prompt]
[Kinetic MCP Bridge]
[API Provider]
[Response back]

Prompt travels. Code stays.

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

Zero-Knowledge Processing

&
[Inbound Prompt]
[LOCAL MODEL]
[Result]

Air-Gapped Equivalent

The Vault Standards

vault.enc security protocol v2.4

├── Encrypted with: AES-256-GCM

├── Key derived from: BIP-39 16-word passphrase

├── Security Guard: Self-Destruct on 5 fails

├── Location: Local disk block storage

└── Cloud sync: Blocked

Cloud Sync Matrix

File TypeCloud SyncSecurity Enforcement
Settings config
Yes		Theme & Preferences
Pulse archive
Encrypted		Session memory context
vault.enc
NEVER		Local hardware locked
RAG index
Local Only		Contextual code map
API keys
NEVER		SecretStorage restricted

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 & CEO, Alayra Group LLC

Authenticated On

MAY 2, 2026