This kind of rejection means Google found issues with how your app requests or explains access to user data or device features — and it’s more common than you’d think.
Whether you’re building a new app or converting a website into a mobile app, if your app asks for camera, location, contacts, or SMS access and can’t justify it, your Google Play app submission is at risk.
Let’s break it down — what this means, how to fix it, and how ShopApper helps you stay compliant without headaches.
Google Play enforces the principle of least privilege. In simple terms, that means your app should only ask for permissions that are absolutely necessary to function.
If your app:
Requests access to features it doesn’t use (like the microphone)
Doesn’t explain why it needs sensitive permissions (like location)
Collects personal data without clear justification
…then your Play Store submission is likely to get rejected.
Let’s say your app:
Links to YouTube videos but asks for camera access → ❌ rejected
Displays local news but asks for location without saying why → ❌ rejected
Shows contact info but asks for SMS access → ❌ rejected
Even if your intention is innocent, if your app doesn’t clearly use and justify these permissions, you’re going to run into issues.
Start with your AndroidManifest.xml file. Remove any permissions your app doesn’t use directly. Ask:
Do I really need access to the camera, location, or SMS?
Can I achieve this feature without sensitive access?
💡 ShopApper Tip: Our platform automatically limits your app to core-required permissions — no unnecessary risk.
If your app truly needs access to location, camera, microphone, contacts, or messages, you must explain why in both your:
App Store listing (description and update notes)
In-app onboarding or settings
✔ Example: “We use your location to show nearby deals and pickup options.”
Any time your app touches personal data — especially with permissions like contacts or SMS — your privacy policy must:
Explicitly mention each type of data collected
Explain why you collect it
Describe how it’s stored, used, and (if applicable) shared
💡 ShopApper Tip: We help create and link a clear, mobile-friendly privacy policy that aligns with your app’s permissions — a must-have for Play Store compliance.
If your app needs to request permissions during use (like accessing the camera after tapping “Take a Photo”), use Google’s built-in permission prompts — and not your own custom dialogs.
This helps users understand what’s happening and keeps your app aligned with Android’s evolving security guidelines.
Answer a few quick questions and get a custom report on your app potential, missed opportunities, and where to level up.
❌ Don’t leave unnecessary permissions in your manifest “just in case”
❌ Don’t skip permission explanations in your app or Play listing
❌ Don’t ask for sensitive permissions without clear use
❌ Don’t forget to mention data collection in your privacy policy
❌ Don’t assume small apps can skip these rules — they apply to everyone
Permission |
Needs Clear Justification |
Example Use Case |
|---|---|---|
Here’s what we do for you:
Features
Start By Industry
I’m Ece, your Account Manager. I’m eager to learn about your business and assist you in achieving your goals.
Please share some info about your business so I can be fully prepared to answer your queries. I’ll reply within 15-20 minutes. Thanks! 
