Apple is expanding its age-verification system in more countries to match stricter child-protection laws. The changes mainly affect how people download 18+ (adult-rated) apps and how developers confirm whether a user is a minor or an adult—without collecting sensitive personal details.

What’s changing for users

• New 18+ download blocks: In Brazil, Australia, and Singapore, users must confirm they are 18 or older before downloading apps rated 18+.
• Less access for minors to adult content: This is meant to stop children from downloading adult-only apps through the App Store.

What’s changing for developers

• Declared Age Range API (updated): Apple is updating an API that lets apps know only an age category (example: minor vs adult), not the person’s exact age.
  • Developers do not receive private data, such as date of birth.
  • The app receives a simple “category signal” to follow local rules.
• Parental control options: For child accounts, parents/guardians can choose whether to share age information and whether permission is required in certain situations.

Loot boxes and “gambling-like” features

Apple is also targeting apps with features regulators often consider risky for minors, such as loot boxes.

• In Brazil, if an app includes loot boxes, Apple may automatically rate it 18+.
• That means minors can’t download it, because the App Store will treat it as adult-only.

U.S. states: Utah and Louisiana

Apple is adding tools to help apps comply with state-level child safety laws:

• In Utah and Louisiana, Apple can share a new user’s age category with developers.
• The system can also flag when parental permission is required, including for major app updates.

Why Apple says it’s doing this

Apple’s message is: protect kids + respect privacy.

• The App Store handles most of the verification.
• Apps get only a yes/no type age signal (minor/adult), not personal identity details.
• The goal is to comply with various laws without forcing developers to collect sensitive data.

If you want, paste the original version you want to keep, word-for-word, and I’ll rewrite it just as clear while keeping the same word count.

Everything is changing in the camming industry. As a clear example, after years of being known as a traffic company—especially for promotion within the adult cams space—2026 is the year the industry says goodbye to Diva Traffic!

Behind this exit is an announcement posted by the company under the headline “Important Service Update.” Diva Traffic stated that effective February 20, 2026, it will discontinue its operations, including all traffic purchase services. The platform also noted that all previously purchased tokens must be used to activate traffic boost campaigns by that date, and that as of today, token purchases and subscriptions are no longer available.

The shutdown closes the chapter on a brand that, for some, was a useful promotional tool—and for others, a recurring source of controversy. Over time, countless rumors circulated across studios and among models, with many in the community alleging the service relied heavily on bots, fake clicks, and non-human traffic rather than real users.

Whatever side of the debate people were on, the outcome is now the same: a familiar name in cam-focused traffic services is exiting the scene, and studios and creators will need to rethink and adjust their promotion strategies moving forward.

Arizona lawmakers are weighing a sweeping app-store age-verification proposal that would apply not only to app downloads but also to core phone functions most users take for granted, according to Reclaim The Net.

The measure, House Bill 2920, was introduced on January 27, 2026, and is pending before the Arizona House Science & Technology Committee. As described, the bill would require age checks for app store accounts and would also cover preinstalled software and built-in tools such as the web browser, text messaging app, search bar, calculator, and weather widget, effectively placing nearly every piece of mobile software under age-gating requirements.

How HB 2920 would work

Under the proposal, app store providers would be required to determine each account holder’s age category using “commercially available” verification methods. The bill, as reported, does not precisely define what verification methods would qualify, and it assigns the Arizona Attorney General the role of setting rules for acceptable processes.

HB 2920 would divide users into four groups:

• Under 13
• Ages 13–16
• Ages 16–18
• Adults

For anyone under 18, the bill would require the minor’s account to be “affiliated” with a parent account and mandate “verifiable parental consent” before a minor could download or purchase an app or make in-app purchases. Reclaim The Net notes that this consent framework would also extend to preinstalled apps, meaning the first time a minor attempts to open certain default phone functions, the system could require parent approval before access is granted.

A key issue raised in the coverage is that the bill does not specify how parent-child relationships will be verified. Instead, app stores would have wide discretion to determine parenthood via unspecified “commercially reasonable” methods.

Updates could trigger new consent requests

The bill’s scope would extend beyond initial access and downloads. If a developer makes a “significant change” to an application, the proposal would require renewed parental consent before the minor can access the updated version.

In the Reclaim The Net description, “significant change” would include:

• Privacy policy modifications
• Changes to categories of data collected
• Age rating changes
• Adding in-app purchases
• Introducing advertisements

That could mean routine software maintenance becomes a gatekeeping event. A weather app that adds a banner ad, for example, could require fresh parental approval. A note-taking app’s privacy policy update could also trigger a new consent prompt before a minor can keep using it.

To make this system function, developers would be required to notify app stores of “significant changes,” while app stores would need to notify parent accounts and secure renewed permission before restoring access.

Penalties and lawsuits

Reclaim The Net reports that HB 2920 would include civil penalties up to $75,000 per violation, alongside a private right of action allowing parents and minors to sue for $1,000 per violation, plus potential punitive damages. The piece argues these provisions could increase compliance pressure on both app stores and developers.

Because consent status would need to be tracked, app stores would have to collect and maintain records tied to age categories, parental affiliations, verification records, and consent histories, and share age-category data with developers during downloads, purchases, or app launches. While the bill includes language around “industry standard encryption” and limiting data use to compliance purposes, it would still require extensive data collection and transmission to operate as designed.

Comparisons to other states and legal scrutiny

The coverage points to Texas as a recent example of similar legislation. Reclaim The Net notes that a federal judge blocked Texas’ law before it took effect, describing it as comparable to requiring every bookstore to verify every customer’s age and to require parental consent for minors to enter and buy books. The ruling found the law likely unconstitutional, concluding that it imposed content-based restrictions and failed strict scrutiny.

Arizona’s HB 2920 is framed as part of a broader state-level push toward app-store age verification. Reclaim The Net lists Texas, Utah, Louisiana, and California as states that have passed versions of these measures, with different effective dates and enforcement approaches.

HB 2920 is described as going further than most by explicitly covering preinstalled applications, raising the possibility that a minor could purchase a phone and be unable to use built-in tools until a parent account is established and consent is granted.

Proposed effective date

Reclaim The Net reports that if HB 2920 advances through the legislature, it would take effect on November 30, 2026, setting a compliance timeline for app stores and developers.