The privacy policy has a very large hole in it. Was this intentional?

[MrPointerOuter]

The public dns privacy policy specifies two levels of logging:
temporary and permanent. The temporary logs are deleted
"within 24 to 48 hours." The temporary logs contain a variety of
stuff that I'd prefer google not hold onto permanently. The
permanent logs are pretty benign.

The odd thing is that the policy makes it very clear that for the
permanent logs, they "don't correlate or combine your
information from these logs with any other log data that
Google might have ..." This is great. What's not so great is
that no such claim is made for the temporary logs.

Is google willing to make the same claim for the temporary
logs, and to do so unambiguously in their privacy policy?
(And by unambiguously, I mean that it -is- possible to argue that
the wording of the current policy covers the temporary logs.
But it is also possible to argue that it does not. An unambiguous
policy would explicitly name both sets of logs.]

Thanks,
Mr.P.O.

[Prem Ramaswami]

The temporary logs are not and will never be correlated with search logs, toolbar logs, etc.  Will see if we need to clarify the lang.

-- 
=======================
Prem Ramaswami 
Product Manager - Google
http://www.google.co.in/internetbus
=======================

--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to
public-dns-disc...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================

[Sterex]

Also,

"In the permanent logs, we don't keep personally identifiable
information or IP information. We do keep some location information
(at the city/metro level) so that we can conduct debugging, analyze
abuse phenomena and improve the Google Public DNS prefetching
feature."

So does this mean:
Temporary log: 1.2.3.4 (User IP) -> 5.6.7.8 (Request IP)
BECOMES (after 24-48 hours)
Permanent log: City/Metro Name -> 5.6.7.8 (Request IP)
?

On Dec 4, 1:38 am, Prem Ramaswami <pr...@google.com> wrote:
> The temporary logs are not and will never be correlated with search logs,
> toolbar logs, etc.  Will see if we need to clarify the lang.
>
> --
> =======================
> Prem Ramaswami

> Product Manager - Googlehttp://www.google.co.in/internetbus
> =======================

> > public-dns-disc...@googlegroups.com<public-dns-discuss%2Bunsu...@googlegroups.com>

[Alex Nizhner]

"In the permanent logs, we don't keep personally identifiable
information or IP information. We do keep some location information
(at the city/metro level) so that we can conduct debugging, analyze
abuse phenomena and improve the Google Public DNS prefetching
feature."

So does this mean:
Temporary log: 1.2.3.4 (User IP) -> 5.6.7.8 (Request IP)
BECOMES (after 24-48 hours)
Permanent log: City/Metro Name -> 5.6.7.8 (Request IP)
?

No--the actual results of your lookups, other than the status code, don't make into permanent logs.

Alex
 

[MrPointerOuter]

Alex, that's sortof the answer to a different question.

To re-ask Sterex's question more accurately:

So does this mean:
Temporary log: 1.2.3.4 (User IP) QUERIES persiankitty.com
BECOMES (more than 24 but less than 48 hours later)
Permanent log: City/Metro Name QUERIES persiankitty.com
?

Again, there are ambiguities in the logging privacy policy.
At one point the policy states that:

" We do keep some location information (at the city/metro level)"

but then later it states that google keeps
"User's geolocation information: i.e. geocode ..."

The policy should make it precisely clear what that geocode
information is, what the resolution of that geocode is (possibly
using the same accuracy codes as the google maps API uses?)
and what the results of a reverse-geocoding using the stored
values would be. Because it's possible to imagine simple and
maybe common scenarios where a unique geocode would be
far more intrusive if saved than an ip address.

Mr.P.O.

> > > > public-dns-disc...@googlegroups.com<public-dns-discuss%2Bunsubs cr...@googlegroups.com>
> > <public-dns-discuss%2Bunsu...@googlegroups.com<public-dns-discuss%252Bu nsubs...@googlegroups.com>

>
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/public-dns-discuss?hl=en
> > > > For more information on Google Public DNS, please visit
> > > >http://code.google.com/speed/public-dns
> > > > ========================================================
>
> > --
> > ========================================================
> > You received this message because you are subscribed to the Google
> > Groups "public-dns-discuss" group.
> > To post to this group, send email to public-dn...@googlegroups.com
> > To unsubscribe from this group, send email to

> > public-dns-disc...@googlegroups.com<public-dns-discuss%2Bunsubs cr...@googlegroups.com>