Este contenido no está disponible en español.

Archiving chats

If your company requires that chats are stored externally for auditing or reporting purposes, you can ask users to export chats.

Due to the end-to-end encryption, it’s not possible to create transcripts using the management cockpit or the API.

Artículos relacionados

Threema is trusted by millions and known for its unparalleled security and privacy protection. No other messenger offers a comparable level of security, metadata restraint, and confidentiality.

  • Top-grade end-to-end encryption of the entire communication.
  • Strong encryption on users’ devices: Chats and messages are stored with strong encryption on the device.
  • Decentralized handling: No central storage of personal data.
  • Company-owned hardware in Switzerland: Threema GmbH runs its own servers in data centers of an ISO 27001-certified collocation partner.

Details about the encryption, key-pair management, physical data security, data protection laws, and other security advantages of our decentralized architecture are summarized in the Security and Privacy Reference Sheet.

The Threema Work apps are open source, and the Cryptography Whitepaper contains comprehensive information about Threema’s technical architecture. Furthermore, external experts audit Threema on a regular basis.

Compare Threema Work with other business communication-tools in our comprehensive business-messenger comparison, and have a look at the in-depth comparison of Threema and WhatsApp.

We don’t require a data-processing agreement, but we provide a standard agreement. Individual agreements are not possible.

App users can retrieve the information listed below at any time (by following the instructions listed in this FAQ article).

Details about the Threema ID

  • Public key
  • Date of creation
  • Hash of the linked phone number
  • Hash of the linked email address
  • Presence of a revocation password (yes/no)
  • Nickname

App details

  • Date of the last licence check
  • Version number and language
  • Bitmask of features supported by the version in use
  • Push token of the service in use (GCM/FCM, APNS)
  • Name of the chosen sound file for push messages

Values of the following MDM parameters

  • th_firstname
  • th_lastname
  • th_category
  • th_csi
  • th_nickname

Mostrar todas las preguntas frecuentes

Mostrar todas las preguntas frecuentes