When a teacher says an app is required, families may feel there is nothing to decide. The school may have a sound educational reason and a formal agreement with the provider—but it is still reasonable to understand the tool before a child signs in. A focused set of questions can improve access and privacy without placing the child in the middle of an adult dispute.
Begin with the learning purpose
Ask what task the app supports, how often it will be used and whether it is essential or optional. “It helps pupils practise multiplication twice a week” is more informative than “everyone uses it.” Find out whether work is graded, whether the app makes automated recommendations and what happens if a child cannot use it at home.
Request the school-approved download link and account instructions. Avoid creating a separate personal account when the school expects a managed login. Confirm whether the child should use a real name, school email, class code or pseudonymous identifier.
Ask who approved it and who controls the data
The US Department of Education advises educators to check school approval and the conditions under which an online tool may be used under FERPA. Requirements differ outside the United States, so ask about the school’s own policy and local law rather than assuming one jurisdiction’s rules apply everywhere.
Useful questions include:
- Who reviewed the app and its terms?
- What student information does the school send, and what does the app collect directly?
- May the provider use data for advertising, product development or training automated systems?
- How long is information kept, and who requests deletion when a pupil leaves?
- Can families see or correct the child’s information?
- Who should receive a privacy or security concern?
Test the child’s actual route
Check the app on the device and connection the child will use. Can the student sign in without adult workarounds? Are instructions readable? Do captions, keyboard access, screen readers, magnification or alternative input work for the required tasks? If the app blocks participation, ask for an equivalent route while the school addresses the barrier.
EdCaptain’s guide to teaching digital access tools one useful task at a time can help families document what works. The private digital portfolio guide offers a model for minimising personal information in student work.
Clarify home expectations
Ask how much time a typical assignment should take, whether offline work is available during an outage and whether the app sends notifications outside school hours. Find out who provides technical support. Parents should not have to share a child’s password with informal chat groups or contact an unknown provider employee through personal social media.
If the app includes chat, public profiles or peer comments, ask how interactions are moderated and how a child reports a problem. If it includes purchases or advertisements, ask why those features are present in a required learning environment and whether they can be disabled.
Raise concerns without blocking the child’s learning
Keep the request specific: “The app asks for precise location, but the assignment is a reading quiz. Can you confirm why that permission is needed?” Share screenshots of the prompt, device and app version. Ask for the school’s privacy contact or accessibility lead when the teacher is not the right person to answer.
While the issue is reviewed, request a temporary equivalent such as a browser version, printed task or different approved tool. Avoid telling the child to refuse in front of classmates or using their account to test a confrontation.
Revisit at transitions
Check what happens at the end of the term, when the child changes school or when the provider changes its terms. Export genuinely needed work, close personal accounts that are no longer required and ask the school about managed-account deletion. A school app should not become a permanent personal profile by default.
A constructive review does not assume the app is unsafe. It asks the school and family to make the purpose, responsibilities and exit route visible before a child’s data and learning depend on the service.
