Description
Given the breadth of localStorage-backed features described across the project (wallet preference, bookmarks, notification read-state, onboarding completion, filter preferences), an audit is needed confirming nothing sensitive (partial transaction data, email addresses from the reminder opt-in, evidence text from disputes) is ever persisted to localStorage, which is readable by any script on the origin and persists indefinitely.
Requirements and context
- Grep all
localStorage.setItem call sites
- Classify each by data sensitivity
- Fix or flag any storing genuinely sensitive data (recommend moving anything sensitive server-side or at minimum documenting the accepted risk with maintainer sign-off)
Suggested execution
git checkout -b fix/audit-localstorage-sensitive-data
- Audit all localStorage usage sites
- Fix or document flagged sensitive-data storage
Example commit message
fix: audit and remediate sensitive data stored in localStorage
Description
Given the breadth of localStorage-backed features described across the project (wallet preference, bookmarks, notification read-state, onboarding completion, filter preferences), an audit is needed confirming nothing sensitive (partial transaction data, email addresses from the reminder opt-in, evidence text from disputes) is ever persisted to localStorage, which is readable by any script on the origin and persists indefinitely.
Requirements and context
localStorage.setItemcall sitesSuggested execution
Example commit message
fix: audit and remediate sensitive data stored in localStorage