What this policy covers
HostScout is a static hosting comparison site for readers checking servers, cloud, domains, CDN, email, and related infrastructure offers. You do not create an account here. HostScout does not sell personal data. The practical privacy risk starts when you leave for a provider checkout or affiliate network.
Before you click through, assume three separate privacy zones:
- HostScout handles the page you read and the outbound click you make.
- The hosting provider handles its own checkout, account, support, billing, and renewal flow.
- The affiliate network may handle click attribution when a marked partner link is involved.
Data we do not ask for
HostScout does not require registration. HostScout does not ask for a password, payment card, tax number, server root password, SSH key, domain authorization code, or customer control panel login.
Do not send credentials in email. A hosting migration already has enough ways to go wrong without handing secrets to a comparison site.
Analytics
HostScout uses Umami analytics in cookieless mode and Yandex.Metrika for traffic measurement, click maps, link tracking, and session-quality diagnostics. The analytics setup measures page views, referrers, device classes, countries, and affiliate click events.
Yandex.Metrika may use cookies and similar browser storage. HostScout uses those signals to see which comparisons people actually read, which provider pages send outbound traffic, and where the interface needs clearer wording. HostScout does not sell personal data.
Analytics can tell us that readers compare VPS, cloud, domains, CDN, email, GPU servers, or datacenter offers. Analytics does not tell HostScout your renewal price, provider account balance, support tickets, DNS zone content, or workload details.
Affiliate and provider links
Some outbound links on HostScout may lead to a hosting provider or an affiliate network. That click can be used for attribution. It can also move you into a different privacy policy, cookie policy, billing policy, and dispute process.
Treat the provider site as the place where tracking usually becomes heavier. A checkout page may use cookies, fraud checks, payment processors, live chat tools, advertising tags, and account analytics. HostScout does not control those systems after you leave.
Affiliate attribution does not decide rankings on HostScout. A paid link does not change the privacy rule either: the seller controls the purchase flow, and you should read the seller’s policy before paying.
Email contact
If you contact HostScout by email, we use your message to answer the request and handle directly related follow-up. That includes provider corrections, legal notices, privacy questions, and reports about inaccurate hosting data.
Send the affected HostScout page URL, the provider page URL, and the date you checked the provider page when you report a correction. Do not include passwords, server access tokens, customer account numbers, or payment card details.
What to check before buying
Privacy is not separate from hosting cost. A provider that looks cheap can still be expensive if cancellation is hostile, backups are paid, egress is unclear, or support pushes every request through a tracked account portal.
Check these items on the provider site before you pay:
- Whether checkout requires an account before showing the renewal price.
- Whether the provider uses third-party payment processors, fraud checks, or live chat.
- Whether backups, snapshots, DDoS mitigation, and support tickets expose workload details.
- Whether domain registration adds WHOIS privacy by default or as a paid extra.
- Whether cancellation and refund requests must go through the same account that owns production services.
Corrections and contact
HostScout compares information that can change without notice. Provider locations, hardware inventory, control panels, domain privacy rules, backup policies, and affiliate routing can change faster than a static privacy page.
For privacy questions or corrections, contact [EMAIL]. Include only the information needed to identify the page and the issue. If a provider or affiliate network created the privacy problem, contact that provider or network as well.
Legal contact: [EMAIL]