aibrevoGet a quote

Question8 min read

Do I Need a Website for My App?

Quick answer

You do not need a full marketing website to publish an app, but you do need a few public web pages. Apple requires a Support URL for every app and a Privacy Policy URL for iOS and macOS apps. Google Play requires a privacy policy URL for every app and, if users can create accounts, a web page where they can ask for their account and data to be deleted.

Reviewed by Alpit Patel, Founder and CEO · Updated November 11, 2026

On this page 9 sections
  1. Do you need a website for your app?
  2. Which web pages do Apple and Google require?
  3. What does each required page need to say?
  4. Do you need a domain for links that open your app?
  5. Is a full website worth it for an app?
  6. What is the minimum website for an app launch?
  7. When is a web app the better plan?
  8. How we handle the launch pages
  9. Sources

Key takeaways

  1. You can build an app without a website, but you cannot publish one without at least a privacy policy page and a way for users to reach you.
  2. Apple requires a Support URL that leads to real contact information, and a Privacy Policy URL for iOS and macOS apps. The Marketing URL is optional.
  3. Google Play requires a privacy policy on a public web page (no PDFs) for every app, even apps that collect no personal data, plus a contact email.
  4. If users can create an account, both stores require deletion. Apple wants it started inside the app; Google also wants a web page where people can request it without re-downloading the app.
  5. If you want links to open your app, or passwords to autofill between your site and app, you need a domain you control that hosts a small verification file.

Do you need a website for your app?

You need a few web pages, not a full website. Both app stores ask for public links before they will list your app: at minimum a privacy policy and a way for users to contact you, and on Google Play an account deletion page if people can sign up. Many founders first meet this on the App Store Connect or Play Console form, close to launch day. You can build the app with no website at all, but you cannot publish it without these pages.

Whether a bigger website is worth it comes further down. The pages you cannot skip come first.

Which web pages do Apple and Google require?

Each store’s requirements, taken from Apple’s and Google’s own help pages:

Requirement Apple App Store Google Play Source
Privacy policy Privacy Policy URL required in App Store Connect for iOS and macOS apps. Guideline 5.1.1(i) also requires a link inside the app. Required for all apps, in the Play Console field and inside the app. Must be a public, active, non-geofenced URL, no PDFs. Required even if the app collects no personal data. App Store Connect, Guidelines, Google Play
Support or contact Support URL required. It must lead to actual contact information. Contact email required. A website where users can contact you is recommended, not required. App Store Connect, Google Play
Marketing website Marketing URL is optional. Website field is optional. Same as above
Account deletion (apps with sign-up) Users must be able to start deletion inside the app. If they finish on a website, link directly to that page. In force since June 30, 2022. An in-app path plus a web link where users can request account and data deletion without re-downloading the app. Entered in the Data safety form. Apple, Google Play
Privacy questionnaire App privacy details required to submit new apps and updates. Data safety form required for every published app, even apps that collect no data. Needs a privacy policy to complete. Apple, Google Play
Terms of use Not required. Apple’s standard EULA applies if you do not add your own. Not a requirement on the pages we checked. App Store Connect
Links that open the app Universal Links need an apple-app-site-association file on your domain. Android App Links need an assetlinks.json file on your domain. Apple, Android

Sources: Apple Developer and Google Play Console Help pages linked in each row, checked Nov 11, 2026. Store rules change; check each page again before you submit.

The stores do not charge for any of these pages. The store fees themselves are covered in what it costs to put an app on the App Store.

What does each required page need to say?

A link that loads is not enough. Reviewers can open these pages, and a broken or empty one can hold up your listing. If your submission comes back, our answer on how long App Store review takes explains what delays each store.

Privacy policy. Apple’s guideline 5.1.1(i) says the policy must identify what data the app collects, how it collects it and every use of it. It must confirm that third parties you share data with, such as analytics tools, ad networks and SDKs, give the same protection. It must explain your retention and deletion policies and how a user can revoke consent or request deletion. Google adds that the page must be public, active and non-editable, with no PDFs. Write it about your actual app and the actual tools inside it, and have a lawyer look at it if you handle health, financial or children’s data.

Support page. Apple says the Support URL must lead to actual contact information, listing legal address, email address and telephone number as details local law may require, so users can reach you about problems, feedback and feature requests. Guideline 1.5 repeats that the app and its Support URL should include an easy way to contact you. A support email and a short FAQ on one page is a sensible minimum.

Account deletion page. Google says the web link must load without errors, must reference the app or developer name exactly as it appears on your store listing, and must feature the deletion request prominently. If users have to do something first, such as cancel a subscription, the steps must be spelled out. Both stores say temporary deactivation or freezing does not count as deletion. Apple adds that apps outside highly regulated industries should not make people phone, email or go through a support flow to delete an account.

Yes, if you want a web link to open the app instead of the browser. Apple calls these Universal Links and Android calls them App Links, and both work by putting a small file on your website that proves the app and the domain belong together.

  • Apple. You create a file named apple-app-site-association, with no file extension, and place it in your site’s .well-known folder. Apple says you must host it over HTTPS with a valid certificate and no redirects. Apple’s content delivery network requests the file within 24 hours, and devices check for updates about once a week after the app is installed.
  • Android. Android looks for a Digital Asset Links file at https://your-domain.com/.well-known/assetlinks.json. App Links work on Android 6 and later on devices with Google services. Without verification, Android 12 and later open the link in the browser instead of your app. On Android 15 and later, changes to the file can take up to seven days to reach all devices.
  • Password autofill. Apple’s associated domains also power shared web credentials, which let saved passwords work in both your website and your app, using the same file on the same domain.

In practice, the domain should be yours, not a free subdomain on someone else’s platform, because you need to place files at exact paths on it and keep it running for as long as the app is live.

Is a full website worth it for an app?

Usually yes, but a small one. The required pages handle the stores. A simple landing site handles the people who never open a store at all: someone who hears your app’s name and searches Google, a journalist who wants a press photo, a partner who wants to know who is behind it. Store listings can show up in Google too, but your own site is the page you control for your name on the web.

It is also where your links point. Every email, QR code and social post can go to one web address that sends phones to the right store and opens the app for people who already have it. That only works if the site and the verification files are set up properly.

What is the minimum website for an app launch?

Five pages cover most apps. Use this as a checklist before you open App Store Connect or Play Console:

  1. Home page with what the app does in one sentence, screenshots, and App Store and Google Play badges linking to your listings.
  2. Privacy policy written for this app, on a plain web page at a stable URL, linked from the app too.
  3. Support or contact page with a support email and real contact details, plus answers to the questions users ask most.
  4. Account deletion page if users can sign up, naming the app exactly as it appears in the store and explaining how to request deletion.
  5. Terms of use if you sell subscriptions, run accounts or host user content. The stores do not demand it, but your lawyer may.

Then add the apple-app-site-association and assetlinks.json files to the same domain if you use Universal Links, App Links or password autofill. A site like this is small; our website development work covers it whether it stands alone or sits on your existing company site.

When is a web app the better plan?

When your users mostly sit at a desk, or you need every device on day one, a web app can be the product itself, and the website question goes away. We cover that decision in web app vs mobile app, including when a progressive web app is enough.

How we handle the launch pages

As part of our mobile app builds, we can set up the support page, the account deletion page and the link verification files on your domain, and publish the privacy policy text you supply or approve. The app is published under your own Apple and Google developer accounts and the code is yours. Builds run from $7,000 for a focused first version to about $25,000-$30,000 for apps with many features, user roles, payments and integrations. Larger builds are quoted on their scope, and project builds get a fixed-price quote in writing after a free 30-minute call. Book the call and bring the App Store Connect or Play Console screen that is asking for URLs; we will tell you what you actually need.

Sources

Related questions

Short, direct answers. Ask an engineer if yours is not here.

Ask on a free call

Do I need a website to create an app?

No, you can design and build an app without any website. You need web pages only when you publish. Apple asks for a Support URL and, for iPhone and Mac apps, a Privacy Policy URL. Google Play asks for a privacy policy link for every app and a web page for account deletion if users can sign up. A few simple pages on your own domain cover all of it.

Do I need a privacy policy for my app?

Yes. Apple's App Review Guidelines say all apps must link to a privacy policy in App Store Connect and inside the app. Google Play requires a privacy policy link in Play Console and inside the app for every app, including apps that collect no personal data. On Google Play the policy must sit on a public, active web page, not a PDF, and it must explain what data you collect and how you use it.

Does my app need a support page?

On the App Store, yes. Support URL is a required field in App Store Connect, and Apple says the page must lead to actual contact information so users can reach you about problems and feedback. Google Play only requires a contact email on the store listing, but it recommends adding a website where users can contact you. One support page on your own site works for both stores.

Do I need an account deletion page for my app?

If people can create an account in your app, plan for one. Google Play requires a web link where users can request deletion of their account and associated data, entered in the Data safety form. Apple requires that users can start deletion inside the app, and if they must finish on a website, the app should link straight to that page. Deactivating or freezing an account does not count as deleting it.

Can my app's privacy policy be a PDF?

Not on Google Play. Google's User Data policy says the privacy policy must be on an active, publicly accessible, non-geofenced URL, and it says no PDFs. It must also be non-editable, so a shared document that anyone can change is a poor choice. The simplest fix is a plain web page on your own domain that you update when your data practices change.

Do I need a website for deep links to open my app?

For links that open your app straight from a web address, yes. Apple's Universal Links need an apple-app-site-association file in the .well-known folder of your website, served over HTTPS with no redirects. Android App Links need an assetlinks.json file at the same kind of address. Both prove you own the domain. Without them, links open in the browser or Android shows a chooser.

Start a project

Thinking about a build?

A free 30-minute call with one of our engineers. You leave with a first-release scope, a realistic timeline and a price range, whether or not we work together.

  • A first-release scope
  • A realistic timeline
  • A written quote, fixed-price or hourly

Written scope and quote after the call. NDA on request. You own the code.

Prefer email?

Send one question about your app, software or AI idea. An engineer replies within one business day.