> When you send a message, the Signal service temporarily queues that message for delivery. As soon as your message is delivered, that small bundle of encrypted data (i.e. your message) can be dropped from the queue. The storage of end-to-end encrypted files is temporary too, and any undelivered end-to-end encrypted data is automatically purged after a period of inactivity. Even though everything is only temporary, this storage still costs Signal around $1.3 million dollars per year.
I assume they're probably speaking honestly, and have no reason to investigate (since I don't use it). But if you were doing a critical analysis, I guess you could consider that, for $1.3M/year, one could also store a lot of "metadata" for later traffic analysis, social network mapping, propagation tracking, etc. It'd be tickling to think that fact could be hiding in plain sight the whole time, in invoices and accounting disclosures.
> When you send a message, the Signal service temporarily queues that message for delivery. As soon as your message is delivered, that small bundle of encrypted data (i.e. your message) can be dropped from the queue. The storage of end-to-end encrypted files is temporary too, and any undelivered end-to-end encrypted data is automatically purged after a period of inactivity. Even though everything is only temporary, this storage still costs Signal around $1.3 million dollars per year.
I assume they're probably speaking honestly, and have no reason to investigate (since I don't use it). But if you were doing a critical analysis, I guess you could consider that, for $1.3M/year, one could also store a lot of "metadata" for later traffic analysis, social network mapping, propagation tracking, etc. It'd be tickling to think that fact could be hiding in plain sight the whole time, in invoices and accounting disclosures.