QuickLaunch — Privacy Policy

Last updated: September 2026 · Applies to QuickLaunch 2.6

      Short version: QuickLaunch stores your shortcuts, snippets, and settings locally in Chrome. The developer does not receive this data.
    

1. What data QuickLaunch stores

QuickLaunch saves the following data using Chrome's built-in chrome.storage.local API, which stores data only on your device and is never shared with anyone:

Your shortcut titles, URLs, and favicons
Your workspace names, organisation, and last selected workspace
Your snippets (titles, text, and tags), including an unfinished new-snippet draft until you save or reset it
Your appearance and behaviour preferences (theme, grid size, hotkey settings, etc.)
Usage counts for "Most-Used" sorting (stored as URL → click count pairs)

This data remains in Chrome's local extension storage until you edit it, import a replacement backup, reset the extension, or uninstall it. You can review and delete shortcuts, snippets, and usage counts in Settings. Chrome extension storage is not encrypted; do not save passwords or other secrets as snippets.

2. External network requests

QuickLaunch does not send saved data to the developer, analytics services, or an icon service. When you choose to open a saved shortcut or click a link in a snippet, Chrome makes the normal request to that destination site.

Shortcut icons are read from your browser's own favicon cache using Chrome's built-in extension favicon API (_favicon/). These are local lookups inside your browser — no request leaves your device, and no third party is contacted or informed about which sites you have saved. Sites your browser has no cached icon for display a generic or letter-based icon instead.

Snippet previews show text and code formatting without loading remote images or other remote resources.

There are no analytics, no telemetry, no crash reporting, no advertising, and no external APIs of any kind.

      Note on earlier versions: QuickLaunch 2.5 and earlier fetched icons from Google's public favicon service (google.com/s2/favicons), which meant Google received a request identifying a saved site's domain each time the popup displayed that icon. Version 2.6 removed this entirely and ignores any icon addresses stored by earlier versions.
    

3. Permissions used and why

storage — To save and load your shortcuts, snippets, and settings locally on your device.
activeTab — To read the current tab's URL and title when you click "Add current tab" or use the right-click menu. Only accessed after you explicitly trigger the extension.
contextMenus — To add a right-click "Add to QuickLaunch" menu item on pages and links.
notifications — To show a brief desktop notification when a shortcut is added or already exists via the right-click menu.
tabGroups — To name and colour the tab group created when you click "Open all shortcuts in a tab group". The extension uses the IDs of tabs it just opened to create the group; it does not store those IDs.
favicon — To read shortcut icons from your browser's local favicon cache. This performs no network request and reveals nothing to anyone outside your device.
clipboardWrite — To copy snippet text to your clipboard when you click a snippet or press its number hotkey.

Our use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements. Data accessed through Chrome APIs is used only to provide QuickLaunch's described features. We do not sell user data or use it for advertising.

Optional permission (off by default, never requested at install):

clipboardRead — Used only when a snippet you are copying contains the {{clipboard}} placeholder, to insert your current clipboard text into the snippet. You must turn this on yourself under Settings → Behavior, and you can revoke it there at any time. While it is off, {{clipboard}} simply expands to nothing. Clipboard content is never stored, logged, or transmitted anywhere — it goes straight back onto your clipboard as part of the expanded snippet.

4. Data you export

QuickLaunch lets you export your data as a JSON file saved to your device. This file is created and downloaded locally. The developer never receives a copy of your exported data.

5. Children's privacy

QuickLaunch is not directed to children under 13. It stores only the shortcuts, snippets, and preferences the user chooses to save, as described above; the developer does not receive that data.

6. Changes to this policy

If this policy changes in a way that involves new data practices, we will update the "Last updated" date above and describe the changes clearly. The extension will not begin sending data externally without an explicit update to this policy and the extension itself.

7. Contact

If you have questions about this privacy policy, please open an issue on the QuickLaunch GitHub repository.