Abstract: In particular embodiments, a sensitive data management system is configured to remove sensitive data after a period of non-use. Credentials used to access remote systems and/or third-party systems are stored with metadata that is updated with each use of the credentials. After a period of non-use, determined based on credential metadata, the credentials are deleted. Personal data retrieved to process a consumer request is stored with metadata that is updated with each use of the personal data. After a period of non-use, determined based on personal data metadata, the personal data is deleted. The personal data is also deleted if the system determines that the process or system that caused the personal data to be retrieved is no longer in use. An encrypted version of personal data may be stored for later use in verifying proper consumer request fulfillment.

Abstract: In particular embodiments, a sensitive data management system is configured to remove sensitive data after a period of non-use. Credentials used to access remote systems and/or third-party systems are stored with metadata that is updated with each use of the credentials. After a period of non-use, determined based on credential metadata, the credentials are deleted. Personal data retrieved to process a consumer request is stored with metadata that is updated with each use of the personal data. After a period of non-use, determined based on personal data metadata, the personal data is deleted. The personal data is also deleted if the system determines that the process or system that caused the personal data to be retrieved is no longer in use. An encrypted version of personal data may be stored for later use in verifying proper consumer request fulfillment.

Abstract: In particular embodiments, a sensitive data management system is configured to remove sensitive data after a period of non-use. Credentials used to access remote systems and/or third-party systems are stored with metadata that is updated with each use of the credentials. After a period of non-use, determined based on credential metadata, the credentials are deleted. Personal data retrieved to process a consumer request is stored with metadata that is updated with each use of the personal data. After a period of non-use, determined based on personal data metadata, the personal data is deleted. The personal data is also deleted if the system determines that the process or system that caused the personal data to be retrieved is no longer in use. An encrypted version of personal data may be stored for later use in verifying proper consumer request fulfillment.

Abstract: Embodiments of the present invention provide methods, apparatus, systems, computing devices, computing entities, and/or the like for verifying the identity of a data subject. In one embodiment, a method is provided comprising: receiving, via a browser, a consumer rights request for a data subject for performing an action with regard to personal data associated with the data subject; detecting a state of the browser indicating a location; identifying a law based on the location; determining a level of identity verification required based on the law; generating, based on the level, a GUI by configuring a first prompt on the GUI configured for receiving input for a first type of identity verification; transmitting an instruction to present the GUI; receiving the input for the first type of identity verification; verifying the identity of the data subject based on the input; and responsive to verifying the identity, causing performance of the action.

Abstract: Embodiments of the present invention provide methods, apparatus, systems, computing devices, computing entities, and/or the like for verifying the identity of a data subject. In one embodiment, a method is provided comprising: receiving, via a browser, a consumer rights request for a data subject for performing an action with regard to personal data associated with the data subject; detecting a state of the browser indicating a location; identifying a law based on the location; determining a level of identity verification required based on the law; generating, based on the level, a GUI by configuring a first prompt on the GUI configured for receiving input for a first type of identity verification; transmitting an instruction to present the GUI; receiving the input for the first type of identity verification; verifying the identity of the data subject based on the input; and responsive to verifying the identity, causing performance of the action.

Abstract: In particular embodiments, a sensitive data management system is configured to remove sensitive data after a period of non-use. Credentials used to access remote systems and/or third-party systems are stored with metadata that is updated with each use of the credentials. After a period of non-use, determined based on credential metadata, the credentials are deleted. Personal data retrieved to process a consumer request is stored with metadata that is updated with each use of the personal data. After a period of non-use, determined based on personal data metadata, the personal data is deleted. The personal data is also deleted if the system determines that the process or system that caused the personal data to be retrieved is no longer in use. An encrypted version of personal data may be stored for later use in verifying proper consumer request fulfillment.

Abstract: Embodiments of the present invention provide methods, apparatus, systems, computing devices, computing entities, and/or the like for verifying the identity of a data subject. In one embodiment, a method is provided comprising: receiving, via a browser, a consumer rights request for a data subject for performing an action with regard to personal data associated with the data subject; detecting a state of the browser indicating a location; identifying a law based on the location; determining a level of identity verification required based on the law; generating, based on the level, a GUI by configuring a first prompt on the GUI configured for receiving input for a first type of identity verification; transmitting an instruction to present the GUI; receiving the input for the first type of identity verification; verifying the identity of the data subject based on the input; and responsive to verifying the identity, causing performance of the action.

Abstract: In particular embodiments, a sensitive data management system is configured to remove sensitive data after a period of non-use. Credentials used to access remote systems and/or third-party systems are stored with metadata that is updated with each use of the credentials. After a period of non-use, determined based on credential metadata, the credentials are deleted. Personal data retrieved to process a consumer request is stored with metadata that is updated with each use of the personal data. After a period of non-use, determined based on personal data metadata, the personal data is deleted. The personal data is also deleted if the system determines that the process or system that caused the personal data to be retrieved is no longer in use. An encrypted version of personal data may be stored for later use in verifying proper consumer request fulfillment.

Abstract: In various embodiments, before a data subject request can be processed, the data subject's identity may need to be verified. In various embodiments, the system provides a mechanism to automatically detect the type of authentication required for a particular data subject based on the type of Data Subject Access Request being made and automatically issues a request to the data subject to verify their identity against that form of identification. For example, a subject rights request might only require two types of authentication, but a deletion request may require four types of data to verify authentication. The system may automatically detect which is type of authentication is required based on the DSAR and send an appropriate request to the data subject to verify their identity.

Abstract: In particular embodiments, a sensitive data management system is configured to remove sensitive data after a period of non-use. Credentials used to access remote systems and/or third-party systems are stored with metadata that is updated with each use of the credentials. After a period of non-use, determined based on credential metadata, the credentials are deleted. Personal data retrieved to process a consumer request is stored with metadata that is updated with each use of the personal data. After a period of non-use, determined based on personal data metadata, the personal data is deleted. The personal data is also deleted if the system determines that the process or system that caused the personal data to be retrieved is no longer in use. An encrypted version of personal data may be stored for later use in verifying proper consumer request fulfillment.

Abstract: In various embodiments, before a data subject request can be processed, the data subject's identity may need to be verified. In various embodiments, the system provides a mechanism to automatically detect the type of authentication required for a particular data subject based on the type of Data Subject Access Request being made and automatically issues a request to the data subject to verify their identity against that form of identification. For example, a subject rights request might only require two types of authentication, but a deletion request may require four types of data to verify authentication. The system may automatically detect which is type of authentication is required based on the DSAR and send an appropriate request to the data subject to verify their identity.

Abstract: Apparatuses, systems and methods are presented for handling calls. In one embodiment, an emergency call handling system capable of receiving visual information from callers and correlating the visual information to particular incidents is disclosed. To obtain visual information, a call handler may generate and send an electronic mail message to the caller. The caller may reply to the electronic mail message and attach an image captured with, for example, a camera phone. The visual information may then be correlated to the call between the caller and call handler. In addition, unsolicited visual information received by the emergency call handling system may be prioritized, triaged and delivered to the call handler. The visual information may be used to assess an emergency situation. The visual information may be forwarded to emergency service providers.

Abstract: Systems and methods are presented for handling calls. In one embodiment of the invention, a call handling system is configured for handling a variety of emergency and/or non emergency related calls. For example, the call handling system may allow a call handler to recognize and respond to certain received call information, such as that information relating to fire, police, emergency medical and/or homeland security. The call handling system comprises a call interface configured for receiving the call information. A processor is communicatively coupled to the call interface and configured for processing the call information to initiate a protocol. This protocol may, as it progresses, be used to generate data for use in a CAD system. The CAD system may subsequently dispatch responders based on the generated data.