Data processing consent capture systems and related methods
In various embodiments, a data processing consent capture system may be configured to prompt the data subject to consent to one or more types of data processing (e.g., to provide a desired consent) in response to identifying particular cookies (e.g., or types of data processing) that a data subject has not consented to. The system may, for example, substantially automatically prompt the data subject to consent for one or more particular types of data processing in response to determining that the user (e.g., data subject) has requested that a website or other system perform one or more functions that are not possible without a particular type of consent from the data subject. The system may, for example, prompt the user to consent in time for a certain interaction with the website, application, etc.
1. A method comprising:
identifying, by computing hardware, a transaction that is conducted via a piece of software;
accessing, by the computing hardware, a consent map associated with a user, the consent map defining:
a plurality of types of consent required from the user associated with interacting with the piece of software; and
for each respective type of consent of the plurality of types of consent, one of an indicator of provided consent by the user or an indicator of unprovided consent by the user;
analyzing, by the computing hardware, the consent map to determine a first type of consent having the indicator of unprovided consent by the user and a second type of consent having the indicator of provided consent by the user, wherein the transaction requires the first type of consent and the second type of consent to have the indicator of provided consent;
responsive to determining that the first type of consent has the indicator of unprovided consent by the user:
generating, by the computing hardware, a consent prompt that is customized to request consent for the first type of consent; and
providing, by the computing hardware, the consent prompt to the user;
receiving, by the computing hardware, an indication of the user providing the consent for the first type of consent; and
modifying, by the computing hardware, the consent map to identify the first type of consent as having the indicator of provided consent by the user, wherein identifying the transaction conducted via the piece of software is performed based on at least one of:
a passage of an amount of time from an initial access time by the user of the piece of software,
a number of clicks performed by the user within the piece of software, or
a particular scroll distance performed by the user within the piece of software.
2. The method of claim 1 further comprising, responsive to the consent map identifying the first type of consent and the second type of consent having the indicator of provided consent by the user, allowing for the user to conduct the transaction via the piece of software.
3. The method of claim 1 , wherein the transaction involves at least one of installing a cookie, installing tracking technology, or collecting personal data of the user.
4. The method of claim 1 further comprising:
subsequent to modifying the consent map to identify the first type of consent as having the indicator of provided consent by the user, identifying, by the computing hardware, the user attempting to conduct a second transaction via the piece of software, wherein the second transaction requires the first type of consent to have the indicator of provided consent;
responsive to identifying the user attempting to conduct the second transaction, analyzing, by the computing hardware, the consent map to determine the first type of consent has the indicator of provided consent; and
responsive to determining that the first type of consent has the indicator of provided consent, allowing, by the computing hardware, the user to conduct the second transaction via the piece of software.
5. The method of claim 1 , wherein the piece of software comprises at least one of a webpage or a mobile application.
6. The method of claim 1 further comprising:
analyzing at least one privacy related attribute of the piece of software;
analyzing at least one consent receipt for the user; and
generating the consent map based on the at least one privacy related attribute and the at least one consent receipt.
7. A system comprising:
a non-transitory computer-readable medium storing instructions; and
a processing device communicatively coupled to the non-transitory computer-readable medium,
wherein, the processing device is configured to execute the instructions and thereby perform operations comprising:
identifying functionality provided through a piece of software;
accessing a consent map associated with a user, the consent map defining:
a plurality of types of consent required from the user associated with interacting with the piece of software; and
for each respective type of consent of the plurality of types of consent, one of an indicator of provided consent by the user or an indicator of unprovided consent by the user;
analyzing the consent map to determine a first type of consent having the indicator of unprovided consent by the user and a second type of consent having the indicator of provided consent by the user, wherein the functionality requires the first type of consent and the second type of consent to have the indicator of provided consent;
responsive to determining that the first type of consent has the indicator of unprovided consent by the user, providing a consent prompt to the user, wherein the consent prompt requests consent for the first type of consent;
receiving an indication of the user providing the consent for the first type of consent; and
modifying the consent map to identify the first type of consent as having the indicator of provided consent by the user, wherein identifying the functionality provided through the piece of software is performed based on at least one of:
a passage of an amount of time from an initial access time by the user of the piece of software,
a number of clicks performed by the user within the piece of software, or
a particular scroll distance performed by the user within the piece of software.
8. The system of claim 7 , wherein the operations further comprise, responsive to the consent map identifying the first type of consent and the second type of consent having the indicator of provided consent by the user, allowing for the user to perform the functionality through the piece of software.
9. The system of claim 7 , wherein the operations further comprise:
subsequent to modifying the consent map to identify the first type of consent as having the indicator of provided consent by the user, identifying the user attempting to perform second functionality through the piece of software, wherein the second functionality requires the first type of consent to have the indicator of provided consent;
responsive to identifying the user attempting to perform the second functionality, analyzing the consent map to determine the first type of consent has the indicator of provided consent; and
responsive to determining that the first type of consent has the indicator of provided consent, allowing the user to perform the second functionality through the piece of software.
10. The system of claim 7 , wherein the piece of software comprises at least one of a webpage or a mobile application.
11. The system of claim 7 , wherein the operations further comprise:
analyzing at least one privacy related attribute of the piece of software;
analyzing at least one consent receipt for the user; and
generating the consent map based on the at least one privacy related attribute and the at least one consent receipt.
12. The system of claim 7 , wherein providing the consent prompt to the user comprises:
identifying at least one term related to the piece of software; and
generating the consent prompt to comprises the at least one term.
13. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by computing hardware, configure the computing hardware to perform operations comprising:
identifying at least one of a transaction or functionality provided through a piece of software;
accessing a consent map associated with a user, the consent map defining:
a first type of consent and a second type of consent required from the user associated with interacting with the piece of software; and
analyzing the consent map to determine the first type of consent having an indicator of unprovided consent by the user and the second type of consent having an indicator of provided consent by the user, wherein at least one of the transaction or the functionality requires the first type of consent and the second type of consent to have the indicator of provided consent;
responsive to determining that the first type of consent has the indicator of unprovided consent by the user, providing a consent prompt to the user, wherein the consent prompt requests consent for the first type of consent;
receiving an indication of the user providing the consent for the first type of consent; and
modifying the consent map to identify the first type of consent as having the indicator of provided consent by the user, wherein identifying at least one of the transaction or the functionality provided through the piece of software is performed based on at least one of:
a passage of an amount of time from an initial access time by the user of the piece of software,
a number of clicks performed by the user within the piece of software, or
a particular scroll distance performed by the user within the piece of software.
14. The non-transitory computer-readable medium of claim 13 , wherein the operations further comprise, responsive to the consent map identifying the first type of consent and the second type of consent having the indicator of provided consent by the user, allowing for the user to perform at least one of the transaction or the functionality through the piece of software.
15. The non-transitory computer-readable medium of claim 13 , wherein the operations further comprise:
subsequent to modifying the consent map to identify the first type of consent as having the indicator of provided consent by the user, identifying the user attempting to perform at least one of a second transaction or second functionality through the piece of software, wherein at least one of the second transaction or the second functionality requires the first type of consent to have the indicator of provided consent;
responsive to identifying the user attempting to perform at least one of the second transaction or the second functionality, analyzing the consent map to determine the first type of consent has the indicator of provided consent; and
responsive to determining that the first type of consent has the indicator of provided consent, allowing the user to perform at least one of the second transaction or the second functionality through the piece of software.
16. The non-transitory computer-readable medium of claim 13 , wherein the piece of software comprises at least one of a webpage or a mobile application.
17. The non-transitory computer-readable medium of claim 13 , wherein the operations further comprise:
analyzing at least one privacy related attribute of the piece of software;
analyzing at least one consent receipt for the user; and
generating the consent map based on the at least one privacy related attribute and the at least one consent receipt.