귀하가 서비스를 사용할 때 Google이 수집하는 정보로 사용자가 무엇을 하는지 사용자가 알고 있어야 합니다.
Google에서 준수하는 기본 정책을 읽으려면 개인 정보 보호 센터를 참고하세요.
그러나 이 페이지를 읽고 있다면 Google 공개 DNS를 사용할 때 데이터가 어떻게 되는지에 관한 구체적이고도 빠른 답변을 원할 수 있습니다.
Google은 빠른 제품 환경을 추구했기 때문에 개인 정보 보호에 대해서도 신속하게 파악할 수 있었습니다.
기록 내용
Google Public DNS는 임시 및 영구라는 두 가지 로그 세트를 저장합니다.
임시 로그는 사용 중인 머신의 전체 IP 주소를 저장합니다.
이렇게 해야 DDoS 공격과 같이 잠재적으로 유해한 요소를 파악하고 특정 사용자에게 특정 도메인이 표시되지 않는 문제를 해결할 수 있습니다.
임시 로그는 24~48시간 내에 삭제됩니다.
영구 로그에는 개인 식별 정보나 IP 정보가 보관되지 않습니다.
Google은 디버깅을 수행하고 악용 사례를 분석할 수 있도록 일부 위치 정보 (도시/대도시)를 보관합니다.
이 데이터를 2주 동안 보관한 후 영구 저장을 위해 소규모 하위 집합을 무작위로 샘플링합니다.
Google은 임시 또는 영구 로그의 정보를 사용자가 다른 서비스에 Google에 제공한 개인 정보와 연관 지거나 결합하지 않습니다.
마지막으로 Google 공개 DNS를 사용할 때 Google이 기록하는 다른 정보를 알고 싶은 경우 영구 로그에 포함되는 항목의 전체 목록은 다음과 같습니다.
[null,null,[],[[["\u003cp\u003eGoogle Public DNS does not permanently store your personally identifiable information.\u003c/p\u003e\n"],["\u003cp\u003eTemporary logs containing full IP addresses are kept for 24-48 hours to address issues like DDoS attacks and domain resolution problems.\u003c/p\u003e\n"],["\u003cp\u003ePermanent logs retain anonymized location data (city/metro level) for debugging and abuse analysis, with a small subset sampled for permanent storage after two weeks.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Public DNS logs technical data such as request domain, type, protocol, location, and response codes, without correlating it with any personal information from other Google services.\u003c/p\u003e\n"]]],["Google Public DNS retains minimal data to ensure speed and problem resolution. Temporary logs, including full IP addresses, are deleted within 24-48 hours. Permanent logs exclude personally identifiable information and IP addresses, retaining only city/metro-level location data for debugging and abuse analysis. A subset of this data is randomly sampled for permanent storage after two weeks. Permanent logs include request details like domain name, type, transport protocol, client's ISP, user's geolocation, response codes, caching information, and timing. Google does not link this data with other personal user information.\n"],null,["# Your Privacy\n\n| **Note:** This is an archived version of our Privacy Policy. View the [current version](/speed/public-dns/privacy) or [all past versions](/speed/public-dns/archive/privacy-changes).\n\nWe understand that our users need to know what we do with information we collect\nwhen you use our services.\nIf you'd like to read the main policy which Google adheres to, see the\n[Privacy Center](//www.google.com/intl/en/policies/privacy/).\n\nHowever, if you're reading this page, you probably want some specific,\nrapid answers about what happens to your data when you use Google Public DNS.\nWe designed the product to be fast, so let's get to the point quickly on privacy\nas well.\n| **Important:** We built Google Public DNS to make the web faster and to retain as little information about usage as we could, while still being able to detect and fix problems. Google Public DNS does not permanently store personally identifiable information.\n\nWhat we log\n-----------\n\nGoogle Public DNS stores two sets of logs: temporary and permanent.\nThe temporary logs store the full IP address of the machine you're using.\nWe have to do this so that we can spot potentially bad things like DDoS attacks\nand so we can fix problems, such as particular domains not showing up for\nspecific users.\n\nWe delete these temporary logs within 24 to 48 hours.\n\nIn the permanent logs, we don't keep personally identifiable information or IP\ninformation.\nWe do keep some location information (at the city/metro level) so that we can\nconduct debugging, analyze abuse phenomena.\nAfter keeping this data for two weeks, we randomly sample a small subset for\npermanent storage.\n\nWe don't correlate or combine information from our temporary or permanent logs\nwith any personal information that you have provided Google for other services.\n\nFinally, if you're interested in knowing what else we log when you use Google\nPublic DNS, here is the full list of items that are included in our permanent\nlogs:\n\n- Request domain name, e.g. www.google.com\n- Request type, e.g. A (which stands for IPv4 record), AAAA (IPv6 record), NS, MX, TXT, etc.\n- Transport protocol on which the request arrived, i.e. TCP, UDP, or [HTTPS](/speed/public-dns/docs/dns-over-https)\n- Client's AS (autonomous system or ISP), e.g. AS15169\n- User's geolocation information: i.e. geocode, region ID, city ID, and metro code\n- Response code sent, e.g. SUCCESS, SERVFAIL, NXDOMAIN, etc.\n- Whether the request hit our frontend cache\n- Whether the request hit a cache elsewhere in the system (but not in the frontend)\n- Absolute arrival time in seconds\n- Total time taken to process the request end-to-end, in seconds\n- Name of the Google machine that processed this request, e.g. machine101\n- Google target IP to which this request was addressed, e.g. one of our anycast IP addresses (no relation to the user's IP)"]]
