| **Important:** [Express interest in developing the Video Discovery
| API](http://g.co/tv/vda).

Continue Watching leverages the **Continuation cluster** to show unfinished
videos, and next episodes to be watched from the same TV season, from multiple
apps in one UI grouping. You can feature their entities in this
continuation cluster. Follow this guide to learn how to enhance user engagement
through the Continue Watching experience using [Engage SDK](https://developer.android.com/guide/playcore/engage).

### Pre-work

Before you begin, complete the following steps:

1. update to Target API 19 or higher

2. Add the `com.google.android.engage` library to your app:

   There are separate SDKs to use in the integration: one for mobile apps and one
   for TV apps.  

   ### Mobile


         dependencies {
           implementation 'com.google.android.engage:engage-core:1.5.11
         }

   ### TV


         dependencies {
           implementation 'com.google.android.engage:engage-tv:1.0.5
         }

3. Set the Engage service environment to production in the `AndroidManifest.xml` file.

   **Important:** This should only be done before creating a release build. For your local testing with verification app, remove this.  

   ### Mobile


       `<meta-data
           android:name="com.google.android.engage.service.ENV"
           android:value="PRODUCTION" />`

   ### TV


       `<meta-data
           android:name="com.google.android.engage.service.ENV"
           android:value="PRODUCTION" />`

4. Add permission for `WRITE_EPG_DATA` for tv apk

       <uses-permission android:name="com.android.providers.tv.permission.WRITE_EPG_DATA" />

5. Verify reliable content publishing by using a background service,
   such as `androidx.work`, for scheduling.

6. To provide a seamless viewing experience, publish continue watching data
   when these events occur:

   1. First Login: When a user logs in for the first time, publish data to make sure their viewing history is immediately available.
   2. Profile Creation or Switching (Multi-Profile Apps): If your app supports multiple profiles, publish data when a user creates or switches profiles.
   3. Video Playback Interruption: To help users pick up where they left off, publish data when they pause or stop a video, or when the app exits during playback.
   4. Continue Watching Tray Updates (If Supported): When a user removes an item from their Continue Watching tray, reflect that change by publishing updated data.
   5. Video Completion:
      1. For movies, remove the completed movie from the Continue Watching tray. If the movie is part of a series, add the next movie to keep the user engaged.
      2. For episodes, remove the completed episode and add the next episode in the series, if available, to encourage continued viewing.

### Sample code

This [sample app](https://github.com/googlesamples/tv-video-discovery-samples) demonstrates how developers can integrate
with the video discovery APIs to send personalized user data to Google.
The sample app also demonstrates how to build a common module that can be
imported in both the mobile and TV apps, when to invoke the publish and delete
APIs, and how to use Workers to invoke the publish and delete APIs.

### Integration

| **Note:** The Continue Watching API works differently from the [Watch Next API](https://developer.android.com/training/tv/discovery/watch-next-add-programs). Instead of adding or removing items one by one, it replaces the entire list of "continue watching" items each time it updates. This means you need to send all the items you want to show every time you update. You should display as many entities as possible in the continue watching row, but now more than 10. Also, the new API combines the steps for publishing the list and the items into one, making it simpler. Keep in mind that Google TV might not show all the items you send, as it combines lists from different apps.

#### AccountProfile

To allow a personalized "continue watching" experience on Google TV,
provide account and profile information. Use the AccountProfile to
provide:

1. Account ID: A unique identifier that represents the user's account within
   your application. This can be the actual account ID or an appropriately
   obfuscated version.

2. Profile ID (optional): If your application supports multiple profiles within
   a single account, provide a unique identifier for the specific user profile
   (again, real or obfuscated).

**Note:** If you choose to obfuscate the account ID or profile ID, use the same obfuscation logic consistently.  

    // If your app only supports account
    val accountProfile = AccountProfile.Builder()
        .setAccountId("your_users_account_id")
        .build()

    // If your app supports both account and profile
    val accountProfile = AccountProfile.Builder()
        .setAccountId("your_users_account_id")
        .setProfileId("your_users_profile_id")
        .build()

#### Create entities

The SDK has defined different entities to represent each item type. Continuation
cluster supports following entities:

1. [`MovieEntity`](https://developer.android.com/guide/playcore/engage/watch#movieentity)
2. [`TvEpisodeEntity`](https://developer.android.com/guide/playcore/engage/watch#tvepisodeentity)
3. [`LiveStreamingVideoEntity`](https://developer.android.com/guide/playcore/engage/watch#livestreamingvideoentity)
4. [`VideoClipEntity`](https://developer.android.com/guide/playcore/engage/watch#videoclipentity)

| **Note:** [`TvShowEntity`](https://developer.android.com/guide/playcore/engage/watch#tvshowentity) and [`TvSeasonEntity`](https://developer.android.com/guide/playcore/engage/watch#tvseasonentity) are not supported for the Continuation cluster for continue watching. When a user finishes one TV Episode, the next `TvEpisodeEntity` should be published for the user to continue watching the next episode.

Specify the platform-specific URIs and poster images for these entities.

Also, create playback URIs for each platform---such as Android
TV, Android, or iOS---if you haven't already. So when a user continues watching
on each platform, the app uses a targeted playback URI to play the video
content.
**Note:** In the rare case when the playback URIs are identical for all platforms, you will still have to repeat it for every platform that you want to continue watching to happen.  

    // Required. Set this when you want continue watching entities to show up on
    // Google TV
    val playbackUriTv = PlatformSpecificUri.Builder()
        .setPlatformType(PlatformType.TYPE_ANDROID_TV)
        .setActionUri(Uri.parse("https://www.example.com/entity_uri_for_tv"))
        .build()

    // Required. Set this when you want continue watching entities to show up on
    // Google TV Android app, Entertainment Space, Playstore Widget
    val playbackUriAndroid = PlatformSpecificUri.Builder()
        .setPlatformType(PlatformType.TYPE_ANDROID_MOBILE)
        .setActionUri(Uri.parse("https://www.example.com/entity_uri_for_android"))
        .build()

    // Optional. Set this when you want continue watching entities to show up on
    // Google TV iOS app
    val playbackUriIos = PlatformSpecificUri.Builder()
        .setPlatformType(PlatformType.TYPE_IOS)
        .setActionUri(Uri.parse("https://www.example.com/entity_uri_for_ios"))
        .build()

    val platformSpecificPlaybackUris =
        Arrays.asList(playbackUriTv, playbackUriAndroid, playbackUriIos)

Poster images require a URI and pixel dimensions (height and width). Target
different form factors by providing multiple poster images, but verify that all
images maintain a 16:9 aspect ratio and a minimum height of 200 pixels for
correct display of the "Continue Watching" entity, especially within Google's
[Entertainment Space](https://support.google.com/entertainmentspace/answer/10346911). Images with a height less than 200 pixels
may not be shown.  

    val images = Arrays.asList(
        Image.Builder()
            .setImageUri(Uri.parse("http://www.example.com/entity_image1.png"))
            .setImageHeightInPixel(300)
            .setImageWidthInPixel(169)
            .build(),
        Image.Builder()
            .setImageUri(Uri.parse("http://www.example.com/entity_image2.png"))
            .setImageHeightInPixel(640)
            .setImageWidthInPixel(360)
            .build()
        // Consider adding other images for different form factors
    )

##### MovieEntity

This example show how to create a `MovieEntity` with all the required fields:  

    val movieEntity = MovieEntity.Builder()
       .setWatchNextType(WatchNextType.TYPE_CONTINUE)
       .setName("Movie name")
       .addPlatformSpecificPlaybackUri(platformSpecificPlaybackUris)
       .addPosterImages(images)
       // Timestamp in millis for sample last engagement time 12/1/2023 00:00:00
       .setLastEngagementTimeMillis(1701388800000)
       // Suppose the duration is 2 hours, it is 72000000 in milliseconds
       .setDurationMills(72000000)
       // Suppose last playback offset is 1 hour, 36000000 in milliseconds
       .setLastPlayBackPositionTimeMillis(36000000)
       .build()

Providing details like genres and content ratings gives Google TV the power to
showcase your content in more dynamic ways and connect it with the right
viewers.  

    val genres = Arrays.asList("Action", "Science fiction")
    val rating1 = RatingSystem.Builder().setAgencyName("MPAA").setRating("PG-13").build()
    val contentRatings = Arrays.asList(rating1)
    val movieEntity = MovieEntity.Builder()
        ...
        .addGenres(genres)
        .addContentRatings(contentRatings)
        .build()

Entities automatically remain available for 60 days unless you specify a shorter
expiration time. Only set a custom expiration if you need the entity to be
removed before this default period.  

    // Set the expiration time to be now plus 30 days in milliseconds
    val expirationTime = DisplayTimeWindow.Builder()
        .setEndTimestampMillis(now().toMillis()+2592000000).build()
    val movieEntity = MovieEntity.Builder()
        ...
        .addAvailabilityTimeWindow(expirationTime)
        .build()

##### TvEpisodeEntity

This example show how to create a `TvEpisodeEntity` with all the required
fields:  

    val tvEpisodeEntity = TvEpisodeEntity.Builder()
        .setWatchNextType(WatchNextType.TYPE_CONTINUE)
        .setName("Episode name")
        .addPlatformSpecificPlaybackUri(platformSpecificPlaybackUris)
        .addPosterImages(images)
        // Timestamp in millis for sample last engagement time 12/1/2023 00:00:00
        .setLastEngagementTimeMillis(1701388800000)
        .setDurationMills(72000000) // 2 hours in milliseconds
        // 45 minutes and 15 seconds in milliseconds is 2715000
        .setLastPlayBackPositionTimeMillis(2715000)
        .setEpisodeNumber("2")
        .setSeasonNumber("1")
        .setShowTitle("Title of the show")
        .build()

Episode number string (such as `"2"`), and season number string (such as `"1"`)
will be expanded to the proper form before being displayed on the continue
watching card. Note that they should be a numeric string, don't put "e2",
or "episode 2", or "s1" or "season 1".

If a particular TV show has a single season, set season number as 1.

To maximize the chances of viewers finding your content on Google TV, consider
providing additional data such as genres, content ratings, and availability time
windows, as these details can enhance displays and filtering options.  

    val genres = Arrays.asList("Action", "Science fiction")
    val rating1 = RatingSystem.Builder().setAgencyName("MPAA").setRating("PG-13").build()
    val contentRatings = Arrays.asList(rating1)
    val tvEpisodeEntity = TvEpisodeEntity.Builder()
        ...
        .addGenres(genres)
        .addContentRatings(contentRatings)
        .setSeasonTitle("Season Title")
        .setShowTitle("Show Title")
        .build()

##### VideoClipEntity

Here's an example of creating a `VideoClipEntity` with all the required fields.

`VideoClipEntity` represents a user generated clip like a Youtube video.  

    val videoClipEntity = VideoClipEntity.Builder()
        .setPlaybackUri(Uri.parse("https://www.example.com/uri_for_current_platform")
        .setWatchNextType(WatchNextType.TYPE_CONTINUE)
        .setName("Video clip name")
        .addPlatformSpecificPlaybackUri(platformSpecificPlaybackUris)
        .addPosterImages(images)
        // Timestamp in millis for sample last engagement time 12/1/2023 00:00:00
        .setLastEngagementTimeMillis(1701388800000)
        .setDurationMills(600000) //10 minutes in milliseconds
        .setLastPlayBackPositionTimeMillis(300000) //5 minutes in milliseconds
        .addContentRating(contentRating)
        .build()

You can optionally set the creator, creator image, created time in milliseconds,
or availability time window .

##### LiveStreamingVideoEntity

Here's an example of creating an `LiveStreamingVideoEntity` with all the
required fields.  

    val liveStreamingVideoEntity = LiveStreamingVideoEntity.Builder()
        .setPlaybackUri(Uri.parse("https://www.example.com/uri_for_current_platform")
        .setWatchNextType(WatchNextType.TYPE_CONTINUE)
        .setName("Live streaming name")
        .addPlatformSpecificPlaybackUri(platformSpecificPlaybackUris)
        .addPosterImages(images)
        // Timestamp in millis for sample last engagement time 12/1/2023 00:00:00
        .setLastEngagementTimeMillis(1701388800000)
        .setDurationMills(72000000) //2 hours in milliseconds
        .setLastPlayBackPositionTimeMillis(36000000) //1 hour in milliseconds
        .addContentRating(contentRating)
        .build()

Optionally, you can set the start time, broadcaster, broadcaster icon, or
availability time window for the live streaming entity.

For detailed information on attributes and requirements,
see the [API reference](https://developer.android.com/reference/com/google/android/engage/video/datamodel/package-summary).

#### Provide Continuation cluster data

`AppEngagePublishClient` is responsible for publishing the Continuation cluster.
You use the `publishContinuationCluster()` method to publish a
`ContinuationCluster` object.

First, you should use [isServiceAvailable()](https://developer.android.com/guide/playcore/engage/watch#isserviceavailable) to check if the service is
available for integration.  

    client.publishContinuationCluster(
        PublishContinuationClusterRequest
            .Builder()
            .setContinuationCluster(
                ContinuationCluster.Builder()
                    .setAccountProfile(accountProfile)
                    .addEntity(movieEntity1)
                    .addEntity(movieEntity2)
                    .addEntity(tvEpisodeEntity1)
                    .addEntity(tvEpisodeEntity2)
                    .setSyncAcrossDevices(true)
                    .build()
            )
            .build()
    )

When the service receives the request, the following actions take place within
one transaction:

- Existing `ContinuationCluster` data from the developer partner is removed.
- Data from the request is parsed and stored in the updated `ContinuationCluster`.

In case of an error, the entire request is rejected and the existing state is
maintained.

The publish APIs are upsert APIs; it replaces the existing content.
If you need to update a specific entity in the ContinuationCluster, you will
need to publish all entities again.

ContinuationCluster data should only be provided for adult accounts.
Publish only when the AccountProfile belongs to an adult.
| **Warning:** Don't call delete and publish APIs subsequently to replace the content as the publish APIs do that inherently.

##### Cross-device syncing

`SyncAcrossDevices` flag controls whether a user's `ContinuationCluster` data is
synchronized across devices such as TV, phone, tablets, etc.
Cross-device syncing is disabled by default.

Values:

- true: ContinuationCluster data is shared across all the user's devices for a seamless viewing experience. We strongly recommend this option for the best cross-device experience.
- false: ContinuationCluster data is restricted to the current device.

##### Obtain Consent:

The media application must provide a clear setting to enable/disable
cross-device syncing. Explain the benefits to the user and store the user's
preference once and apply it in publishContinuationCluster accordingly.  

    // Example to allow cross device syncing.
    client.publishContinuationCluster(
        PublishContinuationClusterRequest
            .Builder()
            .setContinuationCluster(
                ContinuationCluster.Builder()
                    .setAccountProfile(accountProfile)
                    .setSyncAcrossDevices(true)
                    .build()
            )
            .build()
    )

To get the most out of our cross-device feature, verify that the app obtains
user consent and enable `SyncAcrossDevices` to `true`. This allows content to
seamlessly sync across devices, leading to a better user experience and
increased engagement. For example, a partner who implemented this saw a 40%
increase in "continue watching" clicks because their content was surfaced on
multiple devices.

##### Delete the Video discovery data

To manually delete a user's data from the Google TV server before the standard
60-day retention period, use the client.deleteClusters() method. Upon receiving
the request, the service will delete all existing video discovery data for the
account profile, or for the entire account.
| **Important:** It is important to set syncAcrossDevices flag to true even in the delete requests so that the data is deleted from the server (even when the delete reason is USER_LOGOUT).

The [`DeleteReason`](https://developer.android.com/reference/com/google/android/engage/service/DeleteReason) enum defines the reason for data deletion.
The following code removes continue watching data on logout.  


    // If the user logs out from your media app, you must make the following call
    // to remove continue watching data from the current google TV device,
    // otherwise, the continue watching data will persist on the current
    // google TV device until 60 days later.
    client.deleteClusters(
        DeleteClustersRequest.Builder()
            .setAccountProfile(AccountProfile())
            .setReason(DeleteReason.DELETE_REASON_USER_LOG_OUT)
            .setSyncAcrossDevices(true)
            .build()
    )

| **Warning:** Don't call delete and publish APIs subsequently to replace the content as the publish APIs do that inherently.

### Testing

Use the verification app to verify that Engage SDK integration is working
correctly.
The [verification app](https://developer.android.com/guide/playcore/engage/tv#lightbox-trigger)
provides tools to help you verify your data and confirm that broadcast intents
are being handled properly.
| **Note:** Check if your app is correctly calling `isServiceAvailable` and `publishClusters` APIs in logcat. Before submitting the APK, check if you are able to see `publishClusters()` is called logs in your logcat during development to verify that you are calling the APIs at the correct events.

After you invoke the publish API, confirm that your data is being correctly
published by checking the verification app. Your continuation cluster should be
displayed as a distinct row within the app's interface.

- Set [Engage Service Flag](https://developer.android.com/guide/playcore/engage/workflow#switch-to-prod) only for non-production builds in your app's Android Manifest file.
- Install and open the Engage Verify app
- If `isServiceAvailable` is `false`, click the "Toggle" button to enable.
- Enter your app's package name to automatically view published data once you begin publishing.
- Test these actions in your app:
  - Sign in.
  - Switch between profiles(if applicable).
  - Start, then pause a video, or return to the home page.
  - Close the app during video playback.
  - Remove an item from the "Continue Watching" row (if supported).
- After each action, confirm that your app invoked the `publishContinuationClusters` API and that the data is correctly displayed in the verification app.
- The verification app will show a green "All Good" check for correctly
  implemented entities.

  ![Verification App Success Screenshot](https://developer.android.com/static/images/guide/playcore/engage/va-success.png) **Figure 1.** Verification App Success
- The verification app will flag any problematic entities.

  ![Verification App Error Screenshot](https://developer.android.com/static/images/guide/playcore/engage/va-error.png) **Figure 2.** Verification App Error
- To troubleshoot entities with errors, use your TV remote to select and click
  the entity in the verification app. The specific problems will be displayed
  and highlighted in red for your review (see example below).

  ![Verification App error details](https://developer.android.com/static/images/guide/playcore/engage/va-error-details.png) **Figure 3.** Verification App Error Details

### REST API

Engage SDK offers a REST API to provide a consistent continue watching
experience across non-Android platforms such as iOS, Roku TV. The API allows
developers to update the "Continue-Watching" status for opted-in users from
non-Android platforms.

#### Prerequisites

- You must first finish the [on-device Engage SDK-based](https://developer.android.com/guide/playcore/engage/tv#integration) integration. This critical step establishes the necessary association between Google's user ID and your app's `AccountProfile`.
- API Access and Authentication: To view and enable the API in your Google Cloud Project, you must go through an allowlist process. All API requests require authentication.

#### Gaining Access

In order to gain access to view and enable the API in your Google Cloud Console,
your account need to be enrolled.

1. Google Workspace Customer Id should be available. If not available you may need to set up a Google Workspace as well as any Google Accounts you want to use to call the API.
2. Setup an account with Google Cloud Console using an email associated with the Google Workspace.
3. [Create a new project](https://support.google.com/googleapi/answer/6251787?ref_topic=7014522#zippy=%2Ccreate-a-project)
4. Create a [service account](https://developer.android.com/identity/protocols/oauth2/service-account) for API Authentication. Once you create the service account, you will have two items:
   - A service account ID.
   - A JSON file with your service account key. Keep this file secure, you'll need it to authenticate your client to the API later.
5. Workspace and associated Google Accounts can now be able to use REST APIs. Once the change has propagated you will be notified whether the API is ready to be called by your service accounts.
6. Follow these [steps](https://developer.android.com/identity/protocols/oauth2/service-account#authorizingrequests) to preparing to make a delegated API call.

#### Publish Continuation Cluster

To publish the Video Discovery Data, perform a POST request to the
`publishContinuationCluster` API using the following syntax.  

    https://tvvideodiscovery.googleapis.com/v1/packages/{package_name}/accounts/{account_id}/profiles/{profile_id}/publishContinuationCluster

Where:

- `package_name`: The media provider package name
- `accountId`: The unique ID for the user's account in your system. It must match the `accountId` used in the on-device path.
- `profileId`: The unique ID for the user's profile within the account in your system. It must match the profileId used in the on-device path.

The URL for the account without profile is:  

    https://tvvideodiscovery.googleapis.com/v1/packages/{package_name}/accounts/{account_id}/publishContinuationCluster

The payload to the request is represented in the `entities` field. `entities`
represents a list of content entities which can be either `MovieEntity` or
`TVEpisodeEntity`. This is a required field.

##### Request Body

|---|---|---|---|
| **Field** | **Type** | **Required** | **Description** |
| entities | List of MediaEntity Objects | Yes | List of content entities (max 5), only the top five will be retained and the rest dropped.Empty list is allowed to signify the user has finished watching all entities. |

Field `entities` contains individual `movieEntity` and `tvEpisodeEntity`.

|---|---|---|---|
| **Field** | **Type** | **Required** | **Description** |
| movieEntity | MovieEntity | Yes | An object representing a movie within the ContinuationCluster. |
| tvEpisodeEntity | TvEpisodeEntity | Yes | An object representing a tv episode within the ContinuationCluster. |

Each object in the entities array must be one of the available MediaEntity types
namely [`MovieEntity`](https://developer.android.com/reference/com/google/android/engage/video/datamodel/MovieEntity) and [`TvEpisodeEntity`](https://developer.android.com/reference/com/google/android/engage/video/datamodel/TvEpisodeEntity),along with common and
type-specific fields.

Following code snippet showcase the request body payload for the
`publishContinuationCluster` API.  

    {
      "entities": [
        {
          "movieEntity": {
            "watch_next_type": "WATCH_NEXT_TYPE_CONTINUE",
            "name": "Movie1",
            "platform_specific_playback_uris": [
              "https://www.example.com/entity_uri_for_android",
              "https://www.example.com/entity_uri_for_iOS"
            ],
            "poster_images": [
              "http://www.example.com/movie1_img1.png",
              "http://www.example.com/movie1_imag2.png"
            ],
            "last_engagement_time_millis": 864600000,
            "duration_millis": 5400000,
            "last_play_back_position_time_millis": 3241111
          }
        },
        {
          "tvEpisodeEntity": {
            "watch_next_type": "WATCH_NEXT_TYPE_CONTINUE",
            "name": "TV SERIES EPISODE 1",
            "platform_specific_playback_uris": [
              "https://www.example.com/entity_uri_for_android",
              "https://www.example.com/entity_uri_for_iOS"
            ],
            "poster_images": [
              "http://www.example.com/episode1_img1.png",
              "http://www.example.com/episode1_imag2.png"
            ],
            "last_engagement_time_millis": 864600000,
            "duration_millis": 1800000,
            "last_play_back_position_time_millis": 2141231,
            "episode_display_number": "1",
            "season_number": "1",
            "show_title": "title"
          }
        }
      ]
    }

#### Delete the video discovery data

Use the `clearClusters` API to remove the video discovery data.

Use POST URL to remove the entities from video discovery data.
To delete the continuation cluster data, perform a POST request to the
`clearClusters` API using the following syntax.  

    https://tvvideodiscovery.googleapis.com/v1/packages/{package_name}/accounts/{account_id}/profiles/{profile_id}/clearClusters

Where:

- `package_name`: The media provider package name.
- `accountId`: The unique ID for the user's account in your system. It must match the `accountId` used in the on-device path.
- `profileId`: The unique ID for the user's profile within the account in your system. It must match the profileId used in the on-device path.

The payload for the `clearClusters` API contains only one field, `reason`,
which contains a [`DeleteReason`](https://developer.android.com/reference/com/google/android/engage/service/DeleteReason) that specifies the reason for removing
data.  

    {
      "reason": "DELETE_REASON_LOSS_OF_CONSENT"
    }

#### Testing

After successfully posting data, use a user test account to verify
that the expected content appears in the "Continue Watching" row on target
Google surfaces such as Google TV and the Android and iOS Google TV mobile apps.

In testing, allow a reasonable propagation delay of few minutes and adhere to
the watch requirements, such as watching part of a movie or finishing an
episode. Consult the [Watch Next guidelines for app developers](https://developer.android.com/training/tv/discovery/guidelines-app-developers#unfinished-movies) for details.  

## Download

Before downloading, you must agree to the following terms and conditions.  

## Terms and Conditions

This is the Android Software Development Kit License Agreement

### 1. Introduction

1.1 The Android Software Development Kit (referred to in the License Agreement as the "SDK" and specifically including the Android system files, packaged APIs, and Google APIs add-ons) is licensed to you subject to the terms of the License Agreement. The License Agreement forms a legally binding contract between you and Google in relation to your use of the SDK. 1.2 "Android" means the Android software stack for devices, as made available under the Android Open Source Project, which is located at the following URL: https://source.android.com/, as updated from time to time. 1.3 A "compatible implementation" means any Android device that (i) complies with the Android Compatibility Definition document, which can be found at the Android compatibility website (https://source.android.com/compatibility) and which may be updated from time to time; and (ii) successfully passes the Android Compatibility Test Suite (CTS). 1.4 "Google" means Google LLC, organized under the laws of the State of Delaware, USA, and operating under the laws of the USA with principal place of business at 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA.

### 2. Accepting this License Agreement

2.1 In order to use the SDK, you must first agree to the License Agreement. You may not use the SDK if you do not accept the License Agreement. 2.2 By clicking to accept and/or using this SDK, you hereby agree to the terms of the License Agreement. 2.3 You may not use the SDK and may not accept the License Agreement if you are a person barred from receiving the SDK under the laws of the United States or other countries, including the country in which you are resident or from which you use the SDK. 2.4 If you are agreeing to be bound by the License Agreement on behalf of your employer or other entity, you represent and warrant that you have full legal authority to bind your employer or such entity to the License Agreement. If you do not have the requisite authority, you may not accept the License Agreement or use the SDK on behalf of your employer or other entity.

### 3. SDK License from Google

3.1 Subject to the terms of the License Agreement, Google grants you a limited, worldwide, royalty-free, non-assignable, non-exclusive, and non-sublicensable license to use the SDK solely to develop applications for compatible implementations of Android. 3.2 You may not use this SDK to develop applications for other platforms (including non-compatible implementations of Android) or to develop another SDK. You are of course free to develop applications for other platforms, including non-compatible implementations of Android, provided that this SDK is not used for that purpose. 3.3 You agree that Google or third parties own all legal right, title and interest in and to the SDK, including any Intellectual Property Rights that subsist in the SDK. "Intellectual Property Rights" means any and all rights under patent law, copyright law, trade secret law, trademark law, and any and all other proprietary rights. Google reserves all rights not expressly granted to you. 3.4 You may not use the SDK for any purpose not expressly permitted by the License Agreement. Except to the extent required by applicable third party licenses, you may not copy (except for backup purposes), modify, adapt, redistribute, decompile, reverse engineer, disassemble, or create derivative works of the SDK or any part of the SDK. 3.5 Use, reproduction and distribution of components of the SDK licensed under an open source software license are governed solely by the terms of that open source software license and not the License Agreement. 3.6 You agree that the form and nature of the SDK that Google provides may change without prior notice to you and that future versions of the SDK may be incompatible with applications developed on previous versions of the SDK. You agree that Google may stop (permanently or temporarily) providing the SDK (or any features within the SDK) to you or to users generally at Google's sole discretion, without prior notice to you. 3.7 Nothing in the License Agreement gives you a right to use any of Google's trade names, trademarks, service marks, logos, domain names, or other distinctive brand features. 3.8 You agree that you will not remove, obscure, or alter any proprietary rights notices (including copyright and trademark notices) that may be affixed to or contained within the SDK.

### 4. Use of the SDK by You

4.1 Google agrees that it obtains no right, title or interest from you (or your licensors) under the License Agreement in or to any software applications that you develop using the SDK, including any intellectual property rights that subsist in those applications. 4.2 You agree to use the SDK and write applications only for purposes that are permitted by (a) the License Agreement and (b) any applicable law, regulation or generally accepted practices or guidelines in the relevant jurisdictions (including any laws regarding the export of data or software to and from the United States or other relevant countries). 4.3 You agree that if you use the SDK to develop applications for general public users, you will protect the privacy and legal rights of those users. If the users provide you with user names, passwords, or other login information or personal information, you must make the users aware that the information will be available to your application, and you must provide legally adequate privacy notice and protection for those users. If your application stores personal or sensitive information provided by users, it must do so securely. If the user provides your application with Google Account information, your application may only use that information to access the user's Google Account when, and for the limited purposes for which, the user has given you permission to do so. 4.4 You agree that you will not engage in any activity with the SDK, including the development or distribution of an application, that interferes with, disrupts, damages, or accesses in an unauthorized manner the servers, networks, or other properties or services of any third party including, but not limited to, Google or any mobile communications carrier. 4.5 You agree that you are solely responsible for (and that Google has no responsibility to you or to any third party for) any data, content, or resources that you create, transmit or display through Android and/or applications for Android, and for the consequences of your actions (including any loss or damage which Google may suffer) by doing so. 4.6 You agree that you are solely responsible for (and that Google has no responsibility to you or to any third party for) any breach of your obligations under the License Agreement, any applicable third party contract or Terms of Service, or any applicable law or regulation, and for the consequences (including any loss or damage which Google or any third party may suffer) of any such breach.

### 5. Your Developer Credentials

5.1 You agree that you are responsible for maintaining the confidentiality of any developer credentials that may be issued to you by Google or which you may choose yourself and that you will be solely responsible for all applications that are developed under your developer credentials.

### 6. Privacy and Information

6.1 In order to continually innovate and improve the SDK, Google may collect certain usage statistics from the software including but not limited to a unique identifier, associated IP address, version number of the software, and information on which tools and/or services in the SDK are being used and how they are being used. Before any of this information is collected, the SDK will notify you and seek your consent. If you withhold consent, the information will not be collected. 6.2 The data collected is examined in the aggregate to improve the SDK and is maintained in accordance with Google's Privacy Policy, which is located at the following URL: https://policies.google.com/privacy 6.3 Anonymized and aggregated sets of the data may be shared with Google partners to improve the SDK.

### 7. Third Party Applications

7.1 If you use the SDK to run applications developed by a third party or that access data, content or resources provided by a third party, you agree that Google is not responsible for those applications, data, content, or resources. You understand that all data, content or resources which you may access through such third party applications are the sole responsibility of the person from which they originated and that Google is not liable for any loss or damage that you may experience as a result of the use or access of any of those third party applications, data, content, or resources. 7.2 You should be aware the data, content, and resources presented to you through such a third party application may be protected by intellectual property rights which are owned by the providers (or by other persons or companies on their behalf). You may not modify, rent, lease, loan, sell, distribute or create derivative works based on these data, content, or resources (either in whole or in part) unless you have been specifically given permission to do so by the relevant owners. 7.3 You acknowledge that your use of such third party applications, data, content, or resources may be subject to separate terms between you and the relevant third party. In that case, the License Agreement does not affect your legal relationship with these third parties.

### 8. Using Android APIs

8.1 Google Data APIs 8.1.1 If you use any API to retrieve data from Google, you acknowledge that the data may be protected by intellectual property rights which are owned by Google or those parties that provide the data (or by other persons or companies on their behalf). Your use of any such API may be subject to additional Terms of Service. You may not modify, rent, lease, loan, sell, distribute or create derivative works based on this data (either in whole or in part) unless allowed by the relevant Terms of Service. 8.1.2 If you use any API to retrieve a user's data from Google, you acknowledge and agree that you shall retrieve data only with the user's explicit consent and only when, and for the limited purposes for which, the user has given you permission to do so. If you use the Android Recognition Service API, documented at the following URL: <https://developer.android.com/reference/android/speech/RecognitionService>, as updated from time to time, you acknowledge that the use of the API is subject to the Data Processing Addendum for Products where Google is a Data Processor, which is located at the following URL: <https://privacy.google.com/businesses/gdprprocessorterms/>, as updated from time to time. By clicking to accept, you hereby agree to the terms of the Data Processing Addendum for Products where Google is a Data Processor.

### 9. Terminating this License Agreement

9.1 The License Agreement will continue to apply until terminated by either you or Google as set out below. 9.2 If you want to terminate the License Agreement, you may do so by ceasing your use of the SDK and any relevant developer credentials. 9.3 Google may at any time, terminate the License Agreement with you if: (A) you have breached any provision of the License Agreement; or (B) Google is required to do so by law; or (C) the partner with whom Google offered certain parts of SDK (such as APIs) to you has terminated its relationship with Google or ceased to offer certain parts of the SDK to you; or (D) Google decides to no longer provide the SDK or certain parts of the SDK to users in the country in which you are resident or from which you use the service, or the provision of the SDK or certain SDK services to you by Google is, in Google's sole discretion, no longer commercially viable. 9.4 When the License Agreement comes to an end, all of the legal rights, obligations and liabilities that you and Google have benefited from, been subject to (or which have accrued over time whilst the License Agreement has been in force) or which are expressed to continue indefinitely, shall be unaffected by this cessation, and the provisions of paragraph 14.7 shall continue to apply to such rights, obligations and liabilities indefinitely.

### 10. DISCLAIMER OF WARRANTIES

10.1 YOU EXPRESSLY UNDERSTAND AND AGREE THAT YOUR USE OF THE SDK IS AT YOUR SOLE RISK AND THAT THE SDK IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTY OF ANY KIND FROM GOOGLE. 10.2 YOUR USE OF THE SDK AND ANY MATERIAL DOWNLOADED OR OTHERWISE OBTAINED THROUGH THE USE OF THE SDK IS AT YOUR OWN DISCRETION AND RISK AND YOU ARE SOLELY RESPONSIBLE FOR ANY DAMAGE TO YOUR COMPUTER SYSTEM OR OTHER DEVICE OR LOSS OF DATA THAT RESULTS FROM SUCH USE. 10.3 GOOGLE FURTHER EXPRESSLY DISCLAIMS ALL WARRANTIES AND CONDITIONS OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

### 11. LIMITATION OF LIABILITY

11.1 YOU EXPRESSLY UNDERSTAND AND AGREE THAT GOOGLE, ITS SUBSIDIARIES AND AFFILIATES, AND ITS LICENSORS SHALL NOT BE LIABLE TO YOU UNDER ANY THEORY OF LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR EXEMPLARY DAMAGES THAT MAY BE INCURRED BY YOU, INCLUDING ANY LOSS OF DATA, WHETHER OR NOT GOOGLE OR ITS REPRESENTATIVES HAVE BEEN ADVISED OF OR SHOULD HAVE BEEN AWARE OF THE POSSIBILITY OF ANY SUCH LOSSES ARISING.

### 12. Indemnification

12.1 To the maximum extent permitted by law, you agree to defend, indemnify and hold harmless Google, its affiliates and their respective directors, officers, employees and agents from and against any and all claims, actions, suits or proceedings, as well as any and all losses, liabilities, damages, costs and expenses (including reasonable attorneys fees) arising out of or accruing from (a) your use of the SDK, (b) any application you develop on the SDK that infringes any copyright, trademark, trade secret, trade dress, patent or other intellectual property right of any person or defames any person or violates their rights of publicity or privacy, and (c) any non-compliance by you with the License Agreement.

### 13. Changes to the License Agreement

13.1 Google may make changes to the License Agreement as it distributes new versions of the SDK. When these changes are made, Google will make a new version of the License Agreement available on the website where the SDK is made available.

### 14. General Legal Terms

14.1 The License Agreement constitutes the whole legal agreement between you and Google and governs your use of the SDK (excluding any services which Google may provide to you under a separate written agreement), and completely replaces any prior agreements between you and Google in relation to the SDK. 14.2 You agree that if Google does not exercise or enforce any legal right or remedy which is contained in the License Agreement (or which Google has the benefit of under any applicable law), this will not be taken to be a formal waiver of Google's rights and that those rights or remedies will still be available to Google. 14.3 If any court of law, having the jurisdiction to decide on this matter, rules that any provision of the License Agreement is invalid, then that provision will be removed from the License Agreement without affecting the rest of the License Agreement. The remaining provisions of the License Agreement will continue to be valid and enforceable. 14.4 You acknowledge and agree that each member of the group of companies of which Google is the parent shall be third party beneficiaries to the License Agreement and that such other companies shall be entitled to directly enforce, and rely upon, any provision of the License Agreement that confers a benefit on (or rights in favor of) them. Other than this, no other person or company shall be third party beneficiaries to the License Agreement. 14.5 EXPORT RESTRICTIONS. THE SDK IS SUBJECT TO UNITED STATES EXPORT LAWS AND REGULATIONS. YOU MUST COMPLY WITH ALL DOMESTIC AND INTERNATIONAL EXPORT LAWS AND REGULATIONS THAT APPLY TO THE SDK. THESE LAWS INCLUDE RESTRICTIONS ON DESTINATIONS, END USERS AND END USE. 14.6 The rights granted in the License Agreement may not be assigned or transferred by either you or Google without the prior written approval of the other party. Neither you nor Google shall be permitted to delegate their responsibilities or obligations under the License Agreement without the prior written approval of the other party. 14.7 The License Agreement, and your relationship with Google under the License Agreement, shall be governed by the laws of the State of California without regard to its conflict of laws provisions. You and Google agree to submit to the exclusive jurisdiction of the courts located within the county of Santa Clara, California to resolve any legal matter arising from the License Agreement. Notwithstanding this, you agree that Google shall still be allowed to apply for injunctive remedies (or an equivalent type of urgent legal relief) in any jurisdiction. *July 27, 2021*  
I have read and agree with the above terms and conditions  
Download [Download](https://dl.google.com/developers/android/channels/verify_app_multiplatform_public_20251215.apk)

*verify_app_multiplatform_public_20251215.apk*