reis-mobile 0.3.6 → 0.4.0

package/skills/android-engage-sdk-integration/references/android/guide/playcore/engage/tv/continue-watching/index.md

@@ -0,0 +1,19 @@
+Continue watching leverages the **Continuation cluster** to show unfinished
+videos, and next episodes to be watched from the same TV show, from multiple
+apps in one UI grouping. You can feature your 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).
+
+You manage the continuation cluster by using the client API in a TV app or from
+a REST API:
+
+- [Integrate continue watching on Android TV](https://developer.android.com/guide/playcore/engage/tv/continue-watching/client)
+- [Integrate continue watching using REST API](https://developer.android.com/guide/playcore/engage/tv/continue-watching/rest)
+
+## Sample code
+
+This [sample app](https://github.com/googlesamples/tv-video-discovery-samples) demonstrates how you can integrate with Engage SDK
+to send personalized user data to Google. It shows how to build a common module
+that you can import in both mobile and TV apps. The sample also illustrates
+when to call the publish and delete APIs, as well as how to use Workers to
+make these calls.

package/skills/android-engage-sdk-integration/references/android/guide/playcore/engage/tv/entitlements.md

@@ -0,0 +1,353 @@
+This guide contains instructions for developers to share app subscription and
+entitlement data with Google TV using [Engage SDK](https://developer.android.com/guide/playcore/engage). Users can find
+content they are entitled to and enable Google TV to deliver highly relevant
+content recommendations to users, directly within Google TV experiences on TV,
+mobile, and tablet.
+
+## Prerequisites
+
+> [!IMPORTANT]
+> **Important:** [Express interest in developing with Engage](http://g.co/tv/vda).
+
+Onboarding the media actions feed is required before you can use the device
+entitlement API. If you haven't already done so, complete the [media actions
+feed](https://developers.google.com/actions/media?authuser=0) onboarding process.
+
+## Pre-work
+
+Complete the [Pre-work](https://developer.android.com/guide/playcore/engage/tv/getting-started#pre-work) instructions in the Getting Started guide.
+
+1. Publish subscription information on the following events:
+   1. User logs in to your app.
+   2. User switches between profiles (if profiles are supported).
+   3. User purchases a new subscription.
+   4. User upgrades an existing subscription.
+   5. User subscription expires.
+
+## Integration
+
+This section provides the necessary code examples and instructions for
+implementing `SubscriptionEntity` to manage various subscription types.
+
+### Common tier subscription
+
+For users with basic subscriptions to media provider services, for example, a
+service that has one subscription tier that grants access to all the paid
+content, provide these essential details:
+
+1. `SubscriptionType`: Clearly indicate the specific subscription plan the user
+   has.
+
+   - `SUBSCRIPTION_TYPE_ACTIVE`: User has an active paid subscription.
+   - `SUBSCRIPTION_TYPE_ACTIVE_TRIAL`: User has a trial subscription.
+   - `SUBSCRIPTION_TYPE_INACTIVE`: User has an account but no active subscription or trial.
+
+   > [!IMPORTANT]
+   > **Important:** Only users with `SUBSCRIPTION_TYPE_ACTIVE` or `SUBSCRIPTION_TYPE_ACTIVE_TRIAL` are eligible for personalized content recommendations based on their subscription.
+
+2. `ExpirationTimeMillis`: Optional time in milliseconds. Specify when the
+   subscription is set to expire.
+
+3. `ProviderPackageName`: Specify the package name of the app that handles the
+   subscription.
+
+Example for the sample media provider feed.
+
+    "actionAccessibilityRequirement": [
+      {
+        "@type": "ActionAccessSpecification",
+        "category": "subscription",
+        "availabilityStarts": "2022-06-01T07:00:00Z",
+        "availabilityEnds": "2026-05-31T07:00:00Z",
+        "requiresSubscription": {
+        "@type": "MediaSubscription",
+        // Don't match this string,
+        // ID is only used to for reconciliation purpose
+        "@id": "https://www.example.com/971bfc78-d13a-4419",
+        // Don't match this, as name is only used for displaying purpose
+        "name": "Basic common name",
+        "commonTier": true
+      }
+
+The following example creates a `SubscriptionEntity` for a user:
+
+    val subscription = SubscriptionEntity.Builder()
+      setSubscriptionType(
+        SubscriptionType.SUBSCRIPTION_TYPE_ACTIVE
+      )
+      .setProviderPackageName("com.google.android.example")
+      // Optional
+      // December 30, 2025 12:00:00AM in milliseconds since epoch
+      .setExpirationTimeMillis(1767052800000)
+      .build()
+
+### Premium subscription
+
+If app offer multi-tiered premium subscription packages, which includes expanded
+content or features beyond the common tier, represent this by adding one or more
+entitlements to Subscription.
+
+This entitlement has the following fields:
+
+1. `Identifier`: Required identifier string for this entitlement. This must match one of the [entitlement identifiers](https://developers.google.com/actions/media/concepts/access-requirements#entitlement-identifier) (note that this isn't the ID field) provided in the media provider's feed published to Google TV.
+2. `Name`: This is auxiliary information and is used for entitlement matching. While optional, providing a human readable entitlement name enhances understanding of user entitlements for both developers and support teams. For example: Sling Orange.
+3. `ExpirationTimeMillis`: Optionally specify the expiration time in milliseconds for this entitlement, if it differs from the subscription expiration time. By default, the entitlement will expire with the expiry of subscription.
+
+For the following sample media provider feed snippet:
+
+    "actionAccessibilityRequirement": [
+      {
+        "@type": "ActionAccessSpecification",
+        "category": "subscription",
+        "availabilityStarts": "2022-06-01T07:00:00Z",
+        "availabilityEnds": "2026-05-31T07:00:00Z",
+        "requiresSubscription": {
+        "@type": "MediaSubscription",
+        // Don't match this string,
+        // ID is only used to for reconciliation purpose
+        "@id": "https://www.example.com/971bfc78-d13a-4419",
+
+        // Don't match this, as name is only used for displaying purpose
+        "name": "Example entitlement name",
+        "commonTier": false,
+        // match this identifier in your API. This is the crucial
+        // entitlement identifier used for recommendation purpose.
+        "identifier": "example.com:entitlementString1"
+      }
+
+The following example creates a `SubscriptionEntity` for a subscribed user:
+
+    // Subscription with entitlements.
+    // The entitlement expires at the same time as its subscription.
+    val subscription = SubscriptionEntity.Builder()
+      .setSubscriptionType(
+        SubscriptionType.SUBSCRIPTION_TYPE_ACTIVE
+      )
+      .setProviderPackageName("com.google.android.example")
+      // Optional
+      // December 30, 2025 12:00:00AM in milliseconds
+      .setExpirationTimeMillis(1767052800000)
+      .addEntitlement(
+        SubscriptionEntitlement.Builder()
+        // matches with the identifier in media provider feed
+        .setEntitlementId("example.com:entitlementString1")
+        .setDisplayName("entitlement name1")
+        .build()
+      )
+      .build()
+
+    // Subscription with entitlements
+    // The entitement has different expiration time from its subscription
+    val subscription = SubscriptionEntity.Builder()
+      .setSubscriptionType(
+        SubscriptionType.SUBSCRIPTION_TYPE_ACTIVE
+      )
+      .setProviderPackageName("com.google.android.example")
+      // Optional
+      // December 30, 2025 12:00:00AM in milliseconds
+      .setExpirationTimeMillis(1767052800000)
+      .addEntitlement(
+        SubscriptionEntitlement.Builder()
+        .setEntitlementId("example.com:entitlementString1")
+        .setDisplayName("entitlement name1")
+        // You may set the expiration time for entitlement
+        // December 15, 2025 10:00:00 AM in milliseconds
+        .setExpirationTimeMillis(1765792800000)
+        .build())
+      .build()
+
+### Subscription for linked service package
+
+While subscriptions typically belong to the originating app's media provider, a
+subscription can be attributed to a linked service package by specifying the
+linked service package name within the subscription.
+
+Following code sample demonstrate how to create user subscription.
+
+    // Subscription for linked service package
+    val subscription = SubscriptionEntity.Builder()
+      .setSubscriptionType(
+        SubscriptionType.SUBSCRIPTION_TYPE_ACTIVE
+      )
+      .setProviderPackageName("com.google.android.example")
+      // Optional
+      // December 30, 2025 12:00:00AM in milliseconds since epoch
+      .setExpirationTimeMillis(1767052800000)
+      .build()
+
+In addition, if the user has another subscription to a subsidiary service, add
+another subscription and set the linked service package name accordingly.
+
+    // Subscription for linked service package
+    val linkedSubscription = Subscription.Builder()
+      .setSubscriptionType(
+        SubscriptionType.SUBSCRIPTION_TYPE_ACTIVE
+      )
+      .setProviderPackageName("linked service package name")
+      // Optional
+      // December 30, 2025 12:00:00AM in milliseconds since epoch
+      .setExpirationTimeMillis(1767052800000)
+      .addBundledSubscription(
+        BundledSubscription.Builder()
+          .setBundledSubscriptionProviderPackageName(
+            "bundled-subscription-package-name"
+          )
+          .setSubscriptionType(SubscriptionType.SUBSCRIPTION_TYPE_ACTIVE)
+          .setExpirationTimeMillis(111)
+          .addEntitlement(
+            SubscriptionEntitlement.Builder()
+            .setExpirationTimeMillis(111)
+            .setDisplayName("Silver subscription")
+            .setEntitlementId("subscription.tier.platinum")
+            .build()
+          )
+          .build()
+      )
+        .build()
+
+Optionally, add entitlements to a linked service subscription too.
+
+### Provide subscription set
+
+Run the content publish job while the app is in the foreground.
+
+Use the `publishSubscriptionCluster()` method, from the
+`AppEngagePublishClient` class, to publish a `SubscriptionCluster` object.
+
+Make sure to initialize the client and check for service availability as
+described in the [Getting Started guide](https://developer.android.com/guide/playcore/engage/tv/getting-started#common-integration).
+
+    client.publishSubscription(
+      PublishSubscriptionRequest.Builder()
+        .setAccountProfile(accountProfile)
+        .setSubscription(subscription)
+        .build()
+      )
+
+Use `setSubscription()` to verify that user should have only one subscription to
+the service.
+
+Use `addLinkedSubscription()`, or `addLinkedSubscriptions()` which accept a list
+of linked subscriptions, to enable user to have zero or more linked
+subscriptions.
+
+When the service receives the request, a new entry is created and the old entry
+is automatically deleted after 60 days. The system always uses the latest entry.
+In case of an error, the entire request is rejected and the existing state is
+maintained.
+
+### Keep subscription up-to-date
+
+1. To provide immediate updates upon changes, call
+   `publishSubscriptionCluster` whenever a user's subscription state changes
+   like activation, deactivation, upgrades, downgrades.
+
+2. To provide regular validation for ongoing accuracy, call
+   `publishSubscriptionCluster` at least once per month.
+
+   > [!NOTE]
+   > **Note:** As Google TV automatically deletes historical data beyond 60 days to safeguard user privacy, publishing user subscription data at least once per month verify the validity of data. Unlike `publishContinuationCluster` for continue watching data, don't set `syncAcrossDevices` flag, as subscription information is by default used to provide content across all devices.
+
+3. To delete the Engage data, manually delete a user's data from the
+   Google TV server before the standard 60-day retention period, use the
+   `client.deleteClusters` method. This deletes all existing Engage
+   data for the account profile, or for the entire account depending on the
+   given [`DeleteReason`](https://developer.android.com/reference/com/google/android/engage/service/DeleteReason).
+
+   The following code snippet shows how to remove a user subscription:
+
+       // If the user logs out from your media app, you must make the following call
+       // to remove subscription and other Engage data from the current
+       // google TV device.
+       client.deleteClusters(
+         new DeleteClustersRequest.Builder()
+           .setAccountProfile(accountProfile)
+         .setReason(DeleteReason.DELETE_REASON_USER_LOG_OUT)
+         .build()
+         )
+
+   The following code snippet demonstrates removal of user subscription
+   when user revokes the consent:
+
+       // If the user revokes the consent to share across device, make the call
+       // to remove subscription and other Engage data from all google
+       // TV devices.
+       client.deleteClusters(
+         new DeleteClustersRequest.Builder()
+           .setAccountProfile(accountProfile)
+           .setReason(DeleteReason.DELETE_REASON_LOSS_OF_CONSENT)
+           .build()
+       )
+
+   Following code demonstrates how to remove subscription data on user profile
+   deletion.
+
+       // If the user delete a specific profile, you must make the following call
+       // to remove subscription data and other Engage data.
+       client.deleteClusters(
+         new DeleteClustersRequest.Builder()
+         .setAccountProfile(accountProfile)
+         .setReason(DeleteReason.DELETE_REASON_ACCOUNT_PROFILE_DELETION)
+         .build()
+       )
+
+### Testing
+
+This section provides a step-by-step guide for testing subscription
+implementation. Verify data accuracy and proper functionality before launch.
+
+#### Publish Integration checklist
+
+1. Publishing should happen when the app is in the foreground and user the
+   actively interacting with it.
+
+2. Publish when:
+
+   - User logs in for the first time.
+   - User changes profile (if profiles are supported).
+   - User purchases new subscription.
+   - User upgrades subscription.
+   - User subscription expires.
+3. Check if app is correctly calling `isServiceAvailable` and
+   `publishClusters` APIs in logcat, on the publishing events.
+
+4. Verify that data is visible in the verification app. The verification app
+   should display subscription as a separate row. When the publish API is
+   invoked, the data should show up in the verification app.
+
+   > [!IMPORTANT]
+   > **Important:** Verify that the [Engage Service Flag](https://developer.android.com/guide/playcore/engage/workflow#switch-to-prod) is **not** set to production.
+
+5. Go to app and perform each of the following actions:
+
+   - Sign in.
+   - Switch between profiles (if supported).
+   - Purchase a new subscription.
+   - Upgrade an existing subscription.
+   - Expire the subscription.
+
+#### Verify integration
+
+To test your integration, use the [verification app](https://developer.android.com/guide/playcore/engage/tv/getting-started#testing).
+
+1. For each of the events, check if app has invoked the `publishSubscription` API. Verify the published data in the verification app. **Verify that everything is green in verification app**
+2. If all the entity's information is correct, it shows an "All Good" green
+   check in all entities.
+
+   ![Verification App Success Screenshot](https://developer.android.com/static/images/guide/playcore/engage/ett-va-success.png) **Figure 1.** Successful subscription
+3. Problems are also highlighted in verification app
+
+   ![Verification App Error Screenshot](https://developer.android.com/static/images/guide/playcore/engage/ett-va-error.png) **Figure 2.**Subscription unsuccessful
+4. To see the problems in the bundled subscription, use the TV remote to focus
+   on that specific bundled subscription and click to see the problems. You
+   might have to first focus on the row and move to the right to find Bundled
+   Subscription card. The problems are highlighted as red as shown in Fig 3.
+   Also, use the remote to move down to see problems in the entitlements within
+   bundled subscription
+
+   ![Verification App Error Details Screenshot](https://developer.android.com/static/images/guide/playcore/engage/ett-va-error-details.png) **Figure 3.**Subscription Errors
+5. To see the problems in the entitlement, use the TV remote to focus on that
+   specific entitlement and click to see the problems. The problems are
+   highlighted as red.
+
+   ![Verification App Error Screenshot](https://developer.android.com/static/images/guide/playcore/engage/ett-va-details.png) **Figure 4.**Subscription Error Details

package/skills/android-engage-sdk-integration/references/android/guide/playcore/engage/tv/getting-started.md

@@ -0,0 +1,202 @@
+<br />
+
+[Engage SDK](https://developer.android.com/guide/playcore/engage) lets you deliver personalized recommendations
+and continuation content directly to users on Google TV.
+
+This guide covers how to get started with Engage SDK integrations for TV. After
+you complete the pre-work on this page, you can integrate one or more
+of the TV features:
+
+- [Publish continue watching data](https://developer.android.com/guide/playcore/engage/tv/continue-watching)
+- [Publish device entitlements](https://developer.android.com/guide/playcore/engage/tv/entitlements)
+- [Publish recommendations](https://developer.android.com/guide/playcore/engage/tv/recommendations)
+
+## Pre-work
+
+Before you begin, complete the following steps:
+
+1. [Express interest in developing with Engage SDK](http://g.co/tv/engage) to enroll in
+   the program, if eligible.
+
+2. Verify that your app targets Android 4.4 (API level 19) or higher for this
+   integration.
+
+3. 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.6.0'
+       }
+
+   ### TV
+
+       dependencies {
+         implementation 'com.google.android.engage:engage-tv:1.1.0'
+       }
+
+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. Test your implementation using the verification app as outlined in the
+   [Testing section](https://developer.android.com/guide/playcore/engage/tv/getting-started#testing).
+
+7. In your production app, set the Engage service environment to production by
+   adding the `<meta-data>` element directly under the `<application>` tag
+   in your `AndroidManifest.xml` file.
+   Don't place this tag inside an `<activity>`.
+
+       <application ...>
+           <!-- Other application configurations -->
+
+           <meta-data
+               android:name="com.google.android.engage.service.ENV"
+               android:value="PRODUCTION" />
+       </application>
+
+   > [!IMPORTANT]
+   > **Important:** The Engage service environment declaration is only needed for your release build. For your local testing with the verification app, don't include this element.
+
+## Common integration steps
+
+### Initialize the client
+
+Use `AppEngagePublishClient` to interact with the service. Always check if the
+service is available before publishing.
+
+You can check the service availability for every cluster type that you intend to
+publish. The `isServiceAvailable` API accepts a request object,
+`ServiceAvailabilityRequest`, which contains the cluster types for which service
+availability needs to be checked. You can find the `ClusterType` enum values
+required for `ServiceAvailabilityRequest` from the following table.
+
+| Cluster Type | Cluster Type Constant | Integer Value |
+|---|---|---|
+| Unknown | `TYPE_UNKNOWN` | 0 |
+| Recommendation Cluster | `TYPE_RECOMMENDATION` | 1 |
+| Continuation Cluster | `TYPE_CONTINUATION` | 3 |
+
+    val client = AppEngagePublishClient(context)
+
+    val request = ServiceAvailabilityRequest.Builder()
+        .addIntendedClusterType(ClusterType.TYPE_CONTINUATION)
+        .addIntendedClusterType(ClusterType.TYPE_RECOMMENDATION)
+        .build()
+
+    client.isServiceAvailable(request).addOnCompleteListener { task ->
+      if (task.isSuccessful) {
+        val availabilityMap = task.result
+        if (availabilityMap[ClusterType.TYPE_CONTINUATION] == true) {
+          // Proceed with publishing continuation content
+        }
+        if (availabilityMap[ClusterType.TYPE_RECOMMENDATION] == true) {
+          // Proceed with publishing recommendation content
+        }
+      } else {
+        // Service is not available or call failed
+      }
+    }
+
+### Create an account profile
+
+`AccountProfile` identifies the user. You can specify an account ID, and
+optionally a profile ID and locale.
+
+    val accountProfile = AccountProfile.Builder()
+        .setAccountId("your_users_account_id")
+        .setProfileId("your_users_profile_id") // Optional
+        .setLocale(Locale.US.toLanguageTag())  // Optional, e.g., "en-US"
+        .build()
+
+An `AccountProfile` must be provided with an account ID in order for content to
+be synchronized between devices. See [Cross-device syncing](https://developer.android.com/guide/playcore/engage/tv/continue-watching/client#cross-device_syncing).
+
+## Testing
+
+To test your integration, download the verification app:
+
+[Download verification
+app](https://developer.android.com/guide/playcore/engage/tv/getting-started#lightbox-trigger)
+
+The verification app is an Android app with capabilities to help you test your
+integration. It let you to check data accuracy and proper functionality by
+verifying published data and broadcast intents before launch.
+
+1. Install and open the Engage Verification app.
+2. If the value of `isServiceAvailable` is `false` in the verification app, click the **Toggle** button within the verification app to set it to `true`.
+3. Enter the package name of your app. It automatically shows the published data.
+4. Run your app and perform publishing actions, such as logging in or watching a video.
+5. Verify that the data shows up in the verification app.
+
+## 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 will 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, will be unaffected by this cessation, and the provisions of paragraph 14.7 will 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 WILL 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 will be third party beneficiaries to the License Agreement and that such other companies will 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 will 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 will 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, will 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 will still be allowed to apply for injunctive remedies (or an equivalent type of urgent legal relief) in any jurisdiction. *April 28, 2026* I have read and agree with the above terms and conditions <button class="button button-disabled"> Download </button> [Download](https://dl.google.com/developers/android/channels/verify_app_multiplatform_public_20260701.apk)
+
+*verify_app_multiplatform_public_20260701.apk*