← Back to Arlo

Privacy Policy

Arlo for Chrome · Last updated: October 1, 2026

Summary

Arlo has no backend and no analytics. We do not collect, store, sell, or share any of your data. Your settings and API key stay in your browser. Page content leaves your browser only to reach the model endpoint you configured, and only when you run a task.

What Arlo handles

What Arlo does not do

Your model provider

The endpoint you configure (for example OpenAI, Anthropic, a proxy, or a local server) receives your prompt and any page content Arlo sends with it. That provider’s own privacy policy and terms govern how it handles that data. If you want everything to stay on your machine, point Arlo at a local model server.

Permissions

PermissionWhy Arlo needs it
activeTabRead the page you opened Arlo from, only after you click the toolbar icon.
scriptingRun the page reader inside the current tab to extract its text.
sidePanelArlo’s interface is the Chrome side panel.
storageSave your profiles, API key, and preferences in the browser.
tabGroupsPut every tab Arlo opens into an “Arlo” group so you can see and close them.
Optional site accessNothing is granted at install. Chrome asks for (a) the origin of your model endpoint, or (b) all pages, if you choose to let Arlo read without a toolbar click. You can revoke either in Chrome at any time.

Your control

Children

Arlo is a general-purpose tool and is not directed at children under 13.

Changes to this policy

If this policy changes, the updated version will be posted on this page with a new date. The full history is public in the repository.

Contact

Questions or concerns? Open an issue at github.com/kaija/arlo-extension/issues.