AWS Security ChangesHomeSearch

AWS wickr: Document persisting data retention bot identity and encryption keys

Service: wickr · 2026-10-23 · Documentation medium

File: wickr/latest/adminguide/starting-data-retention-bot.md · Type: encryption

Summary

Adds guidance that the bot stores its device identity and encryption keys in the host folder mounted with -v, that this folder must be on durable storage and reused across restarts/upgrades, and an Important warning that starting without it registers a new device with new keys and breaks decryption of previously encrypted data.

Security assessment

The change documents handling of the bot's device identity and encryption keys, warning that losing the mounted folder causes re-registration with new keys and loss of access to previously encrypted data. This is key-management/hardening guidance with security impact, not a fix for a specific vulnerability.

Evidence

+The data retention bot stores its device identity and encryption keys in the folder that you mount with the `-v` option in the run command (for example, `-v /opt/`compliance_1234567890_bot`:/tmp/`compliance_1234567890_bot``). The bot uses this data to log in as the same device every time it starts. Make sure that the mounted host folder:

Diff

diff --git a/wickr/latest/adminguide/starting-data-retention-bot.md b/wickr/latest/adminguide/starting-data-retention-bot.md
index 0f86d51..99335f8 100644
--- a//wickr/latest/adminguide/starting-data-retention-bot.md
+++ b//wickr/latest/adminguide/starting-data-retention-bot.md
@@ -38,0 +39,17 @@ The following sections show example commands to run the data retention bot Docke
+**Persist bot data across restarts**
+
+The data retention bot stores its device identity and encryption keys in the folder that you mount with the `-v` option in the run command (for example, `-v /opt/`compliance_1234567890_bot`:/tmp/`compliance_1234567890_bot``). The bot uses this data to log in as the same device every time it starts. Make sure that the mounted host folder:
+
+  * Is included in the run command every time you start the bot, with the same host folder and path.
+
+  * Is on durable storage, such as the instance's Amazon EBS volume, and not on temporary storage.
+
+  * Is kept when you restart, upgrade, or replace the container.
+
+
+
+
+###### Important
+
+If you start the bot without this folder (for example, by running `docker run` without the `-v` option, or after deleting the host folder), the bot registers as a new device with new encryption keys. Messages sent to the previous device are not delivered to the new device, and the new device cannot decrypt data that was encrypted with the previous device's keys.
+