liquidvotingio / liquidvotingio/api
Anonymizing emails in traces
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 17
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
On https://github.com/liquidvotingio/api/pull/215#issuecomment-801209450 @jinjagit brought up:
> Should we ignore (not observe) sensitive vars (e.g. emails)? Or do we consider Honeycomb (and communication with it) secure?
We should anonymize them, so we're not able to see and not storing them in an external data store. This is both secure and compliant with GDPR.
We need to see what people have been using for this, with Phoenix
Contributor guide
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
Review the trace instrumentation and Phoenix integration referenced in the issue, including how data is sent to Honeycomb. Identify where email values enter the trace payload and determine an anonymization approach. Done means emails are no longer visible or stored in the external trace data store while preserving useful traces and GDPR compliance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- observability-sre, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100