Privacy

Account. Your email address, and a password stored only as a bcrypt hash by our authentication provider. If you enable two-factor authentication we store the authenticator secret it generates. We never see your password in readable form.

Payments. Card details go directly to Stripe and never reach our servers. We store the Stripe identifiers for your customer record and saved payment method, and the amount and date of each top-up.

Agreement records. When you create an account and each time you add funds, we record which version of the terms you agreed to, the time, the IP address the request came from, and your browser's user agent string. This exists to answer a bank if a payment is disputed.

Usage. For each machine you run: its type, region, when it started and stopped, and one metered record per five minutes with the amount charged. You can see and export all of it from your usage page.

Connection. When you connect to a machine we take the IP address of that request and open remote desktop access to that single address. The rule is removed when the machine stops.

Security. Amazon GuardDuty monitors the infrastructure for abuse. Where a finding concerns a machine you were running, we keep a record of it linked to your account.

We do not collect your name, address, phone number, or date of birth. We do not use advertising or analytics trackers, and we set no cookies other than those required to keep you signed in. We do not look inside your machines: what you store or run on them is not visible to us, and we do not log it.

Amazon Web Services hosts the machines and the control systems. Supabase provides authentication and the database. Stripe processes payments. Cloudflare or hCaptcha provides the anti-bot check on the sign-in form. All of them act as processors for us, under their own terms.

If you dispute a payment, we send Stripe the evidence needed to respond: your email address, the IP address the purchase came from, and the record of machines you ran and what they cost. Without it we cannot answer the dispute.

When you choose a password, we check it against the Have I Been Pwned breach database using a method that sends only the first five characters of its hash. Your password, and its full hash, never leave your browser.

We do not sell personal data, and we do not share it for advertising.

Agreement records, including IP addresses: 24 months, then deleted automatically. A payment can normally only be disputed for a few months after it is made, so older records serve no purpose.

Billing and usage records are kept while your account is open and afterwards for as long as tax and accounting rules require.

Machine contents are not kept at all. Disks are destroyed when an instance is terminated and we hold no backups — see section 5 of the terms.

You can export your full usage history as a CSV file at any time from your usage page, and change your email or password from your settings.

You can ask us to delete your account and the personal data attached to it. We will keep the billing records we are legally required to keep, and nothing else. Any unspent balance is refunded — that is a commitment in section 7 of the terms, not a discretion.

Depending on where you live you may also have the right to a copy of your data, to correct it, or to object to how we use it. Contact us and we will action it.

Access to your account requires your password, and two-factor authentication if you enable it. Machine disks are encrypted. Your instances accept no inbound network connections except remote desktop from the single address you connect from, and only while running.

No system is perfect. If we discover a breach affecting your personal data we will tell you and the relevant regulator as the law requires.

Questions about any of this, or to exercise any of the rights above, use the contact address shown in the terms.