New Apple App Store Rules in 2026: A Compliance Checklist for Small Business Apps

If your small business has an app on the App Store, 2026 is not a quiet year to sit back and ignore your developer dashboard. Apple has rolled out a stack of policy and technical changes this year that affect how apps get approved, what you have to disclose, and how old an app is allowed to be before it gets pulled. None of this is optional, and none of it fixes itself. If you haven't touched your app's settings or metadata in a while, now is a good time to check.

This isn't a doom-and-gloom post. Most of these changes are manageable in an afternoon or two, especially if you catch them before Apple flags your app. Below is a plain-English rundown of what's changed, who it affects, and a checklist you can actually work through.

Why This Matters Now, Not Later

App Store review has always evolved, but 2026 bundled several changes together: a hard SDK deadline, new AI transparency rules, a fresh disclosure requirement for apps with social features, and stricter accessibility review. Miss one of these and the risk isn't a warning email — it's your app being rejected on the next update, or in some cases removed from the store entirely.

For a small business, that's not an abstract inconvenience. If your app is how customers book appointments, order food, manage loyalty points, or check on a service, even a few days of downtime while you scramble to fix a compliance issue can mean lost revenue and frustrated customers.

What Actually Changed

1. Older Apps Need to Be Rebuilt on Current SDKs

Apple has been tightening its policy that apps must be built against a recent SDK version, and 2026 pushed this further: new submissions and updates increasingly need to target the current generation of iOS, iPadOS, and related SDKs, and apps that haven't been meaningfully updated in a few years are at real risk of removal from the store.

If your app was built years ago by a developer who's no longer around, or it was a one-and-done project from a previous agency, this is the change most likely to catch you off guard. Rebuilding against a current SDK isn't always a huge lift, but it does require someone who can open the project, update dependencies, and resubmit — which is harder to do at the last minute than it sounds.

2. AI Features Now Require Disclosure

If your app uses any kind of AI — a chatbot, a recommendation engine, AI-generated content, an AI-powered search feature — Apple now expects you to be upfront about it. That includes:

• Declaring which AI models and third-party AI SDKs your app uses
• Explaining what data those models have access to and how it's shared
• Clearly labeling AI-generated content so users know what they're looking at
• Confirming you actually have the rights to the data your AI features are trained on or pull from

This is part of a broader shift toward transparency in how apps use AI, and it's not unique to Apple — expect similar expectations from Google Play and from privacy-conscious customers regardless of platform. If you added an AI chatbot or AI-powered feature to your app in the last year or two, go back and make sure your App Store listing and in-app disclosures actually reflect what that feature does.

3. Social Features Need Explicit Disclosure

If your app includes any social media capability — sharing to a feed, user-to-user messaging, comments, community features — Apple now requires you to explicitly indicate that when you submit updates. This is a newer requirement, and it's easy to overlook if social isn't the main point of your app but is baked into a smaller feature, like a review or community tab.

4. Accessibility Audits Are Part of Review

Accessibility compliance has moved from a nice-to-have to something Apple is actively checking during review, with an expectation that apps meet WCAG 2.2 Level AA standards. That covers things like sufficient color contrast, proper labeling for screen readers, usable touch targets, and support for text scaling.

This mirrors a trend we've already covered on this blog for websites — ADA compliance for small business websites — and now it's extending to mobile apps in a more formal way. If your app was never audited for accessibility, budget time for this before your next major update.

The One Piece of Good News: Free AI Compute for Small Business Program Members

If your business is enrolled in Apple's App Store Small Business Program — generally available to developers earning under a set annual threshold — there's an upside here. Apple has opened access to its on-device and private cloud AI models at no additional cloud API cost for eligible small business accounts. If you've been holding off on adding an AI feature because of API costs, this is worth a look before you rule it out.

What to Do If You Already Have an App

Start with an honest audit rather than assuming your app is fine. Here's a practical order of operations:

• Check when your app was last updated. If it's been more than a year, treat an SDK update as a priority, not a someday task.
• List every AI feature in your app, even small ones like smart search or auto-suggestions, and confirm they're disclosed correctly in App Store Connect.
• Flag any social functionality, including things you might not think of as social — reviews, sharing buttons, in-app messaging between users.
• Run an accessibility pass on your core user flows: sign-up, checkout, booking, or whatever your main conversion action is.
• Check your Small Business Program eligibility if you're not already enrolled — it affects both commission rates and now AI compute access.

What to Do If You're Building a New App

If you're starting fresh, you're in a better position — build compliance in from day one instead of retrofitting it later. That means:

• Choosing a current, actively maintained framework and SDK from the start
• Designing your AI features with disclosure and data-rights documentation in mind, not as an afterthought before submission
• Running accessibility checks during design and development, not just before you submit
• Budgeting time in your launch timeline for App Store review, which can take longer when new policy areas like AI disclosure are involved

Don't Forget Google Play

Everything above is specific to Apple, but if your app is also on Google Play, don't assume you're in the clear. Google has its own, separately evolving requirements around AI transparency, data safety disclosures, and accessibility. The smart move is to treat compliance review as a recurring part of your release cycle for both platforms, not a one-time fire drill.

The businesses that struggle with these changes are usually the ones treating their app like a website they built once and forgot about. Apps need the same ongoing attention as anything else customer-facing.

A Quick Compliance Checklist

• App built and submitted against a current SDK
• All AI features declared and disclosed, including third-party AI SDKs
• AI-generated content clearly labeled for users
• Data rights confirmed for anything feeding your AI features
• Social capabilities identified and disclosed at submission
• Core user flows checked against WCAG 2.2 AA accessibility standards
• Small Business Program enrollment confirmed or applied for
• Google Play policies checked separately, not assumed to match Apple's

If This Feels Like a Lot

It can be, especially if you're running a business and an app is just one of many things on your plate. That's normal. The point of this checklist isn't to make you panic about your app going down tomorrow — it's to make sure you're not finding out about a rejection the week before a big product launch or busy season.

If you'd rather have someone who does this daily take a look at where your app stands, get in touch with our team. We can review your current app against these requirements, handle the SDK and disclosure updates, and make sure your next submission goes through without surprises.