Privacy Policy

1 Our Principles

Bookmark Shortcut is designed around three commitments:

• Privacy policies should be human-readable and easy to find.
• Data collection should be limited to the absolute minimum needed to make the extension work — and in our case that minimum is zero.
• The extension should behave exactly as a user would expect: it opens bookmarks, nothing more.

2 Information We Collect

We collect no information about you. There is no account registration, no sign-in, no usage tracking, and no crash reporting. The extension does not communicate with any external server operated by us or by any third party on our behalf.

The only data that exists as a result of using this extension is your shortcut configuration (key → URL mappings), which is stored locally in your browser via chrome.storage.sync. This data never reaches our systems because we have no systems.

3 How the Extension Works Locally

To be transparent about what happens inside your browser, here is what each component does:

• Background service worker — runs in Chrome’s background and manages the two-step shortcut chord (activation combo + trigger key). It reads your stored mappings from chrome.storage.sync and calls chrome.tabs.create or chrome.tabs.update to open the bookmark. No data leaves the browser.
• Content script — injected into every webpage to listen for keyboard events. When it detects the activation combo it notifies the background worker. Key events are processed in-memory and are never stored or transmitted.
• Popup — the configuration interface. It reads your Chrome bookmarks (to let you pick one) and reads/writes your shortcut mappings to chrome.storage.sync. It does not make any network requests.

4 No Backend

Bookmark Shortcut has no backend infrastructure. There are no servers, no databases, no API endpoints, and no cloud functions operated by the developer. The extension is a purely client-side tool that runs entirely within Chrome on your device.

The website you are reading now (bookmark-shortcut.web.app) is a static informational page hosted on Firebase Hosting. It does not collect any information from visitors and does not interact with the extension in any way.

5 Permissions Explained

The following permissions are declared in the extension’s manifest.json. Each one is required for a specific feature; none are used for data collection.

• bookmarks — grants read-only access to your Chrome bookmark tree. Used exclusively in the popup so you can search and select a bookmark when creating a shortcut. The extension never creates, modifies, or deletes any of your bookmarks.
• storage — allows the extension to read and write to chrome.storage.sync. This is where your key→URL shortcut mappings are saved. Only the data you configure is stored; nothing else is written.
• scripting — required to programmatically inject the keyboard listener content script into tabs that were already open at the time the extension was installed. Without this, the shortcut would only work on pages opened after installation.
• favicon — allows the extension to load website favicons through Chrome’s internal /_favicon/ API. Used in the popup to display the icon of the website next to each shortcut entry so the list is easier to scan visually.
• <all_urls> (host permission) — the content script that listens for keyboard events must be able to run on every webpage you visit, because a shortcut should work regardless of which site is currently open. This is the most sensitive declaration in the extension: it means the content script is present on all pages. The script does nothing other than listen for the specific key combination and relay it to the background worker; it never reads page content, form data, or any other information from the page.

6 Chrome Sync

Your shortcut configuration is stored in chrome.storage.sync. If you are signed into Chrome, Google may automatically sync this data across your signed-in devices according to Google’s own privacy policy. This sync is managed entirely by Chrome and Google — the extension has no control over it and no access to the synced data outside your local browser.

You can disable Chrome Sync at any time in your Chrome settings, or clear the extension’s stored data by removing all shortcuts in the popup before uninstalling.

7 Cookies and Tracking

The extension does not use cookies, tracking pixels, fingerprinting, or any other tracking technology. The website (bookmark-shortcut.web.app) does not set cookies and does not use analytics services.

8 Third-Party Services

The extension itself does not integrate with any third-party services. It makes no outbound network requests. The only external dependency at runtime is Chrome’s built-in APIs (chrome.bookmarks, chrome.storage, chrome.tabs, chrome.scripting), which are provided by the browser itself and governed by Google’s terms of service.

9 Your Rights and Data Deletion

Because we collect no personal data, there is nothing to access, correct, export, or delete on our end. Your shortcut configuration lives entirely in your browser.

To remove it completely:

• Open the extension popup and delete all shortcuts, or
• Go to chrome://extensions, find Bookmark Shortcut, click “Details” → “Extension options” and clear storage, or
• Simply uninstall the extension — Chrome will erase its storage automatically.

If you are in the European Economic Area or another jurisdiction with applicable data protection law and have questions about how your data is handled, you are welcome to contact us. Given that we hold no personal data, any such request will be resolved by confirming that there is nothing to act upon.

10 Children’s Privacy

This extension is not directed at children under 13. We do not knowingly collect any information from children. Since we collect no information from anyone, this is trivially satisfied.

11 Security

Because no user data is transmitted to external servers, the attack surface is minimal. All data stays within Chrome’s sandboxed extension environment. The extension does not eval code, does not load remote scripts, and declares a strict Content Security Policy. If you discover a security issue, please report it via the contact address below.

12 Changes to This Policy

If this policy changes materially — for example, if a future version of the extension introduces any form of data collection — we will update the date at the top of this page and note the change clearly. Continued use of the extension after a change constitutes acceptance of the updated policy. We will never introduce data collection silently.

13 Contact

Questions about this policy or about the extension’s privacy practices?

dkeycatdev@proton.me