Skip to main content

The new Google Privacy Policy

             A lot of talk is going on these days regarding the changes in the “Google Privacy Policy”. I thought of going through the privacy policy and decided to share my understanding with you all.

             This Google Privacy Policy applies to all of the services offered by Google Inc. and its affiliates, including services offered on other sites (such as Google’s advertising services), but excludes services that have separate privacy policies that do not incorporate this Privacy Policy. This clearly means that, though the new Privacy Policy is more generic and user understandable than its previous versions, it does not state any details for individual services offered by Google. All Google services like Google Maps, Google Earth, Google Gears, etc. which have their own privacy policies, may not share a lot of policies from this more generic Google Privacy Policy. Privacy policies of these Google services will state their own, more service relevant policies.

          I have tried to keep the content as simple as possible and have also tried to not make it boring…What follows are the highlights of the new “Google Privacy Policy” that will be coming in effect from March 1, 2012.

The “Google Privacy Policy” explains 3 key points:
  • What information Google collects and why it collects that information.
  • How Google uses this information. 
  • The choices that Google offers to users, including how to access and update the information.

Let’s have a look at each of these points in further details.

Information that Google collects
Google collects information in 2 ways:
·         Information that the users provide. Several of Google’s services require the user to sign up for a Google Account, where the user is required to provide information like name, email address, phone number or even a credit card number in some cases, e.g. when you are signing up for a Google Maps API Premier (licensed) service or for any other licensed Google service. If the user wishes to take full advantage of the sharing features that Google provides, then the user might have to create a publicly visible Google Profile with a photo and name.


·         Information that Google gathers from the users’ use of various Google services. Google may collect the information about how and which service is being used by the user. For example, if the user visits a website using the Google Ads services and interact with the ads there, then Google may keep a log of the nature of ads clicked to get you more relevant ads the next time you visit the same website. Let’s take a detailed look into what all information Google gathers:
o   Device Information
Google may collect device-specific information (such as the user’s hardware model, operating system version, unique device identifiers, and mobile network information including phone number). Google may associate the user’s device identifiers or phone number with his/her Google Account.

o   Log Information
When a user uses a Google service or views content provided by Google, Google may automatically collect and store certain user information in server logs. This information is generally in the following format.

123.45.67.89 - 25/Mar/2003 10:15:32 -
      http://www.google.com/search?q=cars -
      Firefox 1.0.7; Windows NT 5.1 - 740674ce2123e969

Here, you can see that this information includes the user’s IP, the date and time of accessing Google search page, the search query, the type of browser and local browser language, user’s OS and the unique cookie ID. Google may also maintain telephony log information like the user’s phone number, calling-party number, forwarding numbers, time and date of calls, duration of calls, SMS routing information and types of calls. This information is usually gathered when a user is using the Google Voice service.

o   Location Information
When a user uses a location-enabled Google service, Google may collect and process information about the user’s actual location, like GPS signals sent by a mobile device. Google may also use various technologies to determine location, such as sensor data from the device that may, for example, provide information on nearby Wi-Fi access points and cell towers. This sort of information is maintained by Google to show search results using the Places API service, where the user can search for a place near his/her current location using some keyword like “garage”.

                         


o   Unique Application Numbers
Certain services like Google Earth, Picasa, Google Desktop, etc. include a unique application number which bears the information about the user’s installation (for example, the operating system type and application version number) and this information may be sent to Google when the user installs or uninstalls that service or when that service periodically contacts Google’s servers for automatic updates. Another example is when a user wants to download chrome , Google Gears, Lively or Google Earth’s plug-in, Google first downloads a small setup file that needs an internet connection to obtain the actual software.

o   Local Storage, Cookies and Anonymous Identifiers
Google may collect and store information (including personal information) locally on the user’s device using mechanisms such as browser web storage (including HTML 5) and application data caches. When a user accesses a Google service, Google may send one or more cookies and anonymous identifiers – “A random string of characters that is used for the same purposes as a cookie on platforms, including certain mobile devices, where cookie technology is not available.” Google uses these cookies and identifiers, also when a user interacts with services that Google offers to its partners such as the advertising services.

How Google uses and shares the information it collects
          Google uses all the information collected from the user to provide the user with tailored content to make the user’s Google experience better. The other thing that they do use this information is to provide, maintain, protect and improve the existing Google services and also generate new services. Google may combine a user’s information provided for one service with all other services that he/she uses thereafter. Google does not share any sort of personal information of any user with anybody outside Google, unless under following circumstances:
  • The user has provided opt-in consent on sharing the information. 
  •  If the user’s Google account is managed by a domain administrator (usually in case of Google Apps users) then the domain administrator and resellers who provide user support to the user’s organization will have access to the user’s Google Account information (including your email and other data). 
  •  Google provides personal information to its affiliates or other trusted businesses or persons to process it for them, based on Google’s instruction and in compliance with a Privacy Policy and any other appropriate confidentiality and security measures. 
  •  Google will share personal information with companies, organizations or individuals outside of Google if they have a good-faith belief that access, use, preservation or disclosure of the information is reasonably necessary to:
§  meet any applicable law, regulation, legal process or enforceable governmental request.
§  enforce applicable Terms of Service, including investigation of potential violations.
§   detect, prevent, or otherwise address fraud, security or technical issues.
§  protect against harm to the rights, property or safety of Google, our users or the public as required or permitted by law.
  • Google may share aggregated, non-personally identifiable information publicly and with their partners – like publishers, advertisers or connected sites. This information is usually used to share trends of use of a particular Google service or to bloggers to show the trend of users from various regions across the globe that access the blog, trends of the OS these visitors use, etc. Google trends usually appear as seen in the image below.

 
Google strives to maintain transparency in their privacy settings and hence allows the user to control the privacy of his/her content and information.

Information the user shares
          Several Google services like Google office, Google Fusion Tables allow the users to share information with others users. If this content is shared publicly, then it would become indexable by search engines. However, Google services provide various options on sharing and deleting the data.
Labels:

Comments

Post a Comment

Please leave your comments here...

Recommended for You

Where does Google get it's live traffic data from?

Referring to a post that I wrote earlier, Google’s - Live traffic Layer , ever wondered how Google collected this data? I was wondering the other day, how Google received live data to display it on their maps as a layer! I looked up the web and found something very interesting and am sharing the same with you all. As we all know, the traffic layer is available most accurately in several states in USA. Most major metro areas in the US have sensors embedded in their highways. These sensors track real time traffic data. Easy to miss at high speeds (hopefully anyway, traffic permitting), more commonly noticed may be the similar sensors that often exist at many busy intersections that help the traffic lights most efficiently let the most amount of people through. The information from these tracking sensors is reported back to the Department of Transportation (DOT). The DOT uses this data to update some of the digital signs that report traffic conditions in many metro areas. They als
17 comments
Read more

Geodesic Polyline

    Today we will have a look at a very interesting polyline example - "The geodesic polyline". Now the first question that will pop is "What is geodesic?". Mathematically, geodesic means the shortest line between two points on a mathematically defined surface, as a straight line on a plain or an arc of a great circle or sphere.     The next question after reading the above definition is clearly, "Why do we need geodesic polylines?" and that would be followed up with "What is this Great Circle?". We will discuss this first, before we move on to the actual example today. The example is very very similar to the normal polyline example, with just a small change.     Having said so, I will now try to explain why we need a geodesic polyline? The shortest distance between two locations on the earth is rarely a straight line as the earth is roughly spherical in nature. So any two points on the earth, even if they are very close lie on a curve and n
5 comments
Read more

Playing with the markers and info window bubbles...

    In the last few posts, we have seen some marker examples and some information window examples. Now, lets do something interesting combining these two things. Just writing that "This is an info window" in the information bubble is not very interesting! And I know this...Have gone through the same phase!     So, today we will do something interesting! We will display the latitude- longitude co-ordinates of the point that the user clicks on the map! Doing this is not at all complex! Copy paste the following code and you will see for yourself a map coming to life!     The output of the above code looks as seen in the result section above! If you have any queries regarding the above code please comment on the blog post or feel free to contact me at my mail ID .
3 comments
Read more

The bitter divorce of PSD and HTML

    Today's article is an interesting post that I read. The original post in Portuguese and authored by Fabricio Teixeira  can be found at arquiteturadeinformacao  (Now don't ask me pronounce this =)).     Some are calling it the death of PSD  but I prefer calling it a "divorce". PSD and HTML are both healthy and living strong, just that they do not live together anymore. "PSD to HTML", which for years was the most accurate and sometimes the only right path to web design process, seems like has its days counted.     Firstly you draw a page in Photoshop; impeccable layout, representing exactly how the web pages would appear when opened in a browser. After a sign-off on this picture (PSD) from the client the front end developer transforms these pictures into HTML, CSS and Javascript. The assets are cut, one by one, exported from the PSD and integrated into the HTML. Plugins and new tools are created in the process and some companies even charge upto $1
5 comments
Read more

Google Street View Image API

    Street View is one of most used feature of the Google Maps and why not? You can actually see any part of the world as if you are visiting the place at that very moment. And now with the Google Street View Image API, you don't even need to carry a camera with you to the places you visit. You can take-in all the scenic beauty without even bothering about clicking a single picture. You can come back from your vacation and get a few images using the Google Street View Image API and show those images to your friends and relatives. Create an album of high definition images and go ahead and share it on Facebook for your friends to have a look.     Using the Google Street View Image API is very simple and anybody can make use of it without any programming knowledge required. I will walk you through the entire process of effectively using the Google Street View Image API. So if you are set, let's go on an amazing ride across the globe with the Google Street Views.     The Go
1 comment
Read more