B
Used Phone Data Erasure Certificate
2.65
Derivation Chain
Step 1
Increasing smartphone setup complexity
→
Step 2
Expansion of the used phone market
→
Step 3
Data erasure trust issues between used phone sellers and buyers
→
Step 4
Service that provides third-party certification of data erasure completion
Problem
Used phone buyers (e.g., Mint, Secuware, etc.) process about 8 million units annually, but cannot prove that the previous owner's data has been completely erased, leading to persistent consumer trust issues. Sellers worry whether a factory reset is sufficient, and buyers face legal liability (up to 50 million KRW in fines for violating the Personal Information Protection Act) in case of data leakage. Currently, erasure verification relies on manual sample checks, making full certification impossible.
Solution
A B2B SaaS that automatically records the data erasure process for used phones and issues blockchain-based certificates. (1) Automatically logs the erasure method, scope, and timestamp during the erasure process, (2) records a third-party certified hash on the blockchain after erasure completion, then issues a QR code certificate, (3) allows buyers to verify the erasure history by scanning the QR code.
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. |
N=.15 U=.20 M=.15 R=.30 V=.20
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 (56/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
Backend [medium]
Infrastructure [medium]
Frontend [low]