Privacy Policy

What we collect

• Account: name, email address, a salted hash of your password (never the password itself).
• SSH keys: public keys you upload, installed onto instances you order. We never see or store a private key.
• Billing: a running balance and ledger of charges/payments. Card details are handled entirely by our payment processor — we never see or store full card numbers.
• Infrastructure metadata: which node and IP address(es) an instance holds, and resource usage (CPU/RAM/disk/network throughput) needed to operate and bill the Service.
• Connection metadata: for abuse detection, we record which remote addresses/ports your instance talks to and how much traffic passes between them — never packet contents, never anything sent or received over TLS/SSH. This is retained for a short rolling window (days, not months) and then deleted.
• Audit log: account-level actions (logins, orders, config changes, support-relevant admin actions) for security and support purposes.

What we don't do

We don't inspect the contents of your instance's network traffic, disk, or memory. We don't sell personal data to third parties. We don't use your data to train anything.

Who we share it with

Only the vendors necessary to run the Service: our payment processor (for billing), our email delivery provider (for account and billing notifications), and — where a plan is fulfilled on their infrastructure rather than our own — the upstream provider hosting that specific instance. None of them may use your data for their own purposes.

Retention

Account and billing records are kept for as long as your account is active plus a reasonable period after (typically for tax/accounting requirements), then deleted or anonymised. Connection metadata is deleted on a rolling window, as above. You can request deletion of your account and associated personal data at any time — see below.

Your rights

Depending on where you live, you may have rights to access, correct, export, or delete your personal data, and to object to certain processing. Contact support through your dashboard to exercise any of these — we'll respond within a reasonable time. Deleting an account with active instances requires cancelling them first, since we can't delete billing records for a service still running.

Changes

We may update this policy; material changes will be posted here with a new date.