Effective date: September 4, 2026

Worklink is a Chrome extension for saving, organizing, searching, and reopening work-related web links. This policy describes how Worklink handles user data.

Information handled by Worklink

Worklink handles only information needed for its link-management features:

• URLs and page titles that the user explicitly saves;
• aliases, notes, tags, collections, folder relationships, colors, and favorite status entered or selected by the user;
• timestamps for creation, editing, and the most recent time a saved link was opened from Worklink;
• the user's tile or list display preference; and
• files the user explicitly selects for local import, including Worklink JSON backups, browser bookmark HTML, and Notion HTML or Markdown.

When the user invokes the extension on the current tab, Worklink uses Chrome's activeTab capability to read that tab's URL and title and prefill the save form. Worklink does not read all open tabs, the full browser history, page bodies, cookies, passwords, authentication data, or file contents from linked destinations.

Storage and retention

Saved link data and the display preference are stored locally in chrome.storage.local for the current Chrome profile. Worklink does not use Chrome Sync or a developer-operated cloud service.

Data remains until the user edits or deletes it, removes the extension, deletes the Chrome profile, or Chrome otherwise clears the extension's local storage. JSON backup files are created only when the user requests an export and are saved through the browser's normal download process. Backup files are not encrypted by Worklink; users are responsible for storing them appropriately.

Use of information

Worklink uses locally stored information only to provide its user-facing features: saving, displaying, classifying, searching, importing, exporting, and reopening links, as well as remembering the selected display mode.

Sharing and external communication

Worklink does not send saved data to the developer, sell it, share it with third parties, use it for advertising, or use it for analytics or profiling. Worklink has no account system, analytics SDK, advertising SDK, telemetry service, or developer-operated backend.

Opening a saved link causes Chrome to navigate to the user-selected destination, which results in the ordinary network request to that destination. Worklink requests site icons through Chrome's internal favicon capability. It does not directly contact website favicon URLs or third-party favicon services; Chrome may manage or cache icons as part of normal browser behavior.

Imported files are read locally and are not uploaded. Exported JSON is generated locally. Worklink accepts only HTTP and HTTPS destination URLs and rejects URLs containing embedded usernames or passwords.

Permissions and host access