Gizlilik Politikası

Yürürlük Tarihi: April 3, 2026

At Kernax, privacy is the engineering foundation of our ecosystem. Unlike conventional AI development tools that accumulate vast data lakes of user codebases for model training, Kernax is explicitly architected around a Zero-Retention philosophy. This Gizlilik Politikası details how we protect your intellectual property, what minimal telemetry we collect, and how your data is processed.

1. Giriş

Kernax ("we", "us", "our") provides an advanced Artificial Intelligence Integrated Development Environment (IDE) and related cloud services (collectively, the "Services"). This Gizlilik Politikası applies to all users ("you", "your") accessing our website, desktop applications, APIs, and associated services.

2. The Sıfır-Veri Tutma Mimarisi

We recognize that source code is the most critical asset of any modern enterprise. Our infrastructure functions strictly as a secure, stateless proxy layer:

• No Source Code Storage: Code snippets, workspace context, and file structures transmitted to our APIs are processed entirely in memory (RAM). Once the AI inference response is successfully streamed back to your local IDE, the payload is irrevocably purged from our servers.
• No Prompt Storage: Conversational instructions, queries, and terminal logs integrated into your prompts are not persisted to database systems.
• No AI Fine-Tuning: Kernax categorically does not utilize your codebase or conversational history to train, fine-tune, or reinforce proprietary or open-source language models.

3. Topladığımız Veriler

While we refuse to store proprietary workspace data, the operational and commercial realities of our platform require the minimal collection of Account and Billing information.

3.1 Account Information

To establish and secure your account, we collect your email address, securely hashed passwords, and authentication tokens (e.g., OAuth vectors if utilizing third-party SSO).

3.2 Billing & Token Metrics

To maintain an equitable computing ecosystem, we record absolute mathematical abstractions of your computational usage. This metadata includes:

• Input Token Volume (e.g., 4,500 tokens).
• Output Token Volume (e.g., 850 tokens).
• The specific AI Provider and Model utilized (e.g., `gpt-4`, `claude-3-opus`).
• The financial cost (in USD) incurred during the generation cycle.

Note: Raw billing rows are algorithmically aggregated into monthly summaries and permanently expunged on a rolling 30-day basis to minimize our data footprint.

4. Verilerinizi Nasıl Kullanıyoruz

The minimal data acquired is utilized strictly for the following purposes:

• Service Provision: Authenticating your IDE client and connecting it securely to our computational grid.
• Financial Accounting: Deducting exact balances based on token utilization and generating corporate invoices.
• Fraud Prevention: Identifying automated botnets, credential stuffing, and Terms of Service violations.
• Platform Optimization: Monitoring holistic API latency and orchestrating load-balancing strategies across AI providers.

5. Third-Party AI Subprocessors

Kernax securely routes inference requests to tier-one computational providers (Subprocessors). We utilize enterprise-grade API agreements with these partners ensuring stringent data protection endpoints:

• OpenAI L.L.C: Utilized for GPT-series inference. Under our Enterprise API Agreement, OpenAI is legally prohibited from persistently storing or utilizing payloads for secondary model training.
• OpenRouter: Utilized for dynamic model aggregation (e.g., Anthropic, Meta Llama). Data transmission is entirely secured via TLS 1.3 encryption, enforcing strict ephemeral processing rules.

6. IDE Telemetry & Analytics

The Kernax Desktop Application (based on Microsoft's OSS VS Code architecture) may collect anonymous crash reports and application performance indices (Telemetry). This telemetry strictly excludes source code and is used solely to identify software instability.

You may effortlessly opt-out of all non-essential IDE telemetry by modifying the setting telemetry.telemetryLevel to off within your workspace configuration.

7. GDPR & CCPA / CPRA Compliance

As a global platform, we are committed to upholding the European General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA).

• Right to Erasure (Right to be Forgotten): You may terminate your account via your Dashboard at any moment. Invoking this right instantly triggers a cascading cryptographic deletion of your identity, balance, and association with historical metrics.
• Right to Portability: You may request an export of your account details and billing ledger in a machine-readable JSON format.
• DPA (Data Processing Agreement): For enterprise clients requiring a formal signing of a standard DPA, please direct your legal apparatus to our compliance department.

8. Security & Local Nodes

The Kernax Desktop client orchestrates a highly isolated background Intelligence Node operating physically on your machine. This Node is purposefully bound to the 127.0.0.1 (Localhost) network interface, rendering it mathematically invisible and inaccessible to malicious actors on global or local network perimeters.

All remote communications traversing the internet between your IDE and the Kernax Cloud are secured using Transport Layer Security (TLS) 1.3 cryptographic protocols.

9. Contacting Our Legal Office

If you represent a corporate compliance entity or possess inquiries regarding our Data Processing practices, our designated privacy officers are available at:

Email: privacy@kernax.com
Address: Kernax Legal Operations, [Your Silicon Valley / Enterprise Address]