Privacy Policy for Text Watcher

Last updated: September 10, 2026

Text Watcher 4.0.0 monitors page text and manages automatic refresh operations inside the browser. The repository does not include a developer-operated analytics or application server. Optional Discord and Telegram integrations do transmit alert data to those services when the user enables them.

1. Data handled by the extension

The extension stores monitoring rules, domains, selected rule text, text conditions, refresh state, interface preferences, language, alert preferences, and optional integration settings. A custom MP3 may also be stored in extension storage.

The content script can read visible text, the document title, and page changes on eligible websites to evaluate enabled rules. Text selected for a new rule is sent to the extension service worker only after the user chooses a context-menu action. Text from the full page is not uploaded to a Text Watcher server.

2. Optional external services

External requests occur only for integrations enabled by the user:

• Discord: the monitored domain and rule text are sent to the webhook URL supplied by the user.
• Telegram: the monitored domain and rule text are sent through the Telegram Bot API using the token and chat IDs supplied by the user.

Discord and Telegram process data under their own terms and privacy policies. Do not place sensitive text in a rule connected to an external integration unless you accept that disclosure.

3. Storage and synchronization

The extension uses chrome.storage.local, chrome.storage.session and chrome.storage.sync. Local storage stays with the browser profile unless the extension is removed. Sync storage may be copied by Chrome to other browsers signed in to the same Google account when Chrome Sync is enabled. Session storage holds temporary rules by tab and is not synchronized.

In version 4.0.0, persistent rules created in the popup or context menu remain in sync storage while temporary rules use session storage and are removed with the extension session or owning tab. Discord webhooks and Telegram bot settings remain in local storage. A one-time migration copies legacy integration values from sync storage and removes the old sync keys. Chrome extension storage should not be treated as an encrypted password vault.

4. Permissions

• storage: saves rules, state and preferences.
• activeTab: provides temporary access to the active tab; its continued necessity is under review.
• tabs: identifies and reloads tabs and manages per-tab indicators.
• alarms: schedules automatic refresh operations.
• notifications: displays native alerts.
• offscreen: creates an offscreen document for audio playback.
• contextMenus: provides actions for selected text on HTTP/HTTPS pages.
• host permissions (<all_urls>): loads the content script on eligible pages so persistent and tab-scoped rules, short refresh intervals and the floating overlay can work. Version 4.0.0 requests this access statically rather than per-domain.

5. User control and retention

Rules can be disabled or removed in the popup. Temporary rules are visible only for their owning tab; closing that tab removes them. Persistent rules remain available across matching tabs. Discord and Telegram can be disabled there as well. Removing the extension clears its extension storage from the browser profile. Chrome Sync may follow separate account synchronization behavior.

6. Security limitations

No client-side extension can guarantee that credentials stored in a browser profile are protected from a compromised device or profile. Use dedicated, revocable bot tokens and webhooks. Revoke them directly in Discord or Telegram if exposure is suspected.

7. Changes

This policy may change when features, permissions or external integrations change. The update date above identifies the current document.

8. Contact

Questions may be sent to sevenleo@mail.com.

Back to Home