Privacy Policy
Last updated: July 4, 2026
This policy covers the TabEye Chrome extension ("the extension") and this website. It explains what information is handled when you use them, where that information lives and when it moves.
1. The extension
1.1 What the extension handles
TabEye works with the following information, only for the tabs you actively choose to watch:
| Information | Purpose | Where it is stored |
|---|---|---|
| Title and address of watched tabs | To label your monitors in the popup and to identify the page in alerts | Chrome's local storage on your device |
| Content of watched pages | To detect changes between checks. Only a numeric fingerprint (hash) of the content is kept between checks; the page text itself is used briefly in memory for comparison | Only the fingerprint is stored, locally on your device |
| Your settings | Check intervals, keywords, detection mode, cooldowns and other preferences | Chrome's local storage on your device |
| Alert channel details | A Discord webhook address, Telegram bot token and chat ID, or a sound address, if you choose to enter them | Chrome's local storage on your device |
| Custom scripts | Optional scripts you write for your own monitors | Chrome's local storage on your device |
The extension has no account system and no server of its own. Chrome's local storage stays on your device and is not synced to a Google account by the extension.
1.2 When information leaves your browser
Information moves out of your browser only through alert channels that you set up yourself, and it travels directly from your browser to the service you chose:
- Discord: if you enable Discord alerts, the extension sends the watched page's title, address and an alert label to the Discord webhook address you provide.
- Telegram: if you enable Telegram alerts, the extension uses the Telegram Bot API with the bot token you provide to send alert messages. If you use the screenshot command, an image of the currently visible watched tab is sent to your Telegram chat.
- Sound address: if you set a custom alert sound, the extension fetches audio from the address you provide.
- Custom scripts: if you write your own automation scripts, those scripts can make network requests to whatever addresses you code into them. What a script sends, and where, is entirely defined by you as its author.
Each channel is optional and off until you configure it. Once information reaches Discord or Telegram, their own privacy policies apply.
The developer of TabEye operates no servers and receives none of the information described above. Nothing is sold, shared for advertising, or used for any purpose other than the monitoring and alerting you set up.
1.3 Permissions
The extension asks Chrome for access to tabs and page content so it can read the pages you put on watch, show the countdown overlay and open or focus a tab when an alert fires. This access is used for the watch feature and nothing else.
1.4 Removing your information
You can remove everything the extension stores at any time:
- Delete individual monitors or use "Stop & Clear All Monitors" in the extension's Settings tab; or
- Uninstall the extension, which removes its local storage along with it.
2. This website
This website consists of static pages. It does not have user accounts and does not set cookies of its own. Like most websites, the server that hosts these pages may keep standard technical logs (such as the requested page, the time of the request and the requesting IP address) for security and operational reasons; those logs are governed by the hosting provider's own policies. Fonts on this site are loaded from Google Fonts, which means your browser requests font files from Google's servers when a page loads; that request is governed by Google's privacy policy.
For more detail on cookies, see the Cookies Policy.
3. Children
TabEye is a general purpose productivity tool and is not directed at children under 13.
4. Changes to this policy
If this policy changes in a meaningful way, the "Last updated" date above will be revised and, where appropriate, the change will be noted in the extension's release notes.