Data ownership in microservices: who owns the 'user' data?

data ownership for something as central as 'user' data is a constant debate point for us in a microservices setup. services like Auth, Profile, Billing, and Notifications all need access to user information, but each logically owns a different slice. if Auth owns the core user ID and email, but Profile owns display name and avatar, and Billing owns payment info, how do you keep them consistent? we've explored event-driven replication, where changes to a user's profile in the Profile service emit an event that other services consume to update their own read-only caches or replicas. this works, but introduces eventual consistency and complex choreography. what are the prevailing patterns for managing user data ownership across multiple bounded contexts? what's the least-bad approach to ensure data integrity and consistency without creating a monolithic user service?