TabEye
Privacy Policy
Last updated: October 30, 2026
This policy covers the TabEye Chrome extension and this website. TabEye monitors browser tabs you choose and alerts you to changes. The extension has no account system or developer-operated backend.
1. The extension
1.1 Information handled and stored
TabEye processes page information for tabs you actively choose to monitor. Its broad page-access permission supports monitoring those pages and their accessible frames.
| Information | Purpose | Storage |
|---|---|---|
| Monitored tab title and URL | Label monitors, reopen tabs and identify pages in alerts | Chrome local storage on your device |
| Monitored page content | Detect changes, match keywords and run optional custom scripts. This can include visible text, form-control values, accessible open shadow roots and child frames. Styles, structure, geometry and selected attributes contribute to comparison signatures. Passwords and hidden controls are excluded; image pixels are not inspected. | Text is processed temporarily in memory. Composite and per-region hashes, structural keys and keyword results are stored locally for active monitors; raw page text is not persisted. |
| Settings and language preference | Keep intervals, keywords, detection mode, alert options and your chosen interface language | Chrome local storage on your device |
| Alert configuration | Use the Discord or Slack webhook URL, Telegram bot token and chat ID, or sound URL you provide | Chrome local storage on your device |
| Custom scripts | Run optional scripts you write for your monitors | Chrome local storage on your device |
| Pending alerts and delivery status | Retry temporary delivery failures and show the latest result. Telegram's update cursor prevents repeated command handling. | Chrome local storage until delivery, cancellation or the retry limit; the latest result and cursor remain locally. |
Chrome local storage is kept on your device and is not synced to a Google account by TabEye. Diagnostic logs keep counts and reason codes in memory without raw page values. Zoom and display-scale checks use local source fingerprints; raw source is not saved. Exported settings backups include integration credentials, so keep backups private.
1.2 When information leaves your browser
TabEye does not send data to its developer. The following features contact other services:
- Discord: when enabled, sends the monitored page title, URL and alert label to the Discord webhook you provide.
- Slack: when enabled, sends the monitored page title, URL and alert label to your incoming webhook at hooks.slack.com or hooks.slack-gov.com. Slack chooses the destination channel. No screenshots or raw page content are included.
- Telegram: when enabled, sends alert messages containing the page title and URL through api.telegram.org using the bot credentials you provide. The
/screenshotcommand sends an image of the currently visible monitored tab to your configured chat. Commands from that chat can control monitors; in a group, members able to interact with the bot may do so. - Sound: sound is enabled by default. Playback fetches the selected audio URL; the default sound is hosted at actions.google.com. You may disable sound or choose another URL.
- Custom scripts: a script you write may receive up to 100,000 characters of monitored text, the tab title and URL, and trigger information. It may make network requests to destinations specified by your script.
Discord, Slack and Telegram remain disabled until you configure and enable them. Pressing an integration's Test button sends a test request even if its toggle is off. Requests go directly from your browser to the destination. Those services and audio hosts receive ordinary connection information, including your IP address, and their own privacy policies apply.
1.3 Permissions
Page access, tabs and web navigation support monitoring selected pages and their frames, picking elements, reloading or focusing tabs and Telegram screenshots. Storage saves settings, monitor state and pending alerts. Notifications can show page titles and URLs through your operating system, potentially on a lock screen; desktop alerts are off by default. Offscreen access supports audio and the script host. Alarms support monitoring recovery, Telegram polling and alert retries. Context menus, the side panel and active-tab access provide Chrome controls. These permissions serve TabEye's monitoring and alerting features.
1.4 Retention and deletion
Removing monitors or using Stop & Clear All Monitors removes monitor state, but does not erase integration settings, scripts or already queued alerts. Pending alerts are removed after delivery, cancellation or five attempts. Disabling a channel or changing its destination cancels its pending deliveries when the retry worker checks them. The latest delivery result remains stored locally. Uninstalling TabEye deletes its local storage. Messages already delivered to Discord, Slack or Telegram and exported backups remain outside the extension and are subject to their respective destinations.
1.5 How TabEye uses data
TabEye has no analytics, telemetry or advertising in the extension. It does not sell your data, transmit it to the developer, or collect general browsing history beyond the tabs you choose to monitor. Data is used only for the disclosed monitoring and alerting purpose. TabEye's use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements.
2. This website
This website has no user accounts and does not set its own cookies. Its hosting provider may keep standard request logs, including requested pages, times and IP addresses, for operation and security. The site loads Cloudflare Web Analytics, which receives connection and page-visit information under Cloudflare's policies. Site fonts are served from this website. See the Cookies Policy for more detail.
3. Children
TabEye is a general-purpose productivity tool and is not directed at children under 13. We do not knowingly collect children's personal information.
4. Changes and contact
If this policy changes materially, we will update the date above and, where appropriate, note the change in extension release notes. For privacy questions, contact [email protected].