Privacy Policy
Applies to the ContentChanger browser extension (“the extension”) and this website (contentchanger.ayworks.win). Last updated: 2026-09-17.
Short version
The extension sends no telemetry and does not collect your edits for the developer. Edits are applied inside the browser tab, but this is not an offline or private workspace: image URLs trigger requests to their hosts, and page scripts can observe and transmit edits. Feedback you choose to send is separate from extension editing.
Data the extension collects
The extension has no collection backend, analytics or telemetry. It reads and modifies page content to provide editing, but does not send that content to the developer. The surrounding website and external destinations remain separate:
- Text, image and form edits are applied to the live document. Page scripts can observe these changes, including pasted content and native form input, and may save or transmit them under that site's own practices. Avoid using sensitive information in mockups.
- Applying an image URL makes the browser request that image from its host, which receives normal request information such as an IP address. This is not developer telemetry.
- Clipboard content is read when you explicitly paste, for example into the “Replace image” panel. Content inserted into the document is subject to the same page-script visibility as other edits.
- Reload clears the extension's in-tab changes, but cannot undo information a page has already saved or sent.
- Companion screenshot links open an external store listing with its own privacy practices. Screenshot capture is provided by a separate tool, not built into ContentChanger.
Data stored on your device
The extension stores two small screenshot reminder flags in your browser's own extension storage (chrome.storage.local):
- whether you dismissed the screenshot tip (ctShotHintDismissed),
- whether the end-of-session reminder was shown (ctSummaryShown).
The extension does not transmit these flags. Removing the extension deletes its local storage. The packaged welcome tab opens on installation only, not on updates or first activation, and uses no welcome storage flag.
Permissions the extension requests
- activeTab — lets the extension act on the tab you activated via its toolbar icon, keyboard shortcut or context-menu item. Access is temporary, limited to that tab, and granted by your explicit activation; no host permissions are requested, so the extension never has standing access to any site.
- scripting — injects the editor into the tab you activated, so the on-page editing can start when you ask for it.
- storage — keeps the two local flags described above on your device.
- contextMenus — shows the right-click menu entries (“ContentChanger”: edit this text, replace this image, undo, discard all).
Remote code
The extension contains no remote code. All logic, styles and interface elements ship inside the extension package and run locally.
This website and the feedback form
This static website does not include analytics scripts. Loading it sends normal browser requests to our hosting provider, Cloudflare, which may process request metadata to deliver and secure the site. When the feedback form is enabled, your message and optional email address are delivered to us through Web3Forms, the message-delivery processor. It also receives normal request metadata. We use feedback to investigate issues and reply, not for marketing. When supplied in the feedback link, the form includes the extension version to help reproduce issues.
Data sharing
We do not sell or rent your feedback or use edits for developer analytics. Feedback is handled by us and the delivery processor named above. Image hosts, visited websites and linked services handle their own requests and any information visible to them under their own privacy practices.
Changes to this policy
If the extension's behaviour ever changes, this policy is updated in the same release. The current policy is always available at this address.
Contact
ayworks.win — hello@ayworks.win, or use the feedback form.