Privacy Policy — Auto Refresher Pro
Extension version: 3.0.2 · Effective date: 2026-07-24
Auto Refresher Pro ("the extension") is a browser productivity tool that automatically reloads or re-fetches a web page on a schedule you set, optionally clicks an element ("Auto Click"), watches for a keyword or content change ("Keyword Monitoring"), and can auto-start on pages matching patterns you define ("URL Rules"). This policy explains what data the extension touches and what it does with it.
What data the extension handles
- Tab URLs — read to check your URL Rules and whitelist/blacklist, to show status in the popup, and to run Auto Refresh/Auto Click jobs. Stored locally as part of your active jobs and, if it occurs, your activity history (see below).
- HTTP status information — the extension listens for the HTTP status code (or network error) of the main-page navigation on tabs you're running a job on, so it can detect a failed/error page for the "notify on error" and "stop on error" options. This status information is kept only in memory for the current browser session (not written to storage) and is never transmitted anywhere.
- Page content — read locally in the page you're actively working with, only when a feature needs it: the element picker, Auto Click, DOM/CSS keyword monitoring, or a "watch for a change" hash comparison. This content is used in-browser to decide whether to refresh, click, or notify you, and is not sent anywhere by the extension beyond the request you configured.
- XHR/background response data — when a refresh job is set to "XHR / Background" mode, your browser fetches the URL you configured directly. The response (HTML or JSON, per your setting) is read locally to extract a value (via a CSS selector or JSON path), check it against your keyword rule, and optionally update the page's DOM. The raw response itself is not stored or transmitted anywhere beyond that direct fetch.
- Settings you configure — refresh intervals, Auto Click selectors and timing, URL Rules, saved profiles, and your whitelist/blacklist.
- Notifications — the extension can show local desktop notifications (via Chrome's own notification API) for: an installation welcome message, a detected error page, a detected content/keyword change, and an Auto Click selector that matched nothing. These notifications are generated and shown entirely on your device; no notification data is sent to the developer or any third-party notification service.
- A local activity log (Statistics) — timestamps, tab URLs, and a short description for refreshes, clicks, keyword/content-change hits, and errors.
None of the above is collected by, or transmitted to, the developer. If you enable "Sync across devices," a subset of it (your settings only, not the activity log or in-memory HTTP status — see below) is mirrored through your own Google/Chrome account, not through any server the developer operates.
What the extension stores, and where
-
Your settings — default refresh interval, URL Rules,
Auto Click configs, saved profiles, and your whitelist/blacklist —
are stored locally on your device using Chrome's extension storage
APIs (
chrome.storage.local). - Activity history / Statistics — a local, capped log (most recent 300 entries) of refreshes, clicks, keyword/content-change hits, and errors, used to power the Statistics panel in Settings. This never leaves your device and is not part of sync.
-
Sync across devices (opt-in, off by default) — if you
turn this on in Settings, only your own settings (default interval,
URL Rules, profiles, whitelist/blacklist — never history, tab state,
or in-memory HTTP status) are mirrored through your Google/Chrome
account using
chrome.storage.sync, the same first-party mechanism Chrome uses for bookmark and extension-settings sync. This data is stored and transmitted by Google as part of your Chrome sync account, not by the developer of this extension, and is never sent to the developer or to any other third party.
What happens when the extension fetches a page
When you use "Full Page" refresh mode, your browser reloads the tab exactly as if you'd pressed the browser's reload button. When you use "XHR / Background" mode, your browser fetches the URL you configured directly — that request goes straight from your browser to that URL and never passes through any server operated by the developer of this extension.
Browser permissions this extension uses
storage— to save your settings, profiles, and activity history locally (and to your Chrome sync account if you opt in).tabs— to read a tab's URL and reload it for Auto Refresh.alarms— to schedule refresh/click ticks reliably, including across browser idle periods.scripting— to run the element picker, Auto Click, and content/keyword checks in the context of the page you're working with.notifications— to show the local desktop notifications described above.webRequest— to read the HTTP status code of a tab's page load, used only for the error-detection features described above; not used for tracking or analytics.- Host permission (
<all_urls>) — so Auto Refresh, Auto Click, and Keyword Monitoring can be used on any site you choose to run them on, since the extension can't know in advance which sites you'll want to use it with.
Data retention and deletion
- History entries older than the most recent 300 are automatically dropped, on a rolling basis, so the log never grows without bound.
- In-memory HTTP status information is cleared automatically when a tab closes or the browser restarts; it is never written to disk.
-
Uninstalling the extension removes all data it stored locally
(
chrome.storage.local), per Chrome's standard extension-storage behavior. If you had sync enabled, your synced settings remain in your Chrome/Google account's sync data until you clear them there (Chrome Settings → Sync) or disable sync for this extension before uninstalling. - You can also clear the local activity log at any time from the Statistics panel in Settings.
No analytics or advertising
Auto Refresher Pro does not use analytics services, tracking pixels,
advertising SDKs, or any third-party data-collection library of any
kind. The webRequest permission is used solely for the
local error-detection feature described above, not for tracking,
profiling, or advertising.
The developer does not receive your data
Nothing described in this policy — tab URLs, page content, HTTP status information, XHR response data, settings, notifications, or activity history — is transmitted to, collected by, or accessible to the developer of this extension. Sync data (when enabled) is transmitted only through your own Google/Chrome account, and full XHR/background fetches go directly from your browser to the URL you configured.
Children's privacy
Auto Refresher Pro is a general-purpose browser productivity tool that is not directed at children. It does not knowingly collect information from anyone, of any age, beyond the on-device handling described above, and does not transmit any of it to the developer or a third party.
Changes to this policy
If this policy changes, the effective date above will be updated and the revised policy will be posted at this same URL. Material changes will also be noted in the extension's Chrome Web Store listing / changelog.
Contact
Questions about this policy or the extension can be sent to:
hamza.devx@gmail.com