Mandate Law

Can I use my users' data for something new?

What decides whether data you already collected can power a new AI feature, benchmarks, partnerships, or marketing, including your original promises, FTC limits on retroactive policy changes, and state purpose-limitation rules.

Short answer

Often, if the new use fits what users were told and would reasonably expect when they gave you the data. When it doesn't, the safest path is usually to tell users before the change and, for material changes, get their consent, applying the new use only to data collected afterward or from users who agree. Quietly updating the privacy policy to cover a new use of data you already hold is the approach regulators object to most. Deciding this before you build lets you design the feature around the data you can use, instead of reworking it later.

What decides it

What you already promised

Start with what users were told when the data was collected: the privacy policy in effect at the time, consent screens, app store privacy labels, enterprise contracts, and marketing. If a new use contradicts those promises, changing the policy today doesn't change what users agreed to then.

The FTC on changing your terms

In February 2024, the FTC warned AI companies and others that adopting more permissive data practices, such as sharing data with third parties or using it for AI training, and telling users only through a quiet, retroactive change to the terms of service or privacy policy could be unfair or deceptive. It pointed to earlier cases in which companies changed privacy policies to share data without notifying users or getting their consent. The practical takeaway is to give real notice before a material change and to get consent before applying it to data you already hold.

State purpose-limitation rules

Common AI cases

How to make the change well

Checklist an agent can run against the codebase

Sources

If this applies to you

An AI feature review covers a new use of existing data before you build it: what your earlier promises allow, the notice and consent the change needs, and updated privacy documents. For one planned use, such as a new feature built on existing data, a pre-build feature check covers that decision before it ships.