Prepare the App and Its Declarations Together
Publishing a school app involves more than uploading a working build. Its permissions, privacy information, audience selection, and review instructions should accurately describe the experience delivered to users.
For an Akadvia ERP school app, the following checks help your team prepare a clearer submission. Approval remains subject to Google’s review and the requirements applicable to your app.
Provide an Appropriate Account Deletion Process
Google’s account deletion requirement applies when an app enables account creation, including directing users to an external registration flow. A login screen alone does not establish that requirement.
Where applicable, provide:
- An In-App Request Path: Make the deletion option easy to find within account settings.
- An External Web Page: Allow users to request deletion without reinstalling the app.
- Clear Retention Information: Explain any data retained for legitimate purposes and the reasons for keeping it.
Deleting an account should address associated user data. Routing a request to an administrator is only useful when it leads to a functioning deletion process; it is not a blanket exemption for school records. Google’s account deletion guidance
Match Location Access to the Actual Feature
Review which device supplies location information and why the app needs access. Displaying a bus position is different from collecting the parent’s phone location.
For background location, check that the feature meets Google’s requirements, complete the applicable declaration, and provide a prominent disclosure before requesting permission. Explain what location is collected and how it supports the feature. Google’s background location guidance
Describe What Your App Actually Collects
Your Privacy Policy and Data Safety answers should reflect the released app, including the behaviour of integrated services and SDKs.
- Review Enabled Services: Check analytics, crash reporting, notifications, payment integrations, and location functions.
- Explain Data Use: Describe what information is accessed, collected, shared, and retained.
- Provide Accessible Privacy Information: Include the required privacy policy links in the app and Play Console.
- Verify Security Statements: Claim encryption or other protections only when the implementation supports them.
An SDK’s presence alone is not a complete inventory of your app’s data handling. Review its configuration and actual behaviour. Google’s User Data policy
Select the Audience Honestly
Choose age groups that match the app’s intended users. An adult-only parent utility app may have a different audience from an app that students use directly for homework, exams, or learning.
Do not select 18 and over simply to avoid additional requirements. Google reviews whether the declared audience matches the app. If children are included, assess the applicable Families policies. Target audience guidance, Families policies
Give Reviewers Working Access
Restricted features must be accessible to the review team. Complete the App Access section with working credentials and the instructions needed to reach relevant screens.
Use a dedicated review account with representative demonstration records. Explain any school code, role selection, or additional authentication step, and test those instructions before submission. Sample credentials are useful only if they genuinely work in the submitted app. Google’s app review preparation guide
Classify Payments by What Users Purchase
Google distinguishes purchases of physical services from purchases of digital content and functionality.
For a school app, assess in-person school charges separately from paid digital courses, subscriptions, or app features. A physical-service payment may use an external gateway, while digital purchases generally require Google Play Billing unless an applicable exception or programme permits otherwise.
Writing “offline school fees” in the description does not change the nature of the purchase. Google’s Payments policy guidance
💡 Before submitting, compare the app, its store listing, and its policy declarations. They should tell the same accurate story.
Use this checklist as part of your Akadvia ERP app release review, alongside the remaining requirements shown in your Play Console account.