# App Store Guideline 2.5.14: recording without consent or indication
> Apple rejected the app under Guideline 2.5.14 for recording the camera, microphone, screen or user input without consent and a clear indicator. The fix.
Canonical: https://app369.com/fix/app-store-guideline-2-5-14-recording-consent/
Last updated: 2026-11-09
Guideline 2.5.14 is the App Store rule that apps ask for explicit consent and show a clear indicator while they record or log user activity. It covers the camera, microphone, screen recordings and other user inputs.
**Short answer**
Find every place the app records, logs or captures what the user does, including AI note takers, session replay SDKs and voice features. Ask for explicit consent before the first recording, show a visible or audible indicator for as long as it runs, and consider an easy way to stop. Then reply in App Review with where the consent and indicator appear.
Rather not fix it yourself? [**App Fix Ticket**](https://app369.com/fixed-price/flutter-firebase-bug-fix/) starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.
## **What triggers 2.5.14, and the fix**
1. 01 ### **Recording starts without asking**
> “Apps must request explicit user consent and provide a clear visual and/or audible indication when recording, logging, or otherwise making a record of user activity.” [**Apple, Guideline 2.5.14**](https://developer.apple.com/app-store/review/guidelines/#2.5.14) A meeting recorder or voice assistant that starts on launch, or right after the system permission, has not asked for consent to record. Add an in-app consent step that says what is recorded and why, then start.
2. 02 ### **No indicator while it runs**
> “This includes any use of the device camera, microphone, screen recordings, or other user inputs.” [**Apple, Guideline 2.5.14**](https://developer.apple.com/app-store/review/guidelines/#2.5.14) The user can’t tell that recording is still on after leaving the screen. Keep a visible badge, banner or timer on screen, or a sound cue, for the whole session.
3. 03 ### **An SDK logs user input in the background** Session replay and analytics tools can capture taps, typing and screens. Turn off input and screen capture in the SDK, or put it behind the same consent and indicator.
4. 04 ### **App Review could not find the consent step** Also check: if consent sits deep in settings, App Review may miss it. Describe the steps in App Review notes and include a screen recording of the consent and the indicator.
Checked against the vendor’s docs on November 9, 2026: [App Store Review Guidelines: 2.5.14](https://developer.apple.com/app-store/review/guidelines/#2.5.14); [Apple: App Review (replying and appeals)](https://developer.apple.com/distribute/app-review/).
## **Rather hand it over?**
Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.
**Resubmit before Apple’s holiday slowdown**
Pay for the Diagnosis and send the rejection and access to the app by Monday, December 7 (US Eastern). The Diagnosis is back by Thursday, December 10. Pay for the Fix that day and it arrives as a pull request by Thursday, December 17, in time to build and resubmit before December 20.
In past years Apple said reviews may take longer around the holidays: [December 20 to 26 in 2024 (opens in a new tab)](https://developer.apple.com/news/?id=iwvebnw2), [December 22 to 27 in 2023 (opens in a new tab)](https://developer.apple.com/news/?id=uijoypq9), [December 23 to 27 in 2022 (opens in a new tab)](https://developer.apple.com/news/?id=xpkhwg3l). Apple hasn’t posted its 2026 dates yet (checked October 30). Approval stays Apple’s decision.
- [from $450**App Fix Ticket**One reproducible bug in an existing mobile or web app, diagnosed and fixed.**See scope and start**](https://app369.com/fixed-price/flutter-firebase-bug-fix/)
[**All 127 Fiverr reviews**](https://app369.com/reviews/)
Related: [**App Store Guideline 5.1.1 (data collection)**](https://app369.com/fix/app-store-guideline-5-1-1-data-collection/) · [**App Store Guideline 5.1.2 (data use and sharing)**](https://app369.com/fix/app-store-guideline-5-1-2-data-use-and-sharing/) · [**App Store Guideline 2.5.4 (background modes)**](https://app369.com/fix/app-store-guideline-2-5-4-background-modes/) · [**App Store Guideline 2.5.1**](https://app369.com/fix/app-store-guideline-2-5-1-software-requirements/)
Questions
## **More on this rejection**
**Should I reply to App Review or appeal? **+
Reply first. Apple says you can correspond with App Review in App Store Connect to resolve the issues before resubmitting, which is the place for a demo account, a screen recording or an explanation. Appeal to the App Review Board only if you believe App Review misunderstood the app or treated you unfairly. Apple allows one appeal per rejected submission and asks for specific reasons the app complies.
**Is the iOS permission prompt enough consent? **+
Treat it as not enough. The system prompt grants access to the microphone or camera; 2.5.14 separately asks for explicit consent and a clear indication while recording.
**Can you fix it for me? **+
Yes, through the App Fix Ticket: you send the rejection message and access to the app, Simon writes a diagnosis of what App Review hit and how to fix it, then fixes the code so you can resubmit. Each step has a fixed price, paid upfront. Approval stays Apple’s decision; the ticket covers the fix.
A different error?
## **Describe it and get a written quote**
Send the error and what you were doing. You get a written scope, a fixed price and a timeline; Simon replies by email, usually within one business day.
[**Describe your problem **→](https://app369.com/contact/) [**All fixes**](https://app369.com/fix/)