Create a Public‑Sharing Browser With No Autofill or Saved Sessions

Using a shared computer should not mean sharing your personal information. If a browser stores logins, form history, cookies, or tabs, the next user can accidentally (or intentionally) see parts of your digital life. This guide shows you how to create a “public‑sharing” browser experience on common browsers—one that does not keep autofill data, passwords, history, or session info—along with portable and kiosk options for libraries, classrooms, workplaces, Airbnbs, family computers, or pop‑up events.

What “No Autofill or Saved Sessions” Really Means

When you prepare a browser for public sharing, your goal is to prevent the browser from storing:

• Autofill and passwords: Saved logins, addresses, payment methods, and search suggestions.
• History and open tabs: The next person should not see what you did or resume your session.
• Cookies and local storage: These can keep you signed in or reveal sites you visited.
• Downloads and cache: Files, cached media, and site data that can expose information.

There are two reliable paths: use an ephemeral profile (Guest or Private windows) every time, or configure a dedicated profile with saving disabled and automatic clearing on exit. The first is simpler; the second is useful when you need custom policies (e.g., extensions) while still preventing data retention.

Quick Wins: One-Click “Ephemeral” Modes

Most browsers include a mode that does not retain history or cookies after closing:

• Chrome/Chromium: Use Guest mode. It does not use extensions and erases browsing data when you close all Guest windows.
• Microsoft Edge: Use Guest or InPrivate. Guest creates a temporary profile; InPrivate lets you stay within your own profile but does not save history and clears data on exit.
• Firefox: Use Private Window. It blocks history saving and clears cookies when the private window is closed.
• Safari (macOS/iOS/iPadOS): Use Private Browsing. It prevents history saving and isolates tabs, though some settings persist at the system level.

If you control a shared device, set the default shortcut to open directly into Guest/InPrivate/Private mode, and avoid logging into browser accounts (Google/Microsoft/Firefox Account) that could reintroduce syncing or autofill.

Step-by-Step: Configure Each Major Browser

Google Chrome (Desktop)

1. Use Guest Profile for Shared Sessions: Click your profile picture > Guest. This creates a temporary profile with no saved data or extensions. Close all Guest windows to purge the session.
2. Disable Autofill in a Dedicated “Public” Profile (optional):
   • Create a new local profile (don’t sign into a Google account).
   • Go to Settings > Autofill. Turn off Passwords (disable “Offer to save passwords” and “Auto Sign-in”), Payment methods (toggle off saves/fills), and Addresses and more.
   • Open Privacy and security > Cookies and other site data. Choose “Block third-party cookies” and enable “Clear cookies and site data when you close all windows.”
   • Open Privacy and security > Security and keep Safe Browsing on for protection, but avoid account sign-in.
3. Force Ephemeral Mode via Shortcut (Windows/macOS/Linux): Edit or create a shortcut that launches Guest by default:
   • Windows: Right-click the Chrome shortcut > Properties > Target. Append: –guest
   • macOS: In Terminal: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome –guest
   • Linux: Modify the .desktop Exec line with –guest

   Note: Some managed environments may restrict flags.

4. Disable “Continue where you left off”: Settings > On startup > select “Open the New Tab page.”

Microsoft Edge (Desktop)

1. Use Guest or InPrivate: Click your profile icon > Browse as guest or press Ctrl/Cmd+Shift+N for InPrivate. Guest is ephemeral and avoids existing extensions.
2. Create a “Public” Profile with Session Clearing (optional):
   • Make a local profile without signing into a Microsoft account.
   • Go to Settings > Privacy, search, and services and enable “Clear browsing data on close.” Select Browsing history, Download history, Cookies and other site data, Cached images and files, Passwords, Autofill form data.
   • In Profiles > Passwords, disable “Offer to save passwords” and “Sign-in automatically.”
   • In Cookies and site permissions, block third-party cookies.
3. Launch InPrivate by Default: Right-click the shortcut > Properties > append –inprivate to the Target.

Mozilla Firefox (Desktop)

1. Use Private Windows: Press Ctrl/Cmd+Shift+P to open a Private Window that won’t save history or cookies after closing.
2. Dedicated “Public” Profile with Strict Clearing:
   • Create a new profile using about:profiles and do not sign in.
   • Go to Settings > Privacy & Security. Under History, choose “Never remember history” or “Use custom settings” and uncheck history and form/autofill saving.
   • Enable “Delete cookies and site data when Firefox is closed.”
   • In Logins and Passwords, uncheck “Ask to save logins and passwords.”
   • Set Enhanced Tracking Protection to Strict for additional isolation.
3. Always Launch in Private Browsing: In Settings > Privacy & Security, set History to “Never remember history,” which effectively uses permanent private browsing.

Safari (macOS and iOS/iPadOS)

1. Private Browsing: On macOS, choose File > New Private Window. On iOS/iPadOS, tap the Tabs button > [N] Tabs > select Private and open a new tab.
2. Reduce Autofill: macOS: Safari > Settings > Autofill and uncheck options for Contacts, Credit Cards, and Usernames/Passwords (manage passwords in System Settings > Passwords if needed). iOS/iPadOS: Settings > Safari to disable Autofill and prevent fraudulent website warnings from storing data.
3. Block Cross-Site Tracking: Enable “Prevent cross-site tracking” and disable “Allow websites to check for Apple Pay” if using shared devices.

Portable and “Non‑Saving” Browsers You Can Carry

If you move between computers, a portable browser on a USB drive can enforce your no‑save rules without relying on the host computer’s settings:

• Portable Firefox and Chromium builds: They store profile data within the USB folder so nothing persists on the host machine beyond temporary OS caches.
• Configure your portable profile as above: disable passwords and autofill, block third‑party cookies, and enable “delete on close.”
• Always eject the drive properly to ensure all temporary data is cleared from the OS cache and written back to the portable profile before removal.

Portable setups are ideal for conference kiosks, classrooms, or family computers where you can’t permanently change local settings.

Kiosk and Public Access Setups

For devices that many strangers will use, consider kiosk mode. It locks the machine to a specific browser session and can auto‑reset between users.

• Chromebook Managed Guest Session: In managed environments, you can deploy a Managed Guest Session that wipes data at logout and restricts settings and apps.
• Windows Assigned Access (Kiosk): Assign Microsoft Edge in Kiosk mode to run a single app with InPrivate and session reset on sign‑out.
• macOS Guest User + Automatic Logout: Use a Guest account and configure automatic log out and login window controls; combine with Safari Private Browsing or a third‑party browser set to private by default.

Whichever you choose, test that the session resets cleanly: browse, sign in to a test account, close the session, and confirm no tabs, cookies, or credentials remain.

Turn Off Browser Autofill and Password Saving

A public‑sharing browser should never prompt to save passwords or autofill forms. Confirm the following across all browsers you plan to use:

• Disable “Offer to save passwords” and “Auto sign‑in.”
• Disable addresses, phone numbers, and payment method autofill.
• Clear saved autofill data that might already exist in the profile.
• Do not sign the browser into a cloud account; syncing can reintroduce autofill, history, and payment methods.

Auto‑Clear Data on Close

To ensure nothing lingers after someone closes the browser, enable automatic clearing:

• History and download history cleared on exit.
• Cookies, local storage, and cached files cleared on exit.
• Form data and site permissions reset on exit when available.

Combine this with private/guest modes to reduce mistakes like opening a normal window by accident.

System‑Level Habits That Prevent Leaks

Browsers are only part of the picture. Operating systems and apps can reveal traces too. Build these habits into your public‑sharing setup:

• Never download sensitive files (PDFs, statements) on shared machines. If you must, use a temporary cloud viewer, then sign out and delete from trash. Empty the browser’s download list and the OS Downloads folder.
• Avoid extensions in guest/public profiles. Extensions can store data, log keystrokes, or sync settings.
• Use webmail in basic mode rather than installing native mail or calendar apps.
• Manually sign out of every website and close all browser windows. Do not rely solely on auto‑clearing.
• Clear the clipboard after copying passwords or IDs. On macOS, copy a harmless word; on Windows, run cmd /c “echo off | clip” or copy a blank space.
• Avoid leaving crash reports or recent files by closing apps cleanly and restarting the device between users if possible.
• Use distinct OS accounts (Guest or standard non‑admin) for shared sessions to limit cross‑user exposure.

Recommended Default Settings for a Public‑Sharing Profile

• Start in Guest/Private/InPrivate automatically via shortcut flags.
• Disable password saving and autofill for forms and payments.
• Block third‑party cookies; consider blocking all cookies for specific kiosks.
• Enable “clear on close” for history, cookies, cache, downloads, and form data.
• Disable “Continue where you left off.” Always open a fresh tab.
• No browser sign‑in or syncing to cloud accounts.
• No extensions unless strictly required and vetted.
• Safe Browsing/Enhanced Protection enabled to reduce malicious sites.

Testing: Prove Nothing Is Saved

Before letting others use the setup, run a quick test:

1. Open the browser and visit a few sites. Sign into a disposable test account.
2. Close all windows. Reopen the browser.
3. Confirm there is no history, you are signed out everywhere, there are no saved passwords or form suggestions, and the startup page is fresh.
4. Check the Downloads folder and clear anything left behind.

Repeat this test after updates or policy changes to ensure settings remain intact.

Privacy Limits to Understand

Even with perfect no‑save settings, some data can still leak:

• Network traces: Your ISP, network admin, or router logs can record domains you visit.
• Operating system caches and DNS: Temporary caches may briefly store lookups until reboot or timeout.
• Account sign‑ins: If you stay signed into a website’s own “remember me,” it can restore your session even after cookies clear, using device fingerprints or server‑side sessions. Always log out.

For sensitive tasks on unfamiliar networks, consider a trusted personal device or a secure network connection rather than relying solely on shared computers.

When to Add Monitoring and Identity Protection

If you must use public or shared computers for banking, healthcare, or other sensitive accounts, your risk increases—even with careful browser hygiene. Add ongoing monitoring for early warning signs of misuse, such as new account openings, unusual credit pulls, or identity‑related activity you did not initiate. A dedicated service that tracks your credit and identity signals can help you respond faster if something slips through. Learn more about practical monitoring options here: SmartCredit for privacy, credit monitoring, and identity protection.

Frequently Asked Questions

Is private browsing enough?

Private/Guest mode prevents local history and cookie storage after closing, which solves most shared-device risks. Still, you should disable autofill and avoid downloads, and remember that networks can log your activity.

Should I clear data manually every time?

Set the browser to clear on close, but also build the habit of logging out of websites and closing all windows. Manual clearing is a safety net if someone accidentally used a normal window.

Can I use extensions in a public profile?

Best practice is no. If you must, use only essential, reputable extensions and test that they do not retain data between sessions.

What about shared mobile devices?

Use Private or Incognito tabs, avoid saving passwords to the device keychain, and clear recent apps. On iOS and Android, consider separate user profiles or Screen Time/Family Link restrictions where available.

Conclusion

Creating a public‑sharing browser with no autofill or saved sessions is straightforward: rely on Guest/Private modes, disable password and form saving, clear data on close, and avoid downloads and extensions. For kiosks and shared environments, add kiosk or guest OS user accounts and test that sessions fully reset. These practical steps dramatically reduce the chance that your personal information, accounts, or browsing history are exposed to the next user—and they take only a few minutes to set up.