24 TB to 160 TB of hard drives per server · Amsterdam, Bucharest, Chisinau · no KYC. Pay in crypto: BTC, USDT, USDC, ETH, SOL, LTC
Language: English
Choose a hold

Legal · Effective 2 November 2026

Privacy Policy

Which records Basalthold holds to bill and run your storage server, which logs it never writes, what sits in your browser, and the one way records leave us.

Last updated: · 6 min read

Quick answer

What does Basalthold keep about its customers?

No logs: no connection or traffic records, no IP address of a visitor or customer, and nothing on how you reached the site except a referral code when your link carried one. We keep only what billing and running your server require: the account number, plus an email if you add one; each top-up and order (amount, coin, network, transaction ID, date); and for each server its name, plan, term, location, system, SSH public key, IP addresses and dates, plus the temporary root password we set when you gave no key, which stops working once you change it. The contents of your drives are yours: we do not inspect them. The datacenter’s network equipment is outside our control. Records are handed over only on the order of a Panamanian court. We run no identity check, and an email address appears on an account solely when its owner types one in. The site and the dashboard use no cookies, no analytics and no ad code.

1. Who decides about your data

The controller is DomaineGoat LLC, the Panamanian LLC behind Basalthold and the seller in the terms of service. Privacy questions: [email protected].

2. What we mean by "no logs"

No logs are kept: no connection records, no traffic records and no visitor or customer IP addresses, on the website, in the dashboard or on the servers.

Our web servers necessarily receive your IP address with each request. It serves to send the reply and, held in RAM only, to cap request rates per address. No disk or log file ever receives it.

The datacenter around your hold runs network gear of its own. It falls under that country's rules, and we have no say over it.

3. The records a hold needs

Nothing below is kept for its own sake: each record serves billing, preparing or renewing a storage server.

WhatWhy we need itWhere it comes from
Account numberIt is your login; balance, orders and holds hang off itCreated with your account
Email, only if you add itLets us send you a forgotten account numberYou
Each top-up: transaction ID, coin, network, amount, dateChecked against the chain before we credit itYour transfer, as the blockchain shows it
Order and balance historyBilling each term, renewal and creditYour orders
Each hold: name, type, term, system, city, IP addresses, key dates (ordered, delivered, renewed, suspended, cancelled)Preparing, renewing and billing itYour order, then our preparation work
SSH public key, if you paste onePlaced on root at setup and at every reinstall; password login remains disabledYour checkout form
Temporary root password, key-less orders onlyLets you in once; dead as soon as you run passwdOur team, while preparing the hold
Referral code, from a referral link onlyCredits the link an order came fromThe URL you arrived by
Dashboard languageSent with top-ups, so the team sees which language you useYour dashboard setting
Support emailsReplying, and handling RAID or reinstall requestsYou

Your files are absent from this table on purpose. What is on your drives belongs to you, and we do not inspect it.

4. What we do not collect

  • No KYC: no ID, no selfie, no documents, no card and no phone number, at any point.
  • Name, postal address, birth date: no form on this site has a field for them.
  • Card or bank data: we take crypto and nothing else.
  • Secrets by email: your account number, root password or private key. Nobody from our team will ever ask for your account number, your root password or your private SSH key, by email or in a chat.

5. Cookies, local storage and exchange rates

Nothing on https://basalthold.com or in the dashboard sets a cookie, and neither loads analytics, ad or tracking code. Fonts are served by us, not by a font network.

Your browser keeps a few things locally. They remain on the device until they expire or you wipe them:

  • Website language: your menu choice. It is never sent to us.
  • Dashboard session: a token that spares you a fresh login. Each dashboard call sends your account number to us over HTTPS.
  • Account mirror: account number, any email, language, and each top-up you began with its reference, amount, coin, network, address and status. A payment page survives a reload this way; we already hold all of it.
  • Unacknowledged top-ups: re-sent to our server until it confirms receipt.
  • Fresh account number: kept in the current tab only, until you confirm you wrote it down. Never sent.
  • Dashboard display language: never sent.

Exchange rates. A payment in Bitcoin, Ether, Solana or Litecoin needs a live dollar price. Your browser fetches it from Coinbase's public API, or from CoinGecko's when Coinbase fails. That call carries neither cookies nor a referrer, and nothing about your account. Your IP address does reach the price service, as it reaches every server you contact. Stablecoins skip the call: one USDT or USDC is booked as one dollar.

Using a shared computer? Log out and wipe this site's stored data before you leave it.

6. Public ledgers

Whatever you send on a blockchain stays readable by anyone: amount, time, sending and receiving addresses. Through its transaction ID, your top-up links to everything else the sending wallet has done. Incoming payments are checked against public sanctions lists of blockchain addresses; a payment from a listed address is not credited. Banks and card schemes play no part. To see how other storage services handle crypto, read which cloud storage accepts crypto.

7. The optional email

Email is optional. Keep your account number safe, since it opens your account. With an email on file the number can be recovered; without one, a lost number cannot be replaced. When one is saved, the dashboard can mail your account number to it on request. If you write to support, your message and its sender address are stored so that we can answer.

8. What records are used for, and who can obtain them

Records serve account management, hold preparation and renewal, payment crediting, support and abuse handling. We sell nothing and advertise with nothing.

A Panamanian court order is the single route by which records leave DomaineGoat LLC. DMCA notices and other foreign copyright notices are not acted on: only Panamanian law and the decisions of Panamanian courts apply to us; demands under any other foreign law fare the same.

9. Drive contents and encryption keys

You can encrypt every data drive with LUKS or ZFS native encryption; the keys stay with you and nobody on the team ever asks for them.

Plain, unencrypted drives are readable by whoever has the hardware in hand. Encrypt what matters before it arrives: client-side encryption for backups covers backup tools, and unlocking LUKS remotely covers whole drives.

10. How long drives and local items last

  • Drives of a hold that lapses: held 7 days, wiped after. Cancelling or reinstalling at your request wipes them too.
  • Items in your browser: as long as you leave them there (section 5).

11. Your options

Basalthold works without any email address. Cancelling a hold from the dashboard erases its drives. For questions about what we hold on your account, email [email protected] quoting an order reference, not your account number.

12. Account security

Treat the account number as login and password combined; a password manager suits it. You log in as root over SSH: paste a public key at checkout and password logins stay off, or leave it empty and receive a temporary root password with the server, to replace at your first login. The private half of your SSH key belongs on your computer only, and Basalthold staff have no use for it.

13. Children

Accounts are for adults aged 18 or over. Records about children are not knowingly kept.

14. Revisions

Version of 2 November 2026. A revised policy gets a new date at the top of this page. Questions go to [email protected].