Privacy Policy

Loop — Auto Refresh, Click & Page Monitor

Last updated 12 August 2026

Loop collects nothing. There is no account, no analytics, no telemetry, and no server belonging to this extension. The contents of the pages you watch are never transmitted anywhere.

What stays on your device

Everything Loop remembers is written to Chrome's local extension storage on your own machine:

• Your settings, and the per-site profile saved for each origin you configure
• The keywords, regular expressions and selectors you enter
• Autostart URL patterns and any schedules attached to them
• Any custom alert sound you add
• A short local log of recent autostart decisions, shown in Settings so you can see why a page did or did not start by itself

None of this is synced to any account or sent off the device. Uninstalling the extension removes it.

What Loop reads, and why

To do its job Loop reads the text of the tab you have explicitly started it on: that is how it can tell you when your keyword appears. That reading happens entirely inside your browser. The page text is compared against your keywords and then discarded — it is not stored, and it is not sent anywhere.

Loop acts only on tabs where you have pressed Start or which match an autostart rule you created yourself. It does not read or act on your other tabs.

Webhooks — the only outbound network request

Loop makes no network requests of its own. The single exception is a webhook, which exists only if you add an endpoint URL, and which posts only to the address you supplied.

The payload is metadata about the match, never page content:

• the keyword, pattern or selector you wrote that matched — Loop sends back your own search term, not the text it found in the page
• the match type (found, lost, or changed)
• the page's URL, title and hostname
• a timestamp

Where that data then goes is governed by whoever runs the endpoint you chose — Telegram, Discord, Slack, ntfy, or your own server. Loop has no relationship with those services and receives nothing back from them.

Custom alert sounds from a URL

If you point an alert at an audio file hosted on the web, your browser fetches that file from the address you gave, once, and caches it locally. That request carries nothing about you or the pages you are watching beyond what any ordinary browser request for a file contains.

The debugger permission

Loop's clicking feature delivers real mouse input through the Chrome DevTools Protocol, which is what makes a click indistinguishable from your own. This requires the debugger permission, and it is why Chrome shows a "being debugged" banner while clicking is switched on.

Loop attaches the debugger only to the specific tab you have enabled clicking for, uses only the mouse-input command, and detaches the moment the job stops. No page data is read through it.

Children

Loop is a general-purpose browser utility, is not directed at children, and collects no personal information from anyone.

Changes

If this policy ever changes, the revised version will be published at this address with a new date above. Since Loop collects nothing, a change here would mean a change in the extension itself, which would also appear in the changelog.

Contact

Questions or a problem with the extension: open an issue on GitHub.