Privacy Policy for Extension Deck
Summary
Extension Deck is a local Chrome extension manager. It uses Chrome's extension-management APIs to display installed extensions, change their enabled state when the user requests it, and save local extension-state Profiles.
Extension Deck has no account system, external API, analytics, telemetry, advertising, cloud sync, or publisher-operated server. It does not transmit extension information, Profiles, preferences, or imported files off the user's device.
Information processed on the device
Chrome's management API provides metadata about installed browser items. Extension Deck processes the following information locally:
- Extension name, description, version, extension ID, and item type.
- Whether an extension is enabled or disabled.
- Whether Chrome allows the extension to be enabled or disabled.
- Permission and host-permission metadata that may be present in the ExtensionInfo object returned by Chrome.
Extension Deck uses item type to show only extensions, excludes itself, and uses status information to display and perform user-requested changes. It does not persist the complete installed-extension list or permission list.
Extension Deck does not read webpage content, browsing history, form input, cookies, downloads, passwords, personal communications, or open-tab content.
Information stored locally
Extension Deck uses chrome.storage.local to store:
- Profile names created by the user.
- Extension IDs included in each Profile and their target enabled or disabled states.
- Profile creation and update timestamps.
- Interface preferences such as status filter and sort order.
Search terms and the complete installed-extension list remain in memory only while the popup or manager page is open. They are not stored as Profiles or preferences.
JSON import and export
Extension Deck creates a JSON backup only after the user selects Export JSON. The file contains local Profile names, extension IDs, target states, and timestamps.
Extension Deck reads a JSON file only after the user selects Import JSON and chooses a local file. The file is validated locally. Existing Profiles are replaced only after the user confirms the operation.
Imported and exported files are not uploaded or transmitted by Extension Deck.
Data transmission, sharing, and sale
Extension Deck does not:
- Transmit processed or stored information to the publisher or third parties.
- Sell, rent, license, or share user data.
- Use information for advertising, analytics, profiling, credit decisions, or model training.
- Load or execute remote code.
Permissions
management
Used to read locally installed extension metadata and enabled states, and to enable or disable extensions only after a user action. This permission is essential to Extension Deck's single purpose as an extension manager. Extension Deck excludes itself and non-extension item types.
storage
Used to save Profiles and interface preferences in Chrome's local extension storage. It is not used for cloud sync or transmission.
Extension Deck requests no host permissions and has no content scripts or background service worker.
Retention and deletion
Profiles and interface preferences remain in chrome.storage.local until the user changes them, deletes Profiles, clears the extension's local data, or uninstalls Extension Deck. Chrome controls removal of extension storage after uninstall.
Exported JSON files remain under the user's control and can be deleted using the operating system. Extension Deck does not retain a separate copy.
Limited Use
Extension Deck's use of information received from Chrome APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Changes to this policy
If a future release changes the information processed, permissions requested, or network behavior, this policy and the Chrome Web Store privacy disclosures will be updated before publication.
Contact
Privacy questions can be sent to: kalen010901@gmail.com