Privacy Policy — Auto Refresh | Page Monitor

Last updated: 16 August 2026 Published at: https://autorefresh.xeviora.com/privacy Contact: privacy@xeviora.com

This document is the source for the hosted page. If you edit one, edit the other — the hosted page is frontend/src/app/[locale]/privacy/page.tsx, whose text lives in frontend/content/legal/en.json. English only, unlike the 9-language terms page: this is the URL Chrome Web Store review reads, and one authoritative copy beats nine.

The short version

The extension does its work inside your browser. We do not collect the addresses of the pages you visit, and we do not build a profile of your browsing. If you never create an account, nothing about your use of the extension reaches our servers at all.

What stays on your device

Stored with chrome.storage.local, removed when you uninstall the extension:

• Your refresh rules and monitors, including the URLs or patterns you chose to watch.
• Runtime state: how many times a rule has run, when it fires next, whether it is paused.
• A local history of monitor hits, and any values extracted from pages you configured.
• Your settings, including the start date of the local trial.

We cannot read any of this.

What reaches our servers, and only if you ask

• Account (optional): your email address, a hashed password or the identifier from the sign-in provider you chose, and session records.
• Cloud sync (optional, paid): the rules and monitors you wrote, plus a device name and identifier so you can see which machines are syncing.
• Change history (optional, paid): the hits your monitors produced, the URL of the configured page each hit came from, and a truncated text snapshot used to show what changed. Deleted after the retention period of your plan.
• AI features (optional, paid, per request): the text you typed, the page URL, and a bounded excerpt of the page, sent to our model provider to produce the result. Not used to train models.
• Alerts (optional, paid): the destinations you configure — an email address, a webhook URL, a chat identifier — and the alert contents at the moment we deliver them.
• Payments: handled by Paddle as merchant of record. We receive a customer and subscription identifier and your plan status. We never see your card details.

What we never collect

A list of the sites you have visited, your browsing history, page content from sites you have not configured a monitor for, or analytics identifying individual pages you open.

Permissions and why they are needed

Granted at install:

Permission	Why
activeTab	Read the address of the tab you are looking at, at the moment you open the popup or press the shortcut, so the extension can offer to reload that page. It is a one-off grant for that one tab and that one gesture — it does not let us watch your other tabs.
storage	Save your rules, monitors and settings on your device.
unlimitedStorage	Keep local hit history and recorded values past the 5 MB default quota.
alarms	Wake the service worker so a running timer survives it being suspended.
notifications	Tell you when a monitor you configured fires.
offscreen	Play the alert sound; a service worker cannot produce audio on its own.
scripting	Inject the on-page countdown and the page scan — only into sites you granted.
contextMenus	Offer "start refreshing at 5s / 10s / …" on right-click.
sidePanel	Show the rule editor beside the page so you can pick elements while configuring.
power	Optional, off by default: keep the machine awake while a rule is running.

Requested only when you use a feature that needs it:

Permission	Why
tabs (optional)	List which of your tabs are currently refreshing, with their titles.
http://*/*, https://*/* (optional host permissions)	Requested one site at a time, from a user gesture, when you first enable the on-page countdown or keyword monitoring on that site.

Reloading a tab on a timer needs none of the host permissions. Until you grant a specific site, the extension executes no code on it. Every granted site is listed on the options page with a Revoke button.

Retention and deletion

Account data is kept while the account exists. Change history and recorded values are deleted after your plan's retention period. Deleting your account removes your account record, sync data, history and alert destinations. Local data is removed by uninstalling the extension.

Your rights

Write to privacy@xeviora.com to request access to, correction of, or deletion of your data. Because most of what the product handles never leaves your device, such requests generally concern only the account and sync records described above.

Children

The service is not directed at children under 13 and we do not knowingly collect their data.

Changes

Material changes are announced in the extension's release notes before they take effect. The date at the top of this document always reflects the current version.