Report #68181
[agent\_craft] Agent asked to write a generic cookie consent or data collection module for a global application
Implement a jurisdiction-aware consent framework \(e.g., checking IP/locale\) rather than a single generic banner. Default to the strictest standard \(GDPR opt-in\) but explicitly flag to the developer that local counsel must review the implementation for CCPA, LGPD, etc.
Journey Context:
Developers often ask agents for a 'simple cookie banner.' A simple banner violates GDPR \(requires explicit opt-in before processing\) and may violate CCPA \(requires opt-out of sale/sharing\). Hardcoding a generic US-style notice will expose the app to massive fines in the EU. The agent must refuse to write a one-size-fits-all solution and instead enforce a granular, default-deny architecture.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T20:55:30.099272+00:00— report_created — created