1 · What we store
| Data | Why | Kept until |
|---|---|---|
| Email address | sign-in, service notices, ticket answers | account deletion |
| Password (Argon2id hash) | authentication — we never see the password itself | account deletion |
| Balance & usage ledger | metering, statements, dispute resolution | account deletion + 90 days |
| Instance/volume metadata | operating your resources (not their contents) | resource destruction + 90 days |
| Top-up records (coin, amount, tx reference) | crediting and troubleshooting payments | account deletion + 90 days |
| Support tickets | answering you, quality | account deletion |
| API key hashes & last-use time | authentication, your own audit | key revocation |
2 · What we deliberately do not collect
- No identity data — no name, address, phone, ID documents. Payment is cryptocurrency; there is no KYC process.
- No IP retention — connection addresses are used transiently to serve requests and are not written to logs or the database.
- No trackers — no analytics scripts, no advertising pixels, no fingerprinting. The only cookies are the session cookie and a CSRF token on the console.
- No content inspection — we do not read instance disks, volumes or traffic in the normal course of operations (see §4 for the narrow exceptions).
3 · How the data is used
To run the Service you asked for: authenticate you, meter usage, credit payments, answer tickets and send the few operational emails that matter (password reset, instances stopped at zero balance, top-up receipts, ticket answers). No marketing lists, no profiling, no sale or rental of data — ever.
4 · When data leaves us
- Processors — a transactional email provider delivers the emails above (recipient and message only); payment infrastructure sees deposit addresses and amounts, never your account data.
- Legal compulsion — we answer valid legal process with what we hold, which §1 and §2 keep minimal, and we push back on overbroad requests. We cannot hand over what we never collected.
- Abuse response — investigating a concrete AUP violation may require inspecting the specific resource involved; such access is logged and limited to the incident.
5 · Your controls
- Export — your ledger and account data are downloadable from the console (or via the API) in machine-readable form.
- Deletion — deleting the account (Settings) destroys resources, erases content cryptographically and removes personal data after the 90-day accounting window.
- Correction — the email address is editable in Settings; everything else we hold is operational data you generate.
- Questions or requests beyond the console's buttons: a support ticket reaches the people responsible directly.
6 · Legal bases & transfers
Where GDPR-style laws apply, processing rests on contract performance (running the Service) and legitimate interest (security, abuse prevention). Data is processed in datacenters under contractual safeguards; the storage footprint in §1 is identical in every region.
7 · Changes
Material changes are announced in-console 14 days ahead. The changelog of this document lives at the bottom of the page source, dated.
Version 1.0, effective 2026-09-03. Material changes are announced in-console 14 days ahead; previous versions are available on request through a support ticket.