Guideline explainers

App Store Guideline 1.4.3 explained: Regulated substances

Guideline 1.4.3 is an App Review safety rule about regulated substances. For iOS developers, the practical risk is usually not the guideline number itself; it is whether the submitted build, product page, screenshots, policies, and review notes make compliance easy for Apple to verify. Use this explainer to turn the rule into a pre-submission checklist, a resubmission fix plan, and a concise reviewer reply for health, safety, and physical harm.

Developers searching for App Store Guideline 1.4.3 help, rejection causes, or fix guidance. Guideline 1.4.3 Official Apple source

What this guideline means in practice

Guideline 1.4.3 sits in Apple's Safety section and is most relevant to health, safety, and physical harm.

This page summarizes the review risk in practical terms and links to the official Apple source for the exact rule text.

Apple applies extra scrutiny to apps that could affect health, safety, diagnosis, treatment, or physical behavior.

What Apple is likely checking

Apple applies extra scrutiny to apps that could affect health, safety, diagnosis, treatment, or physical behavior.

Claims about measurements, medical outcomes, or safety-critical behavior need strong support.

Review notes should include documentation when the app depends on regulated or specialist functionality.

Common rejection triggers

The app makes health or safety claims that are not supported in the submission.

Medical, dosage, emergency, or physical-risk features lack documentation or disclaimers.

Screenshots or descriptions imply diagnostic accuracy beyond what can be validated.

Fix checklist before resubmission

Add conservative disclaimers and remove unsupported claims.

Provide regulatory, institutional, or methodology documentation when relevant.

Explain safety limits clearly in metadata, onboarding, and reviewer notes.

Reviewer reply angle

If Apple cited Guideline 1.4.3, reply with the exact change you made and where the reviewer can verify it.

If you believe the app already complies, provide concise evidence, navigation steps, and any supporting documentation instead of a generic appeal.

Keep the tone factual and cooperative. Avoid promising approval or arguing beyond what the submitted build and metadata can prove.

Check your app against Guideline 1.4.3

AcceptMyApp can compare your metadata, screenshots, privacy pages, app context, and rejection text against Apple guideline risks before you resubmit.

Get started