The system must enable its users to revoke whatever consent they have granted.
Systems usually request information from their users or collect it based on their interactions with the application. Regulations demand that none of these collections occur without the users consent and that this consent be demonstrable afterwards. Regulations also demand that users be allowed to revoke, at any given time, whatever consent they may have granted regarding the collection and processing of their information.
This requirement is verified in following services
- ePrivacy Directive-6_3. Traffic data
- GDPR-7_3. Conditions for consent (3)
- GDPR-18_1. Right to restriction of processing
- GDPR-21_1. Right to object
- CCPA-1798_120. Consumer's right to opt out of sale or sharing of personal information
- CPRA-1798_102. Right to say no to sale of personal information
- GLBA-502_B. Obligations with respect to disclosures of personal information – Opt out
- PDPA-4_16. Withdrawal of consent
- HITRUST CSF-13_e. Choice
- LGPD-8-5. Requirements for the Processing of Personal Data
- LGPD-15_III. Termination of Data Processing
- LGPD-18_IX. Data Subjects Rights
- LGPD-60. Final and Transitional Provisions
- OWASP Top 10 Privacy Risks-P4. Consent on everything
- SIG Core-P_6. Privacy
- OWASP MASVS-PRIVACY-4. The app offers user control over their data
Search for vulnerabilities in your apps for free with our automated security testing! Start your 21-day free trial and discover the benefits of our Continuous Hacking Machine Plan. If you prefer a full service that includes the expertise of our ethical hackers, don't hesitate to contact us for our Continuous Hacking Squad Plan.