Vibe Migration — Privacy Policy

Last updated: March 18, 2026

Vibe Migration ("the Extension") is a developer tool that analyzes and migrates web pages to Adobe Experience Manager Edge Delivery Services (AEM EDS). This privacy policy describes what data the Extension collects, how it is used, and how it is stored.

Data We Collect

Page Content (Collected When You Analyze a Page)

When you click "Analyze Page," the Extension captures:

This data is transmitted to Cloudflare Workers operated by the Extension developer for LLM-based page decomposition. It is used solely to identify page structure and UI components for migration.

Cookies (Collected When You Migrate a Block)

When you trigger a block migration, the Extension reads cookies for the active tab's domain using the chrome.cookies API. These cookies are sent to a sandboxed worker so it can access the page with the same authenticated session as your browser. Cookies are used only for the duration of that migration task and are not stored persistently on the server.

Brand Assets (Collected When You Extract a Brand Kit)

The Extension reads fonts, colors, spacing, and favicon references from the active page's DOM. This data is packaged into a ZIP file and committed to a GitHub repository as part of the migration output.

Extension Settings (Stored Locally)

User preferences (environment prefix, workers domain, API secret, theme) are stored in chrome.storage.local on your device. These settings are never transmitted to any server.

Monitoring Events (Transmitted During Migration)

The Extension sends anonymized usage events (event type, duration, block count, error codes) to a monitoring worker for migration quality tracking. These events do not contain page content, cookies, or personally identifiable information.

How Data Is Processed

All server-side processing occurs on Cloudflare Workers infrastructure. Specifically:

Data Destination Retention
Visual tree + URL Playwright Worker (LLM decomposition) Not persisted after response
Cookies Sandbox Worker (session replication) Discarded after task completes
Screenshots R2 object storage Retained for migration reference; deletable on request
Migration output (HTML, CSS, images) GitHub repository Controlled by the repository owner
Monitoring events D1 database Retained for analytics; no PII

What We Do NOT Do

Permissions Explained

Permission Why It Is Needed
activeTab Access the current tab's URL and DOM when you activate the Extension
tabs Read tab URL and title to display the current page identity in the side panel
storage Save extension settings locally on your device
sidePanel Display the migration UI in Chrome's side panel
scripting Inject the visual tree capture and element picker into the active tab
cookies Read cookies for the active tab's domain to replicate authenticated sessions during migration

Your Control

Contact

For questions about this privacy policy or data handling, contact:

Changes to This Policy

We may update this privacy policy from time to time. Changes will be posted to this page with an updated "Last updated" date.