> We don't need to send any information to our service to protect you from bad sites because that is handled locally. The browser history already exists so the load on your machine is the same with or without Apozy. We use the headers to make it efficient for a large number of sites - 1M+
Okay so the local version is comparing the user's current page vs. the sites they've gone to prior? And if it seems off based on some heuristics it flags the page. Interesting idea.
Wouldn't work for me though as I have my browser set to nuke everything each time it's closed.
> Using the extension without opting in means you don't see site privacy grades but you're still protected using a Trust on First Use model of security created with your browsing history.
I originally thought it was just this piece which would need some type of client / server interaction to either fetch the "bad lists" or send the current URL/FQDN for validation.
Okay so the local version is comparing the user's current page vs. the sites they've gone to prior? And if it seems off based on some heuristics it flags the page. Interesting idea.
Wouldn't work for me though as I have my browser set to nuke everything each time it's closed.
> Using the extension without opting in means you don't see site privacy grades but you're still protected using a Trust on First Use model of security created with your browsing history.
I originally thought it was just this piece which would need some type of client / server interaction to either fetch the "bad lists" or send the current URL/FQDN for validation.