macOS 27.3 Privacy Changes: How to Prepare Your App

macOS 27.3 Privacy Changes: How to Prepare Your App

Written by

in

Quick answer: Update your Mac app’s onboarding to explain why it requests access and prepare it to work with access to only selected folders or apps. Previously granted permissions remain in effect; developers of eligible backup and assistive technology apps can request entitlements for the prior experience on new installations.

What changed

Apple announced changes to Device Control and Data Access and Full Disk Access in macOS 27.3 beta 2. The changes give users more visibility into the data an app can access or control, along with more granular choices when approving new requests.

Device Control and Data Access is being split into two settings: System & App Protection Override and Accessibility. Apple also describes a single permission-granting method in which users select the requesting app from a list.

The updated experience encourages users to grant access only to the apps needed for a workflow under System & App Protection Override, or only to the necessary folders under Full Disk Access. Users will also have an option to configure apps to ask each time they require access. A transparency indicator will appear when a requesting app controls another app using System & App Protection Override.

Apple says permissions users have already granted will remain in effect. The new approval experience matters when users approve new app permission requests, including requests associated with new installations.

Who is affected

Review the announcement if your Mac app uses Device Control and Data Access or Full Disk Access. In particular, check workflows that depend on controlling another app or reading files across multiple folders. Your app should be prepared for users to authorize a narrower scope than the full access it requests.

The entitlement announcement is more specific. Developers of apps that use Full Disk Access for disk backup, or the new Accessibility settings to provide assistive technologies, can request entitlements intended to preserve the experience they offered before macOS 27.3 for new installations. Apple says currently known apps are not affected and will keep the same experience without an entitlement. It has not yet provided the additional entitlement details.

Previously granted permissions and the entitlement provision are separate points: existing user grants remain in effect, while the announced entitlements concern the experience for eligible new installations. Do not assume that every app using Full Disk Access or Accessibility qualifies for an entitlement based on this announcement alone.

What you need to do

  1. Identify the workflows that depend on broad access. List the features that need to read user files or control other apps. For each feature, identify which folders or target apps are actually necessary. This gives you a basis for explaining the request and checking whether the feature can operate with a limited grant.

  2. Review your onboarding instructions. Update any instructions that describe Device Control and Data Access as a single setting. Explain the purpose of the permission your workflow needs, and account for Apple’s new method of selecting the requesting app from a list. Avoid promising that a user must grant unrestricted access if a narrower grant is sufficient.

  3. Handle limited access as a normal outcome. Apple explicitly advises developers to handle access to only a limited set of folders or apps gracefully. For example, a file-processing workflow should avoid presenting an entire operation as successful if it could access only some of the intended folders. Make clear which part of the workflow needs additional access and let the user decide whether to grant it.

  4. Prepare for repeat requests and visible control. Consider how your workflow will behave if a user configures the app to ask every time access is required. Keep explanations close to the action that needs access so the request has context. If your app controls another app using System & App Protection Override, account for the transparency indicator in user-facing guidance rather than implying that control is invisible.

  5. Check the entitlement announcement against your use case. If your app uses Full Disk Access for disk backup or the new Accessibility settings for assistive technologies, review Apple’s entitlement option for new installations. Apple says further details are coming, so avoid building your release plan around an assumed entitlement name, application process, or approval timeline.

  6. Test new requests separately from existing grants. On macOS 27.3 beta 2, review the experience when your app makes a new permission request. Also check how your app behaves with previously granted access, which Apple says remains in effect. Exercise the limited-access paths your app supports and verify that its instructions and messages match what the user encounters.

Key dates

  • November 16, 2026: Apple published the announcement and said the changes were introduced in macOS 27.3 beta 2.

Apple did not provide a general-release date or an entitlement deadline in the announcement.

FAQ

Will users lose permissions they already granted?

Apple says all previously granted app permissions remain in effect. Users see the updated experience when approving new app permission requests. Developers should still check their app’s behavior when a user grants only a limited scope for a new request.

Does every app that uses Full Disk Access need an entitlement?

Apple did not say that. It announced an entitlement option for developers using Full Disk Access for disk backup and for developers using the new Accessibility settings to provide assistive technologies. The option is intended to preserve the earlier experience for eligible new installations; more details are forthcoming.

Should my app request access to every folder or app it can use?

Ask for the access the user’s chosen workflow requires, and design for a narrower grant. Apple says the updated experience encourages users to allow only specific folders or apps where appropriate. Your onboarding should explain the relevant access without suggesting that a broader grant is always necessary.