Privacy and App Tracking Transparency
The information is provided below to help you to fill out the Apple app privacy form.describe
Walkthrough
As the app developer, you are responsible for filling out the form correctly, and you will need to customize your responses to match your app and services. If you would like legal advice on filling out Apple’s app privacy form, please consult a lawyer.
Adalo only ever collects data to provide app functionality and to help us improve our products. This data is never used for tracking or advertising and is not rented, sold, or given to advertisers.
Recently, Apple has released two new privacy-related features, Privacy Labels, and App Tracking Transparency.
Privacy labels are designed to help end-users understand how apps handle their data. You can learn more about them here: https://developer.apple.com/app-store/app-privacy-details/
App Tracking Transparency is a new feature of iOS and iPadOS 14.5 that requires applications to ask permission if they want to track your activity across other companies’ apps and websites. You can read more about it here: https://developer.apple.com/news/?id=ecvrtzt2
Before publishing your app on the iOS App Store, you’ll need to report on your privacy practices. These steps will determine what your app’s Privacy Labels look like in the App Store listing.
There are two parts to this process:
Data Collection: Identifying the data collected
Data Use: Indicating how each data is used, whether it is tied to the user’s identity, and whether or not it is used for tracking purposes.
Data Collection
The first question you’ll be asked is whether or not your app ‘collects’ data according to Apple’s definitions.
Because your app stores and retrieves data from Adalo’s servers, you’ll need to select “Yes, we collect data from this app”.
After clicking “Next”, you’ll report the data that your app ‘collects’. The answers here will vary depending on the components you use and the data you collect from your end-users. Then, for each type of data collected, you’ll report on how that data is used.
For guidance on data that Adalo collects and how that data is used, please refer to the list below.
Adalo’s Required Data Disclosures
There are certain boxes that you must check, due to the way your Adalo app works:
Identifiers > User ID
Adalo uses User ID for App Functionality, and is linked to the user’s identity. User ID is NOT used for tracking purposes.
Usage Data > Product Interaction
Adalo uses product interaction data for Analytics, and is linked to the user’s identity. Product interaction data are NOT used for tracking purposes.
Diagnostics > Other Diagnostic Data
Adalo uses other diagnostic data for Analytics, and is NOT linked to the user’s identity. Other diagnostic data are NOT used for tracking purposes.
Feature Dependent Data Disclosures
Email & Password Sign-in If you are using the email and password form components provided by Adalo, you’ll need to disclose the collection and use of:
Contact Info > Email Address
Adalo uses email addresses for App Functionality, and is linked to the user’s identity. Email Address is NOT used for tracking purposes.
Notifications When an end-user agrees to receive notifications from your app, Adalo stores their Device ID so we can deliver the notification. If you request permissions to send notifications to your end-users, you’ll need to check the box for:
Identifiers > Device ID
Adalo uses Device ID for App Functionality, and is linked to the user’s identity. Device ID is NOT used for tracking purposes.
Sign in with Apple When an end-user signs in with Apple, your app will prompt them for their name and email address. If your app uses this feature, you’ll need to check the box for the following two properties:
Contact Info > Name
Adalo uses the name for App Functionality, and is linked to the user’s identity. Name is NOT used for tracking purposes.
Contact Info > Email Address
Adalo uses email addresses for App Functionality, and is linked to the user’s identity. Email Address is NOT used for tracking purposes.
Google Maps If you are using the Google Maps component to request location permissions from your end-users, you will need to disclose both of the following location properties: Location > Precise Location > Coarse
Your app will use location for App Functionality, and is NOT linked to the user’s identity. Location data is NOT used for tracking purposes. For more information regarding Google Map’s privacy practices, read their documentation:
https://developers.google.com/maps/documentation/ios-sdk/apple-privacy-policy
Google Sign-in If you are using Google Sign-in, please refer to that service’s data disclosure documentation: https://developers.google.com/identity/sign-in/ios/app-privacy
Stripe If you are collecting payments using the Stripe Kit components, please refer to the documentation they have provided. https://support.stripe.com/questions/stripe-ios-sdk-privacy-details
Google Admob If you are displaying ads using the Google Admob component, please refer to that service’s data disclosure documentation: https://developers.google.com/admob/ios/data-disclosure Mixpanel If you are using Mixpanel, please refer to that service’s data disclosure documentation: https://mixpanel.com/legal/app-store-privacy-details/ If you have additional questions about the types of data you might need to disclose, please see Apple’s Additional Guidance: https://developer.apple.com/app-store/app-privacy-details/#additional-guidance
Help
If you need additional help with this article, you can always ask in our community forum! Be sure to paste the link to this article in your post as well!
Last updated