https://community.signalusers.org/t/proper-secure-value-secu...
https://community.signalusers.org/t/what-contact-info-does-t...
https://community.signalusers.org/t/can-signal-please-update...
https://community.signalusers.org/t/dont-want-pin-dont-want-...
https://community.signalusers.org/t/sgx-cacheout-sgaxe-attac...
Edit: This bit is apparently not the case. And more's the pity.
====Section affected by edit=========
I can't (and wouldn't try to) speak for anyone else, but if you disable the PIN functionality[0], Signal doesn't upload the information you're talking about.
==== End section affected by edit=========
Which isn't a new change (IIUC, PIN disablement was introduced ~2 years ago). I'd say that using the PIN functionality should be opt-in rather than opt-out, so in that respect I agree.
Further, Signal should probably update their policy documents to reflect the current state of affairs.
But I stand by my previous comment[1].
[0] https://support.signal.org/hc/en-us/articles/360007059792#pi...
This is also incorrect. If you opt out of setting a pin, Signal creates a pin for you and uses that to encrypt the data it uploads to their servers. Again, not your fault. Signal has gone out of their way to avoid answering direct questions about this in a plain way.
See: https://old.reddit.com/r/signal/comments/htmzrr/psa_disablin...
This is the first I've heard of that. And if it's true, it's a big problem.
Is there any documentation of this behavior that you can direct me to?