Google API 服務條款：主要異動內容摘要
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
本文件概述上述日期對《Google API 服務條款》做出的主要修訂。(另請參閱《2020 年服務條款》)。
2021 年 11 月 9 日：
3b：將「個人識別資訊」('PII') 變更為「個人資料」。
3d：明確連結至《Google API 服務使用者資料政策》，明確指出「條款」即包含此政策。
2020 年 11 月 18 日：
2i：加入條件式語言，以納入《Google 控管者與控管者資料保護條款》。
2019 年 1 月 16 日：
將「Google Inc.」變更為「Google LLC」。在第二段中。
2014 年 11 月 5 日和 2014 年 12 月 5 日：
第一段：闡明「條款」的適用範圍，以納入 API、其他開發人員服務及相關軟體；清楚說明「條款」與「Google」的相關關係，包括《Google API 服務條款》、其他 API 專屬條款、特定 API 的說明文件條款，以及適用政策和規範。
第 2 段：在 2014 年 11 月 5 日發布的「條款」中，我們更新了「Google 合約」實體。Google Asia Pacific Pte. Ltd. 或 Google Inc. (視帳單地址所在位置而定，以及 Google 是否提供帳單地址)。但在 2014 年 12 月 5 日發布的最新更新版本中，我們已經恢復為 Google 簽約實體，不過 Google API 合約實體可能僅由該 API 適用的其他條款取代了該 API。這個版本是在 2014 年 12 月 5 日進行的唯一變更。
1b：省略條款表示使用 API 可能需要建立 Google 帳戶；省略有關保留帳戶憑證與密碼的相關規定，如「條款」所涵蓋的條文；新增該 API 代表您代表實體，亦代表您有權代表該實體 (並因此同意) 本條款。
1c：只要新增資訊，您就能立即通知我們。
2b：加入您同意遵守第三方權利且不會違反 Google (或我們的關聯企業) 的任何其他服務條款。
2d：清楚說明 Google 對您的 API 使用情形設有使用限制，而如果您要超出這些限制，必須取得 Google 的明確同意 (Google 可以拒絕或條件接受您針對該使用方式提出的其他條款和/或費用接受協議)；請新增此內容以尋求相關核准，例如使用 Google Developer Console 與 Google API 小組聯絡。
2e：清楚說明開放原始碼軟體授權構成不同的書面協議，針對特定 API 的原始碼可能列於說明文件中；若開放原始碼軟體授權明確取代「條款」，在少數情況下，開放原始碼授權將另行與 Google 針對適用開放原始碼軟體達成協議。
2f (先前)：將監控語言移至其他區段 (第 3(a) 節)。
2h：清楚說明「條款」並非專屬條款，Google 可能會開發出可與 API 用戶端或其他產品或服務競爭的產品或服務。
3a：新增先前在第 2f 節所述的監控語言，並使該條文更加顯眼 (亦即全部大寫)。
3b：在「適用法律」的適用範圍內，加入報表義務。
3d：省略安全港的最後一個句子。
4a:除此之外，Google 無意使用 API 來建立《健康保險流通與責任法案》規範的義務，亦不聲明該 API 亦符合《健康保險流通與責任法案》的規定，且除非 Google 事先書面同意，否則您不得利用本 API 將受保護的健康資訊傳輸至 Google。
4b1：清楚說明開發人員憑證的用途為何，並指明您的 API 用戶端。您知道，機密性憑證必須保密，採取合理措施防止和防止其他 API 用戶端使用這些資料，也不得將其嵌入開放原始碼專案。
4b2：清楚說明我們的 API 可能包含 Google 機密資訊，如果您收到 Google 提供的資訊為機密資訊，或一般為機密資訊，那麼在未取得 Google 事先書面同意的情況下，您不得向任何第三方揭露這類資訊；而在法律上，如有必要事先提出通知，請事先保密。
5b (先前)：省略廣告規定。
5b：清楚說明 Google 提供內容授權的目的，僅讓 Google 得以根據適用的 Google 隱私權政策，提供、保護及改善 API (及相關服務)；清楚說明 Google 向「使用」內容授權之內容，定義為「使用」、「代管」、「儲存」、「修改」、「進行通訊」及「發布」等。
5d：清楚說明在您使用或儲存您透過 API 取得的使用者資料時，資料可攜權的義務依然有效；新增這項規定禁止您將資料提供給未遵守這項義務的第三方。
5e：加入他人的代理人不得從事任何禁止行為。
8a：清楚說明您停止使用或停止使用 API 時應立即終止；如果您想終止本條款，則必須事先向 Google 發出書面通知，並清楚說明 Google 有權基於任何理由終止您對本「條款」或其任何部分或功能的使用權。
8c：清楚說明第 4b、5 和 80 節在條款終止後仍然有效。
9a：清楚說明，除非「條款」另有明文規定，否則在法律允許的範圍內，我們會排除所有擔保、保證、條件、聲明及法律。
9b：清楚說明在法律所允許的最大範圍內。此外，加入 Google、我們的供應商和發布商對於不合理預見之任何費用概不負責。
10a：加入「條款」，您應定期檢閱本「條款」；新增這類聲明，我們可能會在說明文件、本網站及/或 Google Developers Console 上發布本「條款」之修訂通知；但註明，您對變更生效後未滿 30 天即生效 (如果是新的 API 功能，或基於法律原因而採用，可能會立即生效)；如果您不同意 API，請自行同意。
10b：新增適用於美國聯邦機構實體的條文。
1-
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
[null,null,[],[[["\u003cp\u003eThe Google APIs Terms of Service were updated to clarify the scope, usage, and responsibilities for developers utilizing Google's APIs.\u003c/p\u003e\n"],["\u003cp\u003eThe updates include changes in terminology, such as replacing "personally identifiable data" with "personal data," and incorporating the Google API Services User Data Policy.\u003c/p\u003e\n"],["\u003cp\u003eGoogle clarified limitations on API usage, data portability obligations, content licensing, and the handling of confidential information.\u003c/p\u003e\n"],["\u003cp\u003eThe revised terms address liability, warranties, termination of services, and the process for modifications and legal disputes.\u003c/p\u003e\n"],["\u003cp\u003eSpecific provisions were added for U.S. federal agency entities, and the contracting entity was changed to Google LLC.\u003c/p\u003e\n"]]],["Key changes to Google APIs Terms of Service include: updating \"personally identifiable data\" to \"personal data\"; explicitly linking to the User Data Policy; incorporating Data Protection Terms; changing the contracting entity; expanding the scope to include various developer services; clarifying limits on API usage and consent requirements; adding monitoring language; prohibiting certain API uses (e.g. ITAR data, health information); clarifying content licenses; adding data portability obligations; refining termination clauses; adding warranty exclusions and indemnity; updating notification procedures for term modifications; and adding provisions for government entities.\n"],null,["# Google APIs Terms of Service: Summary of Principal Changes\n\nThis document summarizes the principal changes made to the [Google APIs Terms of Service](/terms) on the dates above. (See also the [2020 Terms of Service](/terms/2020).)\n\n**November 9, 2021**:\n\n**3b**: Changed \"personally identifiable data ('PII')\" to \"personal data.\"\n\n**3d** : Explicitly link to the [Google API Services User Data Policy to clarify that the Terms include such policy](/terms/api-services-user-data-policy).\n\n**November 18, 2020**:\n\n**2i** : Adding conditional language incorporating the [Google Controller-Controller Data Protection Terms](https://privacy.google.com/businesses/gdprcontrollerterms).\n\n**January 16, 2019**:\n\nChanged \"Google Inc.\" to \"Google LLC\" in the second paragraph.\n\n**November 5, 2014 and December 5, 2014**:\n\n**1st paragraph**: Clarifying that scope of Terms expanded to include APIs, other developer services, and associated software; clarifying that the \"Terms\" governing relationship between you and Google include the terms set forth in the Google APIs Terms of Service, additional API specific terms, terms within documentation for a given API, and applicable policies and guidelines.\n\n**2nd paragraph**: In an interim updated version of the Terms published November 5, 2014, we changed the Google contracting entity from Google Inc. to either Google Ireland Ltd., Google Asia Pacific Pte. Ltd., or Google Inc. depending on the location of your billing address (and whether Google has a billing address for you). But in the latest updated version published December 5, 2014, we have reverted to just Google Inc. as the Google contracting entity, though that may be superseded for a given API by additional terms applicable just to that API. That reversion was the only change made in the December 5, 2014 version.\n\n**1b**: Omitting language stating that use of the APIs may require Google account creation; omitting provision around keeping account credentials and password secure, as that's covered elsewhere in the Terms; adding that if you use the APIs on behalf of an entity, you represent and warrant that you have authority to (and do thereby agree to) the Terms on behalf of that entity.\n\n**1c**: Adding that you will inform us promptly of updates.\n\n**2b**: Adding that you agree to comply with third party rights and to not violate any other terms of service with Google (or our affiliates).\n\n**2d**: Clarifying that Google enforces limits on your use of the APIs and if you want to use beyond these limits, you must obtain Google's express consent (which Google may decline or condition acceptance on your agreement to additional terms and/or charges for that use); adding that to seek such approval, you'll need to contact the relevant Google API team (e.g. by using the Google developer console).\n\n**2e**: Clarifying that open source software licenses constitute separate written agreements, for certain APIs, open source software may be listed in the documentation, and to the limited extent an open source software license expressly supersedes the Terms, the open source license instead sets forth your agreement with Google for the applicable open source software.\n\n**2f (prior)**: Moving the monitoring language to another section (Section 3(a)).\n\n**2h**: Clarifying that the Terms are non-exclusive and Google may develop products or services that may compete with the API Clients or other products or services.\n\n**3a**: Adding the monitoring language which was previously in section 2f and making that provision more prominent (i.e. all caps).\n\n**3b**: Adding that the reporting obligation applies to the extent required by applicable law.\n\n**3d**: Omitting the last sentence on Safe Harbor.\n\n**4a**: Adding that you may not allow those acting on your behalf to take any of the prohibited actions and adding new prohibitions against: (i) use of the APIs for activities where the use or failure of the APIs could lead to death, personal injury, or environmental damage; (ii) use of the APIs to process or store any data subject to ITAR; (iii) removing, obscuring, or altering any Google terms of service or any links to or notices of those terms. Adding that Google does not intend use of the APIs to create obligations under HIPAA, and makes no representations that the APIs satisfy HIPAA requirements, and that you will not use the APIs in connection with transmitting protected health information to Google unless Google has consented in writing in advance.\n\n**4b1**: Clarifying that developer credentials are intended to be used by you and identify your API Client and that you'll keep your credentials confidential, make reasonable efforts to prevent and discourage other API Clients from using them, and not embed them in open source projects.\n\n**4b2**: Clarifying that our APIs may include Google confidential information and if you receive Google information marked confidential or that would normally be considered confidential you won't disclose it to any third party without Google's prior written consent; adding new exceptions to the confidentiality definition and allowing disclosure when compelled by law if you provide us reasonable prior notice (unless a court orders otherwise).\n\n**5b (prior)**: Omitting advertising provisions.\n\n**5b**: Clarifying that the content license to Google is provided for the sole purpose of enabling Google to provide, secure, and improve the APIs (and the related service(s)) and only in accordance with the applicable Google privacy policies; clarifying that Google receives license to \"Use\" the content, defined to mean use, host, store, modify, communicate, and publish.\n\n**5d**: Clarifying that the data portability obligation lasts for as long as you use or store any user data that you obtained through the APIs; adding prohibition against you making the data available to third parties who do not also abide by this obligation.\n\n**5e**: Adding that others acting on your behalf may not commit any of the prohibited acts.\n\n**8a**: Clarifying that you may cease using the APIs with or without notice; if you want to terminate the Terms you must provide Google prior written notice, and clarifying that Google reserves the right to terminate the Terms with you or discontinue your access to the APIs or any portion or feature for any reason at any time without liability or obligation to you.\n\n**8c**: Clarifying that sections 4b, 5, and 8-10 survive termination of the Terms.\n\n**9a**: Clarifying that except as expressly set out in the Terms, to the extent permitted by law, we exclude all warranties, guarantees, conditions, representations, and undertakings.\n\n**9b**: Clarifying that the limitations are to the extent permitted by law; adding that Google, our suppliers, and our distributors are not responsible for any expense that is not reasonably foreseeable.\n\n**9c**: Clarifying that, unless prohibited by applicable law, if you are a business, you will defend and indemnify Google and the listed indemnitees against any liabilities, damages, losses, costs, fees (including legal fees), and expenses relating to any allegation or third-party legal proceeding to the extent arising from: (i) your (or your end users') misuse of the APIs; (ii) your (or your end users') violation of the Terms; or (iii) any content or data routed into or used with the APIs by you, those acting on your behalf, or your end users.\n\n**10a**: Adding that you should look at the Terms regularly; adding that we may post notice of modifications to the Terms in the documentation, to this website, and/or in the Google developers console; revising to reflect that changes are effective no sooner than 30 days after they are posted (other than changes specific to new API functionality or made for legal reasons, which may be immediate); adding that if you don't agree to modified Terms for an API, you should stop using that API.\n\n**10b**: Adding provisions applicable for U.S. federal agency entities.\n\n**10c**: Clarifying that we each agree to contract in English and if Google provides a translated version of the Terms, that's purely for convenience and the English version still governs; adding that the Terms don't create any agency, partnership, or joint venture and that nothing in the Terms will limit either party's ability to seek injunctive relief; adding that we are not liable for failure or delay in performance to the extent caused by circumstances beyond our reasonable control; adding that the Terms are the entire agreement between you and Google relating to its subject and supersede prior or contemporaneous agreements on that subject; adding a link to information about how to contact Google; adding governing law and venue provisions applicable for U.S. federal government entities and U.S. city, county, or state government entities."]]
