RevBeacon Privacy Policy
Last updated: May 13, 2026
RevBeacon is designed around on-demand page inspection and minimal permissions.
Data Used
When you open the popup on a supported product page, RevBeacon reads only the current page metadata needed to match community signals: URL, tab title, page title, Open Graph title, first heading, canonical URL, domain, and visible or structured product price when available.
When you post a signal or comment, RevBeacon sends your submitted text, public display name, product/page metadata, rating, tag, helpful votes, reports, and moderation state to RevBeacon's online service.
If price history is enabled, RevBeacon saves one daily price snapshot for the current product when you open the popup on that product page. It stores product key, price, currency, price source type, date, and number of observations. It does not run a background price crawler.
Bug reports include the message you submit, app version, app view, the current product page when available, and basic browser user-agent details so issues can be reproduced.
Toolbar badge checks are limited to supported shopping/product URLs and can be turned off in Settings.
Data Not Collected
- RevBeacon does not collect browsing history.
- RevBeacon does not scrape every page in the background.
- RevBeacon does not track prices unless you open the popup on that product page.
- RevBeacon does not request access to all websites.
- RevBeacon does not store service-role secrets in the extension.
Accounts
Users may use an anonymous browser identity with a public display name or create an optional email/password account to keep history across computers.
Sharing
Public signals, comments, display names, and reputation scores are visible to other RevBeacon users. Reports and moderation details are visible to authorized RevBeacon moderators for safety and abuse handling.
Contact
Questions or deletion requests can be sent to revbeaconapp@gmail.com.