Is Keybase GDPR Compliant?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Is Keybase GDPR compliant? Keybase is a great service, and I'd hate to see it shut down by the massive fines that a company can get by violating GDPR. Even though Keybase is a U.S. based company, it can still be fined by the EU for violating GDPR if it has even a single EU citizen as a user. There is precedent in international law for enforcing judgements on foregin countries, and U.S. courts have enforced fines from foreign counties on U.S. companies before (see LICRA v. Yahoo! for a prominent example).
What policies and procedures has Keybase put into place to ensure it is GDPR compliant?
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
No files, tests, or implementation entry points are identified; begin by reviewing Keybase's published policies and procedures related to GDPR. Done would require a maintainer-backed explanation of the measures in place, rather than a code change.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100