Security

How we keep your GPUs, data and money safe, in plain words. Questions, or something to report: write to [email protected].

Where your data lives

• In the EU. The dashboard, API and database run on DigitalOcean in Amsterdam. When you launch a GPU, each region shows where it is.
• Hivello Ltd is based in the Netherlands and is the data controller. The privacy policy lists what we keep and for how long; you can export or delete your account data from Settings › Your data.

Isolation between customers

• Your own space. Every team's GPUs run in their own Kubernetes namespace, with a network policy that stops them reaching other customers or our internal network.
• Fair GPU slices. Shared cards are split with HAMi: each slice gets its own share of memory and compute, enforced on the card. We measure the limits on every GPU model before selling it.
• Clean memory. The GPU driver zeroes memory before it is handed to the next customer. We have tested it: a new slice finds nothing left behind.
• Protected from the start. Your programs only run once the network rules for your GPU are in force. If they can't be applied, it doesn't start.

Network and abuse controls

• Outgoing mail (SMTP), Tor and common mining-pool ports are blocked, and each GPU has a bandwidth cap. Mining of any kind isn't allowed.
• We screen sign-ups, payments and API keys against sanctioned countries, using the country of the connecting IP. If the check can't run, we refuse rather than guess.

Signing in

• No passwords to leak. You sign in with a link or a 6-digit code sent to your email, or with Google. Codes work once, for 15 minutes, and five wrong tries use them up.
• Two-factor sign-in. Turn it on in Settings › Security: signing in then also needs a code from an authenticator app. You get eight one-time backup codes in case you lose your phone.
• Sessions you can end. Signing out ends the session on that device.
• Teams and roles. Give each person only what they need; see Teams & roles.

Keys and secrets

• API keys are shown once when you create them. We store only a hash, so nobody here can read them back.
• Team invitation links and sign-in codes are stored the same way.
• The browser terminal uses a one-time ticket that lasts two minutes, and idle sessions are closed.

Payments

• Card payments are handled by Stripe. Card numbers go straight to Stripe and never touch our servers.
• Credit is prepaid. We only take money when you add credit, or when you've turned on auto top-up with the amount you chose.

Reporting a vulnerability

Write to [email protected] with what you found and how to reproduce it. Please don't access other customers' data or disrupt the service while testing. We'll reply, and keep you posted until it's fixed.