Jump to content

Signal cloud backups

From Consumer Rights Wiki
Revision as of 14:10, 29 August 2025 by Illerfish2 (talk | contribs) (Removed unrelated incident (source states that Signal was unable to comply with requests for user data), cleaned up source organization, tone edit)

Article Status Notice: Inappropriate Tone/Word Usage

This article needs additional work to meet the wiki's Content Guidelines and be in line with our Mission Statement for comprehensive coverage of consumer protection issues. Specifically it uses wording throughout that is non-compliant with the Editorial guidelines of this wiki.

Learn more ▼

Signal is a privacy-focused, open source encrypted messaging service. In 2020, the company was accused of collecting and storing sensitive user data on their cloud database without user consent.

Background

Signal states on their website that they can't "read your messages or listen to your calls, and no one else can either."[1]

"We’ve designed the Signal service to minimize the data we retain about Signal users, so the only information we can produce in response to a request like this is the date and time a user registered with Signal and the last date of a user’s connectivity to the Signal service. Notably, things we don’t have stored include anything about a user’s contacts (such as the contacts themselves, a hash of the contacts, any other derivative contact information), anything about a user’s groups (such as how many groups a user is in, which groups a user is in, the membership lists of a user’s groups), or any records of who a user has been communicating with."[2]

Incident

In 2019, Signal previewed a feature called "secure value recovery" which would allow users installing the app on a new device to retrieve data from cloud servers.[3] While the data is stored in Signal's cloud, it is stored in a securely encrypted manner.[4] The data collected and stored includes the user's name, photo, phone number, and a list of each Signal user that had been contacted.[5][disputed contact discovery on Signal is private and does not share the phone number as explained later in the cited sources - discuss] Messages are not saved.

Some users objected on philosophical grounds,[6][7][8][9] requesting that Signal instead provide a means to export encrypted backups that could be imported locally which would eliminate dependence on cloud-based servers. Some users also raised technical concerns about the security of the system and doubt it could sufficiently protect their data.[10] Some of these concerns were also shared by cybersecurity experts,[11][12][13] and security researchers demonstrated that the system was vulnerable to attacks, which allowed them to access the user data being stored.[14][disputed "In recent weeks, Signal has introduced more features that make it more user friendly to people who may not have extremely paranoid threat models. For example, it’s now possible to migrate all Signal data, including message history, from one phone to another, using a feature that does not rely on cloud servers and is also encrypted, according to Signal. " - discuss]

Signal's privacy policy remains unaltered from its latest version updated in 2018 and does not reflect the new cloud feature.

Signal's response

Signal began to roll out the cloud-based recovery feature in 2020 without clear communication with the public or app users about the new feature.[15][16][17][18][19][20][21] Signal users queried the need for the PIN, and communication from the team suggested it was to ensure messages were not missed or lost by keeping messages logged in a cloud format.[22] A more detailed response from Signal following user backlash explains that cloud backups were encrypted in the same way as messages, and were safe.[4] Several users requested that Signal update their policy following the change in data collection.[23][24]

References

  1. "Signal".
  2. "Grand jury subpoena for Signal user data, Eastern District of Virginia". Archived from the original on 2 Mar 2025. Retrieved 6 Mar 2025.
  3. "Technology Preview for secure value recovery". Archived from the original on 28 Dec 2024. Retrieved 6 Mar 2025.
  4. 4.0 4.1 "PSA: Disabling PINs will now upload nothing to the server". Archived from the original on 16 Jun 2023. Retrieved 6 Mar 2025.
  5. "What contact info does the Signal PIN functionality actually save". Retrieved 6 Mar 2025.
  6. "Don't want PIN, don't want anything stored in cloud". Archived from the original on 1 Mar 2024. Retrieved 6 Mar 2025.
  7. "PIN, cloud storage are showstoppers".
  8. "Forced PIN, bite it Signal".
  9. "Welcome to the cloud Signal users!".
  10. "Proper secure value security: PINs are too easy to brute force, SGX is not reliable enough". Archived from the original on 1 Mar 2024. Retrieved 6 Mar 2025.
  11. "Signal's New PIN Feature Worries Cybersecurity Experts". Archived from the original on 17 Jan 2025. Retrieved 6 Mar 2025.
  12. "Signal Going to Cloud? A Discussion with Sean O'Brien".
  13. "Does Signal's "secure value recovery" really work?".
  14. "SGX CacheOut SGAxe attack. Signal's cloud storage and contact discovery vulnerable". Archived from the original on 19 May 2023. Retrieved 6 Mar 2025.
  15. "Can someone explain this new PIN system?".
  16. "Mandatory PIN without clear explanation within the app might cause significant number of users to quit using Signal".
  17. "What exactly is Signal protecting with the mandatory PIN?".
  18. "What contact info does the Signal PIN functionality actually save?".
  19. "Following user backlash, Signal lowers one of its drastic PIN measures".
  20. "What info does Signal store about it's user?". Archived from the original on 11 Oct 2021. Retrieved 6 Mar 2025.
  21. "About data collection and data delivery". Archived from the original on 1 Feb 2025. Retrieved 6 Mar 2025.
  22. "I don't understand what the new PIN requirement is for".
  23. "Can Signal please update its Privacy Policy". Archived from the original on 19 May 2023. Retrieved 6 Mar 2025.
  24. "Signal's Terms of Use and Privacy Policy are not very user friendly". Archived from the original on 6 Mar 2025. Retrieved 6 Mar 2025.