Encryption of calendar and address book

Why calendars and address books are not currently encrypted

The calendar and address book are currently not encrypted.

There are several reasons for this:

Technical limitations

Encryption in this area is always incomplete for technical reasons:

To allow the web client to display the corresponding data, it must be temporarily stored in an unencrypted state. Therefore, users cannot rely on the assumption that their provider would be unable to access their data.

Functional dependencies

Existing functions prevent such encryption:

At mailbox, many accounts are connected as family accounts or business accounts. One of the advantages is the ability to share calendars and address books with each other. However, these functions would not be possible if the data were encrypted in such a way that only the original owner could access it.

Future developments

Planned functions would be prevented:

In the long term, we have several ideas for additional features related to calendars and contacts (for example, reminder services) that would not work if these areas were encrypted.

In principle, it would be possible to implement encryption for calendars and address books by programming many exceptions and changes into the existing server software (for example, by disabling various special functions so that encryption could be enabled). However, we currently do not have the capacity to implement this and prefer to focus on other ideas and concepts that will sustainably and effectively improve the overall security of all users.