MetaMask / MetaMask/metamask-extension
Data Audit Sentry Platform
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
Copied from [mobile](https://github.com/MetaMask/mobile-planning/issues/509)
## Description
Review the current Sentry platform configuration for current logging behavior. Look for potential PII information.
## Technical Details
- Review current Sentry logs for any information that could be used to identify a person if aggregated within Sentry
- Need to check JS and confirm that levels the logging is turned off
- Suggest using Proxyman to watch network traffic as a way to confirm
## Acceptance Criteria
- No data is logged when user opts-out verify with Proxyman
- No Sentry data cannot be combine with other Sentry data to identify someone (i.e. device id and logged out data)
- Remove any identifiable fields in Sentry if something has been discovered
## References
- PII Definition: https://docs.sentry.io/product/security/mobile-privacy/#does-that-data-include-any-personally-identifiable-information-pii
Contributor guide
Research direction
The issue names no files or tests; start by reviewing the current Sentry platform configuration and JavaScript logging behavior. Use Proxyman to inspect network traffic and verify opt-out behavior, then check whether Sentry data can identify someone when combined and remove any identifiable fields found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100