LivePilot — Privacy Policy
Last updated: May 14, 2026
LivePilot ("the extension") is a browser-automation agent that runs inside your Chrome browser. This policy explains what data the extension handles, where it goes, and what it never does.
1. Data we store, locally
The following information is stored using chrome.storage on your own device. It is not transmitted to any server owned or operated by the developer:
Your Groq API key (used only to call api.groq.com from your browser).
Your saved workflows, session recordings, task history, and smart variables (e.g. {{email}}, {{name}}).
Your settings (model choice, human-in-the-loop toggle, screenshot toggle).
2. Data we send, and to whom
When you run a task, LivePilot sends the prompt you authored (plus the page state the AI needs to plan a step) directly from your browser to Groq, using the API key you supplied. Groq's handling of that request is governed by their own privacy policy.
LivePilot does not route data through any server owned by the developer. There is no developer-operated backend.
3. Data we never collect
No analytics, telemetry, or usage tracking.
No advertising identifiers.
No selling or sharing of user data with third parties.
No content from the following sensitive domains, which are explicitly excluded from the content script: mail.google.com, accounts.google.com, paypal.com, stripe.com.
4. Permissions, and why
activeTab, tabs, scripting, host_permissions: <all_urls> — so the agent can read and interact with the page you choose to automate, after you press Run.
storage — to keep your API key, workflows, and settings locally on your device.
sidePanel — the entire UI lives in Chrome's side panel.
5. Remote code
LivePilot does not load remote code at runtime. All JavaScript is bundled in the published package.
6. Children
LivePilot is not directed at children under 13 and does not knowingly collect data from them.
7. Changes
If this policy changes, the new version will be posted at this URL with an updated "Last updated" date.
8. Contact
Questions or concerns: please open an issue on the project's GitHub repository linked in the Chrome Web Store listing.