1. Overview
Vaporkernel ("the Platform", "we", "us") is committed to protecting the privacy of our users. This Privacy Policy explains what data we collect, why we collect it, and how it is handled. It applies to all users of the Platform, including Customers (who deploy VM instances) and Providers (who contribute hardware).
The Platform is designed with privacy as a core principle. We employ multiple layers of encryption, access controls, and isolation to protect Customer data. Hardware-enforced memory encryption (TEE) is planned for full provider isolation. We collect only the minimum data necessary to operate the Platform.
2. Data We Collect
2.1 Customer Data
| Data Type | Purpose | Retention |
|---|---|---|
| API key (SHA-256 hash) | Authentication and authorization | Until key is deleted |
| Customer ID | Account identification, billing, instance ownership | Duration of account |
| SSH public keys | Injected into VMs for root access | Duration of instance lifecycle |
| Instance metadata | Scheduling, billing, status tracking | 30 days after termination |
| Billing records | Usage metering and invoicing | 7 years (financial records) |
| Email address (waitlist) | Early access notifications | Until unsubscribe or launch |
2.2 Provider Data
| Data Type | Purpose | Retention |
|---|---|---|
| Ed25519 public key | Cryptographic authentication (challenge-response) | Duration of registration |
| Hardware fingerprint | Sybil resistance (one registration per machine) | Duration of registration |
| Hardware specs (CPU, RAM, disk) | Instance scheduling and resource verification | Duration of registration |
| Payout address | Earnings distribution | Duration of registration |
| Region | Geographic scheduling | Duration of registration |
| Reputation metrics | Uptime, performance, behavior scoring (0-100) | Duration of registration |
| Network endpoint / IP address | Control plane communication, WireGuard tunnels | Duration of active connection |
3. Data We Do NOT Collect
The following data is explicitly not collected, accessed, or stored by the Platform:
- VM contents: Files, databases, application data, and any other content inside Customer VMs. Note: The Platform employs multiple layers of encryption and isolation to protect VM contents, but full hardware-enforced isolation from Providers requires TEE support (planned). See our Security Model for details.
- VM memory: Guest memory is isolated via KVM/HVF process boundaries. Snapshots are encrypted with instance-specific AES-256-GCM keys derived via HKDF-SHA256. Hardware memory encryption (AMD SEV-SNP / Intel TDX) for full provider isolation is on the roadmap.
- Network traffic: Data-plane traffic is encrypted via WireGuard tunnels between nodes. Full content isolation from providers requires TEE hardware support (planned).
- SSH private keys: Only public keys are collected. Private keys never leave the Customer's machine.
- Plaintext API keys: API keys are SHA-256 hashed before storage. The plaintext is shown once at creation time and is not retained.
- Passwords: The Platform does not use password-based authentication.
4. How We Use Your Data
We use collected data exclusively for:
- Platform operation: Scheduling instances, routing traffic, managing Provider connections, and maintaining system health.
- Authentication: Verifying identity via API keys (Customers) and Ed25519 challenge-response (Providers).
- Billing: Calculating charges based on instance configuration, tier, and running time. Calculating Provider earnings based on the 80/20 revenue split.
- Reputation system: Computing Provider reputation scores from uptime, performance, behavior, and tenure metrics.
- Security: Detecting suspicious activity, enforcing rate limits (token-bucket, 10 req/s default), and preventing abuse.
- Communication: Sending early access notifications to waitlist subscribers.
5. Data Storage and Security
Platform operational data is stored in SQLite databases (WAL mode) on the orchestrator with write-through persistence. The orchestrator supports HA active-passive failover with state synchronization between primary and standby nodes.
Security measures include:
- All control plane communication encrypted with TLS 1.3 (rustls, pure Rust)
- API keys stored as SHA-256 hashes only
- Provider authentication via Ed25519 challenge-response with 30-second nonce expiry
- Snapshot encryption via per-instance HKDF-derived AES-256-GCM keys
- Epoch-based split-brain fencing on all control messages
- Token-bucket rate limiting per customer
6. Cookies and Analytics
The Vaporkernel landing page (vaporkernel.com) uses Firebase (Google) for the waitlist functionality. Firebase may set cookies for session management. We do not use additional tracking cookies, advertising pixels, or third-party analytics beyond Firebase.
The Platform API and CLI do not use cookies.
7. Third-Party Data Sharing
We do not sell, rent, or share your personal data with third parties, except:
- Firebase (Google): Waitlist email addresses are stored in Google Firestore for the early access signup. Subject to Firebase Privacy Policy.
- Legal requirements: We may disclose data if required by law, court order, or governmental authority.
- Platform operation: Minimal metadata (instance IDs, network endpoints) is shared between Platform components (orchestrator, daemon, edge) as required for service operation. This data does not include Customer VM contents.
8. Your Rights (GDPR)
If you are located in the European Economic Area (EEA), you have the following rights under the General Data Protection Regulation (GDPR):
- Right of access: Request a copy of the personal data we hold about you.
- Right to rectification: Request correction of inaccurate personal data.
- Right to erasure: Request deletion of your personal data (subject to legal retention requirements).
- Right to restrict processing: Request that we limit how we use your data.
- Right to data portability: Receive your data in a structured, machine-readable format.
- Right to object: Object to processing of your data for specific purposes.
- Right to withdraw consent: Withdraw consent at any time where processing is based on consent.
To exercise any of these rights, contact us at [email protected]. We will respond within 30 days.
Our legal basis for processing personal data is:
- Contract performance: Processing necessary to provide the Platform service (API keys, instance metadata, billing).
- Legitimate interest: Security monitoring, abuse prevention, reputation scoring.
- Consent: Waitlist signup, marketing communications.
9. Data Retention
We retain data only as long as necessary for the purposes described in this policy:
- Active accounts: Data retained for the duration of the account.
- Terminated instances: Metadata retained for 30 days, then deleted.
- Billing records: Retained for 7 years for financial compliance.
- Deregistered Providers: Data deleted within 30 days of deregistration.
- Waitlist emails: Retained until unsubscribe or Platform launch, whichever comes first.
10. International Data Transfers
The Platform operates across a decentralized mesh of Provider hardware in multiple regions. Instance metadata and billing data may be processed in regions where the orchestrator is hosted. We ensure that any cross-border data transfers comply with applicable data protection laws, including GDPR standard contractual clauses where applicable.
11. Children's Privacy
The Platform is not directed at individuals under the age of 18. We do not knowingly collect personal data from children. If we become aware that a child has provided us with personal data, we will take steps to delete such information.
12. Changes to This Policy
We may update this Privacy Policy periodically. Material changes will be communicated via the Platform dashboard or email at least 14 days before taking effect. The "Last updated" date at the top of this page reflects the most recent revision.
13. Contact
For privacy-related questions, data requests, or concerns, contact us at:
- Email: [email protected]
- Web: https://vaporkernel.com
- GitHub: github.com/aminems/vaporkernel