Abstract: Devices, systems, and methods are provided for user profile management across multiple devices. A method may include determining, by a first device, that the first device is signed into a customer account; determining that the customer account includes a first user profile and a second user profile, the first user profile having first identity data, and the second user profile having second identity data; determining that third identity data for the first user profile is available for presentation, the third identity data based on a user interaction with a second device; determining that the first user profile is enrolled on the first device; presenting the first identity data using the first device; receiving a second user request to access the first user profile; and presenting, using the first device, content based on the second user request and a user preference associated with the first user profile.

Abstract: Systems, methods, and computer-readable media are disclosed for systems and methods for sending and receiving requests to delete and/or retrieve certain data. Example methods may include sending from an electronic device a request to delete and/or retrieve selected data from a server based on selected categories, receiving the request at the server, and determining data to delete and/or retrieve on the server based on the request from the electronic device, deleting and/or retrieving the data on the server, and/or sending the retrieved selected to the electronic device.

Abstract: Techniques are provided herein for utilizing a push notification action engine (e.g., a push notification action engine of a client device). The techniques include receiving a push notification comprising a structured data payload, the structured data payload comprising a specification of content to be rendered on a display of the client device. The push notification action engine generates display information in accordance with the specification and sends the display information to the operating system of the client device. Sending the display information to the operating system may cause the operating system to render a user interface component on the display of the client device. The push notification action engine may receive user input associated with the user interface component and cause execution of one or more workflows in response to receipt of the user input.

Abstract: Techniques for providing notifications may be described. In particular, responses to past notifications transmitted from a computer system to a user device associated with a user account may be accessed. A notification profile for the user account may be generated based on the responses. The notification profile may include sequence of time slots to transmit notifications within a time period. A notification topic may also be determined based on past interactions of the user device with the computer system. Notifications corresponding to that notification topic may be scheduled for transmission to the user device based on the notification profile. A response to a transmitted notification may be analyzed to determine whether to change the notification topic. If so, remaining notifications may be updated based on the change before transmittal.

Abstract: Disclosed are various embodiments for a gaming content service implemented by a media distribution service. Game content is encoded for concurrent presentation with video content from a media distribution service. Viewers of the video content may interact with the game content using personal client devices. Whether the game content is presented with the video content may be determined according to a number of participating players.

Abstract: Techniques for providing a messaging plan may be provided. A message that conforms to a channel agnostic format may be received. In an example, a messaging plan that includes a channel for delivering the message may be determined based at least in part on a score determined by a machine learning module utilizing metrics of a user. The message may be provided to the user according to the messaging plan. The messaging plan may be updated for subsequent messages based at least in part on updated metrics of the user received in response to the user interacting with the message.