Avoid this
- Starting the consumer app privacy audit before understanding everyday users deciding whether and how to use a popular app
- Treating assumptions or internet opinions as real evidence
- Choosing a scope too large to test and finish with care
High school project idea · Technology & AI
Follow what one app asks for, collects, shares, stores, and leaves unclear before tapping “Allow.”
Conduct a responsible privacy review using public policies, visible permissions, data flows, and user expectations without attempting unauthorized access.
Why this project matters
Conduct a responsible privacy review using public policies, visible permissions, data flows, and user expectations without attempting unauthorized access. This project feels different from a school assignment because the student serves everyday users deciding whether and how to use a popular app, creates something visible, tests it honestly, responds to feedback, and explains the decisions behind the final result.
What you will create
Use these deliverables as milestones for Audit an App’s Privacy Trail. Adapt the details to your interests, available time, and real-world opportunities.
Research permissions, account data, device data, third parties, retention, deletion, children and teen terms, security claims, dark patterns, and user expectations. Document the needs, constraints, credible sources, and perspectives of everyday users deciding whether and how to use a popular app.
Turn the evidence into a focused plan for the consumer app privacy audit, including success criteria, ethical boundaries, scope, and a realistic path to completion.
Create the first complete version of the consumer app privacy audit. Include an app and use-case scope, permission inventory, policy annotations, data-flow map, expectation survey, risk matrix, user settings guide, and improvement proposal.
ask users what data flows they expect before seeing the map, compare expectations with documented practices, and have an informed reviewer audit claims Record what happened, what failed, what users or reviewers said, and which changes you made.
Publish the final consumer app privacy audit with a portfolio-ready case study showing the challenge, evidence, process, revisions, results, limits, and next version.
Make the work stronger
For Audit an App’s Privacy Trail, use these checkpoints to protect the quality of the work without turning the project into a performance for admissions.
Skills you can build
College application value
Can demonstrate initiative, curiosity, reflection, and growth through the student’s choices, response to setbacks, work with everyday users deciding whether and how to use a popular app, and development of Privacy Analysis, Policy Reading, and Threat Modeling.
The goal of Audit an App’s Privacy Trail is not to manufacture an impressive activity. Do real work, keep evidence of the process, and reflect honestly on what changed.
Related college majors
Use Audit an App’s Privacy Trail as a clue, then open a related major guide to compare coursework, career directions, reality checks, and other ways to test the field.
Learn to think like both a defender and an attacker while protecting systems, identities, networks, and information people depend on.
Keep the technology people depend on secure, connected, and useful.
Explore Bitcoin through the disciplines that actually power it: computer science, cryptography, networks, economics, incentives, and financial infrastructure.
Audit an App’s Privacy Trail is an original Compass educational starting point designed around real work, visible evidence, feedback, and reflection. It is not an admissions guarantee.