Vibe Page Edit Assistant Privacy Policy

1. Information We Process

When you use the extension, the following information may be processed:

• Text instructions that you enter in the extension side panel.
• The URL, pathname, and inferred site information of the active page.
• Page context used for edit planning, including candidate element selectors, text snippets, tag names, ids, class names, links, image sources, partial HTML, and selected computed styles.
• Selected element context when you actively choose page elements for more accurate targeting.
• Generated edit records, including change type, selector, before value, after value, reason, run records, and browser-side apply results.
• Settings that you provide, including GitLab access token, LiteLLM API key, OpenClaw webhook URL, OpenClaw webhook token, WeCom webhook URL, pub token, and operator identifier.

2. How We Use Information

We use this information only to provide the extension's core functionality, including:

• Understanding your requested page change and generating structured candidate edits.
• Temporarily applying DOM, link, image, text, style, or HTML changes to the current browser page for preview.
• Creating a structured GitLab issue that records the user request, page context, generated changes, run records, and apply diagnostics.
• Optionally triggering a user-configured OpenClaw webhook after the GitLab issue is created.
• Optionally sending a user-configured WeCom webhook notification with the issue link and automation status.

3. Data Storage and Transmission

• The extension stores user-provided settings in Chrome extension storage so users do not need to enter them repeatedly.
• Page context and user instructions may be sent to the configured LiteLLM endpoint to generate candidate edits.
• Issue payloads are sent to the configured GitLab project API to create vibe-edit issues.
• OpenClaw webhook URL and token are used only when the user configures them and submits an issue.
• WeCom webhook URL is used only when the user configures it and submits an issue.
• The extension does not use collected information for advertising, profiling, analytics, or cross-site tracking.

4. Permissions

The extension requests permissions required to deliver its single purpose:

• activeTab: to work with the currently active page after user interaction.
• scripting: to support page-side interaction and temporary preview behavior.
• sidePanel: to provide the page-editing assistant interface.
• storage: to store extension settings such as tokens, webhook URLs, and operator information.
• tabs: to identify the active tab and send messages between the side panel and content script.
• Host permissions: to run on user-targeted pages and communicate with configured service endpoints such as GitLab, LiteLLM, OpenClaw, and WeCom webhook URLs.

5. Data Sharing

We do not sell, rent, or share your data with unrelated third parties. Information is transmitted only to services required for the extension's workflow, such as the configured LiteLLM endpoint, GitLab API, OpenClaw webhook, and WeCom webhook.

6. What We Do Not Do

• We do not publish production website changes from the browser extension.
• We do not automatically merge code or approve merge requests.
• We do not collect browsing history for advertising or analytics purposes.
• We do not use extension data for marketing, profiling, or cross-site tracking.
• We do not intentionally access unrelated page content beyond what is needed to understand and preview the user's requested edit.

7. Security Notes

• Tokens and webhook URLs should be treated as sensitive configuration. Users should remove or rotate them when access is no longer needed.
• For public or shared environments, configure HTTPS endpoints whenever possible.
• OpenClaw and WeCom webhooks are user-configured. Users are responsible for ensuring those endpoints are trusted and appropriately protected.

8. Your Choices

You may stop using the extension at any time. You may also update or remove stored tokens and webhook URLs from the extension settings, clear browser extension storage, or uninstall the extension.

9. Contact

If this Privacy Policy is updated, the revised version will be published on this page.