Ahead of the release of iOS 8 and HealthKit, Apple has updated its App Store review guidelines, warning developers to keep HealthKit data out of iCloud.
Ahead of Apple's September 9 media event, where it's expected to unveil up to two new iPhones and possibly a wearable device, Apple has listed new dos and don'ts that it will be judging any apps submitted for App Store review against.
The updated version of its App Store Review Guidelines now explains how apps should use new iOS 8 features, including the HomeKit and HealthKit frameworks, its app beta testing program TestFlight, and the new app extensions framework for inter-app data-sharing.
Apple has already said that selling HealthKit data to ad networks would violate its, while the new review guidelines clarify further constraints. Apple warns that: "apps using the HealthKit framework that store users' health information in iCloud will be rejected."
The guidance is not surprising given the sensitivity and regulation of health data, but comes on the heels of.
Apple yesterdayfacilitated the leak, pointing instead to hackers compromising some celebrities' iCloud accounts through user names, passwords and security questions.
Similar to its recent review, apps using HealthKit need to comply with applicable laws in each territory where they're made available.
Similar restrictions on disclosure and advertising apply to apps that use its HomeKit framework for home automation apps. "Apps must not use data gathered from the HomeKit APIs for advertising or other use-based data mining," Apple states. Apps that use HomeKit also need to provide home automation services, and clearly mark that they use HomeKit.
As Apple noted in its, the company will reject beta apps. The company's official beta testing program, TestFlight, caters to unfinished apps, but still comes with strict rules, including that they must comply with the full App Review Guidelines and be intended for public distribution. Developers will need to submit apps for review whenever a build contains material changes to content or functionality, and mustn't compensate testers for trying out the app.