Effective date: August 14, 2026 Last updated: August 14, 2026
Summary
refreshme does not collect, transmit, sell, or share personal data or browsing data. It has no telemetry, no analytics, no accounts, and no servers.
What stays on your device
- Your watches, refresh settings and preferences are stored in Chrome’s
extension storage (
chrome.storage.sync), which Chrome may sync across your own signed-in browsers. This data never touches any server of ours — we do not have servers. - Page snapshots are stored locally (
chrome.storage.local) as a short hash plus a small excerpt, only for the pages you asked refreshme to watch, and only so a change can be detected. They never leave your device.
Requests refreshme makes
- The pages you watch. A tab watch reloads the page you configured in its own open tab — exactly as if you had opened it yourself. A background watch (Pro) fetches the page directly from your browser on the schedule you set, with no open tab needed; cookies are included only for sites you granted access to, the same as a normal page load would send. If the address you gave redirects elsewhere, refreshme follows it as your browser would, but reads the destination page only when you granted access to that site too; otherwise nothing of it is read and the watch simply reports that the address redirects off-site. Either way there is no intermediary and no vendor of ours involved, and the page content itself never leaves your device — only a short hash and excerpt are kept locally (see “What stays on your device” above).
- Webhook alerts (Pro, optional). If you configure a webhook URL, refreshme posts your alert to that URL. It is your URL; nothing is sent anywhere else.
- Licensing (Pro). If you purchase refreshme Pro, the extension talks to
exactly one host of its own:
api.polar.sh— the payment provider (Polar, our merchant of record) — to activate, periodically re-validate and, if you choose, deactivate your license key. Activating sends the license key you entered plus a random label the extension generates (it identifies nothing about you — no hostname, no OS, no profile name); re-validating and deactivating send the license key plus the activation id Polar returned at activation. Every one of these requests also carries refreshme’s own static Polar organization id, so Polar knows which seller’s key it’s checking — that id identifies refreshme, not you, and never changes between installs or users. None of these requests ever contains browsing data, page contents, or your watch list.
On the free tier, with no watches configured, the extension makes no network requests at all.
Purchases themselves happen on Polar’s checkout pages and are governed by Polar’s privacy policy. refreshme never sees your payment details; the extension stores only your license key and its validation status.
Permissions
refreshme requests the minimum permissions each feature needs. Site access is optional and per site: it is requested only when you turn on something that needs to run inside a page (watching a page, sub-30-second refresh, scroll preservation, pause-while-typing, the countdown overlay, auto-click). Basic auto refresh and “reload all tabs” need no site access at all. Notification alerts use Chrome’s own notification system (the “notifications” permission); they are created locally and nothing about them leaves your device. If you configure a webhook (Pro), that same alert is also posted to your URL — see “Requests refreshme makes” above. Sound alerts (Pro) play through Chrome’s offscreen-document mechanism (the “offscreen” permission); the sound is a short tone generated locally, and nothing about it leaves your device.
Contact
Questions: mt@le-max-app.com
Changes
If this policy ever changes, the updated version will be posted on this page with a new “Last updated” date.