Global Privacy Regulations and Data Protection Frameworks Questions

Legitimate interest (LI) is appropriate when processing is necessary for a core product safety, security, or operational purpose where you can demonstrate a clear business need, a user’s reasonable expectation, and the fundamental rights/burdens balancing test favors the business. Example: real‑time fraud detection (transaction scoring, anomaly detection, blocking suspicious logins) — these protect users and the platform, are proportionate, and often can’t wait for granular consent.

Explicit consent should be used when processing is for optional, user‑facing personalization or marketing that users wouldn’t reasonably expect, or when profiling leads to behavioral advertising or uses sensitive data. Example: using browsing history to build personalized marketing emails or targeted ads — this is optional, value‑exchange driven, and requires clear, revocable consent.

Product guidance:

• Always document the balancing test and rationale in product specs.
• Prefer consent when value is directly user‑facing and reversible; prefer LI for safety, fraud, anti‑abuse.

Short list of risk controls to make LI defensible:

• DPIA / documented balancing test specific to the feature
• Purpose limitation and narrow, documented use cases
• Data minimization and feature‑level aggregation (only fields needed)
• Short, enforced retention policies and automated deletion
• Transparency: clear privacy notice and user FAQs
• Easy opt‑out/appeal for decisions affecting users
• Access controls, encryption, and vendor contractual safeguards
• Regular audits, monitoring for bias, and KPIs showing proportionality (false positive rates, impact)