B
SNS Privacy Exposure Analyzer
2.95
Derivation Chain
Step 1
LLM-powered large-scale de-anonymization technology
→
Step 2
Unintentional personal information exposure risk on social media
→
Step 3
Comprehensive privacy score calculation from SNS posts
Problem
Active social media users in their 20s-30s (working professionals posting on Instagram, Twitter, and blogs) are unaware that LLM-based aggregate analysis of their public posts can infer their residential area, workplace, commute route, family relationships, and income level. While individual posts appear harmless, collective analysis of hundreds of posts can build an identity-level profile. This increases the risk of stalking, phishing, and social engineering attacks, yet no self-assessment tool exists.
Solution
(1) Analyze user's public SNS accounts (Instagram, Twitter, blogs) and generate a Report of inferable personal information (residence, workplace, family, schedule patterns, etc.), (2) Display risk scores per category and show 'which posts contributed to this inference,' (3) Recommend deletion or privacy setting changes for high-risk posts.
NUMR-V Scores
NUMR-V Scoring System
| N Novelty | 1-5 | How uncommon the service is in market context. |
| U Urgency | 1-5 | How urgently users need this problem solved now. |
| M Market | 1-5 | Market size and growth potential from proxy indicators. |
| R Realizability | 1-5 | Buildability for a small team with realistic constraints. |
| V Validation | 1-5 | Validation signal quality from competition and demand data. |
SaaS N=.15 U=.20 M=.15 R=.30 V=.20
Senior N=.25 U=.25 M=.05 R=.30 V=.15
Feasibility (69%)
Data Availability
19.4/25
Feasibility Breakdown
| Tech Complexity | / 40 | Difficulty of core implementation stack. |
| Data Availability | / 25 | Practical availability and cost of required data. |
| MVP Timeline | / 20 | Expected time to ship a usable MVP. |
| API Bonus | / 15 | Bonus for viable public API leverage. |
Market Validation (50/100)
Validation Breakdown
| Competition | / 20 | Signal quality from competitor landscape. |
| Market Demand | / 20 | Demand proxies from search and mention patterns. |
| Timing | / 20 | Fit with current shifts in tech, behavior, and regulation. |
| Revenue Signals | / 15 | Reference evidence for monetization viability. |
| Pick-Axe Fit | / 15 | How well the concept serves participants in a trend. |
| Solo Buildability | / 10 | Practicality for lean-team implementation. |
Technical Requirements
AI/ML [medium]
Backend [medium]
Frontend [low]