app store metadata checklist
App Store Metadata Checklist: Website, Support URL, and Privacy Policy Setup for iOS Submissions
A practical app store metadata checklist focused on the items that often delay review: your iOS app website, support URL, and privacy policy. Includes examples you can copy and adapt.
A solid app store metadata checklist goes beyond screenshots and keywords. Many App Store submission delays come from missing or inconsistent URLs: a public website, a working support URL, and a privacy policy that matches what your app actually does. This checklist focuses on setting up those essentials quickly and correctly, with examples you can reuse.
What this app store metadata checklist covers (and why it matters)
Apple expects certain metadata fields to be complete, accurate, and publicly accessible. The most common issues for indie developers are: (1) no functional support URL, (2) a privacy policy that doesn’t match declared data practices, and (3) a website or support page that’s empty, broken, or gated behind a login.
This checklist is specifically about your iOS app website, support URL, and privacy policy setup, plus the consistency checks that keep everything aligned across App Store Connect and your public pages.
Checklist item 1: App website (what it should include)
You don’t always need a large marketing site, but you do need a clean, public page that represents the app and doesn’t mislead users. Keep it simple and accurate. At minimum, your app website should include:
1) App name and a one-sentence value proposition that matches your App Store subtitle/description. Example: “FocusTimer helps you run Pomodoro sessions with flexible breaks and simple stats.”
2) Basic feature overview (3–6 bullet points). Avoid claims you can’t support (for example, “AI-powered” if it’s not).
3) Availability and platform: “Available on iPhone and iPad.” If it’s iPhone-only, say so; if it requires iOS 17+, say so (or keep it in sync with your App Store minimum OS).
Checklist item 2: App website essentials for compliance and user trust
Add these to reduce review risk and support overhead:
1) Links to Support and Privacy Policy pages (public, accessible without login).
2) Contact method: support email address or contact form (support email is usually easiest). Example: support@yourdomain.com.
3) Developer/Company name that matches App Store Connect (or clearly indicates the same entity). If your App Store seller name is “Jane Doe,” your website footer can say “© 2026 Jane Doe.” Consistency matters more than legal complexity for most indie apps.
Checklist item 3: Support URL requirements (must work, must help)
Your Support URL should be a stable page where a user can get help without guessing. Avoid linking to a generic social profile or an app store listing. A strong support page includes:
1) Clear ways to contact you: support email and optionally a form.
2) Common issues and quick answers (even 5 short FAQs helps). Example FAQs: “How do I restore purchases?”, “How do I export data?”, “How do I delete my account?”
3) App version and device info instructions. Example text: “Include your app version (Settings > About) and iOS version.”
Support URL example you can copy
Support - FocusTimer
Contact: support@focustimerapp.com
Response time: Typically within 2 business days
FAQ: • Restore purchases: Open Settings > Purchases > Restore • Data export: Settings > Export • Account deletion: If you created an account, request deletion at support@focustimerapp.com with your account email • Bugs: Include iPhone model, iOS version, app version, and steps to reproduce
Checklist item 4: Privacy policy basics (what Apple expects)
A privacy policy must be publicly accessible and reflect what your app actually does. Keep it readable and specific. It should state:
1) What data you collect (or explicitly say you collect none).
2) Why you collect it (purpose).
3) Whether data is linked to the user, used for tracking, or shared with third parties (and who those parties are, in plain terms).
Frequently asked questions
Do I need a website for my iOS app to pass App Store review?
You can submit without a full marketing site, but you do need valid, public URLs where required (especially Support URL and Privacy Policy URL). A simple app website that links to support and privacy is a reliable way to avoid missing pieces.
What is a good Support URL if I don’t have a help center?
A single support page on your domain with a support email address and a short FAQ is sufficient for many indie apps. The key is that it loads publicly and provides a clear path to help.
Can my privacy policy be a Google Doc or Notion page?
It can work if it’s publicly accessible, stable, and doesn’t require sign-in. For long-term reliability, hosting it on your own domain is usually safer.
How do I keep my privacy policy aligned with App Store privacy “nutrition labels”?
First, document what your app and SDKs collect (analytics, ads, crash reporting, accounts, purchases). Then ensure your policy matches those realities and your App Store Connect privacy answers. If you change SDKs or start collecting new data, update both.
Where does MyAppDeck fit into this checklist?
If you want a quick way to publish an app landing page along with a dedicated support URL and privacy policy page on a consistent, shareable set of URLs, MyAppDeck can be relevant. Regardless of tool, the goal is the same: public pages that match your App Store Connect metadata.
Promote your app
Turn this strategy into real app growth
Launch a polished website for your app with a conversion-ready landing page, support URL, and hosted privacy and terms pages. Get App Store-ready and start promoting faster.
Related articles
app store optimization website content
App Store Optimization Website Content: Build an iOS App Website, Support URL, and Privacy Policy That Convert
contact form for app support
Contact Form for App Support: Set Up a Support URL That Helps Users (and Passes App Review)
app support email best practices
App Support Email Best Practices for iOS Apps (Plus Support URL and Privacy Policy Setup)