Requesting Permission

Users must grant permission for an app to access personal information, including the current location, calendar, contact information, reminders, and photos. Although people appreciate the convenience of using an app that has access to this information, they also expect to have control over their private data. For example, people like being able to automatically tag photos with their physical location or find nearby friends, but they also want the option to disable such features.

μ‚¬μš©μžλŠ” 앱이 ν˜„μž¬ μœ„μΉ˜, μΊ˜λ¦°λ”, μ—°λ½μ²˜ 정보, μ•Œλ¦Ό 및 사진 λ“±μ˜ 개인 정보에 μ•‘μ„ΈμŠ€ ν•  μˆ˜μžˆλŠ” κΆŒν•œμ„ λΆ€μ—¬ν•΄μ•Όν•©λ‹ˆλ‹€. μ‚¬λžŒλ“€μ€μ΄ 정보에 μ•‘μ„ΈμŠ€ ν•  μˆ˜μžˆλŠ” 앱을 μ‚¬μš©ν•˜λŠ” 편리 성을 잘 μ•Œκ³  μžˆμ§€λ§Œ 개인 데이터λ₯Ό μ œμ–΄ ν•  수 있기λ₯Ό κΈ°λŒ€ν•©λ‹ˆλ‹€. 예λ₯Ό λ“€μ–΄ μ‚¬λžŒλ“€μ€ 사진을 μ‹€μ œ μœ„μΉ˜μ— μžλ™μœΌλ‘œ νƒœκ·Έν•˜κ±°λ‚˜ κ°€κΉŒμš΄ 친ꡬλ₯Ό 찾을 μˆ˜μžˆλŠ” 것을 μ’‹μ•„ν•˜μ§€λ§Œ κ·ΈλŸ¬ν•œ κΈ°λŠ₯을 μ‚¬μš©ν•˜μ§€ μ•Šλ„λ‘ μ„€μ •ν•  μˆ˜λ„ μžˆμŠ΅λ‹ˆλ‹€.

Request personal data only when your app clearly needs it. It’s natural to be suspicious of a request for personal information, especially if there’s no obvious need for it. Make sure permission requests occur only when people are using features that clearly need personal data. For example, an app might only request access to the current location when activating a location tracking feature.

앱이 λͺ…ν™•ν•˜κ²Œ ν•„μš”ν•  λ•Œλ§Œ 개인 데이터λ₯Ό μš”μ²­ν•˜μ‹­μ‹œμ˜€. 특히 개인 정보가 ν•„μš”ν•˜μ§€ μ•Šμ€ 경우 개인 정보 μš”μ²­μ— λŒ€ν•΄ μ˜μ‹¬μŠ€λŸ¬μš΄ 것은 λ‹Ήμ—°ν•©λ‹ˆλ‹€. μ‚¬λžŒλ“€μ΄ 개인 데이터가 λΆ„λͺ…νžˆ ν•„μš”ν•œ κΈ°λŠ₯을 μ‚¬μš©ν•˜λŠ” κ²½μš°μ—λ§Œ κΆŒν•œ μš”μ²­μ΄ λ°œμƒν•˜λŠ”μ§€ ν™•μΈν•˜μ‹­μ‹œμ˜€. 예λ₯Ό λ“€μ–΄ 앱은 μœ„μΉ˜ 좔적 κΈ°λŠ₯을 ν™œμ„±ν™” ν•  λ•Œ ν˜„μž¬ μœ„μΉ˜μ— λŒ€ν•œ μ•‘μ„ΈμŠ€ 만 μš”μ²­ν•  수 μžˆμŠ΅λ‹ˆλ‹€.

Explain why your app needs the information. Provide custom text (known as a /purpose string/ or /usage description string/ ) for display in the system's permission request alert, and include an example. Keep the text short and specific, use sentence case, and be polite so people don't feel pressured. There’s no need to include your app nameβ€”the system already identifies your app. For developer guidance, see Protecting the User's Privacy.

앱에 정보가 ν•„μš”ν•œ 이유λ₯Ό μ„€λͺ…ν•˜μ‹­μ‹œμ˜€. μ‹œμŠ€ν…œμ˜ κΆŒν•œ μš”μ²­ 경고에 ν‘œμ‹œ ν•  μ‚¬μš©μž μ§€μ • ν…μŠ€νŠΈ (/ λͺ©μ  λ¬Έμžμ—΄ / λ˜λŠ” / μ‚¬μš©λ²• μ„€λͺ… λ¬Έμžμ—΄ /)λ₯Ό μ œκ³΅ν•˜κ³  예제λ₯Ό μ œκ³΅ν•˜μ‹­μ‹œμ˜€. ν…μŠ€νŠΈλ₯Ό μ§§κ³  ꡬ체적으둜 μœ μ§€ν•˜κ³  λ¬Έμž₯을 μ‚¬μš©ν•˜λ©° μ‚¬λžŒλ“€μ΄ 압박감을 λŠλΌμ§€ μ•Šλ„λ‘ μΉœμ ˆν•©λ‹ˆλ‹€. μ•± 이름을 ν¬ν•¨μ‹œν‚¬ ν•„μš”κ°€ μ—†μŠ΅λ‹ˆλ‹€. μ‹œμŠ€ν…œμ—μ„œ 이미 앱을 μ‹λ³„ν•©λ‹ˆλ‹€.

Request permission at launch only when necessary for your app to function. Users won’t be bothered by this request if it’s obvious that your app depends on their personal information to operate.

μ•± 싀행에 ν•„μš”ν•œ κ²½μš°μ—λ§Œ μ‹€ν–‰ κΆŒν•œμ„ μš”μ²­ν•˜μ‹­μ‹œμ˜€. κ·€ν•˜μ˜ 앱이 개인 정보에 μ˜μ‘΄ν•˜μ—¬ μž‘λ™ν•˜λŠ” 것이 λͺ…λ°±ν•œ 경우 μ‚¬μš©μžλŠ”μ΄ μš”μ²­μœΌλ‘œ 인해 κ³ λ―Όν•˜μ§€ μ•Šμ„ κ²ƒμž…λ‹ˆλ‹€.

Don’t request location information unnecessarily. Before accessing location information, check the system to see whether Location Services is enabled. With this knowledge, you can delay the alert until a feature truly requires it, or perhaps avoid the alert altogether. To learn how to implement location features, see MapKit and Location and Maps Programming Guide.

μœ„μΉ˜ 정보λ₯Ό λΆˆν•„μš”ν•˜κ²Œ μš”μ²­ν•˜μ§€ λ§ˆμ‹­μ‹œμ˜€. μœ„μΉ˜ 정보에 μ•‘μ„ΈμŠ€ν•˜κΈ° 전에 μœ„μΉ˜ μ„œλΉ„μŠ€κ°€ ν™œμ„±ν™”λ˜μ–΄ μžˆλŠ”μ§€ ν™•μΈν•˜μ‹­μ‹œμ˜€. 이 지식을 톡해 κΈ°λŠ₯μ—μ„œ μ§„μ •μœΌλ‘œ ν•„μš”λ‘œ ν•  λ•ŒκΉŒμ§€ κ²½κ³ λ₯Ό μ§€μ—°ν•˜κ±°λ‚˜ κ²½κ³ λ₯Ό ν”Όν•  수 μžˆμŠ΅λ‹ˆλ‹€.

Requesting Permission - App Architecture - iOS - Human Interface Guidelines - Apple Developer

Last updated