> For the complete documentation index, see [llms.txt](https://saral.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://saral.sunbird.org/use/google-play-store-app-publish-recommendations.md).
# Google Play Store App Publish Considerations
Play Store App publish have pre-requisites interms of privacy policy , misleading claim policy etc.
Refer to [Developer Program Policy](https://support.google.com/googleplay/android-developer/answer/11899428) for more details. These policies can be changed by google time to time, so please refer latest policies before publishing App in playstore.
**Privacy Policy** for App to be listed in the playstore to be generated and publish this policy of the app as a URL. The same `Privacy Policy URL` needs to be added in the play store "Store Listing" section of your application before publishing the Application.
**Misleading Claims** Google team reviews the app content including logos , images , content to see if any misleading claims. For example "government affiliation or authorization to facilitate government services through your app". A [Advance Notice Form](https://support.google.com/googleplay/android-developer/contact/adv_note) to be submitted for any such affiliations or claims for google team to review it.
\
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://saral.sunbird.org/use/google-play-store-app-publish-recommendations.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.