Incognito and VPNs: Cookies, History and Travel Privacy

Choose the privacy question before opening a window

Private browsing is useful when you want a separate browser session for a particular task. A traveller might research an accommodation option without mixing it into the usual browser session, or open a second account on a personal laptop. Start by naming that task. Keeping a local history list tidy, separating website sessions and checking a VPN connection are different objectives that need different observations.

Use our explanation of what a VPN can and cannot hide for the wider connection and privacy questions. This guide concentrates on the browser session: what happens to temporary site data, what a sign-in tells a service and which files can remain after the window closes. That narrower view makes an everyday travel decision easier to check.

Understand temporary cookies and session boundaries

Google explains that Chrome Incognito starts a separate session, temporarily uses cookies and site data, and removes that session data when all Incognito windows are closed. Opening another Incognito window continues the existing private session. Chrome also does not automatically sign you into your usual website accounts in that mode. See Google’s Incognito instructions for its current behaviour.

Mozilla’s Firefox guidance describes cookies as holding information such as website preferences and login status. Cookies in private windows are separate from regular-window cookies and are discarded at the end of the private session. Private browsing also excludes visited pages from the ordinary browsing history. Read Mozilla’s Private Browsing documentation for Firefox-specific controls and exceptions.

The practical question is whether you have ended the relevant session. Closing one tab while leaving other private windows open is not the same observation as finishing the whole session. Before handing a device back or beginning a different task, follow your browser’s documented session-ending command and check the remaining windows. Menu names and available controls can vary by browser and version.

Treat a website sign-in as identifying yourself

A private window can be a convenient place to start a separate task, but once you sign in, treat the activity as belonging to that service account. For example, opening a reservation in a private window is not a reason to expect the accommodation provider to forget the reservation or stop recognising the signed-in account. Decide which account you intend to use before approving the sign-in.

Google warns that websites can still gather information in Incognito, including when you are not signed in. Mozilla likewise says Private Browsing does not make a user anonymous online. A browser mode label therefore cannot establish that a destination has no information about you. Keep account actions, local browser storage and the connection question distinct when evaluating a privacy claim.

Our passkey and travel sign-in checklist covers preparing account access and recovery before departure. Use that preparation for your own devices. Do not turn a quick booking check on someone else’s computer into an improvised credential setup simply because the window is private.

Check downloaded files and saved items separately

Both Google and Mozilla document an important exception: downloaded files and newly saved bookmarks can remain after private browsing ends. Firefox also notes that a cleared download-list entry is different from removing the actual file. A booking PDF saved during a private session therefore needs its own file-handling decision.

Consider the complete task before using a shared machine. Will you need to download an itinerary, open an attachment or print a page containing personal details? Where would that file be stored? If you cannot confidently manage those steps, use a personal device or ask for an appropriate alternative. Closing a browser window is not a substitute for understanding the file you deliberately saved.

On your own laptop, check the destination folder after a download and keep the document only where you intended. Leave the original reservation or service record intact unless you actually want to change it. Removing a local copy, signing out and cancelling a booking are separate actions; choose the one that matches your purpose.

Record browser mode and VPN status independently

For a connection question, note the VPN app’s displayed state separately from whether the browser window is private. Then identify what the website actually reported. A sign-in prompt, a remembered preference and an IP-location estimate are different pieces of evidence. Changing several settings at once makes it harder to tell which observation changed.

If a location result is the concern, consult the VPN IP location and device location guide. Do not interpret a familiar account name as an IP measurement, or a location label as proof that the site has forgotten your account. Record the specific result you were trying to understand rather than making a broad claim that a privacy tool has failed.

Finish the travel task deliberately

Before leaving a travel workspace, review the account you used, the files you saved and whether the intended browser session has ended. Keep that short review alongside the public Wi-Fi travel checklist so the local-device and network questions both get attention. A neat browser history is only one part of finishing the task.

For a longer stay, the digital nomad connectivity guide provides a broader arrival routine. Keep the useful distinction simple: decide what you want private, identify the relevant browser or app control, and check the result for that task. Avoid treating any window icon, VPN status label or illustration as a guarantee that every record of your activity has disappeared.