How priyasmit-work/consent-shield works
ConsentShield scans a submitted site’s consent banner and policy evidence, analyzes privacy risks, proposes a protection plan, and presents findings in its frontend. Automatic execution is gated by saved user preferences and can be declined; the documented live mode may click a matching banner action. The graph also preserves preferences and scan-event capabilities. Several service implementations were not excerpted, so their documented relationships are cited to the README; links without direct source evidence are omitted.
Main entry points: browser_agent.py Scan orchestrator · screens.tsx ConsentShield screens · execution.py Apply-plan route · scans.py Scan routes
Components 20
User interface
- ConsentShield screens
frontend/src/components/cs/screens.tsx - API client
frontend/src/lib/consentshield/api.ts
API and preferences
- Scan routes
backend/backend/app/api/v1/routes/scans.py - Preferences routes
backend/backend/app/api/v1/routes/preferences.py - Event routes
backend/backend/app/api/v1/routes/events.py
Scan analysis
- Scan orchestrator
backend/backend/app/services/browser_agent.py - Banner detection
backend/backend/app/services/cookie_detector.py - Policy finding
backend/backend/app/services/policy_finder.py - Privacy analysis
backend/backend/app/services/privacy_analyzer.py - Model adapter
backend/backend/app/services/model_service.py
Protection execution
- Apply-plan route
backend/backend/app/api/v1/routes/execution.py - Plan generation
backend/backend/app/services/protection_planner.py - Browser automation
backend/backend/app/services/agent_browser.py
Persistence
- Scans repository
backend/backend/app/repositories/scans_repository.py - Preferences repository
backend/backend/app/repositories/preferences_repository.py - Events repository
backend/backend/app/repositories/events_repository.py - Supabase storage
backend/backend/app/repositories/supabase_client.py
Other components
- User
- webcmd browser
- LLM provider
Connections 23
- User → ConsentShield screens: submits URL
README.md - ConsentShield screens → API client: requests data
README.md - API client → Scan routes: calls API
README.md - Scan routes → Scan orchestrator: starts scan
backend/backend/app/api/v1/routes/scans.py - Scan orchestrator → Banner detection: parses banner
README.md - Scan orchestrator → Policy finding: finds policies
README.md - Scan orchestrator → Privacy analysis: analyzes evidence
README.md - Privacy analysis → Model adapter: classifies evidence
backend/backend/app/dependencies.py - Model adapter → LLM provider: requests analysis
backend/backend/app/services/model_service.py - Scan orchestrator → webcmd browser: scans live site
README.md - Scan orchestrator → Plan generation: builds plan
backend/backend/app/dependencies.py - Scan routes → Scans repository: stores scan
backend/backend/app/api/v1/routes/scans.py - Scans repository → Supabase storage: persists records
backend/backend/app/repositories/scans_repository.py - Preferences routes → Preferences repository: reads or updates
backend/backend/app/api/v1/routes/preferences.py - Preferences repository → Supabase storage: persists preferences
backend/backend/app/repositories/preferences_repository.py - Event routes → Events repository: records events
backend/backend/app/api/v1/routes/events.py - Events repository → Supabase storage: persists events
backend/backend/app/repositories/events_repository.py - Apply-plan route → Scans repository: loads scan
backend/backend/app/api/v1/routes/execution.py - Apply-plan route → Preferences repository: checks preferences
backend/backend/app/api/v1/routes/execution.py - Apply-plan route → Browser automation: clicks action
backend/backend/app/api/v1/routes/execution.py - Browser automation → webcmd browser: drives browser
README.md - ConsentShield screens → Preferences routes: manages preferences
README.md - ConsentShield screens → Event routes: fetches events
README.md