An external link also creates a network request. Inspect the information sent before relying on assumptions. MAKE A SHORT INVENTORY Choose a public page, search and your own test account area. List external navigation and third-party resources for each. Use invented test values rather than real customer addresses or recovery codes. WHAT THE HEADER CONTROLS MDN explains that Referrer-Policy governs information in Referer. no-referrer omits that header; origin limits it to the origin without path or query. These are different disclosure levels to choose deliberately. INSPECT THE REQUEST Open the developer tools network panel and examine a controlled navigation. Record the policy, actual Referer and expected result. Do not retain full logs containing private data. If the outcome surprises you, check the individual link settings and the page response. THIS DOES NOT CLEAN THE URL A referrer policy does not remove a secret from the link itself, browser history or internal logs. Separately agree what information belongs in an address at all. After a change, test important navigation and analytics without promising complete anonymity. After choosing a domain in the catalogue, add this review to the launch plan. A short table of navigation, expectation and result explains the decision better than a generic “privacy configured” checkbox. Image: a new AI photoillustration for this article; a conceptual scene, not a documentary photograph. Domain catalogue: https://domainevery.com/en/domains Primary sources: https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Referrer-Policy
