Automater Lite Cloud Capture — Extension Privacy Policy

Last updated: 2026-08-17

This policy covers the Automater Lite Cloud Capture browser extension (Chrome, Manifest V3) — the companion that saves AI chat threads you have open into Automater Lite on the same computer. It does not cover Automater Lite, Automater Desktop or the Automater.AI website; those are covered by the main Privacy Policy. This policy is part of Automater.AI’s privacy documentation (Automater.AI is a product of WEBRULON LLC).

The short version

What the extension reads: only the AI chat thread you explicitly save — and, if you turn on optional auto-capture, a provider thread you open on a site you have granted. Nothing else.
Where it goes: to Automater Lite on your own computer, at 127.0.0.1, and into your local Lite archive. Chat transcripts never go to Automater servers.
What is never collected: no analytics, no telemetry beacons, no browsing history, no cookies, passwords or provider login tokens.

The extension uses captured chat content only to provide its single purpose: saving the AI conversation you choose into your local Automater Lite archive. A saved chat is full message text — whatever you typed and whatever the model returned, which may include names or other personal information. We do not try to strip that, and we do not sell it, use it for advertising, or use it to train a model.

What the extension reads

After you pair the extension with Automater Lite, you can save a Claude, ChatGPT, Grok or Perplexity thread that is already open in your browser. When you click save, the extension reads that tab’s conversation — the page address, the title, and the full message list — and sends it to Lite.

Auto-capture (optional, requires Automater Lite PRO or a valid guest license) works the same way but without the click: when you open a provider thread on a site you have explicitly granted, Lite can archive it automatically. It is off by default, you must turn it on, and Chrome asks for the site permission separately. Declining keeps manual save working.

The extension does not read your browsing history, does not watch other tabs, and does not sweep everything you visit. It does not log you into chat sites and does not export cookies, provider tokens or localStorage authentication. If Lite is not running, save simply fails — the extension does not queue chat text in the browser to retry later.

Where the data goes

The only destination for a captured thread is Automater Lite on this computer, over loopback (http://127.0.0.1 on the port Lite advertises). The request carries the scoped pairing token (so Lite knows it is you) and the transcript. It does not go to automater.ai, api.automater.ai, the chat providers, or any other remote host.

There is no Automater cloud copy of these chats, and no Automater cloud inbox.
Automater employees do not receive a copy. Humans at Automater do not read your chats unless you paste one into a support ticket yourself.
Lite’s audit logs record that a submit happened (provider, source, accepted or rejected) — not the message bodies.
The only Automater-server interaction connected to auto-capture is this: your copy of Automater Lite — not the extension — checks your PRO entitlement or guest license with Automater’s account servers when needed. Those checks carry account and license status, never chat content.

After Lite accepts a submit, the transcript is written into Lite’s local archive on your machine — the same archive Recent sessions and the Session library read. Vaulted threads stay vaulted: a re-save of a vaulted session is skipped, not silently stored.

What we never collect or do

No analytics or telemetry beacons, to Automater or to third parties
No browsing history
No provider cookies, session tokens, passwords or localStorage authentication
No payment card data
We do not sell, rent or broker chats
We do not use chats for advertising or retargeting
We do not train Automater or a third party on your saved chats
We do not allow Automater staff to browse your archive

We may disclose data if required by law, or if you send it to us yourself for support.

Permissions

The extension requests these permissions:

storage — keeps the pairing state and your preferences (auto-capture toggle, enabled providers) in this browser profile. Not transcripts.
activeTab / scripting — after you click save, read the thread in that tab. Not a persistent script on every site.
Host http://127.0.0.1/* — the extension’s only network destination: Automater Lite on this computer.

If you enable auto-capture, Chrome additionally asks for optional permissions, per site, only when you turn it on: host access to that provider (claude.ai, chatgpt.com, grok.com, perplexity.ai) and webNavigation, used to notice when a page you have granted finishes loading so an open thread can be saved. None of these are required to install the extension or use manual save.

Data retention and deletion

Data	Retention	How to delete
Pairing token and extension preferences	Until you unpair or uninstall	Unpair or rotate in Lite Settings (invalidates the token); uninstalling removes the extension’s storage
Saved transcripts	Until you delete them in Lite	Delete the session in Lite’s Session library, or reset Lite’s data

Uninstalling the extension does not delete the Lite archive. There is no Automater-hosted copy of these chats to delete.

Security

Pairing uses a scoped extension token; the Desktop/Lite master daemon token is rejected on the extension port. Capture payloads are size-capped and treated as untrusted data — never rendered as HTML. The extension contains no remotely hosted code (Manifest V3).

Children

The extension is not directed at children under 13. Do not pair a child’s browser or save a child’s chats.

Changes to this policy

If we ever send capture data anywhere other than 127.0.0.1, or add required provider host permissions, we will update this policy and ship a new extension version, and Chrome will re-prompt for any new permissions.

Contact

Questions about this policy: hello@automater.ai · support