The fraud team wants to process signup telemetry to prevent repeat account abuse without asking each suspected abuser for consent. LIA = purpose test -> necessity test -> balancing test -> safeguards -> decision conditions. The common shortcut is to write "fraud prevention is legitimate interest" and skip whether every proposed data point is necessary or expected. Purpose Define the interest narrowly: prevent repeat account abuse and payment fraud during signup. A narrow purpose makes necessity testable. "Improve trust" is too vague; fraud prevention at signup is specific. Necessity Compare inputs: device hash, IP risk band, payment-failure pattern, and email-domain…
Read the full lesson
Sign up free: one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in