Kepler JSON Privacy Policy

Effective Date: October 20, 2026

Executive Summary: Kepler JSON is an open-source, local-first developer productivity extension. We do not collect, track, store, or transmit any personal data, browsing history, API keys, or network payloads to any remote server. There are zero cloud servers, zero analytics trackers, and zero external tracking dependencies.

1. Information We Do NOT Collect

Kepler JSON operates entirely on your local machine. We do NOT collect:

Personally Identifiable Information (Name, Email, IP address)
Browsing activity or visited websites
Authentication tokens, cookies, or HTTP request/response payloads
Usage telemetry or analytics

2. Permissions & Technical Usage

Permission	Local Technical Purpose
declarativeNetRequest	Executes user-defined HTTP header modifications and CORS rules natively inside Chromium's network engine without intercepting data.
storage	Saves developer profiles, language preferences, and BYOK LLM settings strictly in `chrome.storage.local` on your device.
activeTab	Identifies the current active tab origin when the popup is opened to provide 1-click CORS unblocking for that domain.
alarms	Schedules local safety self-destruct timers (15m, 1h, or tab close) to auto-revert temporary rules.
<all_urls>	Enables rules on arbitrary developer-specified target API endpoints and detects raw JSON documents for virtualized viewing.

3. AI Features & BYOK (Bring Your Own Key) Architecture

Kepler JSON provides AI capabilities (Local Privacy Vault, Cursor / v0 Component Compiler, and Talk to JSON Radar). All AI features are strictly client-side:

In-Memory Sanitization: PII redaction and synthetic data generation occur purely in client-side memory. Unsanitized data never leaves your device.
Direct Client Calls: If you configure an LLM key (DeepSeek, OpenAI, or local Ollama), API calls are initiated directly from your browser to the specified endpoint with zero intermediary servers.
Local Key Storage: Your API key is stored strictly in chrome.storage.local on your machine.

4. Offline Profile Sharing

Kepler JSON's team sharing feature compresses configuration profiles locally into a text token (kepler://profile/...) using client-side LZ-compression. No server, database, or network request is ever involved.

5. Open Source Auditing & Contact

Kepler JSON is released under the MIT License and built with complete transparency, zero tracking, and local-only processing.

For privacy questions and feedback, reach out via email: support@keplerjson.com.