Design a privacy-safe personalization system for Wallet at global scale

Problem Statement Description

Product context: Uber is a mobility and delivery platform; its products include rides, Uber Eats, grocery and retail delivery, freight, driver and courier tools, and marketplace pricing.

Uber wants to improve Wallet experiences for restaurant partners operating on its global delivery marketplace. These partners use Wallet-related surfaces to understand balances, payouts, fees, credits, promotions, financing options, and payment actions, but their needs vary widely by market, business size, cash-flow situation, seasonality, and operational maturity.

Design a privacy-safe personalization system that can decide what Wallet content, actions, nudges, or financial experiences to show to a restaurant partner while respecting global privacy, security, compliance, and reliability requirements. The system should work at Uber scale across regions with different regulations, languages, payment rails, data availability, and partner expectations.

This is a technical product management question. Focus on how you would define requirements, data flows, APIs, platform capabilities, privacy controls, rollout approach, and operating trade-offs rather than simply proposing UI ideas or campaign rules.

The experience should consider:

- Restaurant partner workflows, including checking earnings, managing payouts, discovering Wallet benefits, resolving payment issues, and taking time-sensitive financial actions.

- What user, business, transaction, and contextual data may be needed, what should be excluded or minimized, and how consent, purpose limitation, retention, and regional compliance should be handled.

- Core system requirements such as personalization decisioning, feature availability by market, policy enforcement, auditability, fallback behavior, and human override mechanisms.

- APIs and data interfaces between Wallet, restaurant systems, identity, payments, risk/fraud, experimentation, communications, and support tooling.

- Reliability, latency, freshness, scalability, observability, and incident response expectations for a global financial product surface.

- Privacy and security risks, including sensitive financial data exposure, inappropriate targeting, model leakage, partner trust erosion, and cross-border data constraints.

- Rollout strategy across markets and restaurant segments, including experimentation, guardrail metrics, compliance review, monitoring, and rollback plans.

- Product trade-offs between personalization quality, explainability, operational complexity, fairness, monetization, and partner trust.

Your goal is to frame a technically sound product design for a global, privacy-safe Wallet personalization platform that can support restaurant partners’ financial workflows while meeting Uber’s standards for marketplace reliability, safety, compliance, and scalable execution.