Zero-Telemetry & BYOK Privacy Guarantee

Keyra Privacy Policy

Effective Date: November 18, 2026 • Published by CODEWITHSK

1. Core Commitment: Zero Server Costs & Zero Data Interception

Keyra is engineered by CODEWITHSK as a client-side Windows application. We do NOT operate intermediate proxy servers or telemetry relay relays that sit between your computer and AI endpoints. Your clipboard contents, prompt instructions, and transformed text are NEVER routed through, viewed by, or saved on CODEWITHSK infrastructure.

2. BYOK (Bring Your Own Key) & Windows DPAPI Local Encryption

Keyra adopts a strict BYOK (Bring Your Own Key) architecture. You bring your own API key (such as Google Gemini Free tier, Groq, OpenAI, Anthropic Claude, or DeepSeek):

  • Your API keys are encrypted locally on your machine using the Windows Data Protection API (ProtectedData.Protect with DataProtectionScope.CurrentUser).
  • Keys cannot be read by other user accounts on the same machine and cannot be decrypted if copied to another computer.
  • Requests are dispatched directly from your device to the official API endpoints (e.g., generativelanguage.googleapis.com, api.openai.com, api.groq.com).

3. 100% Offline Local Ollama & Deterministic Tools

When utilizing Local Ollama or LM Studio (http://localhost:11434) or the built-in deterministic tools (PII Redactor, JSON Beautifier, Markdown Table Generator, Entity Extractor), 100% of the computation executes locally on your CPU/GPU. Zero network requests are made, guaranteeing total air-gapped privacy for sensitive legal, medical, financial, or source code data.

4. Device Fingerprinting for Asymmetric Licensing

To enforce the 7-day trial and validate lifetime Pro licenses without requiring a cloud login, the software computes an irreversible hardware hash (e.g. DEV-8F2B-C91A) using your Windows machine GUID and CPU architecture. This identifier does not reveal your personal identity, files, or browsing history. It is used exclusively for ECDSA P-256 asymmetric cryptographic signature verification.

5. Third-Party Provider Privacy Policies

When you choose to dispatch requests to a third-party AI provider (Google, Groq, OpenAI, Anthropic, DeepSeek), the handling of your prompt text is governed by that provider's commercial terms and privacy policy. We encourage you to review their respective privacy commitments regarding zero-training on API payloads.

6. Contact & Questions

For any questions regarding our architectural privacy model, enterprise source auditing, or licensing verification:

Email: hello@codewithsk.com