Use Play Age Signals API (beta)

// Create an instance of a manager
val ageSignalsManager =
    AgeSignalsManagerFactory.create(ApplicationProvider.getApplicationContext())

// Request an age signals check
ageSignalsManager
    .checkAgeSignals(AgeSignalsRequest.builder().build())
    .addOnSuccessListener { ageSignalsResult ->
        // Store the install ID for later...
        val installId = ageSignalsResult.installId()

        if (ageSignalsResult.userStatus() == AgeSignalsVerificationStatus.SUPERVISED_APPROVAL_DENIED) {
          // Disallow access...
        } else {
           // Do something else if the user is VERIFIED, DECLARED, SUPERVISED, etc.
        }
    }

// Create an instance of a manager
AgeSignalsManager ageSignalsManager =
    AgeSignalsManagerFactory.create(ApplicationProvider.getApplicationContext());

// Request an age signals check
ageSignalsManager
    .checkAgeSignals(AgeSignalsRequest.builder().build())
    .addOnSuccessListener(
        ageSignalsResult -> {
          // Store the install ID for later...
          String installId = ageSignalsResult.installId();

          if (ageSignalsResult
              .userStatus()
              .equals(AgeSignalsVerificationStatus.SUPERVISED_APPROVAL_DENIED)) {
            // Disallow access ...
          } else {
            // Do something else if the user is SUPERVISED, VERIFIED, etc.
          }
        });

(Optional) Receive custom age ranges

The default age ranges that the API returns in applicable jurisdictions and regions are 0-12, 13-15, 16-17, and 18+.

Alternatively, to customize the default age ranges according to your app's minimum ages, you can provide these minimum ages for your app on the Age signals page in your Google Play Console. The age ranges returned will override the default API response. For example, if you provide minimum ages of 9, 15, and 17, a 14-year-old user would fall within the 10-15 age range.

To customize the default age ranges returned by the Age Signals API, you can provide minimum ages for your app:

1. Go to the Age signals page in your Play Console.
2. On the Custom age ranges tab, enter up to three minimum ages for your app. Minimum ages must be at least 2 years apart and can be changed once annually.
3. Click Save.

Age signals responses

The Play Age Signals API (beta) response includes the following fields and values. The values are subject to change. If you want the most recent values, request an API response when your app opens. You are responsible for providing age-appropriate experiences using these signals.

Example responses for users in Brazil

In Brazil, userStatus can only be DECLARED and UNKNOWN.

For a user who declared their age, you would receive the following:

• userStatus would be AgeSignalsVerificationStatus.DECLARED.
• ageLower would be a number (for example, 13).
• ageUpper would be a number or null (for example, 15).
• Other response fields would be null.

For a user whose age is unknown, you would receive the following:

• userStatus would be AgeSignalsVerificationStatus.UNKNOWN.
• Other response fields would be null.

The user status may change from UNKNOWN to DECLARED once the user's age is available to share.

Example responses for users in US states

In applicable US states, userStatus can be VERIFIED, SUPERVISED, SUPERVISED_APPROVAL_PENDING, SUPERVISED_APPROVAL_DENIED, UNKNOWN, or null.

For a verified user, you would receive the following:

• userStatus would be AgeSignalsVerificationStatus.VERIFIED.
• ageLower would be a number (for example, 18).
• ageUpper would be a number or null (for example, null).
• Other response fields would be null.

For a supervised user, you would receive the following:

• userStatus would be AgeSignalsVerificationStatus.SUPERVISED.
• ageLower would be a number (for example, 13).
• ageUpper would be a number or null (for example, 15).
• mostRecentApprovalDate would be a Java date object (for example, 2026-01-01) or null (if no significant change has been approved).
• installID would be a Play-generated alphanumeric ID (for example, 550e8400-e29b-41d4-a716-446655441111).

For a supervised user with a significant change approval pending, you would receive the following:

• userStatus would be AgeSignalsVerificationStatus.SUPERVISED_APPROVAL_PENDING.
• ageLower would be a number (for example, 13).
• ageUpper would be a number or null (for example, 15).
• mostRecentApprovalDate would be a Java date object (for example, 2026-01-01) or null (if no significant change has been approved).
• installID would be a Play-generated alphanumeric ID (for example, 550e8400-e29b-41d4-a716-446655441111).

Handle API error codes

If your app makes a Play Age Signals API request and the call fails, your app receives an error code. These errors can happen for various reasons, such as the Play Store app being out of date.

Retry strategy

In situations where the user is in session, we recommend implementing a retry strategy with a maximum number of attempts as an exit condition so that the error disrupts the user experience as little as possible.