EEA 條款的變更會影響您使用這項服務「With any Map」中的 Google 地圖內容的方式。「搭配任何地圖」係指在任何地圖 (包括 Google 地圖) 上、旁邊或以與任何地圖視覺相關的方式顯示 Google 地圖內容,或將 Google 地圖內容連結至任何地圖,或將任何地圖連結至 Google 地圖內容 (除非所連結的特定地圖是適用 Google 地圖內容的來源)。
為求清楚明確,您可以繼續連結至「服務」提供的 Google 地圖內容來源連結 (例如 Places API 中的 googleMapsLinks)。
[null,null,["上次更新時間:2025-08-31 (世界標準時間)。"],[],[],null,["**Google Maps Platform EEA integration guides**\n\n- [Announcement \\& FAQ](/maps/comms/eea/faq) \n- [Address Validation API](/maps/comms/eea/address-validation)\n- [Directions API (Legacy)](/maps/comms/eea/directions)\n- [Distance Matrix API (Legacy)](/maps/comms/eea/distance-matrix)\n- [Geocoding API](/maps/comms/eea/geocoding)\n- **iOS Geocoder**\n- [Map Tiles API](/maps/comms/eea/map-tiles)\n- [Maps Static API](/maps/comms/eea/maps-static)\n- [Places API (New \\& Legacy)](/maps/comms/eea/places)\n- [Roads API](/maps/comms/eea/roads)\n- [Routes API](/maps/comms/eea/routes)\n- [Routes Preferred API](/maps/comms/eea/routes-preferred)\n- [Street View Static API](/maps/comms/eea/street-view-static)\n- [Solar API](/maps/comms/eea/solar)\n\nEffective **8 July 2025** , new **EEA-specific Google Maps Platform Terms of Service\n(EEA terms)** will impact how you build applications and experiences for users if your project\nis linked to an EEA billing account.\n\nWe strongly recommend that you read and understand the\n[announcement](/maps/comms/eea/faq), as the details potentially impact your\nexisting and new applications that integrate Google Maps Platform.\n\nThis document describes **usage and Google Maps Platform functionality changes** for the\n**iOS Geocoder within Dynamic Maps iOS SDK**.\n\nThe information described in this document reflects the\n[EEA terms\ngoverning your use of Google Maps Platform Services](https://cloud.google.com/terms/maps-platform/eea) as of 8 July 2025,\nwhich may change over time. For the most recent and binding terms applicable to you,\nsee your Google Maps Platform Agreement with Google.\n\niOS Geocoder within Dynamic Maps iOS SDK adjustments for EEA customers\n\nThese adjustments apply to (a) projects created after 8 July 2025 that\nare linked to an account with an EEA billing address,\nand/or to (b) projects that are no longer in the\n[Unmodified State](/maps/comms/eea/faq#material-modification)\nafter 8 July 2025.\n\nThe following table summarizes the adjustments, delineated in the\n[EEA\nService Specific Terms](https://cloud.google.com/terms/maps-platform/eea/maps-service-terms), for each Google Maps Platform service.\n\n| iOS Geocoder within Dynamic Maps iOS SDK Functionality Adjustments | Terms of Service Changes |\n|--------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|\n| None | *No Use With any Map*. Customer may not use (in whole or in part) any addresses from the iOS Geocoder within the Map SDK for iOS With any Map. |\n\nExamples of \"With any Map\" and \"without a map\"\n\nThe EEA terms changes affect how you use Google Maps Content from this service\n\"With any Map.\" \"With any Map\" means to display Google Maps Content on, next to,\nor in a manner that is visually associated with any map, including a Google map,\nor to link Google Maps Content to any map or link any map to Google Maps Content\n(unless the specific map being linked to is the source of the applicable Google Maps\nContent).\n\nFor clarity, you may continue to link to the Google Maps Content source links provided\nby the Service (for example, [`googleMapsLinks`](/maps/documentation/places/web-service/place-details#required-parameters)\nin the Places API).\n\nThe following examples are illustrations of what \"With any Map\" and \"without a map\"\ncan look like, to help you comply with the terms of your Agreement. The examples are not\ncomprehensive. Ultimately, you are responsible for complying with the terms of your\nAgreement.\n\n|---|--------------------------------------------------------------------------------------------------------------|\n| | The blue circles in the following examples represent Google Maps Content from Google Maps Platform Services. |\n\n|---|---|---|\n| | | |\n\n|---|---|---|\n| | | |\n\n\u003cbr /\u003e\n\nAlternative integrations\n\nIf you use the iOS Geocoder to display addresses on or next to a map,\nyou must change your integration. You may use Places UI Kit to\nsupport your application.\n\n\nPlaces UI Kit\n\nGoogle Maps Platform includes Places UI Kit, which lets you build integrations to help\nyour users visualize Places content with any map, or without any map.\nThe [Places API\nPermitted Uses](https://cloud.google.com/terms/maps-platform/eea-places-api-permitted-uses) restrictions don't apply to the Places UI Kit.\n\nFor example, Places UI Kit lets you display Place Details on a map or render a\nList of Places from a search next to a map, as illustrated in the following image.\n| **Note:** Places UI Kit elements for Place Details, Place Autocomplete, and Place Search will be generally available in mid-July 2025.\n\nUse the following resources to help you build with Places UI Kit:\n\n**Integration guides**\n\n- [Adopt Places UI Kit for Existing Places API Users](/maps/documentation/javascript/adopt-places-ui-kit)\n- [Discover Places with Place Search Element and Maps JavaScript API](/maps/architecture/discover-with-place-search-element)\n- [Build an Interactive Store Finder with Places UI Kit](/maps/architecture/ui-kit-store-finder)\n\n**Places UI Kit product documentation**\n\n- [JavaScript](/maps/documentation/javascript/places-ui-kit/overview)\n- [Android](/maps/documentation/places/android-sdk/places-ui-kit-overview)\n- [iOS](/maps/documentation/places/ios-sdk/places-ui-kit-overview)\n\nRoad safety\n\n\nEEA customers may now use Google Maps Platform Services, where suitable, in\nembedded vehicle systems. They may also use Google Maps Platform Services,\nwhere suitable, for real-time navigation with a third-party map, as long as that\nreal-time navigation usage complies with Google's safety requirements.\n\n\nDue to road safety risks that can arise under these new terms, Google now\nrequires that developers adhere to\n[safety\nrequirements](https://cloud.google.com/terms/maps-platform/eea-safety-requirements) in order to, for example, limit the risks of mismatched roads.\n| **Note:** Use of Google Maps Platform Services in embedded vehicle systems in the EEA occurs at each Customer's own discretion, and the Customer is responsible for compliance with any applicable laws, regulations, industry standards, or other requirements.\n\nWhat if I have additional questions not covered in this document?\n\nIf you have any technical questions not addressed in this document or the\n[General FAQ](/maps/comms/eea/faq),\nyou can contact [Google Maps Platform Support](/maps/support?utm_medium=MSA&utm_source=GMP_Billing_Admin&utm_campaign=Dec_24&utm_content=GMP_Support).\n\nIf you have a negotiated agreement with Google and have questions about your contract,\nyou can contact your Google Maps Platform representative. If you are unsure who your\naccount representative is, reach out using our\n[Contact Sales form](https://mapsplatform.google.com/contact-us/?utm_medium=MSA&utm_source=GMP_Billing_Admin&utm_campaign=Dec_24&utm_content=Contact_Sales)."]]