Uber's March 28, 2026 update to its driver/delivery privacy notice reflects only two cosmetic changes: a modification to the displayed 'last updated' date (from March 26, 2026 to January 20, 2026) and a footer city swap (Los Angeles to Vancouver). No substantive data processing terms, consumer rights language, or compliance commitments were altered. This does not implicate GDPR Art. 13/14 transparency obligations, CCPA notice requirements, or any other privacy framework in a material way. No compliance action is required.

This change is cosmetic and does not trigger substantive regulatory obligations. However, the alteration of the 'last updated' date from March 26, 2026 to January 20, 2026 is worth flagging: under GDPR Art. 12(1) and Art. 13(2), controllers must ensure privacy notices are accurate and not misleading. If the backdated timestamp misrepresents when the policy was materially last changed, this could theoretically be scrutinized by the ICO or EDPB as a transparency issue. Under Cal. Civ. Code §1798.130(a)(5) (CPRA), businesses must keep privacy notices current and accurate. The timestamp discrepancy — detection date of March 28, 2026 vs. displayed date of January 20, 2026 — should be noted in case a regulator later asks about notice accuracy. No enforcement actions are directly applicable to this specific change.

Compliance intelligence locked

Obligation analysis, escalation trigger, board language, and recommended action.

Watcher: regulatory citations + obligations. Professional: full compliance memo.