> For the complete documentation index, see [llms.txt](https://docs.onside.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onside.io/store/onside-rules-and-policies-united-states/parental-controls-for-android.md). # Parental Controls for Android Our Approach to Parental Controls Onside gives parents and guardians two layers of control over what a child can download through the Onside Store: (1) a PIN-protected restriction inside the Onside Store itself for apps rated Mature (18+), and (2) the device- and Google Account-level tools Google provides through Family Link. This page describes both, based on Google's published Family Link documentation and on how Onside's own restriction works. ### Layer 1: Onside Store's PIN-Protected Restriction for Mature Apps The Onside Store applies a content rating to every app. Before an app rated Mature (18+) can be downloaded, the Onside Store requires a PIN. \ This restriction and its PIN are set up from within the Onside Store's Parental Controls settings, and once enabled, the PIN is required before any Mature-rated app can be downloaded going forward. This is only an effective control if a parent or guardian sets the PIN. Because the restriction and PIN are configured inside the Onside Store on the device where it is installed, whoever completes this setup is the one who controls it. We recommend that a parent or guardian install the Onside Store and complete this setup themselves — or supervise their child while doing so — before the child uses the device unsupervised, and that they not share the PIN with the child. If a device already has the Onside Store installed without a parent-set PIN, the parent should complete the steps above as soon as possible and change the PIN if there is any reason to believe the child knows it. ### Layer 2: Google Family Link (Device and Google Account Controls) Family Link is Google's own parental supervision system for a child's Google Account and Android device. It is set up by the parent, from the parent's own device and Google Account, by creating a family group and adding the child's account as supervised. Per Google's published Family Link documentation: * Parents can require sign-in through a supervised child Google Account on the child's Android device (Android 5.0+ for basic supervision, per Google's "which devices can be supervised" guidance; Android 6.0+ is referenced for full setup in Google's "Get started" guidance) or a Chromebook (Chrome OS 71+). * Parents can block or allow individual apps, and manage app permissions, for apps obtained through Google Play. * Parents can require approval for purchases made through Google Play's billing system. Google's documentation states this explicitly: "Family Link's purchase approval settings only apply to purchases made through Google Play's billing system." * Parents can restrict content by maturity rating on Google Play, and set screen time limits, bedtimes, and per-app time limits across the device. ### Account-Level Protections As described in Onside's Terms of Use, the Onside Store is not directed to children under 13, and a user between 13 and the age of majority in their state may use the Onside Store only with the involvement and consent of a parent or legal guardian, who is responsible for that user's account and activity. ### App Listings and Content Information Each app listing in the Onside Store includes a description and content rating to help a parent or guardian assess whether an app is appropriate before it is downloaded, in addition to the Mature-content PIN restriction described above. ### Reporting a Concern If you believe your child accessed inappropriate content or made an unauthorized purchase through the Onside Store, contact us at so we can help. ### Changes to This Page Onside may update this page from time to time to reflect new features or changes in applicable law. Material changes will be reflected here.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.onside.io/store/onside-rules-and-policies-united-states/parental-controls-for-android.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.