Abstract: Techniques for determining whether to allow access to a calendar invite and a meeting are disclosed. In this regard, a calendar invite and meeting message are received from a sender. A first time-to-live (TTL) value and a second TTL value associated with the calendar invite and meeting, respectively, are determined. A determination is made that the first and second TTL values have not been exceeded and, if they have not, allowing access to the calendar invite and the meeting. However, when the TTL values have been exceeded, denying access to the calendar invite and the meeting.

Abstract: Screen capture mitigation is disclosed. The presence of a first finger is detected in a first area of a display. In response to the detection, content id displayed. A determination is made that the position of the first finger has changed. A determination is made that the distance by which the first finger has changed position exceeds a tolerance. The content is ceased to be displayed in response to the determination that the tolerance has been exceed.

Abstract: A public/private key pair is generated on a client device for an application. A device identifier for the client device is generated. An application identifier for the application is generated on the client device. At least one of the public key, the device identifier, and the application identifier are transmitted to a server.

Abstract: Multi-party messaging is disclosed. A plurality of public keys is requested from a first server, wherein the plurality of public keys is associated with a plurality of recipients. A message containing one or more components is encrypted using a symmetric key. The symmetric key is encrypted, using each of the respective public keys, resulting in a plurality of encrypted symmetric keys. The encrypted message and the encrypted symmetric keys are encapsulated in an encapsulation. The encapsulation is transmitted to a second server.

Abstract: A digital security bubble encapsulation is disclosed. A first key and a device identifier of at least one recipient is requested from a first server. A message containing one or more components is encrypted using a second key. The second key is encrypted using the first key. The encrypted message, the encrypted second key, and the device identifier are encapsulated in a digital security bubble encapsulation. The digital security bubble encapsulation is transmitted to a second server.

Abstract: Multi-party messaging is disclosed. An encapsulation is received from a first client. The received encapsulation encapsulates an encrypted message encrypted using a symmetric key, and a plurality of keys. Each key in the plurality of keys comprises the symmetric key as encrypted with a respective public key of a respective recipient. An account associated with each of the respective recipients is determined. For each of the respective recipients, a flag is set that is indicative of the arrival of the encapsulation. For each of the respective recipients, which recipients have download the encapsulation is tracked. The encapsulation is deleted.

Abstract: A digital security bubble encapsulation is disclosed. A public key and a device identifier of at least one recipient is requested from a first server. A message containing one or more components is encrypted using a symmetric key. The symmetric key is encrypted with a public key received in response to the request. The encrypted message, the encrypted symmetric key, and the device identifier are encapsulated in a digital security bubble encapsulation. The digital security bubble encapsulation is transmitted to a second server.