Android App Permissions
When you install Uber on your Android phone as a rider, you're shown a list of permissions that the app requests (see image). The descriptions of these permissions are created by Google and are worded the same for every app — currently, there's no way for Uber to customize them. So, to make sure you understand what features we access and what data we actually collect, we've provided a more detailed breakdown and discussion of the permissions below. Click on any of the permissions and you'll be linked to Google's official documentation for that permission. (If you're an iOS user, please see our iOS App Permissions.)
These permissions allow Uber to prepopulate your email address, first name, last name and phone number from your contact card during registration. If you already have a Google Sign-In or Google Wallet account on your device, Uber can also use these permissions to prepopulate your email address. These permissions are also used for signing into Uber using your Google+ account and to pay using Google Wallet. Your email address and encrypted Google Wallet payment profile are sent to Uber’s servers so that your receipts can be emailed to you and you can be billed through Google Wallet.
We use this permission to display an address book in the app that you can use for a number of social features, like splitting fares, sharing ETAs, and inviting friends to join Uber. When you use Split Fare, Uber sends the mobile numbers of the friends you select to its servers so those people can be notified. If you choose to “Connect” your contacts as part of the Invite Friends feature, Uber will sync your contacts to our server in order to find and suggest friends who don’t yet use Uber for you to invite. Uber will not use that information to contact your friends without your consent. This permission is also used to prepopulate your first name, last name, profile image, and mobile number during registration. You can then edit these fields, and the updated values are sent to Uber when you create your account.
The app does not store your location to persistent memory on the device, but may cache recent locations on the device. The app does collect and send approximate and precise location data to Uber's servers to personalize your experience; to display trip history in your receipts; to facilitate driver selection and pickup; to determine what products, promotions, and surveys are relevant to you; to use for analytics purposes at an aggregated level; and to customize and improve the location-based services we provide. In addition to GPS, we may use other methods to determine precise location if Location Services are enabled, including wifi signals.
When you sign up for Uber, we send a 4-digit verification code, via SMS, to the mobile number that you provided. The “Receive SMS” permission allows the app to look for that incoming SMS message and automatically verify that we have your correct mobile number. The window of time during which the app looks for that incoming SMS is limited to 60 minutes. Uber only uses this permission to search for the verification message that we send. We do not send to our servers or save the content of any messages other than the verification message. Uber uses the “Read SMS” permission for features that provide you social context or facilitate social connections for you. For example, if you choose to “Connect” your contacts as part of our Invite Friends feature (available to some users) Uber uses the “Read SMS” permission to surface a quick list of your most frequent contacts so you can send them an invitation with the push of a button. You must opt-in to that feature in order for the app to use the “Read SMS” permission. The “Send SMS” permission lets you automatically send invites to the contacts you select without ever needing to leave the app. We will never send invites from you without your direction.
The app requests access to make phone calls so you can contact your driver from the Uber app if needed.
The mapping libraries in the app use these permissions to allow map data to be saved to your phone's external storage, like SD cards. By saving map data locally, your phone doesn't need to re-download the same map data every time you use the app.
We need access to the camera feature to let you use your phone's camera to scan your credit card instead of manually typing in your payment information. The image of your credit card will never be sent to Uber's servers.
Wi-Fi Connection Information
Uber's mapping libraries use this permission to see if a Wi-Fi connection is available. Determining whether Wi-Fi is available helps optimize the data used to display these maps.
Device ID & Call Information
This permission is used in conjunction with your own contact information to prepopulate your mobile number and country during registration. You can edit these fields, and the updated values are sent to Uber once your account is created. This permission is also used to obtain your Android device ID, which is sent to Uber's servers and used in fraud prevention efforts.
We use this permission if you decide to integrate shortcuts in the Uber app to your scheduled calendar events. If you opt in, the app will be able to access the calendar on your phone and we'll create shortcuts in the app so you no longer have to paste addresses from your calendar app as your destination. Your calendar data shared with Uber may include event title, timing of the event, location information about the event, event descriptions and number of attendees. All the calendar information will be stored on our servers and synced from your phone. Uber will not share your calendar with anyone else or reach out to any event invitees of your contacts on your behalf without your permission.
If you opt out of this permission, we will delete all calendar data from this phone associated with your account. To proactively delete all your calendar data from Uber’s servers, in the Uber App, go to Settings, Calendar Events, and tap “Clear my calendar data from Uber”.
This permission generates Google Cloud Messaging (GCM) tokens associated with a user's account. As with all GCM implementations, the token is sent to Uber's servers so that notifications can be sent to you.
This permission is required by Google Play Services — which provides core Google API functionality to Android applications — to allow your app to make use of Google web-based services (Google Maps API v2 in Uber's case).
**Google doesn't explicitly provide documentation for this permission, but the above link will refer you to the relevant documentation around using the Google Maps Android API.
Uber's mapping libraries use this permission to optimize the data used to display their maps.
This permission is required to access the internet, including communicating with Uber's servers, connecting with third-party services, and downloading map data.
This permission allows the Uber app to vibrate your phone when something important happens, e.g. when you receive a notification that your driver has arrived.
This permission wakes your phone up when a notification is received.
This permission is used by Uber to notify you when a network connection is unavailable.
If you have any questions, you can write us at email@example.com.