What does the Style Panel collect?

What stays on your device

Two things, both held locally through Chrome's own storage and neither ever transmitted:

• Panel position, size and preferences.
• Whether you have seen the first-run tour.

How it talks to Lovable

The extension runs only on Lovable's own domains and their preview hosts. When you save a change, it writes to your project using the Lovable session already open in your browser — the same way Lovable's editor does.

Your project code, credentials and session tokens are read and used only inside your browser, are sent only to Lovable's own services, and never reach me or any third party.

What it does not collect

• Personal information of any kind — no name, no email, no account.
• Browsing history or the content of pages you visit.
• Your project code or file contents.
• Authentication tokens or credentials.
• Usage analytics or telemetry.

Why each permission exists

• storage — remember panel position, size and onboarding state locally.
• scripting — inject the panel itself, and the element selector into the preview frame.
• tabs — tell whether the tab you are on is a Lovable project.
• webNavigation — notice when a preview frame loads, so the selector can attach to it.
• activeTab — act on the Lovable tab you are currently using.
• Host access to lovable.dev, *.lovableproject.com and *.lovable.app — the extension runs on Lovable and nowhere else. It has no access to any other site.

Changes

If a future version ever introduces optional analytics, this page changes first, the collection is off by default, and it is disclosed plainly. The date at the top changes whenever the text does.

Questions

Raise anything at the feedback tracker, or write to yar@yar.website.