Open main menu

WebApps with LocalStorage and AppCache/Privacy friendly Software Design

Privacy Friendly Software DesignEdit

Privacy friendly application minimize the digital footprint of users on remote servers. Of course if you load a WebApp from a server this load operation creates at least a digital footprint in the log-files of the server. Minimizing the digital footprint excludes libraries in the WebApp, that

  • (not AppLSAC) submit information about processed data in the WebApp to a remote server,
  • (not AppLSAC) submits data about an application's use patterns
  • (not AppLSAC) usage of minified compressed libraries only - without the uncompressed version of the library it is difficult to perform a code analysis if the library does not contact remote servers (e.g. having mylib.min.js without the uncompressed version mylib.js of the compressed library).

To minimize the digital footprint of remote servers, the main objective is:

  • (AppLSAC) to perform the task within the browser. This browser is regarded as runtime environment for the WebApp.
  • (AppLSAC) perform the processing without submission of data to a remote server.

Code Analysis for Privacy Friendliness WebAppsEdit

  • Analyse the javascript code elements and list mechanisms by which Javascript can send data to a remote server (e.g. by HTML forms in hidden iFrames).
  • Write a documentation by which you can identify, if the WebApp transmits transparently or intransparently data to a server!
  • Client-Server Interaction is a standard mechanism for database management. Define programming elements by which you would assess, that a WebApp violates the privacy friendliness.
  • Summarize typical data that you don't want to share in a client server interaction, and explain methods to protect your data.
  • Explain the role of OpenSource, that computer scientist can assess and analyse the source code for harmful code.

See alsoEdit