Messengers and address books: Manage business contacts deliberately
Message encryption does not settle contact synchronisation. Data types, legal basis and device settings need separate examination.
Revisión editorial:
El texto de este artículo está disponible en inglés en esta versión del sitio.
Contexto y fuentes
Processing contact details requires an appropriate purpose and basis; consent is not the only possible basis. Technical and organisational measures must match the risk. [1], [2] Assess which contacts are actually transmitted separately from how message content is encrypted.
Alcance y límites
There is no universal answer for every service and recipient. Actual functions, conditions and data flows matter.
Explicación sencilla
A sealed message and a separately processed address directory are different operations. Both need to be understood.
Recomendaciones prácticas
We recommend separating business and personal contacts where appropriate, checking app permissions and service terms, and defining approved channels by data type. Device management can support these decisions but cannot replace them. Recheck permissions and synchronisation after relevant updates.