How DockSpark Keeps Your Browser Setup Local

Profile configuration belongs on your Mac. Here is how DockSpark approaches local data, permissions, and the boundaries between them.

Local by default

DockSpark stores its profile configuration locally on your Mac. There is no DockSpark account to create and no cloud service required to remember which profiles you have added.

This keeps a personal workflow detail where it is most useful: beside the apps and profiles it describes.

Permissions with a purpose

macOS Accessibility access lets DockSpark identify the Dock icon under your cursor and position the profile panel beside it. Some browser actions may also trigger a macOS Automation permission prompt.

These permissions are controlled by macOS, can be reviewed in System Settings, and can be revoked whenever you choose.

What DockSpark does not need

A profile launcher does not need to read the pages you visit or inspect the content inside your browser. DockSpark focuses on the small boundary between the Dock and the browser launch action.

• No DockSpark cloud account.
• No browsing telemetry. TelemetryDeck receives only privacy-friendly usage events, never profile names or page content.
• No need to upload your profile configuration.

Clear boundaries build trust

Utility apps feel best when their scope is easy to explain. DockSpark helps you select a browser profile, then gets out of the way.

We will continue documenting any new capability that changes how data or permissions are handled before it becomes part of the product.