I love this idea, but here's how I think it could be improved:
1. Consider porting the entire service to a browser extension for Chrome or Firefox, and making the homepage more of an information/FAQ center.
2. Demo video. A good demo video explaining why "John Doe" should worry about his personal information being sold would be more convincing - this is how you get your service to less savvy internet users who aren't primarily concerned with privacy.
3. Find a way around inconsistencies. It would be better to report if a website actually sells/uses your personal information rather than returning a simple search result with TOS findings. A website can tweak or flat out lie. You should try to account for this.
4. Are you planning to commercialize this in any way? How do you plan to fund it, if at all?
1. Seems we got a lot of feedback and requests for an extension. Sounds like a good idea to me too!
2. Yes a demo video explaining why this is important would be helpful to folks
3. Not sure how to address this. The tool reads and classifies terms of service. Any suggestions on how we can do what you suggest
4. Potentially, want to explore a bit more and make sure it works well first. We have ideas for premium and related features/services that would key off of this well if it becomes popular and trusted.
As for 3: A simple feature to add would be to add a form for users to submit samples (links, comments).
BTW: Cool tool with a lot of potential! See also http://www.javacoolsoftware.com/eulalyzer.html (They analyze EULAs, not Privacy Policies though. Also I wasn't too impressed when I tested but a nifty idea and I only tested it a few years ago so it might have been improved a lot in the meantime.)
Hm...well, there are a few ways. What you could do is use an automated crawler with a Y|N function to tell you if it's being tracked. For example, when a user submits a website, your engine would send an automated message to the server and detect how much, if any of the information were stored, and then track it to see how it's used. If you've got the tech to do this, it would eliminate a huge amount of false positives and false negatives that the privacy policy's rhetoric generates. But that's just my suggestion.
Comments
I love this idea, but here's how I think it could be improved:
1. Consider porting the entire service to a browser extension for Chrome or Firefox, and making the homepage more of an information/FAQ center.
2. Demo video. A good demo video explaining why "John Doe" should worry about his personal information being sold would be more convincing - this is how you get your service to less savvy internet users who aren't primarily concerned with privacy.
3. Find a way around inconsistencies. It would be better to report if a website actually sells/uses your personal information rather than returning a simple search result with TOS findings. A website can tweak or flat out lie. You should try to account for this.
4. Are you planning to commercialize this in any way? How do you plan to fund it, if at all?
1. Seems we got a lot of feedback and requests for an extension. Sounds like a good idea to me too!
2. Yes a demo video explaining why this is important would be helpful to folks
3. Not sure how to address this. The tool reads and classifies terms of service. Any suggestions on how we can do what you suggest
4. Potentially, want to explore a bit more and make sure it works well first. We have ideas for premium and related features/services that would key off of this well if it becomes popular and trusted.
As for 3: A simple feature to add would be to add a form for users to submit samples (links, comments).
BTW: Cool tool with a lot of potential! See also http://www.javacoolsoftware.com/eulalyzer.html (They analyze EULAs, not Privacy Policies though. Also I wasn't too impressed when I tested but a nifty idea and I only tested it a few years ago so it might have been improved a lot in the meantime.)
Hm...well, there are a few ways. What you could do is use an automated crawler with a Y|N function to tell you if it's being tracked. For example, when a user submits a website, your engine would send an automated message to the server and detect how much, if any of the information were stored, and then track it to see how it's used. If you've got the tech to do this, it would eliminate a huge amount of false positives and false negatives that the privacy policy's rhetoric generates. But that's just my suggestion.