3 ms·
Gives me really bad vibes, sending all your browsing history, page info, etc. to some server, including screenshots of your tabs. You also say it doesn't save
by KomoD 2y ago
Gives me really bad vibes, sending all your browsing history, page info, etc. to some server, including screenshots of your tabs.
You also say it doesn't save in incognito but I can't find anything in the source code to support that claim.
I see a bunch of other red flags too, like no obvious monetization, the privacy policy saying updated in 2021, but then a little bit further down it says updated in 2019 (neither makes sense as the domain was registered in 2023), privacy policy sometimes says Nision Research LLC and sometimes Nision Research Kft, the chrome web store page has an email for "gethaystack.com" but the privacy policy says info@browspilot.com (and that gethaystack site has a policy saying "info@localhost"), both of the reviews on the chrome web store are by people clearly affiliated with browspilot, the FAQ says you can't delete things from your history, privacy policy doesn't say where your data gets sent (i see mentions of firestore, firebase in the code, but it does not appear in the privacy policy)
Also this claim on your home page "Your data will only be read and used by you." doesn't align with what your privacy policy says.
- pedalpete 2y agoThis was my initial concern. Though this is something I want, and I'm surprised isn't built into modern browsers. I'm less interested in having a cache of images, but useful search of my history, which I think could be stored locally, would be helpful. We don't need the search to be particularly clever I wouldn't think. Even straight string search of cached text from the webpages I've viewed would be valuable. I don't need all the images, video, javascript, etc cached.
- tarasglek 2y agoI proposed this at firefox when I was there, was deemed as too niche a feature...I'm still sad that I can't have this feature
- yjftsjthsd-h 2y ago> You also say it doesn't save in incognito but I can't find anything in the source code to support that claim. Doesn't Chrome default to disabling extensions in incognito? So the extension wouldn't actually have to do anything itself for that to be true.