Most rejections for a small business app come from a short list: it's just a website, the privacy answers are missing, the reviewer can't log in, there's no way to delete an account, or there's placeholder content left in.
A rejection isn't a verdict on your business. It's an email from a reviewer who opened your app, couldn't get through it, or found something on a checklist. Most of the time the cause is on a short list, and most of that list is avoidable if you know it's there.
The rules below come from Apple's own App Store Review Guidelines, with the guideline number so you can read the original. The advice on how to meet them is ours. We haven't had an app of our own reviewed yet, and we'll say more about that at the end. So this is a post about what the rules say and where we expect small businesses to trip, not a list of our war stories.
01It looks like a website in a box
This is the big one for small businesses. Guideline 4.2 says your app should include features, content and UI that elevate it beyond a repackaged website, and that if it isn't particularly useful, unique or "app-like," it doesn't belong on the App Store.
If your plan is to take your website, put it in a wrapper and submit it, this is the guideline that applies to you. A wrapped app isn't banned by name, but Apple expects it to offer more than the site does. That usually means something that works because it's an app: notifications that matter, a feature that uses the phone's camera or location, something that works without a signal, or an experience built for the way people use a phone.
Two neighbors of 4.2 are worth knowing. Guideline 4.2.2 says that other than catalogs, apps shouldn't primarily be marketing materials, advertisements, web clippings, content aggregators or a collection of links. And 4.2.6 says apps made from a commercialized template or app generation service will be rejected unless submitted directly by the provider of the app's content. If someone is offering to make you an app in an afternoon from a template, read that one first.
The short test: if the honest answer to "what does the app do that the website doesn't" is "nothing," a reviewer will ask the same question.
02The privacy answers are missing or wrong
Guideline 5.1.1 requires every app to link to a privacy policy, both in the App Store Connect metadata and inside the app in an easily accessible place. The policy has to say what data the app collects, how, and what it's used for. It has to explain retention and deletion, and how someone can ask for their data to be deleted.
On top of that, Apple's App Privacy details page says that you must provide information about your app's privacy practices, including those of third-party partners whose code you add, and that the information is required to submit new apps and app updates. It lists a public privacy policy URL as required.
The trap for a small business is the third-party code. An analytics tool, a crash reporter or a notification service all collect something. If your answers say you collect nothing and the app contains an analytics tool, that's a mismatch. List what the app actually does.
03The reviewer can't log in
Guideline 2.1 says that if your app includes a login, you should include demo account info, and turn on your back-end service. It's a bigger deal than it sounds. A reviewer who can't get past the sign-in screen can't review the app, and a rejection is likely.
So make a real demo account, put the credentials in the review notes, and check that it works from a clean install on a phone that has never seen your app. Make sure whatever the demo account sees has real content in it. An empty account tells the reviewer nothing.
If you can't provide a demo account for legal or security reasons, Apple says you can build in a demo mode with prior approval, and the mode should show the app's full features.
04No way to delete an account
If your app lets people create an account, it has to let them delete it from inside the app. Apple's account deletion page says apps that support account creation must also let people initiate deletion within the app, and the guideline repeats it (5.1.1). Apple says apps shouldn't make people send an email or go through a support flow to delete an account, so a contact form or an "email us" note is a risky shortcut.
Build the delete button at the same time as the sign-up button. It's a small feature and it's much cheaper then.
05Placeholder content and unfinished pages
Also from 2.1: submissions should be final versions with all necessary metadata and fully functional URLs, and placeholder text, empty websites and other temporary content should be scrubbed before submission. A support link that goes to a page that doesn't exist, a "lorem ipsum" in a corner, a screenshot from the design stage. They're all things a reviewer will find, because finding them is the job.
Apple also says it rejects bundles that crash or show obvious technical problems, so test on a real phone, not just in a simulator.
06A checklist before you submit
- The app does something a website alone wouldn't.
- A privacy policy page is live, linked in the store listing and inside the app.
- The privacy answers match every tool inside the app.
- A demo login works on a fresh install, with real content behind it.
- Account deletion works from inside the app.
- No placeholder text, dead links or temporary screenshots.
- It's been tested on a real device.
07What this means for our own
We'll be direct about where we are. Dry Run, our free practice trading app, has an iPhone version that is built and running on our own phone. It's a shell around the website with a few native touches, and that's exactly the shape Guideline 4.2 is written about. It hasn't been submitted, store enrollment is in progress, and we're not assuming it'll sail through. When it's reviewed, whatever Apple says will go into this post. The timeline post already allows for a review round for the same reason.
08Quick answers
What is the most common reason a small business app is rejected?
We can't give you a ranking from data we don't have. The reason most likely to apply to a small business is Guideline 4.2, an app that is just a repackaged website.
Do I need a privacy policy for a simple app?
Yes. Apple's guideline 5.1.1 requires a link to a privacy policy for all apps, and its privacy details page lists the policy URL as required.
Do I have to give the reviewer a login?
If the app has a login, yes. Guideline 2.1 asks for demo account info, and for your back end to be turned on.
Is a rejection permanent?
Apple's guidelines describe an appeals process and the chance to fix and resubmit. A rejection usually means changes needed, not a ban.
09Next step
If you'd like a second pair of eyes on an app before it goes to a reviewer, or you want to know what would count as an app and not a website in a box, tell us what you have. The costs behind all of this are in what a small business app really costs, and the shape of what we build is on the mobile apps page.