WISPHOST / PRIVACY

Privacy, by design.
Only what we need.

WispHost is built around limited collection, private access and clear choices. This page explains what we use, why we use it and when it is removed.

Last updated: November 3, 2026.

01

The short version

WispHost collects the minimum information needed to provide an account, support a service and complete a customer-requested order. A hosting account uses an email address and a password. We do not require identity documents or a standard KYC process for hosting.

Domain registration is different: a domain order can require accurate registrant details, which are sent to the registrar or registry when their rules require it. WHOIS privacy is included for life across the extensions in our catalogue, while fields that a registry must publish can still remain public.

02

Personal data

For a WispHost account, we keep the email address you provide, a one-way password hash, recovery material and the session records needed to keep your access secure.

  • Hosting account: email and access credentials, without identity documents or banking details.
  • Domain registration: the registrant, administrative and technical fields you submit for that domain, limited to registration and support purposes.
  • Orders and support: the information needed to prepare an order, reconcile a crypto payment or answer a support request.

We do not intentionally collect browser fingerprints, advertising identifiers or a visitor IP tied to your customer account.

03

Account and access

Your WispHost account uses your email address and password. Passwords are stored only as Argon2id one-way hashes; we cannot read the original password. Sessions are rotated and can be revoked when you sign out, change security details or remove the account.

Account recovery uses the recovery code shown during the recovery flow. Keep it private: it is designed to help you regain access without turning your password into a support ticket. No email activation link is required.

04

Website tracking

Analytics and advertising

There is no third-party analytics platform, advertising pixel, social embed or behavioural advertising profile on the WispHost website.

Cookies

Only cookies that are necessary for the service are used: a session cookie for the client area and a small locale preference when you choose a language. They are not used to follow you across unrelated websites.

Fingerprinting

We do not use canvas, WebGL or other browser-fingerprinting techniques to identify visitors.

05

Server monitoring

We do not routinely inspect customer traffic or content, perform deep packet inspection, keep per-user DNS or connection histories, or build an activity profile from bandwidth usage. Network operations may use aggregate availability and DDoS signals to protect the platform; those signals are not a record of an individual customer’s activity.

06

Payment data

WispHost accepts cryptocurrency for the services presented on the site. To reconcile an order, we may retain the selected asset and network, the amount, the receiving address, the transaction hash once available and the internal order reference. We do not ask for card or bank details and do not need the sender’s private wallet information.

07

Data retention

  • Account and billing records are kept while the relationship is active and removed within 30 days after account closure, subject to a legal or accounting obligation.
  • Support messages are removed when a request is closed or resolved. If our team is waiting for your reply, an unanswered request is removed after three days.
  • Temporary carts and quotes expire automatically. Service data is handled according to the applicable service lifecycle and is not retained longer than necessary after termination.
  • Backups and operational copies follow the same minimisation and deletion controls; they are not used to create a permanent customer profile.
08

Disclosure, rights and changes

Who receives information

We do not sell customer information or share it for advertising. A domain registration necessarily sends the required registrant fields to the registrar and registry responsible for the extension. A payment or infrastructure provider may receive only the information needed to deliver the service. We may disclose information when a legal obligation, a security incident or a serious network abuse requires it.

Your choices

Where data-protection law applies, you can ask to access, correct, delete, restrict or receive the personal data we hold about you. You can delete your account from the client area or contact support for a question. Domain registries may require certain records to be retained or published even after WHOIS privacy is enabled.

Policy updates

We will update the date at the top of this page when the policy changes. The current version explains the practices used by the WispHost site and services, and does not replace any service-specific terms shown during an order.

WISPHOST / PRIVATE BY DEFAULT

Clear access.
Limited data.

If something in this policy is unclear, contact the WispHost support team from your client area.

Contact support
WISPHOST INFORMATION