Repository navigation
|
How can a team catch Unencrypted sensitive personal data stored in localStorage automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rn 'localStorage.setItem\|localStorage' --include='*.js' --include='*.ts' --include='*.html' . && ! grep -rn 'encryptedStorage\|encryptToken\|consentLocalStorage\|clearLocalStorage' .Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. Storing sensitive details or JWT tokens in plain text in localStorage without encryption or user consent check. The fix. Avoid storing plain sensitive personal info in localStorage, encrypt any stored tokens, and respect storage preferences. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
WEB-LOCAL-STORAGEwith a coverage line and a proper exit code.What the hit means. Storing sensitive details or JWT tokens in plain text in localStorage without encryption or user consent check.
The fix. …