Before sharing a browser exposure report, choose what to leave out
Choose the minimum useful browser-report fields for a support question, and understand what a share link reveals.
A browser exposure report can help explain a problem without requiring someone to take remote control of your device. It can also include more information than the recipient needs. Before copying a link into a support ticket or public forum, decide what question the snapshot should answer.
CheapVPN’s browser exposure report lets you choose the fields in a shared snapshot. It is a view of one connection and browser at one moment, rather than a certificate of anonymity or a complete VPN leak test.
Start with the question, not the full report
Write one sentence describing the problem. For example: “The website chooses the wrong country when I connect through my VPN.” That is a narrower task than asking strangers to inspect every detail of your device.
For that question, the estimated country, the time of the observation and whether the VPN was connected may be enough for an initial conversation. Your full public IP address, screen dimensions and raw browser headers do not automatically help. If a support team requests something more specific, ask what it will establish and use the organisation’s genuine support channel.
IP location is an estimate. DB-IP’s own guidance explains that accuracy varies with the network and that its free datasets have reduced accuracy compared with commercial products. A city label should therefore be treated as a clue to investigate, rather than proof of your physical location or someone else’s identity.
A fictional support example
Imagine Rowan is asking why a streaming website presents a different country. This is a teaching example, not a test of a provider or a claim that a particular service can be accessed.
| Possible detail | First message | Reason for that choice |
|---|---|---|
| Estimated country | Include if relevant | Describes the unexpected result |
| Broad browser and device labels | Include | Gives the support team basic context |
| Full public IP | Leave out initially | Ask whether the team needs this exact address |
| Estimated city and coordinates | Leave out | The question is country selection, not precise location |
| Raw user agent and allowed headers | Leave out | Add only for a defined diagnostic reason |
| Account name, password or recovery code | Never add to the message | These are not needed to describe this observation |
Rowan’s accompanying text could read: “At 19:10, with my VPN connected, this report estimated country A while the website displayed country B. I used the same browser for both observations. What further information would help you investigate?” The country letters deliberately avoid suggesting a real result.
The message records conditions without asserting which system is wrong. A VPN exit, mobile network or relay can affect what an IP-based service sees. Different services may use different reference data.
Use the snapshot preview before generating a link
Open the report and select Create share link. The sharing panel begins with broad labels and omits the full IP address. Optional boxes add the public IP, estimated city, estimated coordinates, raw user agent and allowed request headers, or more detailed device and connection values.
Leave those boxes unticked unless they serve the question you wrote. Read Snapshot preview, then choose Generate share link. Review the result before choosing Copy link. You can also decide that a short written description is enough and share no report at all.
Do not put a work-device snapshot in a public discussion without checking your organisation’s rules. Combining otherwise ordinary details can reveal more context than you intended.
A long encoded link is still readable
This feature puts the selected snapshot after the # in the URL. MDN explains that this fragment is processed by the browser and is not included in the HTTP request for the page. That explains the transport mechanism; it does not make the snapshot secret.
The report’s link is encoded, not encrypted. Anyone holding the complete link can read the included information. A recipient can forward it, and messaging tools or browser history may retain it. The feature has no expiry or revocation control. Deleting your own message cannot guarantee that every copy disappears.
Make a comparison useful without oversharing
If support asks for a comparison with the VPN disconnected, first consider whether you are comfortable disclosing information about that connection. Use the same browser, note the time and label each observation clearly. Do not post an unmasked before-and-after pair publicly by default.
Finish with a small checklist: one question, one intended recipient, only relevant fields, preview checked, connection state labelled, and no credentials in the message. A smaller report with clear context is often easier to investigate than a large unexplained snapshot.
Sources
Related reading

Does Proton VPN include email at your own domain?
Separate a VPN subscription, paid Mail features and domain registration before comparing the cost of a Proton bundle.
Read feature
VPN split tunnelling: choose an exception and check its limits
Understand which traffic leaves the VPN, why platform and DNS behaviour matter, and how to record a narrow check without assuming complete privacy.
Read feature
Free VPN or cheap paid VPN? Decide what is worth paying for
Proton and Windscribe both offer a lasting free plan, but they ration different things. Match their limits to an ordinary week of use before paying for an upgrade.
Read feature