Is TravelPins – Save Places You Want to Visit safe?
TravelPins stores your saved locations in a browser cookie on google.com and sends the full list to its own server every week.
Instead of using the extension's private storage, TravelPins writes your entire list of saved places (names, notes, URLs) into a year-long cookie scoped to www.google.com, so that data rides along in the Cookie header on every request you make to Google. Separately, once a week (and after each new pin), it reads that cookie back and posts your full pin list to travelpins.vq.pe/sync.php, with part of the payload broken into base64-encoded chunks disguised as fake map pins alongside the same data sent in plain form.
Part of this rating comes from analysis signals we haven't published as detailed findings yet.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
Where it sends data
Destinations our analysis observed TravelPins contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- www.google.comwidely used
TravelPins sends data to www.google.com. A widely used service: 169 other extensions we have analyzed send data here.
- travelpins.vq.pe
TravelPins sends data to travelpins.vq.pe. No other extension we have analyzed sends data here.