Purpose
LivePin lets a user explicitly select changing values from websites and keep those values available as browser pins, local history, and user-configured alerts.
Default behavior
LivePin does not require a LivePin account or LivePin server. By default, tracker configuration is stored in Chrome local extension storage, change history is stored in extension IndexedDB, selected values and source-discovery samples are processed in the browser, and visual/audio alerts are generated locally.
Data handled for a pin
When the user explicitly creates a pin, LivePin may process the selected page URL and title, selected value, selector/fingerprint information, local change history, compact JSON paths and primitive values observed from authorized page fetch/XHR responses, and pin preferences such as name, icon, refresh interval, floating position/style, groups, tags, conditions, and alert channels.
LivePin does not intentionally build or upload a general browsing-history profile. Source observers are installed only on origins for which the user granted LivePin access.
Optional Chrome Sync
If enabled, Chrome Sync stores tracker configuration through the user's Chrome account. LivePin does not sync local history, current tracked values, privacy-consent state, or page-text fingerprint samples. Synced configuration can include source URLs, selectors, groups/tags, alert configuration, and per-pin floating configuration.
Optional webhooks
If the user configures a webhook alert and its condition matches, LivePin sends the configured endpoint an event containing the tracker ID/name, source URL, previous/current value, matched condition types, and event time. LivePin asks for access to that webhook origin first.
Chrome notifications
Native notifications are created locally by Chrome only after the user enables a notification alert and grants the optional notification permission.
Website access
LivePin asks for host access when the user chooses to track a value on a site. Floating is configured per pin. If the user enables Floating for a pin, LivePin requests all-sites host access because that chosen pin must be rendered over other webpages. This permission does not cause LivePin to automatically create trackers from unrelated pages.
Retention and deletion
Users can pause or delete an individual pin, choose history retention, export data, or reset all local LivePin data from Settings. Deleting a pin removes its local history and saved floating position. Removing the extension removes its local extension data subject to Chrome's normal browser behavior.
Advertising, sale, and human access
LivePin does not sell user data and does not use tracker data for personalized advertising. LivePin does not intentionally expose tracker data to humans. Optional Chrome Sync and webhook transfers are used only to provide those user-selected features.
Security
LivePin uses Chrome extension APIs and browser-managed storage. Webhook endpoints should use HTTPS. LivePin's diagnostics intentionally omit tracked values, source URLs, selectors, and page content.
Contact
For privacy questions, use the LivePin support page.