Repository navigation
|
How can a team catch Processing web personal data without GDPR compliance controls automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rn 'processData\|personalData\|submitForm\|registerWeb\|webForm' --include='*.js' --include='*.ts' --include='*.html' . && ! grep -rn 'GDPR\|opt-in\|privacyConsent\|deletePersonalData\|exportData' .Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. Collecting or processing personal web data without explicit opt-in controls, privacy policy links, or right to be forgotten (delete) options. The fix. Integrate standard GDPR compliance gates including explicit opt-in for data processing and a mechanism for data deletion. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
WEB-GDPR-COMPLIANCEwith a coverage line and a proper exit code.What the hit means. Collecting or processing personal web data without explicit opt-in controls, privacy policy links, or …