Private Windows Belong Next to Your Profiles

A private window is not another browser. It is a session you do not want mixed into Work or Personal — and that choice is easier at the Dock than in a menu.

A private window is a different kind of start

Private or incognito browsing is not a second browser. It is a session that should not reuse the cookies, history, and sign-ins sitting in a named profile.

The usual path is late. You open Chrome, notice you are still signed in, then go looking for a new incognito window. By then you have already touched the session you meant to avoid.

Named profiles and private windows do different jobs

Keep Work and Personal as profiles you return to. Use a private window when this visit should not land in that history.

The two choices are easier to tell apart when they sit in the same Dock panel. You are not opening a browser and deciding afterward. You are choosing the kind of session first.

When a private window is the wrong tool

If you will need the bookmarks, extensions, or signed-in account tomorrow, a named profile is the better boundary. A throwaway window is a poor substitute for a durable work or personal setup.

Private browsing is a better fit when:

• You want to check a site without the current account.
• You do not want this visit stored in everyday history.
• Borrowing Work or Personal would mix in something you intend to discard.

It is also not anonymity. The browser still talks to the network; your employer, school, or the site itself may still see the visit. DockSpark only asks the browser to open the private or incognito window. The browser keeps its own rules for history, cookies, and extensions.

Put the command where you already click

Safari can open a private window from the same hover panel as your profiles. Supported Chromium-based browsers can expose their incognito action there as well. The useful part is not a new keyboard shortcut. It is that the command sits next to Work and Personal, at the Dock icon you were going to click anyway.

The first time a browser action needs it, macOS may ask for Automation permission. The steps are in the private browsing docs.