How to Discuss Companion-App Online Safety and Boundaries with Children
A useful family safety conversation is not a one-time lecture about an app being good or bad. It begins with what the companion app actually lets a child do: chat with an automated character, interact with other users, upload photos or voice, make purchases, follow links, receive notifications, or move a conversation elsewhere. Those features create different decisions, so a single rule such as “be careful online” gives the child little to apply at the moment it matters. Build a short agreement together using observable actions: which information stays private, which contacts need a check-in, which purchases require approval, what content should not be uploaded, and how to leave an uncomfortable or confusing interaction. Pair the agreement with device controls, but explain what each control does. The goal is not secret surveillance or a promise that settings catch everything. It is a shared response plan that a child can remember, use, and bring back for revision.
Map the app together before setting rules
Ask the child to show how they enter the app, what appears on the first screen, who or what can send a message, and where profile, upload, purchase, report, block, and delete controls live. Do not begin by reading private conversations. First classify the features together: automated interaction only, public or group spaces, direct contact with people, media upload, location or contact permissions, external links, and paid items. Check the age rating and current store description, but do not treat either as a complete description of every conversation. Make a note when neither of you can tell whether a reply comes from AI, staff, or another user. The map turns the discussion from abstract danger into concrete decisions and reveals which rules are relevant. An AI-only diary, a public community, and a marketplace should not receive identical family boundaries.
Write five boundaries as actions a child can recognize
Use five headings. Identity covers full name, school, routine, address, live location, account recovery details, and recognizable usernames. Contact covers friend requests, private messages, links, and moving to another platform. Media covers photos, voice, documents, and background details that reveal a place or person. Money covers trials, subscriptions, tips, gifts, and virtual currency. Exit covers muting, blocking, reporting, closing the app, and asking an adult to help. Under each heading, write one allowed action, one action that needs a check-in, and one action to stop. “You may customize an avatar; ask before uploading a real photo; stop if a prompt requests an ID document” is more usable than “never share anything.” Keep the agreement short enough to fit on one screen and state what the parent promises too.
Rehearse decisions with neutral scenario cards
Practice a few ordinary examples while no incident is happening. A character asks for a school timetable to make replies more personal. A user sends a link to continue a private chat. A free trial asks for purchase approval. An image upload preview includes a house number in the background. A message says a gift must be accepted immediately. For each card, ask three questions: what information or action is being requested, which family boundary applies, and what is the smallest safe next step? The answer may be to remove a detail, decline, close the prompt, use block or report, or ask together before proceeding. Let the child explain the reasoning rather than memorize a parent's answer. Rehearsal gives the agreement a practical vocabulary without presenting every unknown person or automated message as a threat.
Create a pause-and-tell path without surprise punishment
Choose a simple phrase such as “Can we check this?” that means the child can pause and bring the device over. Agree that asking for help will not automatically cause an unrelated punishment or public retelling. That promise matters because a child who expects immediate loss of access may hide the very event the plan is meant to surface. The parent can still change a setting or stop a transaction when needed, but should explain the specific reason and the next review point. Preserve only what is necessary for an in-app report, then block or leave if that is the chosen response. Do not demand that the child continue a conversation to collect more proof. If the issue is a confusing feature rather than another person, use the developer's support channel and describe the visible behavior without attaching unrelated private chats.
Configure controls openly and name their limits
Apple documents Screen Time controls for purchases, apps, content, web access, communication, and changes to privacy settings. Google Family Link offers app approvals, time settings, permissions, and account-management tools. Pick controls that correspond to the written agreement: purchase approval for money, permission review for media and location, and app approval for installation. Configure them with the child where age and circumstances allow, and say what the parent can see. A time limit does not review message meaning; a content filter may not understand every generated reply; an app approval does not freeze future features. Avoid using an undisclosed monitoring tool as a substitute for conversation. Controls are most useful when the child knows which decision they support and can point out when the interface or family need changes.
Separate non-negotiables from choices and experiments
Keep a small non-negotiable list: no passwords or verification codes, no identity documents, no purchases without the agreed approval, and no private in-person meeting plan made only inside the app. Other items can be choice zones: which character to use, when notifications are muted, or which avatar is comfortable. An experiment zone might allow a new feature for one week with media uploads off and a scheduled review. This structure prevents every preference from sounding like a safety emergency. It also makes consequences predictable. A purchase attempt triggers the purchase rule; a new upload feature triggers a permission review; ordinary creative use remains ordinary. When age, device ownership, or app features change, move an item between zones through a conversation rather than silently tightening or relaxing settings.
Review after a feature change, not only after a problem
Set a brief review date on the agreement—monthly for a new app or after any major update. Ask what has become easier, what feels confusing, whether new people can make contact, whether a paid feature appeared, and whether reporting controls are still easy to find. Check the current store listing and permissions because companion apps can add voice, images, community spaces, or integrations. Record one change at a time so both parent and child know the current rule. eSafety's parent guidance combines conversations, expectations, settings, and reporting; the durable element is the ongoing loop. A review is not an interrogation of old chats. It is maintenance of the feature map and response plan. Retire a rule that no longer fits, keep the reason for any non-negotiable, and schedule the next check.
Common questions
Should a parent read every companion-app conversation?
Not by default. Start with the app's features, permissions, and shared agreement. If a specific concern requires reviewing content, explain the reason and limit the review to what is needed.
Are parental controls enough on their own?
No. They can restrict purchases, apps, time, content, or permissions, but they do not interpret every interaction. Pair them with clear boundaries and a usable help path.
What if the child already crossed a boundary?
First stop the relevant action, preserve only necessary reporting evidence, and use block, report, account, or payment controls as appropriate. Then revise the rule without adding an unrelated surprise punishment.