When personal data appears in a web address
Web addresses travel through histories, logs and messages. Confidential query parameters can acquire extra copies along the way.
An address carries data
A URL question mark often precedes search terms or filters. An email address in that position reaches the destination server. HTTPS protects transport but does not remove the value from histories or logs. Copied links also retain the complete parameter.
Example: an appointment confirmation
A fictional portal appends a surname and visit reason to a confirmation link. Forwarding it to reception places both details in a chat. A neutral reference would suffice for navigation. Confidential details could appear inside the application after an appropriate access check.
The process at a glance
- InputInvented test data
- AddressVisible parameters
- CopiesHistory and logs
Checking the whole chain
A test with invented details covers the address bar, redirects and error logs. POST forms do not automatically prevent recording either. What matters is the content participating systems store. A documented filter and inspection of actual output reveal more than the HTTP method alone.
