⏱️ Lectura: 9 min
As of September 14, a teenager with iOS 27 cannot open a new website in Safari without a parent approving it first from their own iPhone. The feature is called Ask to Browse, and it’s the centerpiece of a complete redesign of parental controls that Apple released alongside iOS 27, iPadOS 27, and macOS 27.
📑 En este artículo
The same update package brings Siri AI, the new version of Siri with generative artificial intelligence, but the change with the most immediate impact for millions of families is different: how Apple decides what a minor can see and who they can talk to on their devices.
TL;DR
- Apple released iOS 27, iPadOS 27, and macOS 27 on September 14, 2026, with redesigned parental controls.
- Ask to Browse requires a parent’s approval before entering a new website in Safari.
- Communication Safety now detects and blocks gore or violent content in minors’ conversations.
- A new child account setup flow applies age-based safeguards from the very first startup.
- Parents choose which apps each child can use from day one and enable them gradually.
- The same release brings Siri AI, the new generative AI-powered Siri, in beta and English-only for now.
- Apple confirmed that Siri AI adds Spanish, French, Japanese, Korean, and Portuguese in October 2026.
What happened
Apple confirmed the release of its software updates on September 14, 2026, focusing on two fronts: Siri AI and a set of redesigned parental controls. The second front rewrites how child accounts work across Apple’s ecosystem from the very first time a device is turned on.
The most visible change is Ask to Browse. Through iOS 26, Safari filtered websites by category: a parent would block “adult content” or “social media” and trust that automatic classification worked. With iOS 27, every new site a child tries to open triggers a notification to the parent’s device, who must approve or deny access before the page loads.
The second major change is the expansion of Communication Safety. The feature, originally designed to detect nudity in photos and videos sent through Messages, now also identifies and blocks graphic violence or gore before the minor sees it. All the analysis runs on the device: Apple states it does not receive or review the content of conversations.
A third piece covers account setup. The new configuration flow requires defining the minor’s age from the first step and automatically applies matching safeguards, instead of leaving parents to activate them manually afterward. From day one, parents choose exactly which apps their child can use and enable them gradually.
Context and history
Screen Time debuted in 2018 with iOS 12 in response to pressure from investors and parent groups who accused Apple of designing addictive devices for minors. Communication Safety arrived in 2021, initially limited to nudity in photos sent through Messages. That same year, Apple abandoned a more aggressive plan to scan for CSAM in iCloud after pushback from privacy organizations, and since then has shifted its child safety strategy toward on-device processing and optional controls for parents.
iOS 27 arrives at a moment of growing regulatory pressure. Several countries are debating or have already passed age verification laws for apps and social media, and platforms like Google (Family Link) and Microsoft (Family Safety) are competing to offer the most complete set of parental controls. Ask to Browse and the expanded Communication Safety are Apple’s direct response to that pressure, without relying on identity verification or cloud scanning.
How it works under the hood: parental controls
iOS 27’s parental controls rely on the same framework Apple has exposed to third-party developers since iOS 16: FamilyControls. Any third-party app that manages screen time, app blocking, or usage reports goes through the same authorization layer that Ask to Browse now uses.
| Feature | Before (iOS 26 and earlier) | Now (iOS 27) | Requires |
|---|---|---|---|
| Web content | Blocking by whole category (adult, social media) | Ask to Browse: site-by-site approval before the first visit | Child account + Family Sharing |
| Communication Safety | Detects nudity in photos and videos from Messages | Adds detection of graphic violence content (gore) | iOS 27 on the child’s device |
| Account setup | Restrictions activated manually after setting up the device | Setup flow that applies age-based safeguards from the first step | Creating the account as a child account |
| App access | All preinstalled apps available from the start | Parents choose which apps are available from day one | iOS 27 / iPadOS 27 |
The table sums up the conceptual shift: Apple moved from static category-based rules to individual, site-by-site decisions approved in real time. It’s a model similar to the one already used by temporary access managers in corporate environments: nothing opens by default, everything requires explicit permission.
flowchart TD
A["Child opens a new site in Safari"] --> B["iOS 27 checks if the domain has already been approved"]
B --> C{"New site?"}
C -->|"Yes"| D["Ask to Browse notification sent to the parent's iPhone"]
D --> E{"Does the parent approve?"}
E -->|"Approves"| F["The site opens on the child's device"]
E -->|"Rejects"| G["The site remains blocked"]
C -->|"No"| F💡 Tip: All processing for Ask to Browse and Communication Safety runs on-device: neither one sends content to Apple’s servers for classification.
How to start using it today
Turning on Ask to Browse doesn’t require anything special beyond staying up to date with the updates. A parent needs three things: an active Family Sharing group, the child’s account set up as a child account, and both devices updated to iOS 27 or later.
- On the parent’s iPhone: Settings > Screen Time > [child’s name] > Content and Privacy > Content Restrictions > Web Content.
- Turn on “Ask Before Visiting New Sites” (Ask to Browse).
- On the child’s iPhone, every new site triggers a push notification to the parent with the domain and the option to approve or reject it.
For developers building parental control apps or alternative browsers, the entry point is the same as always: request the Family Controls entitlement in Apple’s developer portal, add the capability in Xcode, and call AuthorizationCenter.shared.requestAuthorization(for:) before reading or modifying Screen Time state.
import FamilyControls
let center = AuthorizationCenter.shared
Task {
do {
try await center.requestAuthorization(for: .child)
print("Screen Time permissions granted")
} catch {
print("User denied the permission: \(error)")
}
}This first block requests authorization to manage Screen Time on the child’s account. Without this step, no subsequent call to the framework has any effect.
import FamilyControls
import ManagedSettings
import SwiftUI
struct ControlParentalView: View {
@State private var seleccion = FamilyActivityPicker.Selection()
private let store = ManagedSettingsStore()
var body: some View {
FamilyActivityPicker(selection: $seleccion)
.onChange(of: seleccion) { nuevaSeleccion in
store.shield.applications = nuevaSeleccion.applicationTokens
store.shield.webDomains = nuevaSeleccion.webDomainTokens
}
}
}
func verificarAutorizacion() {
let estado = AuthorizationCenter.shared.authorizationStatus
print("Current status: \(estado == .approved ? \"approved\" : \"pending\")")
}This second block shows the realistic case: an app and domain picker that a parent chooses from a native picker, and a verificarAutorizacion() function to confirm in code that Family Controls permission is still active, without needing to check the Settings interface by hand.
Impact and analysis
For families, the immediate effect is more friction while browsing: every new site depends on an adult responding to a notification. For browser and parental control app developers, the message is that Apple continues centralizing child safety logic in FamilyControls instead of leaving it to third parties, which shrinks the space for independent monitoring apps.
The model has a real cost: every new site adds friction and depends on the parent responding to the notification in time, which is impractical if the adult is busy or asleep. Apple doesn’t currently offer an automatic approval window or an “approve later” mode, so a site with no response simply stays blocked.
⚠️ Heads up: Without a response from the parent, the site stays blocked indefinitely: there’s no automatic expiration of the request in this first version.
What’s next
Apple confirmed that Siri AI adds Spanish, French, Japanese, Korean, and Portuguese in October 2026, so much of Latin America won’t get access to the new Siri until next month. There’s no public roadmap for the parental controls: this is the first version, and Apple hasn’t said whether it will add temporary approval or shared lists across devices in the same family.
📖 Summary on Telegram: View summary
Try it yourself: if you manage a child’s iPhone, update both devices today from Settings > General > Software Update and turn on Ask to Browse in Screen Time > Content and Privacy.
Frequently Asked Questions
What is Ask to Browse in iOS 27?
It’s a Safari feature that requires a parent to approve every new website before a child account can visit it for the first time.
Does Communication Safety see the content my child sends?
No. Classification runs on the device using on-device models; Apple doesn’t receive or review the content of messages.
Do I need Family Sharing to use these controls?
Yes, the minor’s account must be set up as a child account within a Family Sharing group managed by an adult.
Can developers integrate these controls into their apps?
Yes, through the FamilyControls framework (AuthorizationCenter, ManagedSettingsStore, DeviceActivity), available to third-party apps that manage screen time.
When is Siri AI coming in Spanish?
Apple announced that support for Spanish, French, Japanese, Korean, and Portuguese arrives in October 2026; for now, Siri AI is in beta only in English.
What if my child already has an account that isn’t a “child” account?
It needs to be migrated to a child account from Settings > Family Sharing for the new age-based safeguards to apply.
References
- Apple Newsroom: official announcement of the iOS 27, iPadOS 27, and macOS 27 updates.
- Apple Developer, Family Controls: documentation for the framework used by parental control apps.
- Apple, Child Safety: official page detailing Apple’s approach to child safety.
- Apple, Family Sharing: how the setup for child and shared accounts works.
📱 Do you like this content? Follow @programacion on Telegram for daily tech content in Spanish: quick summaries, fresh content every day.
0 Comments