How data is handled here
Revised
Data we keep about you
None. HushViewer has no user accounts at all. Without a sign-up or a login, there is nothing about you for us to hold. The site is a set of static pages, and we keep no history of your lookups. One exception is covered below. Apart from the visitor-origin tally explained below, nothing on this site measures visitors for us; advertising is dealt with in a section further down. Should that change, this notice gets updated first and its date moves.
A single anonymous measurement exists: the origin of visitors. When a page has stayed open briefly, HushViewer is told which website referred the visit (hostname only, no complete link), where the visitor landed, the visitor’s country, and optionally a small campaign tag. These feed daily totals. Neither cookies nor identifiers nor IP addresses are stored for it. A browser that asks not to be tracked, through DNT or through GPC, is left out, and totals are dropped after roughly 90 days. Returning visitors are told apart from new ones through a day stamp that HushViewer asks your browser to remember. What reaches us is a label such as new, today again, yesterday or longer ago. No profile can be built from it, and when you empty the browser’s website storage it disappears. DNT and GPC visitors never get one.
When a handle lands in the address
The handle always sits in the page address: each search typed into the box loads a fresh /?u=-plus-handle page, and a link somebody shared looks the same. Our host and CDN receive that address just as they receive every other one, and their access logs can keep it. Beyond those logs, HushViewer writes down no lookups.
On your own device
Your browser keeps a short list of handles you recently opened, in its local storage. It is never sent to us. The Clear link wipes it. Wiping site data or closing a private window has the same effect. No other device can see it. One more local item: a service worker keeps some of HushViewer’s pages on hand for offline use. It holds no handles or profiles.
How a lookup travels
A lookup is answered by an outside data source, but your browser never talks to it. Your browser puts the request to our server, which relays just the handle to that source; that source pulls the open profile from Instagram, then answers us. Its whole view of you is a handle arriving from our server’s IP: no IP of yours, no browser fingerprint, no clue which site you were on. How long it retains the handle is up to that source, not us.
Pictures and clips you open are downloaded by your browser from Instagram’s content servers, skipping our machines entirely. Your IP address is known to those servers, just like any server that hands you a file, though not the site you are reading. One exception runs the other way: profile photos, the tiny highlight thumbnails and anything you press Save on are piped through our server. A VPN or a privacy-minded browser reduces what any server, ours included, can learn from a request.
A quiet human test on every search
Before any lookup runs, our CDN slips a human check into the page: Cloudflare’s Turnstile. It weighs details of the browser and the network it comes from, IP address included, decides whether a person is at the keyboard and hands our server a token good for one use. Usually it stays out of sight; a long burst of lookups can make it ask for a click. The same CDN puts a ceiling on lookups per connection over a short stretch.
Advertising
HushViewer is meant to be paid for by ads. They are chosen and served by an advertising company outside our walls, whose policies decide how it handles data; we have no say in that. Expect that company, plus the advertisers behind it, to leave cookies, comparable IDs or small tracking beacons in your browser each time an ad shows.
- What the company sees: the address your connection uses, your browser type with its interface language, how large the window is, which page holds the ad, and whether anyone looked at or tapped it. Ads can be tailored using your earlier visits to this and other sites.
- Your say: visitors in the European Economic Area, the United Kingdom and Switzerland are shown a consent window first, where tailored ads can be declined. Elsewhere, blocking third-party cookies or browsing privately cuts the same tracking down.
- Searched handles: we never hand a name you looked up to the company. A result page does carry the name in its address (
/?u=), though, and an ad script running there can read that address like any script on the page.
Who else is involved
- The company hosting the site’s pages.
- The CDN in front of it, which blocks abusive traffic, runs the human test on every search and holds your IP address briefly while doing so.
- The outside data source described above, which gets handles from our server and nothing about you.
- Instagram’s content servers, from which your browser pulls pictures and clips.
- The advertising company that supplies the ads and shows the consent window.
Beyond these five, nothing is passed on. We do not sell or share data.
Your rights
You may ask us what we hold on you and have it fixed or erased. The honest answer will be that we hold nothing linked to you, and we will confirm that in writing. Responsibility for HushViewer lies with the people who run it, and hello@hushviewer.com is how you reach them. You can also take it to the privacy regulator where you live.