This user has not filled out their profile!
What are we building?
We are implementing a living archive of all privacy policies!!! The backend crawler uses git as inherently efficient, inherently versioned storage mechanism for all the privacy policies, terms of service, and other web content that they depend on (CSS, videos, images, etc...). We are fixing and re-implementing http://tosback.org so that it is maintainable and scalable for thousands of privacy policies, and building a web interface for multiple audiences as a first user of this archive.
Who is it for?
The audience for this project is developers, lawyers, and users interested in aspects of corporate privacy policies.
What is our goal for this weekend?
To get TOSBack2 alpha functional and begin to snapshot privacy policies and to build a simple front end to present some access to the policies that we are tracking.
What is our starting point?
TOSBack2 is 30% completed and hours away from alpha functionality. We are building an API and web interface from scratch.
What did we accomplish?
TOSBack2 was successfully updated and a simple web interface providing basic analysis of policies including visual markup and a timeline of changes was developed.
What is significant?
This provides an online archive of over 800 privacy policies. This archive can then be used as the basis of various tools developed for specific user communities including lawyers who need in depth analysis of the detailed changes to specific policies to users who are interested in monitoring the policies of sites they frequent. One such example application was developed using analysis and visualization techniques to help users understand the amount of change.
Anyone who needs or wants to understand evolving policies. (See who is it for? question above.)
What is the sustainability model?
The effort to build and maintain the archive is automated and thus fairly sustainable. Further analysis is needed to develop reasonable sustainability for any deployed user interfaces to the data. Some challenges were encountered in the parsing and use of the archive.
What license is it available under?
Peter Eckersley (TOSBack2 component)
Asa Hardcastle (API and web interface)
Demonstration will need to be done on local laptop because of the complexity of the getting all the various components deployed in the timeframe available.
Code for tosback2 is at https://github.com/pde/tosback2.git
Code for web interface is on a local laptop.
Special thanks to Jim Brock of privacyscore.com who provided the large list of terms of service urls to expand the coverage provided by TOSBack2.
Python, C, jQuery, Algorithms