DeskVexa Privacy Policy

Last updated: October 12, 2026

DeskVexa is a Chrome browser extension that replaces the new tab page with a workspace for organizing tabs, saved links, folders, workspaces, pinned items, imported Chrome bookmarks, and Chrome tab groups.

This Privacy Policy explains what information DeskVexa handles, how that information is used, where it is stored, and when information is sent to third-party services.

1. Information DeskVexa handles

DeskVexa handles information needed to provide its browser-organization and tab-management features. This may include:

• Browser tab information: tab titles, URLs, window identifiers, tab-group information, and Chrome's tab access-time metadata used to show open tabs, the current window, duplicate groups, and stale tabs.
• Saved workspace information: workspace and folder names, colors, emojis, saved link titles and URLs, notes, pinned status, and ordering.
• Chrome bookmark information during user-initiated import: bookmark titles, URLs, and bookmark-folder structure for the Chrome bookmark folders the user selects to import. DeskVexa reads this information only to perform the import requested by the user. Imported bookmarks are copied into DeskVexa workspaces and folders; DeskVexa does not modify or delete the original Chrome bookmarks.
• DeskVexa activity information: click counts and last-opened timestamps for saved links, recent DeskVexa search terms, and other settings used to provide features such as Frequent items and search history.
• Ticker preferences: the symbols the user chooses to display in the optional market ticker.
• Imported or exported DeskVexa data: when the user chooses to import or export a DeskVexa JSON file, the file is processed locally by the extension and/or downloaded to the user's device.

DeskVexa does not require a DeskVexa account and does not collect names, email addresses, passwords, payment information, health information, or precise location information through the extension.

2. How DeskVexa uses this information

DeskVexa uses the information above only to provide and improve its user-facing browser workspace and tab-management features, including:

• organizing saved links into workspaces and folders;
• displaying and managing open tabs;
• showing the current browser window;
• identifying duplicate and stale tabs;
• creating, displaying, and managing Chrome tab groups;
• importing Chrome bookmark folders selected by the user into DeskVexa workspaces;
• displaying pinned and frequently used items;
• remembering extension settings and recent DeskVexa searches; and
• allowing user-initiated backup, import, and clean-copy export operations.

DeskVexa does not use browsing or bookmark data for advertising, profiling, creditworthiness, lending, or data-broker purposes.

3. Chrome bookmark import

The Chrome bookmarks permission is an optional permission. DeskVexa requests it only after the user starts Import Chrome Bookmarks from either Settings → Import / Export or the Data menu. Both entry points open the same importer.

When the user starts an import, DeskVexa reads the Chrome bookmark tree to show selectable top-level bookmark folders and bookmark counts. Only the folders the user selects are copied into DeskVexa.

During import:

• each selected top-level Chrome bookmark folder becomes a DeskVexa workspace;
• supported bookmark URLs and their titles are copied into DeskVexa;
• nested Chrome bookmark folders are represented as DeskVexa folder paths;
• unsupported non-HTTP/HTTPS bookmark URLs are skipped;
• duplicate URLs within the same imported destination can be skipped; and
• the original Chrome bookmarks are not modified, moved, or deleted.

After import, the copied bookmark titles, URLs, and folder names are stored as ordinary DeskVexa workspace data and follow the same storage behavior described below.

4. Storage and Chrome Sync

DeskVexa stores its data using the Chrome extension storage APIs.

When the stored data is small enough and Chrome Sync is available, DeskVexa uses chrome.storage.sync. If Chrome Sync is enabled in the user's browser, Chrome may sync that information to other Chrome browsers where the same user is signed in.

If the data is too large for DeskVexa's sync-storage strategy, or a sync write fails, DeskVexa falls back to chrome.storage.local, which stores the data locally in the browser profile.

DeskVexa does not operate a DeskVexa-owned backend server for storing workspace data.

Users should not use DeskVexa notes or saved fields to store passwords, authentication tokens, or other highly sensitive secrets.

5. Third-party services and external requests

DeskVexa currently uses the following third-party resources:

Google Favicon Service

DeskVexa uses Google's favicon service to display website icons. To request a favicon, DeskVexa sends the hostname/domain of a saved link or displayed open tab to Google's favicon service over HTTPS. DeskVexa does not send the URL path or query string to the favicon service for this purpose.

Google may also receive standard network information associated with the request, such as an IP address and browser/request metadata, according to Google's own practices.

Google Fonts

DeskVexa loads fonts from Google Fonts. These requests may provide Google with standard network information such as an IP address and browser/request metadata.

TradingView

If the optional ticker is enabled, DeskVexa embeds a TradingView ticker in a sandboxed iframe. TradingView receives the ticker configuration needed to display the selected market symbols and may receive standard network information associated with the iframe request.

Links opened by the user

DeskVexa contains links to the DeskVexa website, the DeskVexa support page on Buy Me a Coffee, and the user's email application through a mailto: link. These destinations are opened only when the user chooses them, and their own privacy practices apply after the user leaves the extension.

Chrome bookmark data is not sent to DeskVexa's website, Buy Me a Coffee, Google Favicon Service, Google Fonts, or TradingView as part of the bookmark-import process.

6. Sharing and sale of information

DeskVexa does not sell user data.

DeskVexa does not transfer user data to advertising platforms, data brokers, or other information resellers.

The limited third-party transfers described above are used only to provide visible extension features, such as favicons, fonts, and the optional ticker.

Because DeskVexa does not maintain a DeskVexa-owned server containing users' workspace data, DeskVexa personnel do not have routine access to users' saved workspace, bookmark-import, or browsing information.

7. Data retention and deletion

DeskVexa data remains in Chrome extension storage until it is removed by the user, reset through DeskVexa, or otherwise removed by Chrome.

DeskVexa provides controls to clear click/frequent history, restore default data, and clear all DeskVexa data. Imported bookmarks become DeskVexa workspaces and can be deleted from DeskVexa without deleting the original Chrome bookmarks.

Data stored in chrome.storage.local is cleared when the extension is removed. Data stored through Chrome Sync is managed by Chrome Sync and the user's Google/Chrome settings.

Exported DeskVexa JSON files remain wherever the user saves them until the user deletes them.

8. Security

DeskVexa does not transmit workspace data to a DeskVexa-owned server.

Third-party requests described in this policy use HTTPS. DeskVexa relies on Chrome's extension storage mechanisms for local and synced storage and does not add separate application-level encryption to the workspace data stored through those APIs.

9. Chrome Web Store Limited Use disclosure

DeskVexa uses information obtained through Chrome APIs only to provide or improve its disclosed browser workspace, bookmark-import, and tab-management features.

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

DeskVexa does not use or transfer user data for personalized advertising, does not sell user data, does not use user data for creditworthiness or lending purposes, and does not permit human access to user data except where permitted by the Chrome Web Store User Data Policy.

10. Changes to this policy

This policy may be updated when DeskVexa's features or data practices change. The date at the top of this page identifies the latest revision.

11. Contact

Questions, privacy concerns, feature requests, or other feedback can be sent to:

[email protected]

Project website: https://deskvexa.com