1. Introduction & Architectural Perimeter
This Privacy Policy explains how AetherKube ("we", "us", or "our") processes information when you browse our public website, request access to the Private Beta, download release artifacts, and operate the AetherKube software.
AetherKube is distributed exclusively as self-hosted, customer-operated infrastructure software. It executes within your private network perimeter (workstations, virtual machines, or Kubernetes clusters) and does NOT operate as a multi-tenant Software-as-a-Service (SaaS) hosting engine.
The platform operates across four decoupled architectural boundaries:
- Public Website (
https://aetherkube.pages.dev): Static marketing, documentation, and private beta registration. - Customer Product (Local): Self-hosted backend daemon and diagnostic engine running on your infrastructure (
http://localhost:8080). - Cloudflare Worker Edge Control Plane: Edge gateway managing license token verification, single-use download token issuance, and activation event processing.
- Private Owner Control Plane: An isolated administrative proxy (
port 9090) and append-only event ledger accessed solely by authorized platform operators.
2. Information We DO NOT Collect
AetherKube respects the confidentiality and regulatory boundaries of enterprise infrastructure. Our licensing and edge systems never intentionally collect, log, or export:
- Cluster Credentials: Kubeconfig files, bearer tokens, client certificates, or cloud provider service credentials.
- Kubernetes Secrets: Kubernetes Secret manifests, ConfigMaps containing sensitive keys, private SSH keys, or environment variables.
- Application Data & Workload Payloads: Database contents, customer personal records, internal network packets, or pod stdout/stderr logs.
- AI Copilot Prompts: Copilot queries are executed deterministically against the LLM provider configured in your local instance (e.g., local Ollama, vLLM, or your own API key). Prompts and outputs are never sent to AetherKube servers or retained for model training.
3. Information We Collect and Process
We process only minimal, sanitized telemetry necessary to evaluate beta applications and administer cryptographic licensing:
A. Registration & Account Information
Name, business email address, company or organization name, requested edition tier, and system-generated identifiers (cust-..., org-...).
B. Download Telemetry
Single-use download session tokens, requested release artifact name (.exe, .zip, docker-compose), version (v1.0.0), platform, architecture, edge-derived country code, and timestamp.
C. Activation Telemetry
License key ID (lic-...), Organization ID (org-...), anonymous installation UUID (inst-...), activation timestamp, and environment platform.
4. Retention & Append-Only Event Model
Operational licensing records are stored in an append-only administrative ledger. Event records (downloads, activations, status changes) are retained for the duration of the Private Beta testing program to ensure license lineage, cryptographic verification, and dispute resolution.
All local application databases (platform.db), incident snapshots, and operational diagnostics remain entirely on your local filesystem under your unilateral custody.
5. Legal Inquiries & Contact
For privacy inquiries or data verification, contact: