# Pkg.jl telemetry should be opt-in

**URL:** <https://discourse.julialang.org/t/pkg-jl-telemetry-should-be-opt-in/42209>\
**Category:** Internals & Design\
**Created:** [June 28, 2020, 9:11pm UTC](https://discourse.julialang.org/t/pkg-jl-telemetry-should-be-opt-in/42209 "2020-06-28T21:11:37Z")\
**Posts on this page:** 1\
**Showing post:** 288

<div class="post-metadata">

**Author:** ![heliosdrm](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/heliosdrm/32/3851_2.png) [@heliosdrm](https://discourse.julialang.org/u/heliosdrm)\
**Post date:** [July 6, 2020, 5:09pm UTC](https://discourse.julialang.org/t/pkg-jl-telemetry-should-be-opt-in/42209/288 "2020-07-06T17:09:23Z")

</div>

> [@heliosdrm](#):
>
> Re-reading the section about data access, analysis and retention, I have noticed that it should also mention that there will be means for users to request the deletion of their data

I retract that statement: even if using a client uuid implies a potential risk of de-anonymization, that would not mean at all that the data controllers would be able to identify me - or verify my claim of being the user associated to some uuid. In such a situation, a minimal data retention policy like the one presented in the legal notice looks like a reasonable method to ensure the user’s right to data erasure.

With respect to data portability, a local copy of the submitted records might be a solution, as proposed in [this issue](https://github.com/JuliaLang/Pkg.jl/issues/1905).

---

_[View the full topic](https://discourse.julialang.org/t/pkg-jl-telemetry-should-be-opt-in/42209)._