{"id":382,"date":"2014-04-07T19:45:13","date_gmt":"2014-04-07T19:45:13","guid":{"rendered":"http:\/\/blog.soton.ac.uk\/orion\/?p=382"},"modified":"2014-05-02T11:30:28","modified_gmt":"2014-05-02T11:30:28","slug":"privacy-in-leap-in-it-system","status":"publish","type":"post","link":"https:\/\/blog.soton.ac.uk\/orion\/design\/privacy-in-leap-in-it-system\/","title":{"rendered":"Privacy in LeapIn.it"},"content":{"rendered":"<p>The purpose of this post is to explain the privacy issues that are considered in designing LeapIn.it system. The following sections demonstrate the privacy related issues from five perspectives which are the personal information, information security, visibility of profile pages, privacy policy and cookie policy.<\/p>\n<h3>Personal information<\/h3>\n<p>In <em>LeapIn.it<\/em>, no personally identifiable information is collected from the users except their geographical location (which will be specific to the nearest city), which will be used for advertising purposes. Furthermore, the user will be asked before their location is tracked.<\/p>\n<p>To use LeapIn.it!, a user only needs to provide a unique username and password. After that, they can create their own avatars that act as digital representations of themselves in the virtual world. The users are therefore anonymous &#8211; they can use the system without providing their real names or any personal information.<\/p>\n<p>In a survey conducted on Facebook users to identify the level of sensitivity of the information which is taken from the users, it was shown that the participants considered email addresses to be the most sensitive piece of information as shown in Figure 1 [1]. This reaffirmed our decision to not ask for an email addresses from the users.<\/p>\n<figure id=\"attachment_383\" class=\"wp-caption aligncenter\" style=\"width: 678px\"><a href=\"http:\/\/blog.soton.ac.uk\/orion\/files\/2014\/04\/figure1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-383\" alt=\"Figure1: The level of sensitivity of the information shared by Facebook users [1]\" src=\"http:\/\/blog.soton.ac.uk\/orion\/files\/2014\/04\/figure1.png\" width=\"678\" height=\"376\" srcset=\"https:\/\/blog.soton.ac.uk\/orion\/files\/2014\/04\/figure1.png 678w, https:\/\/blog.soton.ac.uk\/orion\/files\/2014\/04\/figure1-300x166.png 300w\" sizes=\"auto, (max-width: 678px) 100vw, 678px\" \/><\/a><figcaption class=\"wp-caption-text\">Figure1: The level of sensitivity of the information shared by Facebook users [1]<\/figcaption><\/figure>\n<h3>Security<\/h3>\n<p>In order to ensure that user information is kept secure, the data will be stored on a database with access restricted to only those who need it. To ensure that a user account can only be accessed by that user, the user sets a password for their account when registering. The password is stored on the database as a <a href=\"http:\/\/security.stackexchange.com\/questions\/35523\/is-salting-a-hash-really-as-secure-as-common-knowledge-implies\">salted hash, preventing any damage done if the contents of the database were to be revealed<\/a>.<\/p>\n<h3>Visibility<\/h3>\n<p>Users of leapin.it are given the option to control the visibility of their profiles, such that they can set it as public or private to restrict the access to their pages in the searches made by other users of the network. This is similar to the implementation by Facebook, which protects the privacy of the users as illustrated in Figure 2 [1] . In leapin.it, private profiles can only be seen by the members of the user\u2019s friends list. Furthermore, users are provided with a feature that allows them to limit the visibility of their posts and hence increase the level of privacy. This is also relatively similar to what has been implemented in Facebook as shown in Figure 3, \u00a0Figure 4 and Figure 5 [1 and 2]. They can hide a post from their profile pages and show it in the relevant room and vice versa to give them more control over what they want their friends to know about them.<\/p>\n<p>&nbsp;<\/p>\n<p><figure id=\"attachment_384\" class=\"wp-caption aligncenter\" style=\"width: 432px\"><a href=\"http:\/\/blog.soton.ac.uk\/orion\/files\/2014\/04\/figure3.png\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-384\" alt=\"Figure 2: Customization of search results in Facebook [1]\" src=\"http:\/\/blog.soton.ac.uk\/orion\/files\/2014\/04\/figure3.png\" width=\"432\" height=\"455\" srcset=\"https:\/\/blog.soton.ac.uk\/orion\/files\/2014\/04\/figure3.png 432w, https:\/\/blog.soton.ac.uk\/orion\/files\/2014\/04\/figure3-284x300.png 284w\" sizes=\"auto, (max-width: 432px) 100vw, 432px\" \/><\/a><figcaption class=\"wp-caption-text\">Figure 2: Customization of search results in Facebook [1]<\/figcaption><\/figure><figure id=\"attachment_385\" class=\"wp-caption aligncenter\" style=\"width: 198px\"><a href=\"http:\/\/blog.soton.ac.uk\/orion\/files\/2014\/04\/figure2.png\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-385\" alt=\"Figure 3: Customization of user's timeline in Facebook [1]\" src=\"http:\/\/blog.soton.ac.uk\/orion\/files\/2014\/04\/figure2.png\" width=\"198\" height=\"366\" srcset=\"https:\/\/blog.soton.ac.uk\/orion\/files\/2014\/04\/figure2.png 198w, https:\/\/blog.soton.ac.uk\/orion\/files\/2014\/04\/figure2-162x300.png 162w\" sizes=\"auto, (max-width: 198px) 100vw, 198px\" \/><\/a><figcaption class=\"wp-caption-text\">Figure 3: Customization of the visibility of user&#8217;s stories\u00a0 in Facebook [1]<\/figcaption><\/figure><figure id=\"attachment_386\" class=\"wp-caption aligncenter\" style=\"width: 564px\"><a href=\"http:\/\/blog.soton.ac.uk\/orion\/files\/2014\/04\/44.png\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-386\" alt=\"Figure 4: Visibility options of Facebook posts [2]\" src=\"http:\/\/blog.soton.ac.uk\/orion\/files\/2014\/04\/44.png\" width=\"564\" height=\"210\" srcset=\"https:\/\/blog.soton.ac.uk\/orion\/files\/2014\/04\/44.png 564w, https:\/\/blog.soton.ac.uk\/orion\/files\/2014\/04\/44-300x111.png 300w\" sizes=\"auto, (max-width: 564px) 100vw, 564px\" \/><\/a><figcaption class=\"wp-caption-text\">Figure 4: Visibility options of Facebook posts [2]<\/figcaption><\/figure>&nbsp;<\/p>\n<figure id=\"attachment_387\" class=\"wp-caption aligncenter\" style=\"width: 606px\"><a href=\"http:\/\/blog.soton.ac.uk\/orion\/files\/2014\/04\/55.png\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-387\" alt=\"Figure 5: Choosing the audience for a post in Facebook [3]\" src=\"http:\/\/blog.soton.ac.uk\/orion\/files\/2014\/04\/55.png\" width=\"606\" height=\"189\" srcset=\"https:\/\/blog.soton.ac.uk\/orion\/files\/2014\/04\/55.png 606w, https:\/\/blog.soton.ac.uk\/orion\/files\/2014\/04\/55-300x93.png 300w\" sizes=\"auto, (max-width: 606px) 100vw, 606px\" \/><\/a><figcaption class=\"wp-caption-text\">Figure 5: Choosing the audience for a post in Facebook [2]<\/figcaption><\/figure>\n<p>The information posted in a room can only be viewed by the users who scanned the QR code of that room and therefore limiting the scope of information sharing which has been expressed by the users of Facebook as a factor that increases their level of comfort and trust when using a social network [1].<\/p>\n<h3>Privacy Policy<\/h3>\n<p>LeapIn.it will provide users with a document entitled &#8220;Privacy Policy&#8221; which will detail what the user should expect from the service in protecting their privacy<\/p>\n<p>It will be mentioned that the user\u2019s information including their geographical locations will used within the system to improve the service by personalizing the delivered content and adverts.\u00a0Although the users are anonymous in our system, they might choose to post information about themselves (e.g. photos or videos), therefore the privacy policy will mention that sharing this type of information is under the user\u2019s responsibility.<\/p>\n<p>The service will use the IP addresses for the users for the purpose of preventing spamming in the rooms and that will be mentioned in the terms of service section of our project. In addition, the privacy policy will mention all the data that might be received from the user when using the system such as their locations, IP addresses, their interests which might be inferred from the added rooms, date and time of using the system, their friends, their posts, the operating system of their smartphones etc. to help the users in being aware of what will be known about them in this social network.<\/p>\n<p>If a user deletes his\/her account, all the information associated with a particular user will be deleted permanently from the system. However, the users are given a feature that allows them to deactivate their accounts temporarily which means that their data will remain in the system but will not be shown to other users until the account becomes reactivated. \u00a0In addition, a user might comment or like posts which are published in sponsored rooms and since these rooms are public rooms, these comments are visible to everyone inside the network and to increase the awareness of the users, this will be written in the privacy policy.<\/p>\n<h3>Cookie Policy<\/h3>\n<p>In the privacy policy of our system, it will be mentioned that cookies will be used only for authentication purposes and will not be passed to any advertisers or to third parties.<\/p>\n<h3>References:<\/h3>\n<p>[1]Grude, Amy, Matt Scholl, and Robert Thompson. &#8220;Privacy on FaceBook.&#8221;<i>Computer Supported Cooperative Work<\/i>\u00a015.4 (2007).\u200f<\/p>\n<p>[2]Sharing and Finding you on Facebook. [Online] Available: https:\/\/www.facebook.com\/about\/privacy\/your-info-on-fb [Accessed: 7\/4\/2014].<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The purpose of this post is to explain the privacy issues that are considered in designing LeapIn.it system. The following sections demonstrate the privacy related issues from five perspectives which are the personal information, information security, visibility of profile pages, privacy policy and cookie policy. Personal information In LeapIn.it, no personally identifiable information is collected from the users except their&#8230;<span class=\"path-read-more\"><a class=\"more-link\" href=\"https:\/\/blog.soton.ac.uk\/orion\/design\/privacy-in-leap-in-it-system\/\" title=\"Privacy in LeapIn.it\">  Read more &rarr; <\/a><\/span><\/p>\n","protected":false},"author":94018,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6502],"tags":[723292,723297],"class_list":["post-382","post","type-post","status-publish","format-standard","hentry","category-design","tag-leapin-it","tag-social-factors"],"_links":{"self":[{"href":"https:\/\/blog.soton.ac.uk\/orion\/wp-json\/wp\/v2\/posts\/382","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.soton.ac.uk\/orion\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.soton.ac.uk\/orion\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.soton.ac.uk\/orion\/wp-json\/wp\/v2\/users\/94018"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.soton.ac.uk\/orion\/wp-json\/wp\/v2\/comments?post=382"}],"version-history":[{"count":8,"href":"https:\/\/blog.soton.ac.uk\/orion\/wp-json\/wp\/v2\/posts\/382\/revisions"}],"predecessor-version":[{"id":832,"href":"https:\/\/blog.soton.ac.uk\/orion\/wp-json\/wp\/v2\/posts\/382\/revisions\/832"}],"wp:attachment":[{"href":"https:\/\/blog.soton.ac.uk\/orion\/wp-json\/wp\/v2\/media?parent=382"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.soton.ac.uk\/orion\/wp-json\/wp\/v2\/categories?post=382"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.soton.ac.uk\/orion\/wp-json\/wp\/v2\/tags?post=382"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}