Privacy Policy
1. Overview
"Open Bookmarks in New Tab" is a Chrome extension that automatically opens bookmarks in a new tab instead of replacing your current tab. This privacy policy explains what data the extension handles (and does not handle) and why each permission is required.
2. Data Collection
Preferences (enabled/disabled state, tab focus, position, and popup
language) use chrome.storage.sync and may sync through
Chrome according to your browser settings. IDs and original URLs of
bookmarks awaiting delayed marking use chrome.storage.session
to protect native bookmark editing and recover pending work. Modified
bookmark URLs may also sync through Chrome's bookmark synchronization.
3. Permissions and Justifications
The extension requests the following permissions. Each one is essential to the extension's core, single purpose. No permission is used for data collection or tracking.
| Permission | Why It Is Needed |
|---|---|
| bookmarks |
Required to read and modify bookmark URLs by adding a
newtab@ username prefix. This prefix is the
mechanism that allows the extension to identify
bookmark-triggered navigations and redirect them to new
tabs. When the extension is disabled, all bookmark URLs
are restored to their original state.
|
| tabs | Required to create new tabs when a bookmark is clicked, and to manage tab focus and position (end of tab bar or right of current tab). Also used to determine the current tab's index for correct placement. |
| webNavigation |
Used to detect marked main-frame navigations via
onBeforeNavigate and correlate their completion
or cancellation with the source tab.
No browsing history is collected or stored.
|
| declarativeNetRequest |
Used to redirect requests containing the
newtab@ username marker to an internal
cancel.html endpoint. The service worker returns
an empty HTTP 204 response with an HTML content type to stop
navigation without deliberately creating a download.
Only URLs with the specific prefix are matched — no
other web traffic is affected.
|
| storage |
Used to persist user preferences using
chrome.storage.sync, which Chrome may sync
between signed-in devices. Stored settings
include: enabled/disabled state, focus preference, and
tab position and popup language. Pending bookmark IDs and
original URLs use chrome.storage.session for
native editing protection and worker recovery.
|
| Host permissions |
Required for declarativeNetRequest redirect
rules to function. The extension needs to intercept
requests from any URL that contains the
newtab@ username prefix (which the
extension itself adds). Without host permissions, the
redirect rules cannot match these requests. The
extension does not read, modify, or collect any page
content.
|
4. Third-Party Services
The extension does not include analytics, advertising networks, or tracking tools. Some special-domain bookmarks use a GitHub Pages redirect helper. With interception working, navigation is redirected locally before that page loads. If the helper loads as a fallback, its request URL includes the encoded bookmark destination and is sent to the hosting service. Destination websites receive normal navigation requests when opened.
5. Data Sharing
The extension does not send bookmark or browsing data to a developer-operated collection endpoint. Chrome synchronization, destination websites, and the redirect helper fallback described above may involve network transfers.
6. Data Security
Preferences and pending work use Chrome's extension storage APIs. Bookmark URLs are modified in place, so back up important bookmarks and pause the extension in its popup before disabling or uninstalling it. Pausing restores the URL markers; Chrome does not provide a pre-uninstall cleanup event.
7. Remote Code
This extension does not use any remote code. All JavaScript is
bundled locally within the extension package. There are no
external <script> tags, no remotely
loaded extension scripts, and no use of eval() or similar
functions.
8. Children's Privacy
The extension includes no age-targeted analytics or developer-run collection of children's information. Its bookmark and settings handling is described in the sections above.
9. Changes to This Policy
If this privacy policy is updated, the changes will be reflected in extension updates and on this page. The "Last updated" date at the top of this document will be revised accordingly.
10. Compliance
The use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
11. Contact
If you have any questions or concerns about this privacy
policy, please contact the developer at:
haoshen0226@gmail.com