App Store 审核指南

https://developer.apple.com/cn/app-store/review/guidelines/#acceptable

ios审核被拒3.2.1

https://www.jianshu.com/p/a2a766b97a35

您好，本账号（北京会员宝移动网络科技有限公司），已经成为账号（北京和融通支付科技有限公司）的开发团队。因为这2个公司的企业法人都是“黄师田”，品牌“会员宝”已经在市场发展5年，按照业务发展需要，本APP（会员宝收银台），必须以“会员宝”开头，请给予支持，并审核通过，谢谢！~
北京会员宝移动网络科技有限公司的开发者账号hybunion@hrtpayment.com，已成为北京和融通支付科技有限公司的开发者账号hrtvaluecard@hecard.com.cn的开发团队，请查阅。

 https://www.sohu.com/a/209983544_274033

1、因为您的登录密码输入错误，所以登录失败了。请您仔细输入密码123apple。
请注意我们键盘是自定义的，需要切换数字键盘和字母键盘。请您依次输入数字1、2、3，点击“ABC”，切换到字母键盘，依次输入字符apple。

2、其他电子材料，请见附件或者App审核信息里的附件。
请注意，北京和融通支付科技有限公司和北京会员宝移动网络科技有限公司，企业法人都是黄师田。APP品牌以“会员宝”开头，版权归北京和融通支付科技有限公司所有。
北京和融通支付科技有限公司营业执照网址：http://www.gsxt.gov.cn/%7B152DBA1B724B4B969E3F10292138F79E3F8D454D74C6DF7CEBD2BB1AA8B4EB4A65D7CE6DFAC30BD6BCD50862AA854D743952D57A249B27B7088F099926BD6FC46F476F476F309BC46F309BC4ECC8634BD7DFFB39FBD3785CF7DF8095B199411E3AE22059F44E2DE2FE8DB2BAA36C81AEC7CFF853F8EDC9C70FD2B870C20D053299B199B199B1-1547430167129%7D

北京会员宝移动网络科技有限公司营业执照网址：http://www.gsxt.gov.cn/%7BC5A46A92A2C29B1F4EB6C0A0F1B12717EF0495C4A44F0FF53B5B6B93783D3BC3B55E1EE42A4ADB5F6C5CD8EB7A0C9DFDE9DB05F3F412F73ED806D910F634BF4DBFCEBFCEBFC2B3E23596A50635AECFC93B4AD14AE9986AF19096EB6AC9986203F1265B2AB15268FEBB91F7A6E670C4B282D3BD4FBD6A1B4CDD596AFB1086D7B94B3A4B3A4B3A-1547430141596%7D

中国人民银行颁发的支付业务许可证
http://www.pbc.gov.cn/zhengwugongkai/127924/128041/2951606/1923625/1923629/2862029/index.html

附件包含营业执照、支付业务许可证、账户管理信息表（备付金集中交存）、印鉴卡。请查阅附件。

3、当用户注册我们的APP时，注册协议里有责任范围及责任限制、服务条款的解释、法律适用及争端解决。
注册协议网址：https://download.hybunion.com/aggrement.html
技术支持网址：http://www.hrtpayment.com/payBusiness.html?l=4
隐私协议网址：https://test.hybunion.com/download/appYinSiZhengCe.html

 

 

Guideline 3.2.1 - Business - Other Business Model Issues - Acceptable

We found that your app facilitates loan applications, but the seller and company names associated with your app do not reflect the financial institution in the app or its metadata, as required by Guideline 3.2.1(viii) of the App Store Review Guidelines.

Next Steps

To help us proceed with the review of your app, please provide the following information. The more information you can provide upfront, the sooner we can complete your review.

- Both a copy and the direct link to the government website of your Business License (营业执照)
- A copy of the Rectification Notification issued by the relevant governing authority to your company (当地金融办 (局) 下发给贵公司的「整改通知书」附件)
- A copy of the proof that your company is connected to a bank’s depository system (银行存管证明)
- Your app’s and service’s Terms & Conditions. 
- In the case of dispute, what resolution mechanism does your app and service offer? 
- What is your responsibility in such case? Is such responsibility stated clearly in the Terms & Conditions? 
- How will the involved parties trace one another?

Additionally, please ensure your app’s Support and Privacy URLs in the metadata direct users to the webpages with appropriate information.

Please attach documentary evidence in the App Review Information section in App Store Connect. In accordance with section 3.2(f) of the Apple Developer Program License Agreement, you acknowledge that submitting falsified or fraudulent documentation can result in the termination of your Apple Developer Program account and the removal of your apps from the App Store. Once Legal has reviewed your documentation and confirms its validity, we will proceed with the review of your app.

发件人Apple
3. 2.1业务：其他业务模式问题 - 可接受
5. 1.1法律：隐私 - 数据收集和存储
准则3.2.1 - 业务 - 其他业务模式问题 - 可接受

我们发现您的应用程序有助于贷款申请，但与应用程序相关联的卖家和公司名称并未反映应用程序中的金融机构或其元数据，这是App Store审查指南的准则3.2.1（viii）所要求的。

下一步

为帮助我们继续审核您的应用，请提供以下信息。您可以提前提供的信息越多，我们就能越早完成您的审核。

- 副本和直接链接到营业执照的营业执照的*网站
- 相关管理机构向贵公司发出的整改通知书副本（当地金融办（局）下发给贵公司的“整改通知书”附件）
- 贵公司与银行存款系统相连的证明副本（银行存管证明）
- 您的应用和服务的条款和条件。
- 如有争议，您的应用和服务提供什么解决方案？
- 在这种情况下，您有责任吗？条款和条件中是否明确规定了此类责任？
- 相关各方将如何相互追踪？

此外，请确保元数据中的应用支持和隐私URL将用户引导至具有适当信息的网页。

请在App Store Connect的App Review Information部分附上文档证据。根据Apple开发人员计划许可协议第3.2（f）节，您承认提交伪造或欺诈性文档可能导致Apple Developer Program帐户终止并从App Store中删除您的应用程序。一旦Legal审核了您的文档并确认其有效性，我们将继续审核您的应用。

准则5.1.1 - 法律 - 隐私 - 数据收集和存储

我们注意到您的应用请求用户同意访问其联系人，但未明确在权限模式警报中使用此功能。

下一步

要解决此问题，请修改权限模式警报，以指定应用程序请求访问用户联系人的原因。

权限请求警报应指定您的应用如何使用此功能来帮助用户了解您的应用请求访问其个人数据的原因。

资源

有关配置和显示警报的其他信息和说明，请查看iOS人机界面指南的“请求权限”部分和“信息属性列表”主要参考。您可能还需要查看技术问答QA1937：解决隐私敏感数据应用程序拒绝页面，以获取有关如何提供权限请求警报的使用说明的详细信息。

了解有关保护用户隐私的更多信息。

请参阅随附的屏幕截图了解详情

 

 

2019年1月17日 上午1:11
发件人 Apple
3. 2.1 Business: Other Business Model Issues - Acceptable
Guideline 3.2.1 - Business - Other Business Model Issues - Acceptable

The seller and company names associated with your app do not reflect the financial institute name in the app or its metadata, as required by Guideline 3.2.1(viii) of the App Store Review Guidelines.

Next Steps

Your app must be published under a seller name and company name that reflects the financial institutions name. If you have developed this app on behalf of a client, please advise your client to add you to the development team of their Apple Developer account.

Please note that submitting documentation showing permission to publish this app on behalf of the financial institution will not resolve this issue. This app must be submitted under the financial institution’s own Apple Developer account.

Once created, you cannot change your seller name or company name in App Store Connect. For assistance with changing your company name or seller name, you will need to contact us. Select Membership and Account to request an update to your Apple Developer account information.

 

Guideline 3.2.1 - Business - Other Business Model Issues - Acceptable

We found that your app facilitates loan applications, but the seller and company names associated with your app do not reflect the financial institution in the app or its metadata, as required by Guideline 3.2.1(viii) of the App Store Review Guidelines.

Next Steps

To help us proceed with the review of your app, please provide the following information. The more information you can provide upfront, the sooner we can complete your review.

- Both a copy and the direct link to the government website of your Business License (营业执照)
- A copy of the Rectification Notification issued by the relevant governing authority to your company (当地金融办 (局) 下发给贵公司的「整改通知书」附件)
- A copy of the proof that your company is connected to a bank’s depository system (银行存管证明)
- Your app’s and service’s Terms & Conditions. 
- In the case of dispute, what resolution mechanism does your app and service offer? 
- What is your responsibility in such case? Is such responsibility stated clearly in the Terms & Conditions? 
- How will the involved parties trace one another?

Additionally, please ensure your app’s Support and Privacy URLs in the metadata direct users to the webpages with appropriate information.

Please attach documentary evidence in the App Review Information section in App Store Connect. In accordance with section 3.2(f) of the Apple Developer Program License Agreement, you acknowledge that submitting falsified or fraudulent documentation can result in the termination of your Apple Developer Program account and the removal of your apps from the App Store. Once Legal has reviewed your documentation and confirms its validity, we will proceed with the review of your app.

Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage

We noticed that your app requests the user’s consent to access their contacts but does not clarify the use of this feature in the permission modal alert.

Next Steps

To resolve this issue, please revise the permission modal alert to specify why the app is requesting access to the user's contacts.

The permission request alert should specify how your app will use this feature to help users understand why your app is requesting access to their personal data.

Resources

For additional information and instructions on configuring and presenting an alert, please review the Requesting Permission section of the iOS Human Interface Guidelines and the Information Property List Key Reference. You may also want to review the Technical Q&A QA1937: Resolving the Privacy-Sensitive Data App Rejection page for details on how to provide a usage description for permission request alerts.

Learn more about Protecting the User’s Privacy.

Please see attached screenshot for details.