Browser Privacy Checklist Before Screen Sharing
A browser can leak more than open tabs. The bookmarks bar, profile name, autofill suggestions, password manager prompts, extension popups, downloads, notifications, recent searches, and account menus may all appear during a presentation.
Use this checklist before a call, recording, class, demo, or interview. It takes a few minutes the first time and becomes much faster once you keep a clean presentation profile.
Start with the browser profile and tabs
Create a profile used only for presentations. Keep work-safe bookmarks, demo logins, and approved extensions there. A separate profile reduces the chance that personal history, saved accounts, or private autofill appears when you click a field.
Close every tab that is not part of the presentation. Pinning or grouping a private tab does not hide it from a shared browser window.
Clean the browser chrome
Hide the bookmarks bar, downloads panel, side panel, and profile menu. Check the active tab title and address because both may reveal a customer, internal project, search query, or account identifier.
Review extension icons too. Password managers, wallets, developer tools, and work extensions can reveal which services or accounts you use even when their popups stay closed.
Stop notifications and autofill surprises
Turn on operating-system Do Not Disturb and block browser notifications for the presentation window. Browser notification permissions are separate from the visible page, so check both the system and browser settings.
Avoid clicking login, address, and payment fields while live. Autofill and password manager suggestions can show names, emails, card endings, account labels, and saved identities.
Inspect the page content and run a test
Close chat widgets, comments, inbox previews, customer lists, and account menus. Use demo data or blur the values that must stay visible. Scroll through the presentation path and test any menu or hover state you plan to use.
Make a 10-second recording or join from another device. The audience view is the final check. It catches crop differences, tiny readable text, and a mask that did not survive a page refresh.
- Clean profile selected.
- Only required tabs open.
- Bookmarks, downloads, and side panels hidden.
- Notifications and autofill controlled.
- Sensitive page fields blurred.
- Audience view tested.
Practical examples
Fast preflight by risk
- Personal identity: profile name, avatar, email, bookmarks, autofill.
- Work confidentiality: tab titles, customer names, internal URLs, project labels.
- Account security: password manager prompts, API keys, recovery codes, wallet extensions.
- Communication: chat widgets, comments, email previews, browser notifications.
Related guides
Official sources
Frequently asked questions
Does incognito mode make screen sharing private?
No. Incognito limits what the browser stores after the session. It does not hide visible pages, tabs, notifications, downloads, or account information from the audience.
Should I make a separate browser profile?
Yes, if you present regularly. A clean profile separates demo tabs, accounts, bookmarks, history, and extensions from personal browsing.
Can people see browser notifications when I share one tab?
Desktop notifications usually stay outside a tab share, but in-page notifications and chat toasts remain visible. Turn alerts off and clean the page itself.
Need to hide sensitive details that must stay on screen? Try Safe Screen Share.