Illustrated with AICybersecurity for Juniors · Book 1 · Chapter 3
The Game That Asked for Too Much
Part 1. Just to unlock the fun level
Happy had been begging to play Zoom Dash for a week. Every single kid in Class 4 was talking about it, the one where you race a little cart down a mountain and collect stars. Bunny finally handed over his tablet, mostly to get some peace.
The game installed in a blink, and then a screen popped up asking for permission to use Happy's contacts, his camera, his microphone, his location, and his photos, all at once, with one giant friendly button at the bottom that said Allow All.
Happy did not read a single word of it. He tapped Allow All the way he'd tap anything standing between him and the fun level, and the game roared to life.
Part 2. Bunny notices
Illustrated with AIBunny, a slim 13-year-old who noticed things, wandered back in and glanced at the tablet over Happy's shoulder. "Wait," he said. "Why does a racing game need your camera? You're not even taking a photo in it."
Happy shrugged. "It just asked. I said yes so I could play."
"It also wanted your contacts," said Bunny, scrolling through the settings. "And your microphone. For a game about driving down a mountain."
Part 3. What Allow All actually did
Illustrated with AITwo things happened before dinner. First, Riya's phone buzzed with a message Happy never meant to send. "Hiiii I am also playing Zoom Dash come join meeee," followed by a download link, sent to every single number in Bunny's contacts, including Riya's grandmother and a pizza delivery place saved from last year.
"Did you send me this?" Riya called out from the next flat, holding up her phone.
Then, right as Happy reached the fun level, a bright screen appeared asking if he'd like 999 Zoom Gems for a "special price", with a thumb already hovering helpfully over the Buy button, right next to a saved card that belonged to Bunny's mother.
Happy's thumb was halfway to tapping it when Bunny snatched the tablet away. "That's not pretend money," he said. "That's real money. Mummy's money."
Part 4. Turning permissions off
Bunny opened the phone's settings and found Zoom Dash's permission list. He switched off contacts, camera, microphone, and location, one by one, leaving only the storage permission the game actually needed to save Happy's progress.
The game still worked perfectly. The cart still raced down the mountain. Nothing about the actual game had changed at all.
"See," said Bunny. "It never needed any of that. It just asked, because most people say yes without checking."
Part 5. Nilu chachu's rule
Illustrated with AINilu chachu had dropped by to return a tiffin box, and ended up staying for this instead. He listened to the whole story, nodding along, and then said something Happy wrote down in his notebook to remember.
"Before you tap Allow," chachu said, "ask one simple question: does this app actually need this to do what it promised me? A racing game needs to save your progress, so storage makes sense. It does not need your camera, your contacts, or your microphone to draw a road and a cart. When an app asks for more than its job needs, that has a name. It's called permission creep, and it's usually there because your information is worth something to someone, even if the game itself is free."
"And the Allow All button?" asked Bunny.
"That's a dark pattern," said chachu. "A button made big and friendly on purpose, so you tap it without reading, while the option to say no is small and easy to miss. You can always say no to one thing and yes to another. You almost never have to pick all or nothing."
Part 6. Checking every app
That evening, Bunny, Happy, and Riya went through every app on the tablet together, reading each permission out loud and deciding, one at a time, whether it made sense. A weather app asking for location made sense. A calculator app asking for contacts did not, and it lost that permission on the spot.
Happy, now rather proud of himself, announced that he was going to check his mother's phone next, which made everyone laugh and made his mother lock her phone a little faster than usual.
Part 7. Mitthu asks permission
Illustrated with AILater, Mitthu hopped onto the table, spread his wings with enormous drama, and fixed Happy with one bright eye.
"Permission," he announced, "to access one biscuit."
Happy laughed so hard he nearly fell off his chair. "Request denied," he said. "You don't need the whole biscuit to do your job, Mitthu. Half is enough."
Mitthu considered this for a moment, decided it was an acceptable deal, and happily accepted half a biscuit, which, everyone agreed, was exactly the right amount of permission to grant.
Moral of the story
A good app only asks for what it actually needs to do its job. Before you tap Allow, ask why, and remember that you can almost always say yes to one thing and no to another.
A cart that races down a hill
needs no ear, no eye, no will
to read your friends or watch your face.
Ask it why, before you race.
Spot the red flags
Zoom Dash Wants Permission
Zoom Dash would like to access: 5
Allow All 4
Not now
Contacts, with a reason that sounds friendly but isn't required to play a racing game at all.
Camera access, with no camera feature anywhere in the game.
Microphone access, for a game with no voice chat or sound recording of any kind.
One giant, friendly "Allow All" button, built to be tapped without reading, while "Not now" is tiny underneath.
Five permissions requested at once, with no explanation anywhere for why each one is needed.
Mitthu's notebook
What really happened?
| In the story | The real idea |
|---|---|
| Zoom Dash asking for five permissions at once | Permission creep: an app requesting more access than its actual job requires |
| The huge "Allow All" button next to a tiny "Not now" | A dark pattern: a design built on purpose to push you toward one choice |
| An invite message sent to Riya's grandmother and a pizza place | What the contacts permission actually let the app do, without Happy realising |
| "999 Zoom Gems" with a saved card ready to tap | An in-app purchase: real money, disguised as game currency |
| Turning off camera, microphone, contacts, and location, keeping only storage | Least privilege: giving an app only what it truly needs, nothing more |
| Checking every app's permissions together that evening | A permission can be reviewed and changed anytime, not just at install |
Try it yourself
Does this app really need it?
Here are six apps, each asking for one permission. Decide: does the permission make sense for what the app does, or is it a red flag?
Maths corner
How small taps turn into big money
Suppose a pack of 100 Zoom Gems costs Rs 80. If a child buys a pack almost every day without telling a parent, how much is spent in one week of 7 days?
Rs 80 × 7 = Rs 560 in a single week.
Your turn. At that same rate, roughly how much would be spent in a 30-day month?
Answer: Rs 80 × 30 = Rs 2,400 in a month, all from gems that disappear the moment you close the game. This is exactly why in-app purchases should always go through a parent, and why a sudden pile of small, forgettable taps can add up to a very real amount.
Try it on a computer · optional
A tiny permission checker in Python
# a simplified idea of how an app reviewer might think about this needed = { "racing game": ["storage"], "video call app": ["camera", "microphone", "contacts"], "weather app": ["location"], } def check(app_type, permission): if permission in needed.get(app_type, []): return "Makes sense" return "Red flag, ask why" print(check("racing game", "camera")) print(check("weather app", "location"))
Red flag, ask why
Makes sense
Run this in any free online Python editor, and try adding your own app types and permissions to the dictionary. Real app reviewers at app stores do something similar on a much bigger scale, comparing what an app asks for against what it actually claims to do.
Security tip
One question before every "Allow"
Before tapping Allow on any permission, ask yourself: does this app need this to do the one job it promised me? If the answer isn't obviously yes, say no. You can almost always change your mind later in the phone's settings if a feature genuinely needs it. And never tap a payment button inside a game or app without checking with a parent first, gems and coins and stars are just a costume for real money.
Did you know?
Fun facts
Myth or fact?
"If I don't tap Allow on everything, the app just won't let me play at all."
MythMost apps work perfectly well with only the permissions they truly need. Zoom Dash kept working exactly the same after Bunny switched off contacts, camera, microphone, and location, it only ever needed storage to save Happy's progress.
Try this · no computer needed
Permission court
You need: a small group, and index cards or slips of paper, each listing one app and one permission it's asking for (a few real, a few made up to be unnecessary).
- One person plays "the app", picking a card and loudly announcing the permission it wants, with a made-up reason, convincing or silly.
- The rest of the group are judges. They ask: does this app really need this to do its job?
- Judges vote: Allow, or Deny. Discuss out loud why.
- Take turns being the app, and try to invent the trickiest, most unnecessary permission request you can. Can the judges always catch it?
Careers corner
App reviewer / privacy engineer
Before an app reaches an app store, someone often checks whether the permissions it asks for actually match what it claims to do. A privacy engineer helps a company build apps that only collect what they genuinely need, and an app reviewer checks that promise before millions of people start downloading it.
Useful to learn: reading carefully and questioning claims, understanding how apps are built, caring about fairness to the people using the app, and explaining a concern clearly to a team that wants to ship fast.
Quiz time
How well did you learn?
Think and discuss
No wrong answers here
- Why might a simple flashlight app want access to your contacts list? What could it do with that, that you might not want?
- Happy almost spent real money without realising it was real. How could an app make that clearer, if it wanted to?
- When an app asks for a permission that seems unnecessary, what's one simple question you can ask yourself before tapping Allow?
- Who do you think should decide whether in-app purchases are allowed on a child's device, the child or a parent? Why?
Be curious
Ask a teacher, parent or engineer
Word bank
New words from this chapter
Coming up in Chapter 4
Riya keeps a diary app on her phone, full of her thoughts, her photos, and her plans. One day she realises she never checked who else can see it. How much of our life do we accidentally leave unlocked for anyone to find?
For teachers and parents: this chapter fits two 40-minute periods. Period 1: read Parts 1 to 7 aloud (15 min), the "Spot the red flags" permission panel together (10 min), then the Maths corner (10 min). Period 2: the "Does this app really need it?" interactive, the permission court activity, and the quiz. The key ideas: permissions should match what an app actually does; "Allow All" buttons are often a dark pattern, not a requirement; permissions can be reviewed and changed anytime in settings; and in-app purchases are real money that should always involve a parent. The Python corner is optional. All chapter illustrations are AI-generated scene art; the permission panel and game were built by hand.