Privacy of Electron
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
How does Keybase protect users from Google seeing as it is based on Electron (libchromium)?
What safeguards are in place to make sure Chromium does not leak user data to Google (IP, crashreports, API calls etc etc)?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points; it asks generally how Electron and Chromium protect users from Google. Start by locating the Electron application's privacy, telemetry, crash-reporting, and network configuration, then document the safeguards and any remaining data paths. Done means a repository-backed explanation addressing IP, crash reports, and API calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron
- Domain
- desktop, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100