Skip to main content
a promotional graphic telling you that PCI Compliance is no longer an annual exercise and that continuous monitory must be built in
Personalized Pricing Under FTC Scrutiny: Six Questions AnsweredRegulatory Compliance
5 min readFor GRC Leaders

Personalized Pricing Under FTC Scrutiny: Six Questions Answered

The FTC has ordered nine major airlines, ride-hailing companies, and food-delivery firms to explain how they use personal data to set prices and wages. Named recipients include Delta, United Airlines, Walmart, and Uber. The regulator's concern is that personal data may determine what different customers pay for the same service, or how much gig workers are paid.

Whether or not your company received an order, these questions are landing in GRC channels. Below are the six we hear most, with direct answers.


Q1. We weren't on the list. Do we need to do anything?

Yes. When a regulator compels disclosure from companies across industries, it's mapping a practice, not targeting a few firms. Treat the orders as an indicator of where examination priorities are heading.

Start by confirming that pricing and wage-setting logic is captured in your Risk Portfolio. In most organizations, it isn't. Pricing often sits with commercial teams, and compliance never sees the data inputs. Add a risk entry for algorithmic and data-driven pricing, assign an owner, and tie it to the Regulatory Obligations that could apply, including unfair or deceptive practices authority and state privacy law.


Q2. How do we find out what personal data our pricing models actually use?

Build a data lineage map for every pricing and wage-setting decision. For each model or rule set, document the input data fields, the source system, the legal basis or consent for use, the output, and who can change the logic.

Expect friction. Pricing engines often ingest signals nobody classified as personal data: device type, location history, purchase history, browsing behavior. If a field can be linked to an individual or used to infer something about them, handle it as personal data until counsel concludes otherwise. Where inputs touch Sensitive Personal Data, escalate the use case for formal review before the model runs again.

The deliverable is an inventory you could hand to a regulator within days, not weeks.


Q3. What's the actual compliance exposure? Personalized pricing isn't illegal.

Correct, differentiated pricing isn't unlawful on its face. The exposure comes from how it's done and what you told people about it. The FTC's concern is unfairness. Three questions frame your risk:

  • Did you disclose the practice accurately, or do your privacy notices and terms say something different from what the models do?
  • Does the pricing outcome correlate with a protected characteristic, creating discrimination risk under other laws?
  • Did you collect data for one purpose and quietly repurpose it for pricing?

Disclosure gaps are the easiest for a regulator to prove, so test those first. Compare your published privacy statements against the data lineage map from Q2 and log every mismatch as a finding.


Q4. Where does data governance fit? Isn't this a pricing team problem?

It's a governance problem that pricing teams happen to operate. Data governance determines whether you can answer a regulator's questions at all. The controls that matter most:

  • Purpose limitation. Each data element has a documented permitted use, and pricing is either on the list or it isn't.
  • Access and change control. Model parameters and pricing rules go through formal change management with approval records.
  • Retention and minimization. You keep the data the model needs, not everything it could use.
  • Documentation. Model logic, training data sources, and override rules are written down and versioned.

Frame these as Compliance Controls with named owners and evidence requirements. Where the design is sound, run Control Testing Automation to confirm change approvals and access reviews are happening, rather than relying on annual sampling. Add a Key Control Indicator such as the share of pricing model changes with complete approval records.


Q5. How do we handle the ethics side without turning this into a philosophy debate?

Convert it into decision criteria. "Is this fair?" isn't testable. These are:

  • Would we be comfortable explaining this pricing logic to the customer it affects?
  • Does the model use inputs a reasonable customer wouldn't expect to influence price?
  • Could the outcome systematically disadvantage a group of customers or workers?
  • Does wage-setting based on personal data give workers any visibility into how pay is determined?

Put these into a pre-deployment review that sits alongside existing model risk or product approval steps. Record the outcome and any Approved Exception, with an expiry date. This gives you a defensible record of Principled Performance rather than a values statement with no operational weight. Consumer trust is a commercial asset as much as a compliance one, and the review documents that you weighed it.


Q6. What should we have ready if a regulator asks tomorrow?

Assemble a response file now, not under deadline pressure:

  1. The pricing and wage-setting data lineage inventory.
  2. The current privacy notices and any customer-facing pricing disclosures, with dates.
  3. Policy Standards governing data use for pricing, including Policy Metadata such as owner, version, and last review date.
  4. Evidence of control operation: change approvals, access reviews, test results.
  5. The ethical review records and any Approved Exceptions.
  6. An escalation path naming who coordinates the response, who signs it off, and how counsel is involved.

Run a tabletop exercise using a mock information request. The gaps surface fast, usually in the first hour. If your Chief Audit Executive hasn't yet considered this topic, include algorithmic pricing in Risk-Based Audit Planning for the next cycle so Audit Fieldwork tests the controls independently.


Next Steps

Start with the FTC's announcements and any orders or guidance it publishes on this inquiry, since the scope of questions asked is the clearest signal of what examiners will want from you. Cross-check your obligations against your Regulatory Inventory for applicable state privacy laws and consumer protection statutes. Then bring pricing, privacy, legal, and internal audit into one working group. This risk crosses all four, and no single function owns the full answer.

Promotional banner for the CUI buildout guide

You Might Also Like