User interface collects incident details in a structured way.
Case Study2025
Cyber Harassment Reporting Assistant
A cybersecurity product concept for documenting suspicious calls and preparing safer reporting workflows.
A cybersecurity product concept for helping users document suspicious calls, classify risk, and prepare structured reporting workflows with privacy and safety boundaries.
Problem
What this project solves
People facing suspicious calls or online harassment often do not know how to document what happened clearly or what information matters.
Solution
How I approached it
The assistant guides the user through incident capture, risk classification, and structured report generation while respecting privacy and safety constraints.
Architecture
System structure
Classification layer identifies urgency and risk signals.
Report generator converts details into organized documentation.
Storage rules define deletion, privacy, and access boundaries.
Decisions
Tradeoffs and outcomes
Privacy boundaries before automation
Tradeoff: A reporting assistant could help users document incidents, but it can also create risk if it stores sensitive call data carelessly.
Outcome: Framed the system around documentation, risk classification, and structured reporting with explicit privacy and safety boundaries.
Assistance, not legal replacement
Tradeoff: Automating reports can reduce friction, but the tool should not pretend to replace authorities, emergency services, or legal advice.
Outcome: Kept the concept positioned as workflow support that helps users organize information before escalation.
Structured evidence over free-form notes
Tradeoff: Free-form notes are easy to collect, but they are harder to review, classify, and turn into a useful report.
Outcome: Designed the concept around structured incident fields, risk labels, summaries, and report-ready outputs.
Proof
Evidence and impact
This case study shows cybersecurity product thinking, safety-aware UX, and practical reporting workflow design.
Incident collection flow concept
Risk classification model direction
Structured report generation idea
Privacy-aware system boundaries
Roadmap
Next iteration
Prototype the report flow.
Define ethical and legal boundaries.
Create architecture diagrams and sample outputs.