How mrvarunkumar/numbershield works
NumberShield is a privacy command center for tracking services, consent, exposure risk, and draft privacy requests, with optional exposure discovery integrations. The principal workflow is a user viewing and managing the dashboard: the browser loads data from the FastAPI backend, which reads or updates the database layer. Discovery is a separate opt-in branch, including Gmail registration evidence and breach checks. The README contains no architectural detail, so capabilities and connections here rely on the shown source excerpts; public-web implementation details are not sampled.
Main entry points: main.py API Routes · app.js Dashboard UI · db.py Database Layer · main Public Web Search
Components 14
Dashboard
- Dashboard UI
main/frontend/app.js
Backend API
- API Routes
main.py
Privacy Management
- Service Inventory
main.py - Consent Tracking
main.py - Exposure Risk
main.py - Privacy Requests
main.py - Audit Trail
main.py
Exposure Discovery
- Discovery Runner
main.py - Gmail Evidence
main.py - Public Web Search
main - Breach Checks
main.py
Persistence
- Database Layer
db.py - Application Data
db.py
Other components
- User
Connections 13
- User → Dashboard UI: uses
main/frontend/app.js - Dashboard UI → API Routes: requests data
main/frontend/app.js - API Routes → Service Inventory: routes service APIs
main.py - API Routes → Consent Tracking: routes consent APIs
main.py - API Routes → Exposure Risk: routes exposure APIs
main.py - API Routes → Privacy Requests: routes request APIs
main.py - API Routes → Audit Trail: routes audit APIs
main.py - API Routes → Discovery Runner: routes discovery APIs
main.py - API Routes → Database Layer: calls
main.py - Discovery Runner → Gmail Evidence: queries
main.py - Discovery Runner → Breach Checks: checks
main.py - Discovery Runner → Public Web Search: searches
- Database Layer → Application Data: reads and writes
db.py