PV service example use cases

Examples of how to integrate the KWS PV service into your product's access flow.

Click image for full size.

Parent Verification without an age gate

If you are developing an app that is targeted at kids only, you may choose not to build an age gate into your experience and essentially treat all users as kids. This will very likely reduce friction in your UX and lead to improved conversion rates overall.

This example shows how you could integrate KWS' Parent Verification service into such a flow:

Click image for full size.

Your product interface

  1. When a kid tries to access a feature that requires parental permission/oversight, present a screen/modal to make them aware that they require parental consent/oversight before using certain app features and the reasons why. Avoid legal jargon and tailor this messaging to be clearly understandable to a kid.

  2. The kid is then prompted to provide their parent's email address or get their parent to assist them to complete this step if they can't do so themselves.

  3. When a parent email address is submitted, the KWS PV service is triggered. In the meantime, the kid is sent to a temporary holding screen which informs them that they cannot access the feature until parental permission is granted. If the app experience allows, the kid may be directed to use other features that do not require parental oversight.

The KWS interface

When triggered by the parent email address submission, KWS starts the verification process. This varies, depending on whether the parent has previously been verified or not.

First-time verification

If the parent has not previously been verified, or has opted out of having their email address stored in the ParentGraph, the verification process is as follows:

  1. KWS sends an email to the parent, informing them that they need to complete some verification steps:

    Click image for full size.

  2. When the parent clicks on the call to action (CTA) within the email, a KWS webview opens, similar to this:

    Click image for full size.

  3. The parent is asked to choose a verification method. The available methods vary depending on their country of residence. This is an example of KWS' credit card verification interface:

    Click image for full size.

  4. When the parent has verified successfully, a hash of their email address is stored in the KWS ParentGraph. In the future, KWS will recognize this parent as verified so they never have to repeat the verification process for any app that uses the KWS PV service.

  5. KWS sends a confirmation email to the parent, informing them that they have been successfully verified and added to the ParentGraph. (The email also contains a link to opt out of the ParentGraph.) In the case of payment-based verification methods, the email includes details about authorization, capture, and refunds, depending on the requirements in the child's country. This is an example of the confirmation email:

    Click image for full size.

  6. Finally, the parent is redirected to the URL specified by you when you set up the KWS PV service for your product. For example, you might specify an interface that allows the parent to control their child's activity on your product.

Pre-verified parents

If the parent has previously been verified (and is included in the ParentGraph), KWS sends the parent an email confirming that they are already verified, and directing them to the URL specified by you when you set up the KWS PV service for your product. For example, you might specify an interface that allows the parent to control their child's activity on your product.

NOTE: This email is delayed by a variable amount of time (between 1-2 hours) as an additional security measure.

Parent Verification with age gate

This flow is suited for experiences that are targeted at (or where you expect) a mixed excluded, audience; i.e. including users under and over the age of digital consent in their country. In this case, you may display a neutral age gate to your users when they try to use a feature that requires parental permission/oversight. Once it is established that they are above or below the applicable age of digital consent, the flow treats them accordingly.

This example shows how you could integrate KWS' Parent Verification service into such a flow:

Click image for full size.

Your product interface

  1. When a kid tries to access a feature that requires parental permission/oversight, a neutral age gate screen is presented to them.

    NOTE: There are various ways to implement such an age gate. The most common way is to collect the user's age and country of residence in order to ascertain if they are above or below the age of digital consent in that country.

  2. If the user is deemed to be below the age of digital consent in their country (i.e. they are a ‘kid'), make them aware that they require parental consent/oversight before using certain app features and the reasons why. Avoid legal jargon and tailor this messaging to be clearly understandable to a kid.

  3. The kid is then prompted to provide their parent's email address or get their parent to assist them to complete this step if they can't do so themselves.

  4. When a parent email address is submitted, the KWS PV service is triggered. In the meantime, the kid is sent to a temporary holding screen which informs them that they cannot access the feature until parental permission is granted. If the app experience allows, the kid may be directed to use other features that do not require parental oversight.

The KWS interface

When triggered by the parent email address submission, the KWS verification flow proceeds in exactly the same way as for the no-age-gate scenario above.

Tags