Privacy Policy

Who we are

WebURLTracker (weburltracker.com) is a website change monitoring service. This policy covers the website, the signed-in app, and the Chrome extension “WebURLTracker: Website change detection, monitoring and alerts”.

The extension’s single purpose is to watch page regions you choose in Chrome and sync detected text changes to your account. It does not replace the web app, inject ads, or collect a profile of sites you merely visit.

Questions: email [email protected].

User data collection

We collect user data only to run the account and the monitors you create. We do not collect data from pages you have not chosen to watch, record, or pick.

From the website and signed-in app we collect:

• Account details from Clerk (our authentication provider): name, email address, and user id. We do not receive or store your password.
• Workspace and monitor settings you enter: URLs, selectors, check intervals, alert destinations, and team membership.
• Capture data for monitors you create: text extracts, screenshots, page HTML when a check needs it, diffs, and related metadata (URL, timestamp, check status).
• Billing and plan-limit metadata needed to invoice a paid plan and enforce quotas.
• On the production website only, anonymous usage events via Google Firebase Analytics (page views, device and browser). Analytics is not loaded on localhost, the development host, or inside the Chrome extension.
• Server logs (IP address, user agent, timestamps) for security and abuse prevention.

Chrome extension data collection

The extension collects data only after you install it, sign in, and create or run a watch. A content script is present on http and https pages so you can pick a region or record a step, but it does not read or upload page content until you start one of those actions.

When you use the extension, we collect:

• Sign-in session: Clerk session cookies on our sign-in host, so the extension can stay signed in. We do not ask you to paste an API token, and we do not write session tokens into chrome.storage.
• Settings stored on your device: workspace id, the list of Local watches (monitor id, URL, interval, last extract, last status), unread state, and notification or sound preferences.
• Watched-page content you asked us to check: the page URL, the text of the regions you selected, and, when the page rendered, a screenshot and HTML of that watched page. Those are sent to your account so you can review the change.
• Login or session capture, only when you record a login or a sign-in step for a monitor you created: cookies for that site, localStorage and sessionStorage items on that origin (size-capped), user agent, and viewport. This lets a later check load the page as you. We do not capture cookies or storage for other sites, and we do not capture a dump of every open tab.
• A short notification on your device when a watch you created reports a text change. You can turn desktop notifications off in the extension settings.

User data handling

We handle user data to provide WebURLTracker: authenticate you, run the checks you schedule, store baselines, show diffs, send the alerts you configured, enforce plan limits, and support the workspace when you ask.

Handling is limited to that purpose. We do not sell user data. We do not use watched-page content, browsing activity, or account data for advertising, creditworthiness, or lending. We do not use the content of pages you watch to train AI models.

Humans do not read your captures except to answer a support request you made, to investigate abuse or a security incident, or where the law requires it. Transmission to our API uses HTTPS.

The extension handles page content in your browser for the watch you started, then sends only the capture for that monitor to our API. It does not handle unrelated tabs as monitoring data.

User data storage

We store user data only as long as we need it to provide the service, meet a legal duty, or resolve a security issue.

• On your device (Chrome extension): watch list, workspace id, unread state, and notification preferences in chrome.storage.local. Temporary tab ids used during a check may sit in extension session storage and are discarded when the check ends. Uninstalling the extension removes this local data.
• On our servers: account records, monitor settings, text extracts, screenshots, page HTML, diffs, and login/session state you chose to save for a monitor. Captures are stored in a database and in object storage (Cloudflare R2) tied to your workspace. Access is scoped so one workspace cannot read another’s monitors.
• Authentication records (including passwords) are stored by Clerk, not by us.
• Monitor history and screenshots follow your plan’s retention window. When you delete a monitor, we remove its stored captures from active storage as cleanup runs.
• Account records stay while the account is open. You can ask us to delete the account; see the GDPR page for rights requests.

User data sharing

We do not sell user data. We do not share browsing data or watched-page content with advertisers or data brokers. We share user data only with the parties below, and only as needed to run the service you asked for.

• Clerk: authentication and session management (name, email, user id, session cookies).
• Our hosting: the API, PostgreSQL database, and Cloudflare R2 object storage that hold account data, monitor settings, extracts, screenshots, and session state you saved.
• Google Firebase Analytics: anonymous page-view measurement on the production website only. Not used by the Chrome extension, and not used for ads.
• Alert destinations you configure (for example an email address or webhook you connect). We send the alert content you set up for that monitor, not a copy of your browser profile.
• Support staff, only when you ask for help and the request cannot be answered without looking at the workspace you identify.
• Authorities, if we are required to disclose data by law, or to protect the rights, safety, and security of users and the service.

Chrome extension permissions

The extension requests Chrome permissions only for the single purpose above. None of them are used to build an advertising profile or to read sites you did not choose to watch.

• storage: remember the API workspace, watch list, unread state, and notification preferences on your device.
• cookies: keep your Clerk sign-in session fresh, and read cookies on a site only when you record a login for a monitor you created.
• alarms: run checks on the interval you set, with jitter so checks are not locked to an exact second.
• tabs, windows, scripting, activeTab, and host access to http and https pages: open the watched URL in a temporary tab, run steps you recorded, and extract the text you selected. The temporary tab is closed after the check.
• notifications: tell you when a watch changed. You can disable this in extension settings.
• sidePanel: show the recorder while you record steps for a monitor.

Cookies and similar tech

We use cookies and local storage needed for sign-in, session continuity, and basic product preferences. On the production website we also use Firebase Analytics cookies. See the Cookie Policy for details.

Security

We use encrypted transport (HTTPS), access controls on workspace data, and SSRF guards on monitor URLs. More detail is on the Security page.

Children

WebURLTracker is built for business and professional use. We do not knowingly collect personal data from children under 16.

Changes

We may update this policy. The “Last updated” date at the top of the page will change when we do. Material changes will be reflected here before they take effect for new processing where practical.

Contact

Questions: email [email protected].