1. The outright prohibition. Google's Health Content and Services policy states: "We do not allow apps that facilitate the sale or purchase of prescription drugs without a prescription" (https://support.google.com/googleplay/android-developer/answer/16679511). The same article opens by requiring that any app which contains or promotes health content and services "must ensure your app is compliant with any applicable laws and regulations". Practically: an in-app checkout, a referral link, or a seller directory that routes users to prescription medication without a valid prescription is a hard violation, not a declarable grey area - and local pharmacy law applies on top of the store policy.
2. Unapproved substances are the adjacent trap. Google Play "doesn't allow apps that promote or sell unapproved substances, irrespective of any claims of legality". The listed violations are: items on the non-exhaustive prohibited pharmaceuticals and supplements list (Google points developers to www.legitscript.com to check), products containing ephedra, hCG products promoted for weight loss or alongside anabolic steroids, herbal and dietary supplements with active pharmaceutical or dangerous ingredients, false or misleading health claims - including claims implying a product is as effective as prescription drugs or controlled substances - non-government-approved products marketed as safe or effective for preventing, curing or treating a disease, products subject to government or regulatory action or warning, and product names confusingly similar to an unapproved pharmaceutical, supplement or controlled substance.
3. Telehealth is classified as a medical app - and that pulls the Health apps policy into scope. Google's health app categories article lists "healthcare provider apps such as electronic health records (EHRs) and patient portals, medical reference apps, telehealth, remote monitoring apps, disease management apps, symptom checkers" as medical apps (https://support.google.com/googleplay/android-developer/answer/13996367). Medical apps can also include Software as a Medical Device (SaMD) regulated by a body such as the FDA, in which case the regulatory proof route applies rather than the disclaimer route.
4. The declaration is mandatory for everyone, not just health developers. All developers with an app published on Google Play must complete the Health apps declaration form on the App content page (Policy > App content) in Play Console - including apps on closed testing, open testing or production tracks, and pregranted/preloaded apps that update through Play. Developers whose apps offer no health features must still complete the form and certify that none are offered; only system services and private apps are exempt (https://support.google.com/googleplay/android-developer/answer/14738291). This requirement came out of the April 2024 Health Apps policy update.
5. The disclaimer wording is prescribed, which decides review outcomes for telehealth listings. Apps that are not regulated as a medical device "must include a clear disclaimer in their app description indicating that the app is 'not a medical device and does not diagnose, treat, cure, or prevent any medical condition'" and must remind users to consult a healthcare professional for medical advice, diagnosis or treatment. Apps that are regulated as a medical device must be declared as such, are identified as "Medical Device" on Google Play, and must provide proof of approval, clearance or certification by the relevant authority upon request. Apps that connect to external hardware (a blood glucose monitor, for example) must disclose that hardware requirement in the description and must not imply the app works without it.
6. Privacy policy and permission hygiene. The privacy policy link must be posted in the designated field in Play Console and also inside the app, on an active, publicly accessible, non-geofenced URL (no PDFs) and non-editable per the Data safety requirements; it must comprehensively disclose the access, collection, use and sharing of personal or sensitive user data, beyond what the Data safety section shows. Permissions that are not required for the app's core health functionality must not be requested, and unused permissions must be removed. If the app is not primarily a health app but touches health data, the policy must reflect that limited use.
7. Health Connect and health data. Data accessed through Health Connect permissions is treated as personal and sensitive user data subject to the User Data policy plus additional requirements - so it cannot be repurposed for advertising or targeting, and the Data safety declaration has to match what the app actually does (https://support.google.com/googleplay/android-developer/answer/10144311).
8. Working checklist. Because the prescription rule is a prohibition rather than a declaration: keep drug brand names, dosage guidance and treatment-outcome claims out of the title, short description and screenshots; carry the exact "not a medical device" disclaimer plus the consult-a-professional reminder in the description; complete the health declaration even if the app has no health features; confirm the privacy policy URL is public and non-geofenced; if you claim affiliation with a government or recognised healthcare organisation, submit proof through Google's Advance Notice Form; and keep clinical claims consistent with the Health Misinformation rules. Developer reporting on health-app rejections and appeals is collected at https://www.reddit.com/r/androiddev/search/?q=telehealth+app+play+store+policy+prescription