MetaMask / MetaMask/metamask-extension

Data Audit MixPanel

Open
#16,808 0 comments 0 reactions 0 assignees View on GitHub
area-metrics area-privacy team-extension-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/510)

## Description
Review the current MixPanel platform configuration for current logging behavior. Look for potential PII information.

## Technical Details

- Review current MixPanel data for any information that could be used to identify a person if aggregated within MixPanel
- Need to check JS and confirm that levels the logging is turned off
- Suggest using Proxyman (or other proxy) to watch network traffic as a way to confirm
-

## Acceptance Criteria

- No data is logged when user opts-out verify with Proxyman
- No MixPanel data cannot be combine with other MixPanel data to identify someone (i.e. device id and logged out data)
- Remove any identifiable fields in MixPanel if something has been discovered

## References

- PII Reference: https://help.mixpanel.com/hc/en-us/articles/360000679006-Managing-Personal-Information

Contributor guide

Open the contributing guide

Research direction

Review the current MixPanel platform configuration and JavaScript logging behavior first. Use Proxyman or another proxy to verify that opt-out prevents MixPanel traffic, then inspect the captured data for PII or combinations that could identify a person. Done means no opt-out data is sent and any identifiable MixPanel fields are removed.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, typescript
Domain
analytics, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.