Why is an app asking for a new permission after an update?

Record the request accurately

Research context: Ofcom reported that 88% of children ages 3–7 and 99% of children ages 8–17 went online in 2025. Source: Ofcom: Children and Parents Media Use and Attitudes 2025–26.

Read the prompt before dismissing it. Note the permission name, app version, and action that caused it, without recording private content behind the prompt. Ask the child what they were trying to do. A newly introduced feature may be optional, or a familiar feature may now be explained differently. Find the relevant official information rather than searching for a generic answer about all permissions. If the wording is unclear, pausing the activity is a reasonable immediate response.

Decide whether the feature belongs in the plan

Compare the new capability with what you previously approved. For example, a solo creative tool adding a sharing feature creates a different family question from a change to its drawing controls. You can keep using the original activity if the app supports that without the new permission. If it does not, consider whether the feature and information request fit your needs. Avoid granting broad access simply because the child wants to finish a project quickly; first look for a supported way to save their work.

Test the chosen arrangement

After deciding, try the specific task with harmless material. Explain the result to the child, including any feature you are leaving off. If the app does not behave as documented, use the provider’s support route and keep the question narrow. Revisit your note once the issue is resolved so an outdated warning does not remain the household rule indefinitely. Approval of an earlier version can remain useful context, but it should not be presented as automatic approval of every feature added later.