WWDC21 program is revealed, and will be available free to the more than 30 million Apple developers from 227 regions around the globe
WWDC21 kicks off with a keynote address June 7 at 10 a.m. PDT.
Apple unveiled the lineup for its annual Worldwide Developers Conference, including keynote and Platforms State of the Union timing, and shared more information on how developers will be able to learn about the future of iOS, iPadOS, macOS, tvOS, and watchOS. Free for all developers, WWDC21 will bring together the global Apple developer community and provide them with new insights into the technologies, tools, and frameworks they rely on. The conference will offer developers the opportunity to engage with one another, and directly with Apple engineers for guidance on building innovative and platform-differentiating apps and games.
June 7, 10 a.m. PDT
WWDC21 kicks off with the unveiling of exciting new updates coming to all Apple platforms later this year. Streamed directly from Apple Park, the keynote address will be available via apple.com, the Apple Developer app, the Apple TV app, and YouTube, with on-demand playback available after the conclusion of the stream.
Platforms State of the Union
June 7, 2 p.m. PDT
Take a deeper dive into the new tools, technologies, and advances across Apple platforms that will help Apple developers create even better apps. Platforms State of the Union will stream via the Apple Developer app and the Apple Developer website.
Apple Design Awards
June 10, 2 p.m. PDT
Every year, the Apple Design Awards celebrate the creative artistry, craftsmanship, and technical achievement of Apple developers. The Apple Design Awards will stream via the Apple Developer app and the Apple Developer website.
Access to Experts Featuring over 200 in-depth sessions, one-on-one labs, and more, WWDC21 will provide unprecedented access to Apple engineers and designers so developers can learn about the latest tools and technologies to help them create the next generation of apps. Apple Developer Program members can request one-on-one lab consultations with more than 1,000 Apple experts to ask questions about the latest APIs and best practices, and apply for user interface and design reviews. Apple engineers will also be available in Apple Developer Forums throughout the week to answer questions and engage in technical discussions. Beginning June 8, session videos will be posted each day and will be available in the Apple Developer app and on the Apple Developer website.
In addition to sessions and lab consultations with Apple engineers and designers, WWDC21 will feature special activities and events designed to celebrate developers and bring the community together. Try a coding or design challenge, learn from guest speakers, and more.
New for WWDC21, Pavilions provide an easy way for developers to explore relevant sessions, labs, and special activities for a given topic. Conference attendees can customize their WWDC experience and check out content organized around specific areas like SwiftUI, Developer Tools, Accessibility & Inclusion, and more — exclusively within the Apple Developer app.
On June 1, Apple will celebrate student developers from all over the world with the announcement of winners in the Swift Student Challenge, an opportunity for students of all ages to showcase their love of coding by creating their own Swift playground.
Developers are encouraged to download the Apple Developer app where additional WWDC21 information will be shared ahead of June 7.
Later this year, the App Store will help users understand an app’s privacy practices before they download the app on any Apple platform. On each app’s product page, users can learn about some of the data types the app may collect, and whether that data is linked to them or used to track them. You’ll need to provide information about your app’s privacy practices, including the practices of third-party partners whose code you integrate into your app, in App Store Connect. This information will be required to submit new apps and app updates to the App Store starting December 8, 2020.
Apple will begin requiring developers to provide more privacy details about their apps starting December 8, While this feature is not yet available to users, developers can already submit their privacy reports to the App Store.
Privacy labels have been introduced as a new iOS 14 and macOS Big Sur feature that will inform users about what data third-party apps can access, such as location, photos, and contacts. Each app will have its own privacy report on the App Store so that users can check this information before downloading the app.
The company shared in the Apple Developer portal exactly what it asks developers for the App Store privacy labels. We also checked on the App Store Connect portal how this process works for developers.
Once the developer chooses a specific app in the App Store Connect, there’s a new menu dedicated to App Privacy. From there, the platform guides the developer with everything needed for the new privacy labels. First, Apple asks if the app collects any user data — this also applies to third-party content such as advertisements from other platforms.
Next, the developer must select exactly what kind of personal information the app collects from the user. This includes contacts, health, financial information, location, sensitive information, personal content, browsing history, and more.
For each category, Apple requires details on the data collected. If you have an app that collects contact information, you need to tell Apple what that data is (name, email, phone number) and whether you use that data to track the user over the web or not.
Apps that collect financial information should tell Apple whether this is restricted to payment information such as credit card numbers or also things like salary and credit score. For apps that let users upload files, the developer must specify whether the app collects emails, text messages, photos, videos, or even gameplay content.
Apple will review privacy reports before showing them on the App Store. Once privacy labels are approved for an app, developers cannot modify them unless they launch an app update on the App Store.
The App Store will soon help users understand an app’s privacy practices before they download the app on the Apple platform. On each app’s product page, users can learn about some of the data types the app may collect, and whether that data is linked to them or used to track them.
This feature will be rolled out to users as of December 8. You can find more information about App Store’s new privacy labels on the Apple Developer website.
Answering app privacy questions
As you get ready to select your answers from the options presented in App Store Connect, keep in mind:
You need to identify all of the data you or your third-party partners collect, unless the data meets all of the criteria for optional disclosure listed below.
Your app’s privacy practices should follow the App Store Review Guidelines and all applicable laws.
You’re responsible for keeping your responses accurate and up to date. If your practices change, update your responses in App Store Connect. You may update your answers at any time, and you do not need to submit an app update in order to change your answers.
You’ll need to know the types of data that you and/or your third-party partners collect from your app before answering the questions in App Store Connect.
“Collect” refers to transmitting data off the device in a way that allows you and/or your third-party partners to access it for a period longer than what is necessary to service the transmitted request in real time.
“Third-party partners” refers to analytics tools, advertising networks, third-party SDKs, or other external vendors whose code you’ve added to your app.
Data types that meet all of the following criteria are optional to disclose:
The data is not used for tracking purposes, meaning the data is not linked with Third-Party Data for advertising or advertising measurement purposes, or shared with a data broker. For details, see the Tracking section.
The data is not used for Third-Party Advertising, your Advertising or Marketing purposes, or for Other Purposes, as those terms are defined in the Tracking section.
Collection of the data occurs only in infrequent cases that are not part of your app’s primary functionality, and which are optional for the user.
The data is provided by the user in your app’s interface, it is clear to the user what data is collected, the user’s name or account name is prominently displayed in the submission form alongside the other data elements being submitted, and the user affirmatively chooses to provide the data for collection each time.
If a data type collected by your app meets some, but not all, of the above criteria, it must be disclosed in App Store Connect.
Examples of data that may not need to be disclosed include data collected in optional feedback forms or customer service requests that are unrelated to the primary purpose of the app and meet the other criteria above.
For the purpose of clarity, data collected on an ongoing basis after an initial request for permission must be disclosed.
Types of data
Refer to the list of data types below and compare them to the data collection practices in your app.
Such as first or last name
Including but not limited to a hashed email address
Including but not limited to a hashed phone number
Such as home address, physical address, or mailing address
Other User Contact Info
Any other information that can be used to contact the user outside the app
Health and Fitness
Health and medical data, including but not limited to data from the Clinical Health Records API, HealthKit API, MovementDisorderAPIs, or health-related human subject research or any other user provided health or medical data
Fitness and exercise data, including but not limited to the Motion and Fitness API
Such as form of payment, payment card number, or bank account number. If your app uses a payment service, the payment information is entered outside your app, and you as the developer never have access to the payment information, it is not collected and does not need to be disclosed.
Such as credit score
Other Financial Info
Such as salary, income, assets, debts, or any other financial information
Information that describes the location of a user or device with the same or greater resolution as a latitude and longitude with three or more decimal places
Information that describes the location of a user or device with lower resolution than a latitude and longitude with three or more decimal places, such as Approximate Location Services
Such as racial or ethnic data, sexual orientation, pregnancy or childbirth information, disability, religious or philosophical beliefs, trade union membership, political opinion, genetic information, or biometric data
Such as a list of contacts in the user’s phone, address book, or social graph
Emails or Text Messages
Including subject line, sender, recipients, and contents of the email or message
Photos or Videos
The user’s photos or videos
The user’s voice or sound recordings
Such as user-generated content in-game
Data generated by the user during a customer support request
Other User Content
Any other user-generated content
Information about content the user has viewed that is not part of the app, such as websites
Information about searches performed in the app
Such as screen name, handle, account ID, assigned user ID, customer number, or other user- or account-level ID that can be used to identify a particular user or account
Such as the device’s advertising identifier, or other device-level ID
An account’s or individual’s purchases or purchase tendencies
Such as app launches, taps, clicks, scrolling information, music listening data, video views, saved place in a game, video, or song, or other information about how the user interacts with the app
Such as information about the advertisements the user has seen
Other Usage Data
Any other data about user activity in the app
Such as crash logs
Such as launch time, hang rate, or energy use
Other Diagnostic Data
Any other data collected for the purposes of measuring technical diagnostics related to the app
Other Data Types
Any other data types not mentioned
You should have a clear understanding of how each data type is used by you and your third-party partners.
For example, collecting an email address and using it to authenticate the user and personalize the user’s experience within your app would include App Functionality and Product Personalization.
Such as displaying third-party ads in your app, or sharing data with entities who display third-party ads
Developer’s Advertising or Marketing
Such as displaying first-party ads in your app, sending marketing communications directly to your users, or sharing data with entities who will display your ads
Using data to evaluate user behavior, including to understand the effectiveness of existing product features, plan new features, or measure audience size or characteristics
Customizing what the user sees, such as a list of recommended products, posts, or suggestions
Such as to authenticate the user, enable features, prevent fraud, implement security measures, ensure server up-time, minimize app crashes, improve scalability and performance, or perform customer support
Any other purposes not listed
Data linked to the user
You’ll need to identify whether each data type is linked to the user’s identity (via their account, device, or other details) by you and/or your third-party partners. Data collected from an app is often linked to the user’s identity, unless specific privacy protections are put in place before collection to de-identify or anonymize it, such as:
Stripping data of any direct identifiers, such as user ID or name, before collection.
Manipulating data to break the linkage and prevent re-linkage to real-world identities.
Additionally, in order for data not to be linked to a particular user’s identity, you must avoid certain activities after collection:
You must not attempt to link the data back to the user’s identity.
You must not tie the data to other datasets that enable it to be linked to a particular user’s identity.
Note: “Personal Information” and “Personal Data”, as defined under relevant privacy laws, are considered linked to the user.
You’ll need to understand whether you and/or your third-party partners use data from your app to track users and, if so, which data is used for this purpose.
“Tracking” refers to linking data collected from your app about a particular end-user or device, such as a user ID, device ID, or profile, with Third-Party Data for targeted advertising or advertising measurement purposes, or sharing data collected from your app about a particular end-user or device with a data broker.
“Third-Party Data” refers to any data about a particular end-user or device collected from apps, websites, or offline properties not owned by you.
Examples of tracking include:
Displaying targeted advertisements in your app based on user data collected from apps and websites owned by other companies.
Sharing device location data or email lists with a data broker.
Sharing a list of emails, advertising IDs, or other IDs with a third-party advertising network that uses that information to retarget those users in other developers’ apps or to find similar users.
Placing a third-party SDK in your app that combines user data from your app with user data from other developers’ apps to target advertising or measure advertising efficiency, even if you don’t use the SDK for these purposes. For example, using a login SDK that repurposes the data it collects from your app to enable targeted advertising in other developers’ apps.
The following situations are not considered tracking:
When the data is linked solely on the end-user’s device and is not sent off the device in a way that can identify the end-user or device.
When the data broker uses the data shared with them solely for fraud detection or prevention or security purposes, and solely on your behalf.
Privacy Choices (Optional): A publicly accessible URL where users can learn more about their privacy choices for your app and how to manage them. For example, a webpage where users can access their data, request deletion, or make changes.
You collect different types of data from users depending on whether the user is a child, whether they are a free or paid user, whether they opt in, where they live, or for some other reason.
You use Apple frameworks or services, such as MapKit, CloudKit, or App Analytics.
If you collect data about your app from Apple frameworks or services, you should indicate what data you collect and how you use it. You are not responsible for disclosing data collected by Apple.
You use location, device identifiers, and other sensitive data, but only on device, and the data is never sent to a server.
Data that is processed only on device is not “collected” and does not need to be disclosed in your answers. If you derive anything from that data and send it off device, the resulting data should be considered separately.
You collect precise location, but immediately de-identify and coarsen it before storing.
Disclose that you collect Coarse Location, since the precise location data is immediately coarsened and precise location is not stored.
Your app includes free-form text fields or voice recordings, and users can save any type of information they want through those mediums, including names and health data.
Mark “Other User Content” to represent generic free form text fields and “Audio Data” for voice recordings. You’re not responsible for disclosing all possible data that users may manually enter in the app through free-form fields or voice recordings. However, if you ask a user to input a specific data type into a text field, such as their name or email, then you’ll need to disclose the specific type of data that you request.
You collect data to service a request but do not retain it after servicing the request.
“Collect” refers to transmitting data off the device and storing it in a readable form for longer than the time it takes you and/or your third-party partners to service the request. For example, if an authentication token or IP address is sent on a server call and not retained, or if data is sent to your servers then immediately discarded after servicing the request, you do not need to disclose this in your answers in App Store Connect.