Inspiration
We often tell children to stay safe online, but how often do we explain why? Cookies, website permissions, and browser extensions influence our online experience, yet these concepts can be difficult for younger users to understand.
I built WebWise to bridge this gap between being warned about online risks and actually understanding them. My goal was to make browser privacy approachable and turn online safety from a list of rules into a skill children can practise.
What it does
WebWise is a child-friendly browser extension that helps younger users understand browser privacy and develop safer internet habits through an approachable, interactive interface.
Its main features include:
- Cookie Detective: Explains accessible cookie information and security attributes such as
Secure,HttpOnly, andSameSitein understandable language. - Website X-Ray and Permission Guide: Helps users understand website permissions and what those permissions may allow.
- Extension Inspector: Makes browser extension permissions easier to understand, helping users learn about the capabilities extensions may have.
- Safety Coach: Presents interactive, multiple-choice scenarios about online safety. Users choose how they would respond and receive feedback explaining the reasoning behind safer decisions.
- Website Overview: Brings relevant browser and website information into an accessible experience.
Rather than simply flagging things as dangerous, I designed WebWise to help users understand what they are seeing and make more informed decisions.
How we built it
I built WebWise by combining browser-extension functionality with a deliberately friendly, stylised user interface. My aim was to make the experience approachable for children without losing sight of the technical concepts behind browser privacy.
The project brings together browser information, educational explanations, and interactive decision-making. The Safety Coach uses scenario-based questions and feedback to help users practise applying online safety concepts, while the inspection features make browser-related information easier to explore.
A key design principle was to explain capabilities rather than make unsupported assumptions. For example, a permission indicates what a website or extension may be allowed to do, not necessarily what it is actually doing.
Challenges we ran into
One of my central challenges was simplifying technical concepts without making the explanations misleading. Browser permissions, cookie attributes, and extension capabilities are not always straightforward, especially when explaining them to younger users.
Another challenge was balancing information with usability. A tool filled with technical details could overwhelm its intended audience, while oversimplifying those details could create a false sense of security.
I designed the interface and educational approach to make information easier to understand while preserving important distinctions between what the browser exposes, what a permission allows, and what can actually be verified.
Accomplishments that we're proud of
I'm proud to have built WebWise as a working browser extension with multiple complementary features rather than a standalone awareness page.
The Safety Coach is especially important to my project because it moves beyond passive explanations. Its interactive scenarios encourage users to think through online situations, make decisions, and learn from feedback.
I'm also proud of the child-friendly visual design. I wanted to make a technical subject feel approachable without treating its users as incapable of understanding it.
Most importantly, WebWise connects browser transparency with practical learning: understanding online safety is not just about knowing the rules, but knowing how to apply them.
What we learned
Building WebWise strengthened my understanding of browser security concepts, extension development, user-interface design, and educational experience design.
I learned that presenting information is only part of the solution. The way information is explained, the context in which it appears, and the opportunities users have to practise making decisions all matter.
I also recognised the importance of communicating technical limitations honestly. A responsible privacy tool should help users understand what is known, what a permission means, and what cannot be confidently inferred from the available information.
What's next for WebWise
My next steps are to strengthen testing, refine explanations based on feedback, improve documentation, and prepare WebWise for a potential public release through the Chrome Web Store.
I also want to explore how the learning experience could be expanded with more real-world scenarios and clearer explanations of emerging online risks, while keeping the interface accessible to younger users.
My long-term vision is to make WebWise a practical learning companion that helps children become more informed, confident, and responsible internet users.
WebWise: Understand the web. Browse with confidence.
Log in or sign up for Devpost to join the conversation.