Comprehending App Age Verification: Data Distribution and Information Recipients

Comprehending App Age Verification: Data Distribution and Information Recipients

Comprehending App Age Verification: Data Distribution and Information Recipients


### App Age Verification: Present Situation and Future Consequences

App age verification has moved beyond theoretical discussions; it is now a reality as various regulations enforcing age verification for users are adopted in specific states. This development has significant consequences for both users and app creators.

A prominent instance is Bluesky, a platform akin to Twitter/X, which temporarily ceased operations for users in certain areas due to non-compliance with local age verification laws. Recently, the app has resumed functionality, but users must now submit personal information to a third-party service, KWS (Kids Web Services), to confirm their age. This situation may foreshadow what many other apps will adopt as age verification regulations spread.

#### VPN as a Short-Term Solution

At present, users can bypass age verification mandates by using a VPN (Virtual Private Network). A VPN conceals the user’s actual IP address, making it seem as though they are accessing the internet from a different location. Although some browsers provide free VPN services, a paid VPN is typically essential for extensive coverage across all applications and devices.

This workaround is effective while age verification is restricted to a limited number of states. However, should federal regulations be introduced, users might need to use VPNs to connect via IP addresses from other countries that may have their own age verification requirements.

#### Actual Age Verification Procedure

The real-world application of age verification is evident in Bluesky’s recent modifications. When users click the “Verify now” button, they are prompted to confirm their email and are introduced to KWS, the third-party partner responsible for age verification. KWS states that it retains users’ verified status alongside a hashed email address, enabling other apps utilizing KWS technology to bypass the verification process for that email in the future.

To commence verification, Bluesky sends an email link to the user. The verification process necessitates users providing their full legal name, home address, and one of three methods for age verification: the last four digits of their Social Security number, a temporary credit card transaction, or a scan of a government-issued ID such as a driver’s license or passport.

Bluesky collaborates with various companies for different verification methods, including Veratad for Social Security number verification, Stripe for credit card transactions, and Veriff for ID verification.

#### 9to5Mac’s Perspective

Among the verification options, using a credit card through Stripe might be viewed as the least risky due to its established reputation in online transactions. Conversely, sharing sensitive data like Social Security numbers or government IDs raises privacy issues, as these details are harder to change if compromised.

The primary objective of these age verification efforts is to improve online safety for children. However, the implications for user privacy and data protection are significant. As age verification becomes more prevalent across various platforms, concerns surrounding the handling of sensitive information are likely to grow.

In summary, the current state of app age verification demonstrates that it is beyond a mere policy discussion; it is a developing reality that both users and developers must navigate. As regulations expand, the challenge of ensuring child safety online while safeguarding user privacy will remain a crucial topic of discussion.