Privacy Law Next: Deletion, Children, and AI Training Records

Archi4 min read

privacylawaicompliance

Contents
  1. The notice page is no longer the center of the file
  2. Deletion becomes a propagation test
  3. Children's privacy moves from age gates to defaults
  4. AI training records get a privacy audit
  5. Enforcement gets simpler and slower
  6. What to prepare for the next review

The notice page is no longer the center of the file#

Five years ago, a privacy team could answer an inquiry with a policy page, a cookie banner, and a consent log. The next phase of privacy law asks for the data map, the vendor contract, and the deletion queue. Regulators have moved from asking whether a company told people what it collected to asking whether the company can prove what it deleted, where it kept data, and who used it.

That shift will not arrive as one clean statute. It will arrive through state attorney general actions, EU data protection authority decisions, and app store rules. The pattern is already visible. Enforcement teams are treating privacy notices as marketing copy. They are testing the plumbing underneath.

Deletion becomes a propagation test#

In 2020, deletion rights were often handled as a single support ticket. A customer sent a request, the company removed the record from its main database, and the case closed. The next test is whether deletion reaches every copy. That includes analytics warehouses, email platforms, ad partners, backups, and AI vendors.

Firms should expect questions about service level agreements. If a company tells a customer that data is deleted in 30 days, the vendor list should say 30 days too. If a subprocessor keeps logs for 90 days, that must be disclosed. The answers will decide whether a privacy team can defend the request.

The practical work is unglamorous. Build a data inventory with legal basis. Map each field to a system. Add deletion propagation clauses to contracts. Keep evidence of vendor confirmations. Five years ago, this was a project for large banks. Next, it will be a standard audit item for mid-size software firms and retailers.

Children's privacy moves from age gates to defaults#

COPPA and state child privacy laws spent the last five years arguing about age verification. The next fight is about default settings. Regulators will ask whether a product designed for minors collects location, allows public profiles, sends engagement notifications, or uses targeted ads. A simple age gate will not be enough.

Companies should expect rules that require separate data categories for minors. A teen account may need no behavioral advertising, no contact discovery, and shorter retention. App stores may become the enforcement point because they control distribution and can require age signals.

This creates product design work as well as legal drafting. Teams need to decide what a minor account looks like before launch. They need to test defaults on real devices. They need to keep a record of the choices. Five years ago, many apps treated child safety as a checkbox. Next, it will be a release gate.

AI training records get a privacy audit#

The largest change is AI. Five years ago, privacy teams reviewed vendor contracts and data processing agreements. Now they review model training sets, prompt logs, fine-tuning data, and inference records. The question goes beyond consent. It asks whether the company can show what personal data entered a model and what left it.

Regulators will not demand perfect removal from model weights. They will demand records. Which data sets were used? What was the lawful basis? How were opt-outs handled? Did a vendor train on customer content without a clause? Can the company trace a deletion request to a training pipeline?

The next 12 to 24 months will bring more procurement questions. Buyers will ask for model cards, data lineage, and incident logs. Vendors will need to answer with evidence, not assurances. Five years ago, a privacy addendum was enough. Next, the addendum needs an annex.

Enforcement gets simpler and slower#

New privacy bills will keep arriving. The bigger force is enforcement under existing law. State attorneys general can use unfair and deceptive practice statutes. The FTC can use Section 5. EU regulators can use GDPR articles on consent, transparency, and data minimization. These tools do not need a new law.

That means companies should not wait for a perfect statute. They should expect investigations into dark patterns, cookie walls, children's data, and deletion failures. Penalties may focus on the gap between the privacy notice and the actual system. A company that says it deletes data but keeps it in a warehouse for two years has a problem.

Five years ago, privacy enforcement was uneven. Some states were active, others were quiet. The next phase will be less uneven. Regulators are sharing complaint patterns. They are using consumer reports and app store reviews as leads. The result will be more consistent questions and fewer excuses.

What to prepare for the next review#

Start with the deletion path. Draw it from the customer request to the vendor confirmation. If there is a gap, write it down and fix it. Next, separate minor data. Decide what is collected, what is shared, and what is kept. Then build the AI record. List the data sets, the lawful basis, and the opt-out process.

The next audit will ask for the deletion path, the minor default, and the training record. Firms that cannot show those three artifacts will spend the next cycle explaining why.

More articles