App Store 2.5.14 rejection: Recording consent and indicators

By The Draftbit team · Updated
Sources checked

This guide is for iPhone and iPad apps recording camera, microphone, screen, input, or other user activity.

A permission granted earlier doesn’t necessarily tell someone that recording is happening now. Apple’s 2.5.14 requires explicit consent and a clear visual or audible indication when the app records or logs user activity.

Check every recording path

Review audio/video features, screen capture, session replay, and analytics that record interactions. Include SDKs, which are libraries bundled into the app. We’d test both manual recording and capture that starts automatically after another action.

Make the recording understandable

Explain what’s recorded before it starts and obtain the required consent. Provide a clear indication while the recording is active. Align permission explanations and privacy disclosures with the actual data collected.

Test starting, stopping, cancelling, and denying permission. Check whether recording continues after a screen closes or the app changes state. Give Apple the consent screen, active indicator, and steps to verify them. If a third-party library records activity you don’t need, remove that recording rather than adding a misleading disclosure.

Messages this guide can help with

App Store 2.5.14 rejection; app store 2.5.14 denial; Guideline 2.5.14; Recording consent and indicators

Official sources

We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.

Your next stepSubmit your iPhone or iPad app for review