What we process
Watches you create
For cloud watches, we process the page address, selected scope, watch instruction, visible page text, and results. Browser watches are checked in Chrome; task settings, captured page evidence, and check history are stored in this browser. Password fields, form values, scripts, styles, and hidden content are excluded.
Browser execution
Browser watches require Chrome to be running. Task settings, page evidence, fingerprints, and check history remain in this browser. Page content and check history are not sent to PageLens Cloud for browser execution. If you configure an optional model, bounded page evidence is sent directly to your chosen model provider. Model settings and any API key are saved in trusted extension storage and excluded from account backups and report exports. Browser watches routed to Slack, Discord, or Teams send the watch title, a page URL without query parameters, and a change event through PageLens Cloud to your selected channel; they do not upload page text or local history. If you explicitly enable account backup, PageLens Cloud stores the watch URL, instruction, schedule, and task settings so another signed-in device can restore them. Restored watches require fresh site permission. Legacy PageLens Local watches continue to run through the separately installed Mac service.
AI watch suggestions
AI watch suggestions are on by default. When you open PageLens on a web page with an empty instruction field, the extension reads bounded visible text, the page title and headings, and a page URL with query parameters and fragments removed. This evidence is sent through PageLens Cloud to our configured AI provider to suggest watch instructions. Password fields, form values, and hidden content are excluded. PageLens does not save this evidence as a watch, report, or account backup. Suggestions are optional and separate from local check analysis; you can turn them off in the extension Settings. Turning them off stops future suggestion requests and clears the temporary suggestion cache.
Account and installation
If you sign in with Google, we receive your account identifier, name, email address, profile image, and sign-in provider so your cloud watches can appear in your workspace. Each cloud extension installation also receives a random installation identity and credential. PageLens Local separately pairs with the extension using a short-lived code and a device-local credential.
Website downloads and service logs
When you use a PageLens download link, we add one aggregate count for the link location and release version before redirecting to Google Cloud Storage. This aggregate contains no cookie, account, page address, IP address, or persistent device identifier. Our hosting providers may separately retain ordinary request logs, such as request time, route, IP address, and user agent, for security and reliability.
Signed-in page access
Browser watches can use the existing Chrome session on sites you allow, without exporting cookies. For cloud or legacy Local watches, only after you choose signed-in page access and approve Chrome's site permission does the extension read cookies that apply to that site. They are limited to that site and retained for no more than three days or until the cookie expires, whichever comes first. Cloud grants are encrypted by PageLens cloud; local grants are encrypted with a device-local key and are not uploaded.
Optional product analytics
Only after you opt in do we record whether a feature was used and succeeded, the chosen execution location, a coarse duration range, extension version, and operating-system category. Analytics never include page URLs, domains, text, titles, cookies, email addresses, watch instructions, selectors, screenshots, model keys, or model inputs and outputs. You can turn analytics off at any time.
Account backup
Account backup is optional and can be switched off in the extension. It contains task configuration, including page URLs and watch instructions, but excludes page text, text fingerprints, run results, and cookies. Existing backups can be removed through an account deletion request. Legacy PageLens Local watches use separate plan verification.
Why we process it
- Run the page watches, comparisons, and summaries you request;
- Back up browser task configurations only when you opt in, and synchronize cloud watches with your workspace;
- Protect the service, limit abuse, and diagnose failures;
- Improve feature adoption and reliability after you opt in to analytics.
Service providers and sharing
PageLens uses Google Cloud for Cloud Run, Cloud Storage, identity, and cloud scheduling. For cloud AI summaries and AI watch suggestions, constrained page evidence may be sent to the configured cloud model provider, including GLM or Jev, solely to produce the requested structured result. By default, browser watches compare page text in Chrome without a model provider. If you enable an optional model, the extension sends bounded page evidence directly to the endpoint you configure. Legacy PageLens Local watches may send model evidence directly from your Mac to the provider endpoint you configure. We do not sell or rent information to data brokers and do not use page content for third-party advertising.
Retention and deletion
- Site sessions: up to three days or the cookie's own expiry, whichever is earlier.
- Browser watches: local task settings and saved check history remain until deleted in Chrome or extension data is removed. Recent checks are bounded to 200 per watch; imported Local history may retain up to 1,000 checks. Optional account backups remain until deleted or the account is deleted.
- Cloud watches and results: retained while the watch or account remains active, subject to the product's stated retention period.
- Optional analytics: raw events are kept for up to 30 days and aggregate metrics for up to 13 months.
- Account data: used for sign-in and ownership; export or deletion requests are available through support.
Your choices
You may create unlimited browser watches without signing in. Account backup is optional. Declining cookie access still allows public-page watches, and declining analytics does not affect core monitoring. You can pause watches or request account export and deletion.
Security and limitations
Data is transmitted over HTTPS, site sessions are encrypted before storage, and administrative access is separately authenticated. PageLens stops when it encounters CAPTCHA, MFA, device confirmation, or an expired sign-in. It does not attempt to bypass website security controls.
Updates and contact
We will update the effective date and provide reasonable notice when this policy changes materially. Send privacy, export, or deletion requests to support@pagelens.net, or visit PageLens Support.