Privacy Audit

Understand where you're vulnerable online

By Ross Zeiger

Capstone Project for PDX Code Guild

August 2021

Overview

Privacy Audit is a compilation of Open Source tools that allow users to input their information to see where they are vulnerable.

Features

Users will be walked through the Privacy Audit in this order:

1. The first feature will use the API for Have I Been Pwned. The email that user signed up with will be used to search through the API to be alerted for any data breaches their email has been involved in.
* As a user of the internet with many accounts, I want to know if any of my information has been in the data breaches I read about.
2. The second feature will use the Intelligence X API to allow the user to search for themselves in open source databases. This allows user to understand where sensitive information is available about themselves such as address, phone number, income, etc. There will be recommendations about how to remove or control this information.
* As a private citizen who wants to keep my family and property safe and anonymous, I want to know what information is available about me on the internet.
3. The third feature will use CRXcavator to check your Chrome extensions and let you know if they are safe from a privacy and security standpoint.
* As a user of many different web tools, I want to know if I can trust the ones I am using.
4. The fourth feature will be a tool to check the strength of a password. User inputs a password and receives a rating for how strong it is and recommendations for how it can be improved.
* As someone with critical information on many different sites throughout the internet, I want to know that my information is safe behind a strong password.
5. Further iterations of this project will have features to actively improve your privacy and security posture such as a random password generator, a feature to send masked emails and texts, and a library of links to resources that will further their privacy and security.

Data

Privacy Audit will have a model for each user that will store:

  • email
  • password
  • as many secondary emails, phone numbers, or aliases as they'd like to audit.

Schedule

1. August 6: Proposal submitted. Draft up layout for site. Plan how to build features.

2. August 9-10: Build the framework for the project.

3. August 11-13: Working version of Feature 1 complete.

4. August 16-18: Working version of Feature 2 complete.

5. August 19-20: Working version of Feature 3 complete.

6. August 23-24: Working version of Feature 4 complete.

7. August 25-26: Final touches. Make website attractive. Thoroughly test for bugs.

8. August 27: Present Capstone.