Is Getaway Simplified safe?
Getaway Simplified falls back to an unauthenticated http://localhost:5999 endpoint whenever its main API call fails.
Every backend request the extension makes—loading trips, fetching AI itinerary suggestions, or saving a link added from the right-click menu—first goes to getawaysimplified.com. If that call errors out or returns anything other than a normal success or a 401, the extension silently retries the exact same request, including its full body, against http://localhost:5999 instead, with no check on what is listening there. That hardcoded fallback ships in the production build, not just a development build.
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 Getaway Simplified 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.
- getawaysimplified.com
Getaway Simplified sends data to getawaysimplified.com. No other extension we have analyzed sends data here.
- localhost:5999 (any local process listening on that port)
Getaway Simplified sends data to localhost:5999 (any local process listening on that port). Named as a recipient in this extension's own analysis.