In-App Purchases and Data Safety: What Changes When You Add Billing
Adding Google Play Billing for in-app purchases or subscriptions typically requires a "Purchase history" row in your Data Safety form, since transaction data is collected regardless of whether you as the developer can see individual payment details.
Developers sometimes assume that because Google handles the actual payment processing, they have nothing to declare — but the fact that a purchase occurred, and often which product was purchased, is still data associated with the user.
The fix
Fix: add a purchase history row the moment you integrate any billing SDK, even if you never see raw payment information yourself.
The same check runs automatically when you upload your bundle to the AAB analyzer — permissions, SDK fingerprints, and version info in one pass, free.
Keep going
Run this check on your own AAB
Free analysis, exports when you need them.