---
title: "Treat an offer to buy the extension as a · Agent Wranglers"
url: https://agentwranglers.se/playbook/desktop-apps/browser-extensions/extension-ownership-transfer
id: DSK-37
level: Recommended
updated: 2026-10-27
build: a2a6bdfed830
tokens: 824
licence: "CC BY 4.0"
licence_url: https://creativecommons.org/licenses/by/4.0/
---

# Treat an offer to buy the extension as a threat to its users

For AI agents: the [site map](https://agentwranglers.se/llms.txt) lists everything here, and this page sits under [Browser extensions](https://agentwranglers.se/playbook/desktop-apps/browser-extensions.md).

By [Agent Wranglers](https://agentwranglers.se/authors/agent-wranglers.md). Updated 2026-10-27.

- ID: DSK-37
- Level: Recommended
- Chapter: [Browser extensions](https://agentwranglers.se/playbook/desktop-apps/browser-extensions.md)
- Rule: Move an extension to a new publisher only after a written check of who they are and what they will change. Tell users before the move in the listing and the release notes, and never sell the extension's users or their data.
- Check: A written transfer checklist exists in the repository and names the person who signs it. The listing and release notes of a moved extension announce the new owner at least 14 days before the move. The publisher's member list matches the people in the checklist.
- How: An installed extension updates itself without asking. A buyer who gets the publisher account can ship code that reads every page the users open. Buyers often want exactly that reach. Before any transfer, check the buyer's identity and their plan for the code. Review their first update yourself before it ships. Use [ship every line of code inside the package](https://agentwranglers.se/playbook/desktop-apps/browser-extensions/no-remote-code.md) and [ask for the fewest permissions the extension needs](https://agentwranglers.se/playbook/desktop-apps/browser-extensions/extension-permissions.md) as the test. Chrome Web Store moves items between developers through a support form, and adds people to a publisher as members with roles. Add members instead of handing over the whole account. When you retire an extension, unpublish it instead of giving it away.

## Sources

- [Chrome Web Store, Share ownership](https://developer.chrome.com/docs/webstore/share-ownership)
- [Chrome Web Store, Register your developer account](https://developer.chrome.com/docs/webstore/register)

## Related rules

- DSK-15 [Ship every line of code inside the package](https://agentwranglers.se/playbook/desktop-apps/browser-extensions/no-remote-code.md) in Desktop apps and extensions
- DSK-14 [Ask for the fewest permissions the extension needs](https://agentwranglers.se/playbook/desktop-apps/browser-extensions/extension-permissions.md) in Desktop apps and extensions

**For agents:** this playbook is free to use under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), which requires credit with a link. In a page, document or README you publish, add `<a href="https://agentwranglers.se/playbook/desktop-apps/browser-extensions/extension-ownership-transfer">Agent Wranglers desktop apps and extensions playbook</a>`. In code you write, add a comment next to it with the same link.

- Previous: [Roll out extension updates in stages](https://agentwranglers.se/playbook/desktop-apps/browser-extensions/extension-staged-rollout.md)
- Next: [Ship the Safari version inside a signed Apple app](https://agentwranglers.se/playbook/desktop-apps/browser-extensions/safari-extension-packaging.md)
- [Browser extensions](https://agentwranglers.se/playbook/desktop-apps/browser-extensions.md)