Skip to content
Vladimir Zeltyn
All posts
Aug 31, 2026 · 5 min read

Telegram mini apps now inherit Apple's age gate

Apple's Guideline 4.7 makes the host app responsible for every mini app inside it, and new state age-assurance laws now push a user's age category down from the app store into your product. Here's what that changes in a Telegram mini app's first three screens.

Web3ProductUX
Share
Telegram mini apps now inherit Apple's age gate

If you ship a Telegram mini app, you no longer own your own age gate. Apple holds the host app responsible for everything running inside it, and a run of state laws has started pushing a user's age category down from the app store into the product itself. For anyone building in crypto or iGaming, that quietly rewrites the first three screens.

Apple made Telegram answerable for your mini app

Guideline 4.7 of Apple's App Review Guidelines covers software that isn't embedded in the binary, and since the guidelines update Apple published in November 2025 it says plainly that HTML5 and JavaScript mini apps and mini games are in scope. The sentence that matters is short: the host is responsible for all such software offered in its app, including making sure that software complies with the guidelines and all applicable laws.

Read that from Telegram's side and every mini app is Telegram's compliance surface. Read it from yours and you are a tenant. 4.7.2 says the host may not extend or expose native platform APIs to you without Apple's prior permission. 4.7.1 routes you through Guideline 3.1 the moment you sell digital goods. 4.7.4 requires the host to publish an index of everything it offers, with universal links to each one. And 4.7.5 – the one almost nobody has priced in – requires the host to give users a way to identify software that exceeds the app's age rating, and to use an age restriction mechanism based on verified or declared age.

Your mini app has no App Store age rating. Telegram has one. That asymmetry is the whole story.

The age signal now arrives from outside your product

Apple told developers in November 2025 that starting January 1, 2026, new Apple Accounts in Texas would be subject to SB 2420: age assurance plus parent or guardian consent for downloads, purchases and significant changes to an app. A district court enjoined the law that December and Apple paused. Then the Fifth Circuit stayed the injunction. As the law firm Morrison Foerster wrote in June 2026, the statute is now enforceable, and it sorts users into four bands – under 13, 13 to 15, 16 to 17, and adult.

It doesn't stop at Texas. Apple's February 2026 developer note set out the rest of the calendar: age categories shared for new Apple Accounts in Utah as of May 6, 2026 and Louisiana as of July 1, 2026, and, from February 24, 2026, blocked 18+ downloads without adult verification in Brazil, Australia and Singapore.

So age stops being a field in your signup form. It becomes an input, handed to you through Apple's Declared Age Range API along with a signal describing how the age was established and whether consent is still valid. You are consuming it, not collecting it.

"Verified or declared" is the sentence to design around

Look again at the wording in 4.7.5: verified or declared. Those are wildly different signals wearing one label. A verified adult has been checked. A declared adult tapped a number. If you build one gate that treats both as the same green light, you have built a boolean out of a spectrum, and the first regulator to look at your funnel will notice.

The model that survives has three states, not two: confirmed adult, confirmed minor, and unknown. Unknown is the interesting one, because it's where most of your traffic will sit, and because the product decision there is a business decision. Full access? Read-only lobby? Deposits blocked but browsing open? That is a call for a founder to make with the design in front of them, not something to leave to whatever the API happens to return.

I designed a mini app packed with lootboxes. Now think about the rating

Ton Farm is a tap-to-earn farming and mining simulator I designed as a Telegram mini app – neon isometric 3D farms, power stations, ASIC rigs, and yes, a full set of glowing lootboxes feeding an unlockable progression loop.

Set that next to one line from Apple's February 2026 note: in Brazil, apps identified as containing loot boxes are automatically rated 18+. Ton Farm carries no rating of its own. It lives inside Telegram's. The mechanic that makes the game compelling is now a mechanic that helps decide the age band of the container it ships in, and the container isn't yours.

That's the part I'd want any team building Telegram mini apps to sit with. Your monetization loop is no longer only a retention question. It's a distribution question, decided one level above your product, by rules written for an app you don't control.

Design the blocked state before you design the lobby

Nearly every mini app I've reviewed has a beautifully considered happy path and nothing at all for the cases that now matter most. What does a 16-year-old see? What does a user whose parental consent was revoked mid-session see – and does your app even listen for that notification? What happens to a wallet that already holds a balance when the age category flips?

These aren't error states. In an age-gated vertical they're product states, and they deserve the same design attention as the deposit screen. The teams doing this well are building the restricted view as a real, designed surface: a lobby you can look at but not fund, a clear reason, a route to resolve it. The teams doing it badly ship a gray modal saying "not available in your region" and watch a compliant, spendable adult bounce because a declared birthday was never captured.

I've spent years arguing that onboarding and first deposit are where iGaming and crypto products are won or lost. The age layer just moved into that exact stretch of the funnel, arriving from a platform you don't own, with a legal deadline attached. It is going to be designed by someone. Better it's you than app review.

Sources

  1. Apple Developer – Updated App Review Guidelines now available (November 2025)
  2. Apple Developer – App Review Guidelines, Guideline 4.7 (accessed August 2026)
  3. Apple Developer – Next steps for apps distributed in Texas (November 2025)
  4. Apple Developer – Age requirements for apps distributed in Brazil, Australia, Singapore, Utah, and Louisiana (February 2026)
  5. Morrison Foerster – Update: Texas App Store Law Takes Effect After Fifth Circuit Stays Preliminary Injunction (June 2026)
Share
By Vladimir ZeltynAll posts