Data Sharing permissions
Uber minimizes data storage, fetching only the necessary information for e-receipt forwarding or roster sync, while maintaining strict data privacy and transparency.
-
For clients who enable only the e-receipt integration without roster synchronization, Uber acts purely as a data forwarding service.
- The only data accessed during the process is the Concur User_ID, which is used solely to confirm the employee’s active status within Concur before forwarding the receipt.
-
For clients enabling employee roster sync, the only data stored and visible within the dashboard includes:
- First Name
- Last Name
- Email Address
- Phone Number (optional, if provided)
- Additionally, the Concur User_ID is stored but is not visible or synced to the dashboard.
-
For clients enabling employee roster sync at the parent level, along with the above data fields, the “Address” field is also required to be shared.
- All available addresses (both work and personal) of the employee are fetched to facilitate splitting the roster into individual child dashboards using filters like Country, Region, City, etc.
- However, this address data is not stored by Uber.
¶ Data Sharing Summary
| Feature Enabled | E-Receipt Forwarding | Employee Roster Sync |
|---|---|---|
| Fetched (Pulled from Concur but not stored) | Concur User_ID | Given (First) Name, Last Name, Email, Status (Active/Inactive), Concur User_ID, Phone Numbers (For orgs NOT opted out), Employee address (work and personal) (Only for orgs enabling parent-level roster sync) |
| Stored | None | Given (First) Name, Last Name, Email, Concur User_ID, Phone Numbers (For orgs NOT opted out) |