FAQ

What exactly is a webview?

A webview is a fully-functional mobile web browser screen that runs in your app. The only difference between a webview and a normal mobile web browser screen is that the user cannot edit the URL. If the webpage that is loaded in the webview is very responsive and mobile-friendly, the experience can appear to be fully native.

What level of engineering effort is required to embed the ParqEx app in a native mobile app via the webview method?

Very little. This document contains all the code necessary to accomplish this, so it's mostly just copying and pasting the code for your engineers.

Which URL should be opened in the webview?

Your white-labeled version of the ParqEx app can be launched directly in your app by using a webview. To make this possible, we will provide (host) a blank page where ParqEx is installed and configured to auto-launch. Your app developer/software engineer will provide you with the exact URL once the page is set up and ready for you to use in the webview. This approach feels very native because the ParqEx app takes up the entire screen and loads very fast.

Can ParqEx deep-link to specific screens in our app as part of some workflow?

Yes. The best way to do this is to provide ParqEx support with the deep link they should use, along with appropriate context explaining when that link should be used. Then ParqEx will display the link when the scenario arises.

If you want to direct users to a web app link when they are using a web browser, and instead direct them to a mobile deep link when they are in your app, then use the instructions in the appropriate section "Intercept URL requests from within a webview" below, depending on your platform. Then just add code to translate specific web URLs into the right deep links.

What data does ParqEx collect, so we can know what to disclose in the Apple App Store?

Apple's web page about App Privacy Details (https://developer.apple.com/app-store/app-privacy-details/) explains that some data may not need to be disclosed if it meets the following conditions:

Optional disclosure

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.

All data that is collected by ParqEx meets all of these conditions and therefore does not need to be disclosed. In fact, data from customer support requests is specifically called out as an example of data that may not need to be disclosed.

However, if for some reason you decide to disclose data collected by ParqEx , here are the details:

Types of data

ParqEx only collects 2 of the data types spelled out by Apple:

• User Content > Customer support: Data generated by the user during a customer support request

• Usage Data > Product Interaction: Taps, clicks, scrolling information

Data use

ParqEx uses the User Content and Usage Data collected for Analytics: to evaluate user behavior, including to understand the effectiveness of existing product features, plan new features, or measure audience size or characteristics.

ParqEx also uses the User Content collected for App Functionality: to allow the user to self-service their support request or to make contact with a customer support agent.

Data linked to the user

None of the data that ParqEx collects is linked to a particular user. All Usage Data is anonymized, as is the User Content data ParqEx collects. In order to do this, ParqEx uses state-of-the-art PII redaction software (Google's DLP service) to remove any personal data from customer support requests before storing them in our system.

Tracking

ParqEx does not use any data collected for tracking or advertising purposes.

Privacy Links

ParqEx's privacy policy is here: https://www.parqex.com/privacy