📄️ Using a Previously Verfied Age
Sometimes game developers already know the age of a player when the player starts a new game. This is usually because the player has signed in to the game with an identity known to the game developer. In this case, the game can avoid displaying the age gate, and instead just call /age-gate/check, passing in the location and previously verified date of birth.
📄️ Using Age Status
While k-ID provides a wealth of permission settings that pertain to specific features, some games may need to create a more distinct player experience independent of any one feature. For example, a game might not show any in-game ads at all if a player is not a legal adult. In this case the game can check the ageStatus field in the Session. This field can be either DIGITALMINOR (below the age of digital consent), DIGITALYOUTH (below the civil age, but above the age of digital consent), or LEGAL_ADULT (civil age).
📄️ Sessions and Multiple Devices
When caching Session objects in local storage, different Sessions can exist in the local storage of multiple devices for the same player. If the player plays the game on a new device, the age gate will appear again for the player, and they will need to seek consent again if it was required before.
📄️ Using the Platform Age Signal
Many game platforms (Meta, Xbox, Playstation, etc.) send age platform-specific signals to a game when it launches. When the game shows an age gate, it is possible that the age given by the player is outside the range given by the platform-specific age signal. In this case, to be compliant, it is required that you assume the lower of the two values. However, to prevent the discrepancy in the first place, the game can use the platform age signal to limit the possible ages the player can give in the age gate. To do this, there are two important fields, digitalConsentAge and civilAge, that are returned from the /age-gate/get-requirements API. Using these fields, you can constrain the age gate to only allow ages for a digital minor to values up to the age of digital consent, and only allow age values for a teen between the age of digital consent and civil age.
📄️ Using KWS to Verify Adults
k-ID supports the use of Kids Web Services (KWS) to verify adults. This is an internal configuration option that can be provided for you by k-ID, and is not a setting that can be modified self-serve. When configured, the Family Portal will use KWS automatically when age verification is needed.
📄️ Standalone Parent Verification
k-ID supports the ability to verify a parent within a custom web user experience outside of the k-ID Family Portal. There are two verification APIs provided that enable this, /verification/generate-url and /verification/register-webhook.