What Family Link cannot do on Android

The page describes what is not covered by Google Family Link on Android. It is the companion to Set up Family Link on Android.

The setup article assumes the controls exist. This page documents the gaps where the controls do not, do not reach, or only sometimes reach.

The shortest version: Family Link is account-based. Anything that leaves the supervised account is outside its scope.

Definition

A research-grounded inventory of the parents’ controls that Family Link does not, by Google’s documentation, cover on Android. The list is the inverse of the setup article: the points at which the configuration that appears to work quietly does not.

Scope

The page covers the parent-managed Family Link surface on Android phones and tablets that ship with Google services. It documents what the controls do not do on the supervised account, on the device, on the Play Store, on the in-app purchase flow, on YouTube, on SafeSearch, and across device profiles.

Google documents the per-app time limit surface as Android 7 or later; the underlying Family Link account supervision runs on the cited Android 5.1+ child devices and on the parent-side Android 5+ / iOS 13+ Family Link app [source: google-family-link-screen-time] [source: google-family-link-getting-started]. The limitations below assume that baseline; older devices fall outside the documented Family Link surface and are not covered here.

It does not cover the iOS or Apple-Family-Sharing side of these limits. It does not cover post-Google Huawei devices, which ship without Family Link. The OEM-side variations live on Why the same Android article reads differently on Samsung, Xiaomi, and Huawei.

Where the gaps come from

Family Link binds its controls to a Google Account on a compatible device. The controls travel with the account, not with the device, the phone number, or the person holding the device.

This produces four documented gaps:

1. Separate device profiles are not supervised.
2. OEM forks may rename or relocate the entry points.
3. Non-Play billing routes are not covered.
4. Remote screen, camera, and microphone are not available.

The rest of this article names each gap, names the source for the documented scope, and names the documented exception where one exists.

What the controls do not cover

The list below is what Google documents the controls as not covering. Each line is a separate limit that some forum thread later describes as the controls not working.

Not screen-viewing, not microphone

Family Link does not allow the parent to see the child screen during a session, and does not allow the parent to listen to the child microphone. Google documents the product as a settings surface [source: google-family-link-supervision].

The location setting is a device location, not a remote view. Google states the parent can see the device’s location after location sharing is enabled [source: google-family-link-location]. A parent-side location pin is not a live video feed.

Not a guest-mode lock

Family Link settings on a child account do not apply to other profiles on the same device. Google documents this limitation explicitly: parent settings reach the child account, and stop there [source: google-multiuser].

Google recommends a separate screen lock on every additional or adult profile to prevent the child from switching users and bypassing the configuration [source: google-multiuser]. The parent needs to disable Add/Remove user for the child profile as the next step.

The UI key for the multi-user surface is google.familylink.tablet_users.

Not a Google Kids Space replacement

Google Kids Space is a separate tablet environment. The parent-side controls for Kids Space live under Family Link, but Kids Space is a launcher, not a setting [source: google-kids-space].

A parent who has set up Family Link on a tablet has not automatically enabled Kids Space. Kids Space is a separate configuration step with its own app allowances and its own UI key google.familylink.kids_space.

Not a content firewall

Google Play content restrictions do not block restricted material from appearing in a search result or via a direct link. Google documents this as a scope boundary [source: google-family-link-play-content].

Apps downloaded before the restriction was set may remain visible on the device. The parent can block them individually, but the restriction does not retroactively hide them.

Not a SafeSearch on every app

When a supervised Google account is detected, Google turns SafeSearch on and locks it for the Google Search product [source: google-safesearch]. The same lock does not extend to a third-party search app, an in-app search bar, or a search bar embedded in a browser other than Chrome.

Not a YouTube on every video product

The supervised YouTube content setting is a YouTube product setting. It does not govern videos played in other apps, embedded players on websites, or non-YouTube video platforms [source: youtube-supervised].

Not a system-app limit

Family Link per-app limits do not apply to system apps. Google documents this exception explicitly [source: google-family-link-screen-time]. A child who opens the dialer, the camera, or the system messages app does not see a per-app limit surface there.

Not a call and SMS viewer

Family Link does not list the child’s incoming or outgoing calls and SMS for the parent. Google’s published behaviour is to surface app-level reporting through Play and Family Link, not a call detail record [source: google-family-link-supervision].

Not a third-party app store gate

Family Link app approval applies to Play Store apps. Family Link does not, on its own, gate installs from Samsung Galaxy Store, Huawei AppGallery, Xiaomi GetApps, or any sideloaded APK. Each store has its own restriction mechanism, and each one is a separate page in this wiki.

See Play, AppGallery, and sideloading: where the controls stop for the full list.

Not a Play-billing-only gate for non-Play billing

Purchase approvals cover Google Play billing only [source: google-family-link-purchase-approval]. The documented scope is the Play Store payment flow. A gift card redeemed on a third-party app store, a web checkout for a Roblox Robux top-up, or a carrier-billed purchase fall outside the documented scope.

See Play Store purchases and approvals on Android for the Play side and the documented gaps.

Not an Android 17 device-local control

Family Link is account-based. Android 17 introduced a separate device-local controls surface [source: google-android-device-controls], with a different PIN, different scope, and a documented limitation: it cannot be enabled when the device has multiple profiles [source: google-android-device-controls].

The two surfaces are not redundant. A parent who has set up Family Link has not set up the Android 17 device-local controls, and the device-local controls have their own PIN. Deleting the device-local PIN turns off all device-local controls; it does not turn off Family Link [source: google-android-device-controls].

Not a recovery from a factory reset

A factory reset on the child device removes the supervision link from the device side. The child account may still be supervised on Google’s account side, but the device is no longer enrolled. The parent must set up the device again from the parent-side app, with the device in hand.

See Factory reset, recovery, and the unhappier bypasses for the hard reset path.

Not a per-birthday opt-in

When the child reaches the country minimum age, Family Link supervision becomes opt-in rather than enforced [source: google-supervision-13]. The configuration does not survive a birthday decision by the child to leave supervision.

A parent who wants the limits to continue past the country age must negotiate that with the child, not expect the platform to enforce it [source: google-supervision-setup].

What the gaps cost

The gaps are not abstract. They are the channels through which a configuration appears to work but does not.

• A child switches to a guest profile and the limits fall away. Google says the profile boundary is the parent’s responsibility [source: google-multiuser].

• A child installs an app from a third-party store and the parent’s Play ceiling does not catch it.

• A child buys a gift card with their own money and spends it on a non-Play app. The Play approval flow is documented to not cover this [source: google-family-link-purchase-approval].

• A child holds a friend’s device, and the friend’s account is not supervised. Family Link does not follow the device.

• A child reaches the country age and decides to leave supervision. The platform does not block the choice [source: google-supervision-13].

The U.S. FTC treats parental controls as a layer, not a complete solution [source: consumer-ftc-parental-controls]. The gaps above are the cost of treating one layer as a complete solution.

What to add on top

The list below is the documented scope of common companion controls. None of them is built into Family Link.

• DNS-level filtering. Controls at the DNS layer apply to every device on the home network, including guest devices. Family Link does not provide this.

• Carrier-level controls. Most mobile carriers expose purchase limits or content filters on the account side. These are independent of Family Link.

• School-managed devices. A device that is school- managed carries the school’s policy, not the parent’s Family Link policy. Family Link does not apply to school-managed devices.

• A separate device for the child. A parent who is considering a dedicated device for the child can lean on the Android 17 device-local controls, on a Kids Space tablet, or on a Samsung Kids device. Each is a separate configuration step [source: google-android-device-controls] [source: google-kids-space].

Talking about it

The conversation that makes the limits sustainable is the one where the child understands what the configuration does and does not cover.

Three small habits:

• Name the boundary as the parent defines it. Family Link is the parent-side account supervision. It is not a screen viewer, not a microphone, not a per-device root. Google documents the surfaces as settings [source: google-family-link-supervision].

• Acknowledge the gaps. The gaps above are not bugs. They are the documented scope. A family that says “Family Link does not let me see the child screen” is more accurate than a family that says “Family Link protects our child.”

• Re-check after every birthday, every new device, every new app store. The gaps above are stable, but the child’s reach grows. The U.S. FTC recommends periodic review of the configuration [source: consumer-ftc-parental-controls].

The configuration protects the conversation. The conversation protects the relationship. Both are needed.

Sources

• google-family-link-getting-started — Google Families Help, “Get started with Family Link”. The parent-side setup flow and the supervisor role [source: google-family-link-getting-started].

• google-family-link-supervision — Google Families Help, “Set up supervision to continue using your Google Account”. The product description, the parent-side scope, and the documented gaps [source: google-family-link-supervision].

• google-family-link-screen-time — Google Families Help, “Manage your child’s screen time”. The daily limit, manual lock, and app-limits documentation [source: google-family-link-screen-time].

• google-family-link-play-content — Google Families Help, “Set up content restrictions on Google Play”. The maturity-rating ceiling and the direct-link / search-result scope boundary [source: google-family-link-play-content].

• google-family-link-purchase-approval — Google Families Help, “Purchase approvals on Google Play”. The Play-billing-only scope [source: google-family-link-purchase-approval].

• google-supervision-13 — Google Families Help, “How Google Accounts work when children turn 13”. The supervision-continuation rule [source: google-supervision-13].

• google-supervision-setup — Google Families Help, “Set up supervision to continue using your Google Account”. The continuation-of-supervision flow [source: google-supervision-setup].

• google-safesearch — Google Search Help, “Make Google Search safer with SafeSearch”. The supervised SafeSearch toggle and its scope [source: google-safesearch].

• google-android-device-controls — Android Help, “Set up parental controls on an Android device”. The Android 17 device-local controls and the multi- profile prerequisite [source: google-android-device-controls].

• google-android-wellbeing — Android Help, “Manage how you spend time on your Android phone with Digital Wellbeing”. The per-device app limits and the App limits PIN [source: google-android-wellbeing].

• google-kids-space — Google Kids Space Help, “Use Family Link to manage Google Kids Space”. The Kids Space launcher and its parent-side controls [source: google-kids-space].

• google-multiuser — Google Kids Space Help, “Add users to a device”. The profile boundary and the screen-lock recommendation [source: google-multiuser].

• youtube-supervised — YouTube Help, “Supervised experience on YouTube”. The supervised YouTube product’s scope [source: youtube-supervised].

• consumer-ftc-parental-controls — U.S. FTC, parental controls advice. The layered-defense framing [source: consumer-ftc-parental-controls].