Skip to content
Website and app legal documents

A/B Testing

A/B testing occupies a gray area under privacy regulations—sometimes essential for website functionality, sometimes requiring consent. Proper classification and documentation are key to compliant experimentation.

By Wenceslao M. Spiegel

Published by North End Law, which is responsible for this content.

Published · Last reviewed

Key points

  • →Classify testing as essential vs. optional
  • →Document legitimate interest assessments
  • →Handle consent for personalization tests
  • →Avoid dark pattern implications

A four-step check before you run a test

  1. Does the test store or read anything on the user's device (a cookie, local storage, an SDK)? For users in the EU or the UK, that needs consent unless it is strictly necessary for the service the user asked for.
  2. Does it use personal data? Most product tests can rely on legitimate interest, recorded in a short assessment. Where the test depends on tracking that already needs consent, the test needs it too.
  3. Does it personalize by profile? Tell users in your privacy notice, and keep sensitive data (health, religion, sexuality and similar) out of the test.
  4. Does a vendor run it? Put a DPA in place. In California, the vendor must be bound as a service provider, or the data flow may count as a "sale" or "sharing" that users can opt out of.

Essential vs. non-essential testing

Not all A/B tests require consent. Tests for legitimate website functionality—load time optimization, error reduction, accessibility improvements—may qualify as essential under GDPR's legitimate interest basis. Tests for conversion optimization, personalization, or marketing effectiveness are typically non-essential requiring consent. Document the purpose and basis for each testing program.

Legitimate interest assessments

If relying on legitimate interest for testing, conduct proper balancing tests. Document: the purpose of testing and business benefit, impact on individuals (minimal for UI tests, greater for personalization), user expectations given context, safeguards implemented (data minimization, pseudonymization), and why consent is impractical. Maintain these assessments as records.

Personalization testing considerations

Tests involving personalization based on user profiles require more careful analysis. Creating user segments, testing content tailored to inferred preferences, or experimenting with pricing may require consent under GDPR's automated decision-making provisions or CCPA's profiling disclosures. Consider whether your testing involves 'significant effects' on individuals.

Avoiding dark pattern claims

A/B tests that optimize for conversions can inadvertently create dark patterns—interface designs that manipulate users against their interests. Regulators increasingly scrutinize such practices. Tests should improve user experience, not exploit cognitive biases. Document ethical guidelines for testing and review concerning test variations.

This guide is general information, not legal advice. Reading it does not create an attorney-client relationship. The law is stated as of January 28, 2026.

Got questions?

Every business is different. Let's discuss how these principles apply to your specific situation.

Book a call