Start with the user action
If the product only needs the user to choose one or a few contacts, broad address-book access may be more data than the feature needs.
Use narrower platform flows
A system picker can let a user deliberately choose data without granting permanent broad access. The exact API depends on the Android version and product flow.
Audit SDKs too
Removing READ_CONTACTS from your code does not help if another library still accesses contact data.
Update Data Safety
Declarations should reflect what data is actually collected, transmitted and shared after the architecture change.
Test denied-permission paths
The app should remain understandable and stable when a user declines optional data access.
Official sources
Policies and platform requirements can change. Check the linked official documentation for the latest wording before acting on a time-sensitive case.
Need case-specific help?
If your situation includes a specific warning, rejection or account state, send the exact notice rather than applying generic steps blindly.
Request assessment