PRIVACY POLICY OF TRAFFICAUTH-MOBILE

1. INTRODUCTION

TrafficAuth-Mobile ("us" our" or "we") is committed to protecting your privacy. Our privacy policy, which applies to users of our mobile application, is designed to explain the information we collect and how we use it to provide our services and give users a better experience. Please read this Policy before using the TrafficAuth-Mobile Platform. By using the TrafficAuth-Mobile you agree and consent to the collection, and use of your information as described and collected by us in accordance with this Policy. If you do not agree with the Policy, please do not use or access the TrafficAuth-Mobile application.

2. DEFINITIONS

3. WHAT INFORMATION DO WE COLLECT?

We do not store, collect or process any sensitive data such as personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs; trade-union membership; genetic data, biometric data, etc.

We may ask you to provide us with certain Protected Information. We may collect this information through various means and in various places through the services, including account registration forms, contact us forms, or when you otherwise interact with us. When you sign up to use TrafficAuth-Mobile, you create a user profile. We shall ask you to provide only such Protected Information which is for a lawful purpose connected with our services and necessary to be collected by us for such purpose.

3.1 INFORMATION YOU PROVIDE TO US

Information you give us; This includes information submitted when You:

3.2 HOW TRAFFICAUTH-MOBILE USES USERS LOCATION INFORMATION?

After the application launch, on login, if access fine location permission is not enabled for TrafficAuth-Mobile. You will see an alert dialog with an explanation, why TrafficAuth-Mobile requires the location in the foreground.

If you select the deny option, then the TrafficAuth-Mobile application will not be fully functional and give you another alert dialog to enable location runtime permissions.

If you select the allow option, TrafficAuth-Mobile will ask you location runtime permissions to get your location information, when using core features of TrafficAuth-Mobile, which includes location data. To use our best service available in TrafficAuth-Mobile, the app will ask you to turn on location services and permissions. In android device, you will have three options in runtime location permission to choose from:

  1. Allow all the time: When the app is running in the foreground (app open and on-screen) or background (app open or active but not on-screen) in both states.
  2. Allow only while using the app: If you select this option, then TrafficAuth-Mobile will not be able to get location information in the background state. In this case, you can only use TrafficAuth-Mobile services in the foreground state. To get accurate results of location-based safety alerts you need to give
  3. Deny: This option disables location services for the TrafficAuth-Mobile app. In order to use the application, you need to enable location permission out of the two options mentioned above.

We are using location information as mentioned in the sections below.

3.3 LOCATION DATA

We collect precise location data from the user’s mobile devices if they enable us to do so. We maintain this data only so long, as it is reasonable to provide our service. We use location data to detect nearby intersections devices and beacon devices, to process Signal Phase and Timing Messages from these devices, movement calculation, and detection of mode type (Pedestrian, Cyclist, Motorist) of the user as per the speed and their movement, to show alerts and alarms to different users on basis of their location, speed, and movement.

TrafficAuth-Mobile collects this data when the TrafficAuth-Mobile app is running in the foreground (app open and on-screen) of their mobile device.

3.4 LOG FILES

Our app automatically gathers some information about users, including total runtime, Operating System (Android), and version number. The data collected does not include personally identifiable information and is used for app performance analysis and troubleshooting purposes.

3.5 USE OF INFORMATION COLLECTED