AppStore_隐私政策

从2018年10月3日开始，

App Store Connect将要求所有 新应用 和 应用 更新版本 时提供 隐私政策，

添加后才可以在App Store上提交  或  通过TestFlight外部测试进行分发。

---

苹果通知：

As a reminder,

in June the App Store Review Guidelines were updated to require a privacy policy

for all new apps and app updates as part of the app review process.

Starting October 3, 2018,

App Store Connect will require a privacy policy for all new apps and app updates

before they can be submitted for distribution on the App Store

or through TestFlight external testing.

In addition, your app’s privacy policy link or text will only be editable when you submit a new version of your app.

详情参见：https://developer.apple.com/news/?id=08312018a

 

---

所以，在此提醒各位开发者：

提交App Store 审核前一定要准备自己的隐私权政策，

并在app SafariViewContoller中弹出，

否则会无法通过审核哦！

---

为便于一些开发者准备隐私权政策的条款，我们已起草了一份隐私权政策的中文版本，

开发者可根据自己的业务场景进行修改，

点击可下载隐私权政策范本 苹果隐私条款。

或查看本文最后面的 附录2 和 附录3

---

附录1: 审核指南-隐私部分

 

5.1 Privacy

Protecting user privacy is paramount in the Apple ecosystem,

and you should use care when handling personal data to ensure you’ve complied with privacy best practices, applicable laws and the terms of the Apple Developer Program License Agreement, not to mention customer expectations.

More particularly:

---

• 5.1.1 Data Collection and Storage
  • (i) Privacy Policies: All apps must include a link to their privacy policy in the App Store Connect metadata field and within the app in an easily accessible manner.
  • The privacy policy must clearly and explicitly:
    • Identify what data, if any, the app/service collects, how it collects that data, and all uses of that data.
    • Confirm that any third party with whom an app shares user data (in compliance with these Guidelines) — such as analytics tools, advertising networks and third party SDKs, as well as any parent, subsidiary or other related entities that will have access to user data — will provide the same or equal protection of user data as stated in the app’s privacy policy and required by these Guidelines.
    • Explain its data retention/deletion policies and describe how a user can revoke consent and/or request deletion of the user’s data.

      ---

       

  • (ii) Permission Apps that collect user or usage data must secure user consent for the collection. Paid functionality must not be dependent on or require a user to grant access to this data. Apps must also provide the customer with an easily accessible and understandable way to withdraw consent. Ensure your purpose strings clearly and completely describe your use of the data.
  • Apps that collect data for a legitimate(合法的) interest without consent by relying on the terms of the European Union’s General Data Protection Regulation (“GDPR”) or similar statute
  • 《通用数据保护条例》（General Data Protection Regulation，简称GDPR）为欧洲联盟的条例，前身是欧盟在1995年制定的《计算机数据保护法》。
    2018年5月25日，欧洲联盟出台史上最严的《通用数据保护条例》。
  • must comply with all terms of that law.
  • Learn more about Requesting Permission.

    ---

     

  • (iii) Data Minimization: Apps should only request access to data relevant to the core functionality of the app
  • and should only collect and use data that is required to accomplish the relevant task.
  • Where possible, use the out-of-process picker or a share sheet rather than requesting full access to protected resources like Photos or Contacts.

    ---

     

  • (iv) Access 
  • Apps must respect the user’s permission settings and not attempt to manipulate, trick, or force people to consent to unnecessary data access.
  • For example, apps that include the ability to post photos to a social network must not also require microphone access before allowing the user to upload photos.
  • Where possible, provide alternative solutions for users who don’t grant consent.
  • For example, if a user declines to share Location, offer the ability to manually enter an address.

    ---

     

  • (v) Account Sign-In:
  • If your app doesn’t include significant account-based features, let people use it without a log-in.
  • Apps may not require users to enter personal information to function, except when directly relevant to the core functionality of the app or required by law.
  • If your core app functionality is not related to a specific social network (e.g. Facebook, WeChat, Weibo, Twitter, etc.),
  • you must provide access without a login or via another mechanism.
  • Pulling basic profile information, sharing to the social network, or inviting friends to use the app are not considered core app functionality.
  • The app must also include a mechanism to revoke social network credentials
  • and disable data