Security, privacy, permissions, and platform policy
Security and privacy shape the product boundary. The sandbox limits access, entitlements grant signed capabilities, purpose strings explain protected-resource requests, and privacy declarations describe relevant data and API use.
Design the boundary
- Request location only after the user chooses Add Location and explain the useful no-location path before the prompt.
- Model not determined, allowed, denied, restricted, unavailable, and revoked states when the framework exposes them.
- Keep sensitive values out of logs, analytics, URLs, preferences, and source control. Remove unused entitlements and background modes.
- Hidden controls are not authorization. Server and domain policy still enforce access.
Validation boundary
Permission prompts, entitlement signing, privacy manifests, transport policy, and review behavior require Apple targets and current policy review.
Series navigation
- Previous: Part 80: Persistence, Core Data, files, caches, migrations, and secure storage
- Next: Part 82: Background work, notifications, deep links, and app extensions
- Series index: Zero to iOS Hero