If you’re publishing an app on behalf of a client, the chances are your app will be suspended from the Play Store by Google due to a violation of the impersonation policy. The reason for this is that Google is unable to link the name of your clients app to the name of your developer account. What you can do to prevent this, is to send Google an advanced notice of the app you’re publishing. With this advanced notice, you can provide a document containing a written statement from your client, allowing you to publish the app with the content it holds. Filling out an advanced notice can be done through the following form: https://support.google.com/googleplay/android-developer/contact/adv_note(https://support.google.com/googleplay/android-developer/contact/adv_note) The default format for a package name is com.app.p[appnumber]. This means that the app with app number 1234MY will receive the following package name: com.app.p1234MY The app number of your app can be found on the Publication tab of your app in the Appily App Builder App Editor.

If you want to monetise your app by selling it in the Google Play Store, there are a few additional steps you have to follow. In this situation, you need an additional Google Merchant account. >> Please note: You cannot convert an already published free app to a paid one. << Create an app record in the Google Play developer console. You'll first have to create the app within the Google Play developer console. To do so, you can follow the steps in the regular publishing documentation available in our help center. Make sure not to publish the app yet, as we will have to set a price for the app before doing so. Making your app paid, and setting a price. 1. Login on https://play.google.com/apps/publish (https://play.google.com/apps/publish)with your Google Play developer account. 2. Select your app from the list, navigate to the Monetize section within the left-side menu, and open the App Pricing page. 3. On the App Pricing page, click the 'Make your app paid' option for your app and enter the price. 4. Once you've set the price for your app, save your changes. https://static.wixstatic.com/media/8a55e6_003ba037859240348e439a09de1a453e~mv2.png

This article explains how to manually submit your Android app to the Google Play Store for the first time, using the .ABB file obtained via the Google Play publishing process in Appily App Builder. In the Publication tab in the App Editor, you will be able to download the Android source code to be used with Android Studio,(https://developer.android.com/studio) to allow for manual App submission. In case you require the already compiled APK / AAB of your App, you can also contact and request this from the Appily App Builder team by sending an email request to info@appilyappbuilder.com (info@appilyappbuilder.com)(Please include your App Name), and our team will send you the compiled APK / ABB of your App. Note that the file provided from Appily App Builder is a .zip file. This .zip file contains the following files: - APK / AAB - App icon - Feature image - Screenshots Extract the .APK file (or .AAB file, starting August 2, 2021) from the .zip file, and upload the .APK or .AAB file to Google when required. Attempting to upload the .zip file to Google will result in an error. Creating a new app record Open your browser and navigate to the Google Play developer console: https://play.google.com/apps/publish/?hl=en (https://play.google.com/apps/publish/?hl=en) Once logged in, you'll find yourself on the 'All Apps' page. This is the landing page of the Google Play developer console, which provides you with an overview of all apps that have been created and/or published on the developer account. Use the 'Create app' button in the top-right corner of the screen to create a new app within your developer account. After clicking the button, you should see a page similar to the screenshot below. https://static.wixstatic.com/media/8a55e6_9b117fcbea944148a2f3038787ce669e~mv2.png Enter the name of your app and select the default language. This is the language of the content used in your app. Select the 'App' option between App or Game. * Please note that 'Game' apps through Appily App Builder require different publishing settings and options than regular apps. Select whether your app is Free or Paid. Note that Free apps cannot be made into Paid apps after they have been published to the Google Play Store. Also note that Paid apps require you to set up a Google Merchant account. Lastly, check the boxes for the available declarations and use the 'Create app' button in the bottom-right corner of the screen to continue. If you haven't yet accepted the Play App Signing Terms of Service during a previous app submission, then you will notice a third checkbox being available for this. https://static.wixstatic.com/media/8a55e6_ca9c3c7a77b34bf8a641e19d5228c2e0~mv2.png The tasks listed on the screen show which settings have to be provided by you before you'll be able to publish the app into the Google Play Store. We'll go through these settings one by one. App access. Within the App access settings you'll have to declare whether or not your app contains content which can only be seen if users login, or enter a password, or if they have to perform any other type of authentication. If your app has locked content like this, then you will have to provide Google with a way to access this content. When you've set the app access settings, use the Save button in the bottom-right corner of the screen to save your changes. After saving the changes, use the Dashboard button at the top of the screen to navigate back to the Dashboard. Ads. Within the Ads settings you'll have to declare whether or not the app contains advertisement. When you've set the Ads settings, use the Save button in the bottom-right corner of the screen to save your changes. After saving the changes, use the Dashboard button at the top of the screen to navigate back to the Dashboard. Content rating. Within the Content rating settings, you'll have to answer a series of questions regarding the content used in your app. The answers to these questions will provide your app with an IARC content rating for your app. This rating will provide users in the Google Play Store with an indication of the content which your app displays. The email address you provide for this rating will be used to contact you about your content ratings, and may be shared with rating authorities and IARC. When you've set the Content rating settings, use the Save button in the bottom-right corner of the screen to save your changes. After saving the changes, click Next and use the Dashboard button in the top-left corner of the screen to navigate back to the Dashboard. Target audience. Within the Target audience settings you'll have to answer a series of questions concerning the audience that your app is created for. Note that choosing anything under the age of 18 may place your app in the kids category, which will result in additional restrictions in terms of allowed content. This may impact the review of your app. If your app is not specifically created for a younger audience, then we advise you to always choose the ages 18 and over. When you've set the Target audience settings, use the Save button in the bottom-right corner of the screen to save your changes. After saving the changes, use the Dashboard button at the top of the screen to navigate back to the Dashboard. Select an app category and provide contact details. Within the Store settings you'll have to select a category for your app and enter an email address which will be shown in the Google Play Store with your app listing. All other options displayed on this page are optional. When you've set the Store settings, use the Save button in the bottom-right corner of the screen to save your changes. After saving the changes, use the Dashboard button in the top-left corner of the screen to navigate back to the Dashboard. Privacy policy. This item is not displayed in the initial app setup list, but is required for apps published via Appily App Builder due to usage of the location permission. Scroll all the way to the bottom of the left-side menu of your developer console. At the bottom you will find a Policy submenu in which 'App content' is listed. Open the 'App content' page and click the 'Start' button below the Privacy policy setting. https://static.wixstatic.com/media/8a55e6_7786d907ae6a4b7da41f8cd28b60d734~mv2.png Enter the URL on which your app's privacy policy can be located. When you've set the privacy policy URL, use the Save button in the bottom-right corner of the screen to save your changes. After saving the changes, use the Dashboard button in the top-left corner of the screen to navigate back to the Dashboard. Sensitive app permissions Scroll all the way to the bottom of the left-side menu of your developer console. At the bottom you will find a Policy submenu in which 'App content' is listed. Open the 'App content' page and click the 'Start' button below the Sensitive app permissions setting. https://static.wixstatic.com/media/8a55e6_383947ed47cd4849a3eaf74b6e9bc0e5~mv2.png The next page is titled 'Permission declaration form'. Hit the 'start' button below the 'Location permissions' to provide the required information. https://static.wixstatic.com/media/8a55e6_792f348fea6e4393b515464ea0c3f4a8~mv2.png Next you'll be presented with a question regarding the background use of the location permission. This question can be answered with 'No'. https://static.wixstatic.com/media/8a55e6_30db0353736746ba81015651f80dcbcc~mv2.png Use the Save button in the bottom-right corner of the screen to save your changes and to complete the permission declaration form. News apps Scroll all the way to the bottom of the left-side menu of your developer console. At the bottom you will find a Policy submenu in which 'App content' is listed. Open the 'App content' page and click the 'Start' button below the News apps setting. https://static.wixstatic.com/media/8a55e6_bee61c89fc3a44f5a2e9548f99aa2994~mv2.png You will be asked whether your app is a news app. If this is not the case, answering the question with 'No' will suffice. If your app is a news app, then you'll have to provide Google with additional information to help them verify your credentials as a news publisher. Furthermore, your app will have to comply with the Google Play News Policy. (https://support.google.com/googleplay/android-developer/answer/9914283#news) When you've entered the required information, hit the Save button in the bottom-right of the screen to complete this step. Set up your store listing Within the Store listing settings you'll have to provide the following information for your app: • Short description. • Full description. • App icon. • Feature graphic. • Phone screenshots. Please note that it is not allowed to add keywords to your descriptions, as this is cause for Google to reject the app from the Google Play Store. Concerning the screenshots: You'll only have to upload a minimum of two Phone screenshots to be compliant with Google's guidelines. Screenshots for other displays (e.g. tablet) are displayed, but are not required as long as at least two screenshots are provided for one of the device types. When you've set the Store listing settings, use the Save button in the bottom-right corner of the screen to save your changes. After saving the changes, use the Dashboard button in the top-left corner of the screen to navigate back to the Dashboard. Data safety Scroll all the way to the bottom of the left-side menu of your developer console. At the bottom you will find a Policy submenu in which 'App content' is listed. Open the 'App content' page and click the 'Start' button below the Data safety setting. Release your app: Now that we're finished with the initial app setup, you'll notice that the initial app setup section is no longer displayed on the dashboard page of your app. This means that this part of the publication is successfully completed. The dashboard page now shows a number of ways to release your app. Because we're interested in publishing the app in the Google Play Store, we'll choose the last displayed option titled: "Publish your app on Google Play". https://static.wixstatic.com/media/8a55e6_1b571798460b406880cc9d2ad062983b~mv2.png Opening the 'View tasks' dropdown menu will show you the following list of actions having to be performed before being able to publish the app: https://static.wixstatic.com/media/8a55e6_b6671e33436f4357a058ba68f23da86f~mv2.png https://static.wixstatic.com/media/8a55e6_6c51cc8698fc48febd5a13ea85b32c4f~mv2.png 1. Click the 'add countries and regions' hyperlink. You will be able to select the countries in which you would like your app to be available. When you've selected the countries, use the 'Add countries/regions' button in the top-right corner of the pop-up window to save your changes. 2. Click the 'Create new release' button in the top-right corner of the screen. https://static.wixstatic.com/media/8a55e6_0633e85dc43c4ae09d65be0141503202~mv2.png https://static.wixstatic.com/media/8a55e6_098b1c464e16482d89a2a851f5767188~mv2.png 4. Click the ‘Continue’ button next to the 'Manage preferences' hyperlink and accept the Play App Signing Terms of Service, if required. (you will have to be logged in as account owner or admin to be able to accept these terms) 5. Unzip the package provided by Appily App Builder, which contains your app's APK file (or AAB file, starting August 2, 2021). Upload the APK or AAB file to Google by either dragging and dropping it onto the screen, or by using the Upload button displayed on the page. A name for the release will automatically be filled in. Optionally, you can enter release notes for this version to inform your app users about the changes within this new version of the app. Use the Save button in the bottom-right corner of the screen to save your changes. After saving the changes, use the Review release button. Review the new version and use the 'Start rollout to Production' button to release the app into the Google Play Store. Your app should now be displayed with a 'Pending publication' status in your developer console app overview. Google will review the app and, if accepted, the app will become available to download from the Google Play Store. In case the app is rejected -or suspended as Google calls it- you will receive an email notification from Google on the owner email address of your Google Play developer account explaining why the app was suspended and what needs to be changed. The time it takes Google to review is generally anywhere between 2-7 days, depending on the amount of apps that have been submitted to Google. Congratulations, you've successfully submitted your Android app to the Google Play Store!

This article explains how to manually update your published Android app in the Google Play Store using the .APK / ABB file obtained via the Google Play publishing process in Appily App Builder. Note that the file provided from Appily App Builder is a .zip file. This .zip file contains the following files: - APK / AAB - App icon - Feature image - Screenshots Extract the .APK file (or .AAB file, starting August 2, 2021) from the .zip file, and upload the .APK or .AAB file to Google when required. Attempting to upload the .zip file to Google will result in an error. Updating an already published app in the Google Play Store is a lot less time consuming than publishing an app for the first time. When submitting an app for the first time, all store data has to be provided to Google. When updating an existing app, you only have to update the item(s) that you wish to change. To update your app in the Google Play Store we'll be focusing on the 'Store presence', 'App content', and 'Release management' sections. The app itself can be updated via a new release (APK file), and the information displayed in the Google Play Store, on the download page of your app, is known as the store presence. Store presence After opening your app from the 'All apps' page, the store presence section can be found in the left-side menu of your Google Play developer console. Within the store presence section, there are multiple pages on which the app's presence in the Google Play Store can be edited. Within this article, and to keep things simple, we'll focus on the following: • Main store listing. • The main store listing allows you to edit the title, descriptions, icon, feature graphic and screenshots of your app. This is the main display of your app in the Google Play Store. • Store settings. • The store settings allows you to edit the type and category of your app, as well as the contact details displayed on the download page of your app in the Google Play Store. If you've made any changes on these pages, use the Save button in the bottom-right corner of the screen to save your changes. App content All the way at the bottom of the left-side menu of your Google Play developer console, you will find the Policy section from which the App content page can be opened. On the App content page, make sure that all options are marked as 'Completed'. If there are any open tasks in the To-do list (Google adds new things from time to time), then you will have to make sure to complete these tasks before submitting a new version of your app to the Google Play Store. On this page you will be able to edit the following information: • App access. • If parts of your app are restricted based on login credentials, memberships, location, or other forms of authentication, you will have to provide Google with instructions on how to access them via this section. • Privacy policy. • You can add or edit your app's privacy policy via this section. • Ads. • If your app contains ads, then you can let Google know about this via this section. • Content ratings. • You can view and edit your app's current IARC rating via this section. • Target audience and content. • You can view and edit your app's current target age group, and other content information via this section. • News apps. • If your app is a news app, then you'll have to provide Google with additional information to help them verify your credentials as a news publisher. Furthermore, your app will have to comply with the Google Play News Policy. If your app is not a news app, then a simple 'No' will suffice. • Sensitive app permissions. • If your app requests access to sensitive permissions, like location permissions, you need to tell Google what functions the permission is used for. (more information below) Sensitive app permissions Scroll all the way to the bottom of the left-side menu of your developer console. At the bottom you will find a Policy submenu in which 'App content' is listed. Open the 'App content' page and click the 'Start' button below the Sensitive app permissions setting. https://static.wixstatic.com/media/8a55e6_ce63e40a42254a81ade695c60bedefa7~mv2.png The next page is titled 'Permission declaration form'. Hit the 'start' button below the 'Location permissions' to provide the required information. https://static.wixstatic.com/media/8a55e6_66b0d4a3c7e349d68ae2b47e70009b25~mv2.png Next you'll be presented with a question regarding the background use of the location permission. This question can be answered with 'No'. https://static.wixstatic.com/media/8a55e6_f710a4b4b13d46efbcdbb3995fc3d3ab~mv2.png Use the Save button in the bottom-right corner of the screen to save your changes and to complete the permission declaration form. Data safety Scroll all the way to the bottom of the left-side menu of your developer console. At the bottom you will find a Policy submenu in which 'App content' is listed. Open the 'App content' page and click the 'Start' button below the Data safety setting. Release management Within the Release section of the left-side menu, you'll find the Production option. Opening this page will allow you to create a new release and roll it out to production. To create a new release, use the 'Create new release' button in the top-right corner of the Production page. https://static.wixstatic.com/media/8a55e6_80e3eee4ea684c038071e6ebbbbe9b03~mv2.png If you haven't set the App signing by Google Play option yet, then use the Manage preferences button and choose the option to 'Let Google manage and protect your app signing key (recommended)’. Unzip the package you've downloaded from the Publish page in Appily App Builder, which contains your app's APK or AAB file. Upload the APK or AAB file to Google by either dragging and dropping it onto the screen, or by using the Upload button displayed on the page. A name for the release will automatically be filled in. Optionally, you can enter release notes for this version to inform your app users about the changes within this new version of the app. Use the Save button in the bottom-right corner of the screen to save your changes. After saving the changes, use the Review release button. Review the new version and use the 'Start rollout to Production' button to release the app into the Google Play Store. In case the app is rejected -or suspended as Google calls it- you will receive an email notification from Google on the owner email address of your Google Play developer account explaining why the app was suspended and what needs to be changed. The time it takes Google to review is generally anywhere between 2-7 days, depending on the amount of apps that have been submitted to Google. Congratulations, you've successfully updated your Android app in the Google Play Store!

This article provides a step-by-step guide on how to authorise an additional user to your Google Play developer account. An authorised user can be helpful if: • Your main Google Play developer account has access to multiple developer teams. You don't feel comfortable sharing your main Google Play developer credentials in our system. You're having trouble validating your Google Play developer credentials in our system. Authorising a new user to your existing Google Play developer account is free. After completing the steps in this document you will have a new (additional) Google account which can be used to access your existing Google Play developer console. How to add an additional user to your Google Play developer account. 1. Logout of all Google services. 2. Navigate to https://gmail.com (https://gmail.com)and register a new Gmail account. (e.g.: YourAppName-app@gmail.com) 3. During the account registration, you'll be asked to add login verification to the account. Make sure to only add a recovery phone number here. Do not turn on two-step login verification. 4. After successfully registering a new Gmail account, logout of Google. 5. Navigate to https://play.google.com/apps/publish/ and login with your existing Google Play developer account. Note: If you're asked to register as a Google Play developer, please restart from step 3. 1. After logging in to the Google Play developer console, go to Settings -> Users & permissions. 2. Click the "Invite new user" button in the top-right corner of the screen. https://static.wixstatic.com/media/8a55e6_d16ffd3562024141aecff15b8e475f2b~mv2.png 8. When prompted for an email address, enter the email address you've created in step 2, and give the user Administrator rights. https://static.wixstatic.com/media/8a55e6_d0f102a0416a49baa15de12c2043d93f~mv2.png 9. Logout of the Google Play developer console. 10. Navigate to https://gmail.com and login with the new account created in step 2. 11. Open and accept the invitation mail you've sent yourself in step 7. After completing the steps above, you've created a new user in your Google Play developer console. You will be able to use the email address and password of this new user to publish your app in Appily App Builder.

What if I’m not yet registered as a Google Play developer? • Please read about how to enroll from our documentation. What if I do not have enough rights to create, edit, and publish apps in the Google Play Store? • Contact the owner of the Google Play developer account to increase the rights of your account. User rights can be edited in the “User accounts & rights” section of the settings page in the Google Play developer console. Where do I accept the Google Play developer license agreements? • If there are any Google Play developer license agreements pending, they will automatically be shown upon logging in on https://play.google.com/apps/publish.(https://play.google.com/apps/publish) Where do I add a recovery phone number to my Google account? • You can add a recovery phone number in the security settings of your Google account. The security settings are located on https://myaccount.google.com/security.(https://myaccount.google.com/security) What if I have access to multiple Google Play developer consoles? • If you have access to multiple Google Play developer consoles, you can do one of two things: 1. You can have yourself removed from the team(s) on which the app should not be published, leaving single access to the account on which the app has to be published. The owner of the Google Play developer account will be able to remove you from the team. 2. You can create a new Google account on http://gmail.com/.(http://gmail.com/) Once this Google account has been invited to the Google Play developer console, you will be able to use this new account for the publication of your app. Where do I remove 2-step login verification from my Google account? • You can remove 2-step login verification in the security settings of your Google account. The security settings are located on https://myaccount.google.com/security.(https://myaccount.google.com/security) What if I can't turn off 2-step login verification? • If 2-step login verification cannot be disabled, please make sure to enable the 'Less secure app access' setting instead. The security settings are located on https://myaccount.google.com/security.(https://myaccount.google.com/security)

In order to help users understand how your app collects and shares data, app owners must enter data safety details of their app within the Google Play developer console prior to being able to publish. With this information, users will be able to learn about some of the data types the app may collect, and whether that data is linked to them or used to track them. The information below describes data collection and sharing performed by the app when using the standard building blocks provided by our platform. If you're using web service blocks to extend your app's functionality, then please make sure to take this into account when answering the data safety questions posed by Google. The data safety details can be provided through the Google Play developer console. To do so, please login on https://play.google.com/apps/publish/?hl=en (https://play.google.com/apps/publish/?hl=en)with your Google Play developer account. Please make sure that the account you're using to log in with has at least an Admin role. Any other role is insufficient to perform the required actions. When logged in, open your app from the App Overview page. Once opened, you'll find the Data Safety questions via the App Content page listed in the bottom of the left-side menu. Open this page and click the 'Start' button to start the data safety questionnaire. https://static.wixstatic.com/media/8a55e6_84a97374cb4a4235bd0a7ec3f53f6a51~mv2.png After clicking the Start button, you'll be shown a page with information about the Data Safety questionnaire. After reading the information, use the Next button in the bottom-right corner of the screen to continue. https://static.wixstatic.com/media/8a55e6_9c0593394c384a7bb8784192bb5fecb5~mv2.png After clicking Next, you will be presented with three questions which can all be answered with 'Yes'. https://static.wixstatic.com/media/8a55e6_8a2aa95e6aa54a5a85388626b1949fe5~mv2.png Click the Next button in the bottom-right corner of the screen to continue to the next page. On this page you will have to select all data types that are collected or shared by the app. You can use the 'Show' button to the right side of the data type group to select the specific data type(s). There are a number of data types which are collected by all apps created with Appily App Builder, which we will list below. If you've added any custom functionality to the app through which data is collected or shared, then please make sure to also select the data types which are used for this functionality. • Location All Appily App Builder Android apps use the 'Approximate Location' and 'Precise Location' in order to allow app owners to send location-based push notifications to their app users. Other than that, functionality like maps and location-based lock blocks also require the use of this permission. • Personal info Whether or not you enable the checkboxes in this section depends on the functionality you've added to the app. For example, if the app contains a Contact Form through which personal information is provided, then enable the boxes for the information that the user can provide within the app. Additionally, if users can -or are required to- login to the app, then you'll have to check the boxes concerning the collection of names and email addresses. • Financial info The 'Financial info' option in this section concerns payments which are handled through means other than a payment service. For example, if your app contains a manual payment option, then the 'Payment Info' option has to be checked. If your app uses PayPal checkouts, then you do not have to check this box, because these payments are handled by PayPal without you ever seeing the users payment information. If your app collects or shares any other type of financial information from its users, then check the appropriate box(es) accordingly. • Health and fitness If your app collects or shares any health or fitness related information of the user, for example medical records, symptoms, exercise or physical activity, then check the appropriate box(es) accordingly. Health and fitness information is not collected or shared by Appily App Builder-created Android apps through standard functionality. • Messages If your app collects or shares any information of the user related to messages, for example email, SMS/MMS, or other messaging data, then check the appropriate box(es) accordingly. Messages data (Emails, SMS/MMS, or other forms of messaging) is not collected or shared by Appily App Builder-created Android apps through standard functionality. • Photos and videos If your app collects or shares any photos and videos provided by the user, then check the appropriate box(es) accordingly. For example, if your app uses a Form block through which a photo can be uploaded. • Audio files If your app collects or shares any audio related data provided by the user, for example voice recordings, music file uploads, or other audio files, then check the appropriate box(es) accordingly. Audio related data is not collected or shared by Appily App Builder-created Android apps through standard functionality. • Files and docs If your app collects or shares any file related data provided by the user, for example document uploads, then check the appropriate box(es) accordingly. File related data is not collected or shared by Appily App Builder-created Android apps through standard functionality. • Calendar If your app collects or shares any data related to the app users' calendar, then check this option. Note that this does not concern a calendar / events block in the app, as this block only displays events created by the app developer. This only concerns collecting or sharing data belonging to the app user. • Contacts Contact related data is not collected or shared by Appily App Builder-created Android apps through standard functionality. • App activity All Appily App Builder-created Android apps track user interaction for analytic purposes. Within this section you'll have to select the options 'App interactions' and 'Other actions'. • Web browsing Web browsing related data is not collected or shared by Appily App Builder-created Android apps through standard functionality. • App info and performance All Appily App Builder-created Android apps track app performance for analytic purposes. Within this section you'll have to select the 'Crash logs' option. • Device or other IDs All Appily App Builder-created Android apps support push notifications to be sent to the app user. In order to be able to do this, a Device ID is required. Therefor, within this section you'll have to select the 'Device or other IDs' option. After selecting all the options applicable to your Android app, you can use the Next button to continue. On the next page, you'll have to answer questions on how data is used and handled for each of the options selected on the previous page. The data which is collected and shared by Appily App Builder by default is listed below. • Location: Approximate location https://static.wixstatic.com/media/8a55e6_4bae36097ec0446ea90b942e7a944827~mv2.png • Location: Precise location https://static.wixstatic.com/media/8a55e6_5c7096868d2d4792a37751fcd804fa7c~mv2.png • App info and performance: Crash logs https://static.wixstatic.com/media/8a55e6_23d64514dcc145529b323fd14e0df758~mv2.png • App activity: App interactions https://static.wixstatic.com/media/8a55e6_2dc457b9acfe43a88d607aa01b897dc6~mv2.png • App activity: Other actions https://static.wixstatic.com/media/8a55e6_c0359d5c9c76426a9e98254ff2bb13d2~mv2.png • Device or other IDs https://static.wixstatic.com/media/8a55e6_eaa43758d2b04c83bc97a6e91b38a7ad~mv2.png All other data type collecting and sharing is dependant of whether you've added functionality to the app that requires the user to provide this information. When you've finished providing the answers on how data is used and handled by your app, then you can use the Next button in the bottom-right corner of the screen to continue to the Preview page. Lastly, on the Preview page, use the Save button in the bottom-right corner to complete the data safety questionnaire.

Google Developer Program • Go to http://play.google.com/apps/publish/ and log in with an existing Google account. If you do not yet have a Google account, please create one by clicking on the "Create account"-button. https://static.wixstatic.com/media/8a55e6_2779b0d9ac0740a2b31dea114d292d90~mv2.png • Once you've logged in, you're asked by Google whether you're creating a developer account for personal use, or whether you're creating a developer account for an organisation or business. Select the option that fits the app(s) that you're planning to publish. https://static.wixstatic.com/media/8a55e6_054b50c7b6ec4f0fb66c1db6e92d30d6~mv2.png After choosing for either an individual or a company type account, you will have to provide your (or your companies) contact information. Please note that the email address and phone number that you provide will have to be verified via email and/or text message. https://static.wixstatic.com/media/8a55e6_778e234e3b1140a78159b31db1b35932~mv2.png Payment for the account is next, and can only be completed via credit card. Please make sure that the cardholder name mentioned on the credit card is equal to the contact information that you've provided in the previous step. https://static.wixstatic.com/media/8a55e6_e6fc449641cb432b8d5d86023fe3956a~mv2.png After completing your registration for a Google Developer Account you will automatically be redirected to Google's Developer Console. Once you see an interface similar to the screen shown below, your Google Developer account is ready for use. https://static.wixstatic.com/media/8a55e6_9e31700dd4764abbac1b9c26b1f353bf~mv2.png

In order to use some blocks/features in our platform, the app requires certain permissions to be enabled. Because these permissions are used by the app, Google requires you to provide a privacy policy. You can enter the link to your privacy policy in the Google Play section of the publish page in Appily App Builder. https://static.wixstatic.com/media/8a55e6_a635f39c7eb54e1082004d9584544b07~mv2.png Once you've entered the privacy policy URL, update your app by clicking the "Update Now" button.