Age verification prompt within the Texas App Store. (Illustrative AI-generated image).
At a Glance
Texas SB 2420 now requires age verification for new Apple App Store accounts, with a full compliance deadline of June 4, 2026. Developers must implement new APIs to check user ages, obtain parental consent for minors under 18 for downloads and purchases, and handle consent revocation. While new accounts are already affected, developers have time to integrate these changes, which are designed to streamline compliance across various state regulations.
- Texas SB 2420 mandates age verification and parental consent for new App Store accounts for users under 18.
- Developers must implement Apple’s Declared Age Range API and handle consent for downloads, in-app purchases, and significant app changes.
- A critical requirement is setting up server notifications to manage parental consent revocation.
- The full compliance deadline for developers is June 4, 2026, but new accounts in Texas are already subject to the rules.
- Non-compliance can lead to state penalties, App Store removal, and loss of access to the Texas market.
- This law is part of a growing trend of state-level regulations aimed at protecting minors online.
Texas Implements New App Store Age Verification Rules
Texas is now enforcing age checks for new Apple App Store accounts following a court lifting an injunction on state law SB 2420. This means the law is effective immediately for new account creations in Texas.
The legislation mandates that app marketplaces and developers must verify the age of users and obtain parental or guardian consent for minors under 18. This requirement applies to app downloads, in-app purchases, and significant changes made to apps.
Parents or guardians also have the ability to revoke their consent at any time. If consent is withdrawn, the app must cease charging the child or making further changes for that user.
While the full compliance deadline for developers is set for June 4, 2026, giving them approximately 14 months to update their systems, new accounts in Texas are already subject to these age assurance rules.
Apple announced these changes on April 11, 2026, stating that it is providing developers with the necessary APIs and tools to facilitate compliance. The company has also linked to detailed documentation and a sandbox testing environment for developers.
Who is Affected by Texas App Store Age Verification and When
Affected Users and Developers
Affected users: Anyone creating a new Apple Account in Texas. The law specifically targets minors under 18, requiring age verification at the point of account creation.
Affected developers: All developers distributing apps through the Apple App Store in Texas. This includes independent developers, small studios, and large companies across various sectors like gaming, streaming, and social media.
Key Dates for Compliance
- April 11, 2026: Apple announced the law’s immediate enforceability for new Texas accounts.
- June 4, 2026: The final deadline for all required features, including age checks, consent management, and handling of significant app changes.
Currently, Apple states the changes apply to “new Apple Accounts in Texas.” It remains unclear if existing accounts will be impacted in the future.
While large studios might find integration easier due to established systems, independent developers may face resource constraints. However, Apple’s provided APIs are designed for straightforward implementation, with the main effort lying in integrating the consent and revocation flows.
Developer Requirements for Texas App Store Compliance
Apple has outlined specific steps developers must take to comply with Texas SB 2420 before the June 4, 2026 deadline.
Mandatory Implementation Steps
- Add an app age rating: Developers must include an age rating code in the app’s Info.plist file. This code informs the system about the app’s suitability for different age groups, helping to determine if parental consent is needed for downloads.
- Utilize the Declared Age Range API: This API allows apps to request the user’s age category (e.g., “under 4,” “4 to 12,” “13 to 17,” “18 and over”). Apps must respect these categories and adjust features accordingly, such as requiring parental consent for in-app purchases for users under 18.
- Handle parental consent for purchases and downloads: Apps must prompt for parental approval when a minor attempts to download a restricted app or make an in-app purchase. The app needs to be prepared to receive and act upon the consent status provided by Apple’s system.
- Implement the Significant Change API: This API notifies the app of significant updates, such as major feature additions, privacy policy changes, or increased spending limits. Developers must define what constitutes a “significant change” for their app and re-request parental consent if necessary.
- Manage consent revocation: Developers must set up their servers to receive notifications from Apple when a parent revokes consent. Upon receiving such a notification, the app must disable in-app purchases and revert to a state suitable for a minor user.
- Test in the sandbox environment: Developers should use Apple’s provided sandbox environment to validate their API implementations, including age requests, consent flows, and revocation notifications, before deploying to the live App Store.
Essential APIs for Texas App Store Age Verification
Apple provides three primary tools to help developers meet the requirements of Texas SB 2420.
Declared Age Range API
This is the central tool for age verification. When a user logs in or launches the app, this API is called to return the user’s age category. It’s crucial for gating access to age-restricted features. For instance, it ensures that in-app purchase buttons are not displayed to users under 18 without parental consent. The API respects user privacy by providing a range rather than an exact date of birth.
Significant Change API (PermissionKit Framework)
This API identifies material changes within an app, such as the introduction of new subscription tiers, chat features, or altered data collection policies. When triggered, it requires the app to re-obtain parental consent for minor users before applying the changes. Developers are responsible for defining what constitutes a significant change. This API is integrated with the PermissionKit framework.
Server Notification for Consent Revocation
This webhook system alerts a developer’s server when a parent revokes consent for their child’s access to an app. Developers must configure a server endpoint to receive these notifications, which include the app identifier and user account details. Upon notification, the app must disable in-app purchases, remove newly added features, and revert to a pre-consent state for that user to ensure legal compliance.
Developers are strongly advised to consult the full technical specifications on the Apple Developer website. The APIs are available for testing immediately.
Guidance for Parents and Teens in Texas
For parents in Texas, this new law enhances control over their children’s digital activities on Apple devices.
Understanding Consent and Revocation
How consent works: Upon creating a new Apple Account, the system verifies the user’s age. If the user is under 18, any attempt to download a new app or make an in-app purchase will require parental approval, typically facilitated through Family Sharing.
How revocation works: Parents can access their account settings to view a list of apps their child uses. Consent for any app can be revoked, which will disable in-app purchases and features added after consent was granted. The app may retain basic functionality but will restrict approved features.
Impact on teens: Teens aged 13 to 17 will need parental approval for purchases and downloads, similar to existing Family Sharing features but now legally mandated in Texas. This may result in more frequent prompts for parental approval within apps and games.
Privacy considerations: Apple’s system protects user privacy by providing developers only with an age range, not the child’s exact age, while still meeting legal requirements.
Parents should review and update their Apple Account settings, particularly Family Sharing, to ensure smooth operation of the consent and revocation processes.
Consequences of Non-Compliance with Texas SB 2420
Failure to comply with Texas SB 2420 can lead to significant penalties.
Legal and App Store Penalties
The law includes provisions for penalties, with the Texas Attorney General empowered to initiate enforcement actions. These actions can result in civil fines and potential injunctions that could block app distribution within Texas.
Apple is also enforcing compliance through its App Store review process. Apps that fail to implement the required APIs and age rating codes may be rejected or removed from the Texas App Store, as Apple will not distribute non-compliant applications.
Developers face both legal repercussions from the state and the risk of losing access to the large Texas market, potentially impacting revenue significantly.
While large companies may adapt quickly, smaller developers with limited resources might find the integration challenging. The most complex aspect for any developer is implementing the consent revocation handling, which requires a dedicated server endpoint and logic to disable purchases.
The June 4, 2026 deadline provides ample time, but developers are encouraged to begin implementation early to avoid last-minute issues and potential bugs.
The Growing Trend of State-Specific Age Verification Laws
Texas SB 2420 is part of a broader trend of states enacting or proposing laws to regulate minors’ online activities.
Examples of Similar State Laws
- Ohio: The Parental Notification by Social Media Operators Act requires parental consent for minors under 16 on social media platforms.
- Florida: Florida’s law mandates age verification for adult content websites and restricts social media use for minors under 16.
- Utah: The Social Media Regulation Act requires parental consent for minors’ social media use and imposes time restrictions.
- Arkansas: The Social Media Safety Act requires parental consent for social media accounts, though parts have faced legal challenges.
- California: The Age-Appropriate Design Code prioritizes children’s privacy by requiring default privacy settings for minors.
This patchwork of state laws creates a complex compliance landscape. Apple’s platform-level approach simplifies this for developers by allowing a single implementation to address various state requirements.
Texas SB 2420 stands out for its broad application to all apps, covering downloads, purchases, and significant changes, making it more comprehensive than many other state laws. If SB 2420 withstands legal scrutiny, other states may follow suit, making age verification a standard requirement across the US, similar to regulations like GDPR in Europe.
Developers who proactively comply with the Texas law will be better positioned for future regulatory changes. The immediate next steps for developers include reviewing Apple’s documentation, setting app age ratings, testing APIs in the sandbox, configuring server notifications for revocation, and updating apps to respect age categories and consent status before the June 4, 2026 deadline.
Parents should ensure their Family Sharing settings are up-to-date to manage consent and revocation effectively. Proactive preparation is key to navigating these new regulations and maintaining access to the Texas app market.
Frequently Asked Questions
What is the main requirement of Texas SB 2420 for the App Store?
Texas SB 2420 requires app marketplaces and developers to verify the age of users creating new accounts and obtain parental or guardian consent for minors under 18. This applies to app downloads, in-app purchases, and significant app changes.
When do developers need to comply with these new Texas App Store rules?
The full compliance deadline for developers is June 4, 2026. However, the law is already in effect for new Apple accounts created in Texas, meaning age assurance rules apply immediately to new sign-ups.
Which APIs must developers use to comply with Texas SB 2420?
Developers need to use Apple's Declared Age Range API to determine a user's age category and the Significant Change API to manage updates requiring re-consent. They also need to implement server notifications for consent revocation.
What happens if a parent revokes consent for an app?
If a parent revokes consent, the app must stop allowing in-app purchases for that child and disable any features that were added after consent was initially granted. The app may revert to a basic functionality state.
Are existing App Store accounts in Texas affected by this law?
Currently, Apple has stated that the changes apply specifically to 'new Apple Accounts in Texas.' It is not yet clear if or when existing accounts will be subject to these age verification requirements.
What are the penalties for not complying with Texas SB 2420?
Non-compliance can result in legal penalties from the Texas Attorney General, including civil fines and injunctions that could block app distribution in the state. Apple may also reject or remove non-compliant apps from the App Store.
