This document lists requirements for applications that you develop with
the Navigation SDK for iOS.

## Acceptable use

You can use the Navigation SDK for iOS to provide drivers with real-time
turn-by-turn navigation in a mobile application. You can also use the data
that the API generates in other applications to share information related to
driver status and to track driver locations generally.

## Disallowed use

You can use the Navigation SDK for iOS only for commercial applications.
You can't use the Navigation SDK for iOS for the following categories of
use cases without express prior written consent from Google:

For heavy or large vehicle routing or navigation, such as for buses,
trucks, or vehicles with road restrictions, you must use
[large vehicle routing with a
Google-provisioned project](https://developers.google.com/maps/documentation/routes/lvr) or ensure that the services explicitly
specify support for heavy or large vehicle navigation.

## Content scraping

The road name and speed limit can be returned to you based on user
interactions with your app. If you capture or persist the road name or
speed limit for use in any other context outside of the user session, this
action constitutes scraping, which isn't allowed by Google's terms.

## Acceptable modifications to the Navigation UI

The Navigation SDK for iOS lets you make certain UI customizations, such as
customizing the navigation map, adding custom markers, changing the size
and content of the header and footer surrounding the navigation viewport,
or changing the size of the navigation viewport itself. In some
situations, you might also want to overlay content on top of the active
navigation screen.

When you do so, you can't introduce modifications that inhibit safe use by
drivers. For example, you must avoid the following changes because they can
negatively affect driver safety:

- Showing distracting animations during active navigation.
- Showing overlays on the navigation screen without explicit driver action.
- Positioning overlays on the active navigation screen that hide the driver's current location or permanently block important navigation information. This information includes upcoming turns, lane guidance, compass orientation, and all standard UI elements in the navigation experience.
- Removing the road network from the navigation map or significantly reducing color contrast of map features on the navigation map.

## Other implementation requirements

- You can't modify the Navigation SDK in-product terms without prior written consent from Google.
- Your app must display the following information to users when they first use the app:
  - The Navigation SDK terms of use.
  - Users should always exercise independent judgment when using navigation, because information from the Navigation SDK service might differ from actual real-time conditions.
  - Users are solely responsible for costs incurred when following the directions provided by the Navigation SDK service, such as for toll fees or high-occupancy vehicle lanes.

## Google Maps attribution requirements

This section provides attribution requirements and guidelines for
displaying Google Maps and content through your applications.

> [!NOTE]
> **Note**: The following updated attribution requirements use "Google Maps" instead of only "Google." Your existing implementations might use the attribution of "Google," in alignment with prior guidance, and you can continue using "Google" as an attribution. For new implementations, use "Google Maps" as described in this section. Google provides timelines and instructions to help you transition existing "Google" attributions to "Google Maps" attributions.

### Display Google Maps attribution

You must follow Google Maps attribution requirements when displaying content
from Google Maps Platform APIs in your app or website. You don't need to add
extra attribution if the content is shown on a Google Map where the
attribution is already visible.

### Included Google Maps attribution

Follow these rules for Google Maps attribution that's already provided by
Google Maps Platform in the user interface:

- Don't remove included attribution regardless of where it's displayed. Don't alter, hide, or obscure the attribution, and make sure it's clearly visible against the background.
- Always visually distinguish Google Maps Platform content from other content by using UI cues such as a border, background color, shadow, or sufficient whitespace.
- When making visual modifications, you must follow all Google Maps attribution requirements.

### Google Maps logo and text attribution

Attribution takes the form of the Google Maps logo whenever possible.
In cases where space is limited, the text **Google Maps** is
acceptable. Make sure that it's always clear to users which content is
provided by Google Maps.

### Logo attribution

Follow these requirements for using the Google Maps logo in your app.
![Acceptable variations for Google Maps logo attribution](https://developers.google.com/static/maps/images/02_GMP_Logo_Alternates.jpg) Acceptable variations for Google Maps logo attribution

#### Download Google Maps logos

You can download the official Google Maps logo files and follow the
guidelines in this section.

[Download the Google Maps attribution assets](https://developers.google.com/static/maps/documentation/images/Google_Maps_Attribution_Assets.zip)

When using the Google Maps logo, follow these guidelines:

- Don't modify the logo in any way.
- Maintain the aspect ratio of the logo to prevent distortion.
- On a busy background, such as a map or image, use the outlined logo.
- On a plain background, such as a solid color or subtle gradient, use the non-outlined logo.

#### Logo size specification

Follow these size specifications for the Google Maps logo:

- **Minimum logo height**: 16dp
- **Maximum logo height**: 19dp
- **Minimum logo clear space**: 10dp on left, right, and top, 5dp on the bottom

For more information about pixel density, see
[Pixel density](https://m2.material.io/design/layout/pixel-density.html#pixel-density)
on the Material Design website.
![Google Maps logo showing minimum clear space and acceptable size range](https://developers.google.com/static/maps/images/03_GMP_Logo_Size_Specs.jpg) Google Maps logo showing minimum clear space and acceptable size range

#### Logo accessibility

Follow these accessibility requirements for the Google Maps logo:

- Maintain an [accessible contrast](https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html) between the logo and the background.
- Include an accessibility label with the text **Google Maps**.

![Unacceptable variations and accessibility issues for Google Maps logo attribution](https://developers.google.com/static/maps/images/04_GMP_Accessibility.png) Unacceptable variations and accessibility issues for Google Maps logo attribution

### Text attribution

If the size of your interface doesn't support using the Google Maps logo,
you can spell out **Google Maps** in text. Follow these
guidelines:
![Acceptable variations of the Google Maps text attribution](https://developers.google.com/static/maps/images/05_GMP_Text_Attribution.jpg) Acceptable variations of the Google Maps text attribution

- Don't modify the text **Google Maps** in any way:  
  - Don't change the capitalization of **Google Maps**.
  - Don't wrap **Google Maps** onto multiple lines.
  - Don't localize **Google Maps** into another language.
  - Don't let browsers translate **Google Maps** ; use the HTML attribute `translate="no"`.

![Unacceptable variations of the Google Maps text attribution](https://developers.google.com/static/maps/images/06_GMP_Text_Donts.jpg) Unacceptable variations of the Google Maps text attribution

- Style Google Maps text as described in the following table:

  | Google Maps text-styling requirements ||
  |---|---|
  | **Property** | **Style** |
  | Font family | [Roboto](https://fonts.google.com/specimen/Roboto?preview.text_type=custom). Loading the font is optional. |
  | Fallback font family | Any sans-serif body font already used in your product or "Sans-Serif" to invoke the default system font |
  | Font style | Normal |
  | Font weight | 400 |
  | Font color | White, black (#1F1F1F), or gray (#5E5E5E). Maintain accessible [(4.5:1)](https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html) contrast against the background. |
  | Font size | Minimum font size: 12sp Maximum font size: 16sp For more information about sp, see [Font size units](https://m3.material.io/styles/typography/type-scale-tokens#3f4488e7-3b74-45b0-a143-9d6afa4d62dc) on the Material Design website. |
  | Letter spacing | Normal |

#### Example CSS

The following CSS renders Google Maps with the appropriate typographic style
and color on a white or light background.

```
@import url('https://fonts.googleapis.com/css2?family=Roboto&display=swap');

.GMP-attribution {
font-family: Roboto, Sans-Serif;
font-style: normal;
font-weight: 400;
font-size: 1rem;
letter-spacing: normal;
white-space: nowrap;
color: #5e5e5e;
}
```

### Visual requirements

Follow these requirements for the visual treatment of Google Maps attribution.

- Position attribution near the top or bottom of the content, and within the same visual container. For a single line of content, attribution can be positioned to the right or left.
- Visually distinguish Google Maps Platform content from other content by using UI cues such as a border, background color, shadow, or sufficient whitespace.
- Don't misrepresent Google Maps by attributing it with non-Google Maps Platform content.
- Verify that the attribution is always visible and legible. Don't remove, hide, obscure, or modify it.