Senate Al Franken asked Uber for clarification about an apparent “troubling disregard for customers’ privacy, including the need to protect their sensitive geolocation data.”  On November 19, 2014 Senator Franken sent a letter to Uber CEO Travis Kalanick about a tool known as “God view” which is:

… “widely available to most Uber corporate employees” and allows employees to track the location of Uber customers who have requested car service.

In at least one incident, a corporate employee reportedly admitted to using the tool to track a journalist. The journalist’s permission had not been requested, and the circumstances of the tracking do not suggest any legitimate business purpose. Indeed, it appears that on prior occasions your company has condoned use of customers’ data for questionable purposes

Senator Franken also had serious concerns:

…about the scope, transparency, and enforceability of Uber’s policies. Moreover, it is unclear what steps, if any, you have taken to ensure that your policies are adequately communicated to all employees, contractors, and affiliates, and to ensure that such policies are fully enforced.

The letter included these 10 questions about the Uber Privacy Policies:

1.      Mr. Michael, a senior executive, is reported to have made statements—suggesting that Uber might use private information to target journalists or others who have critiqued the company—that your company has since stated are flatly contrary to company policies. To what do you attribute such a failure at your company’s highest level to heed your own policies?

2.      What Mr. Michael is reported to have said sounds like it was intended to have a chilling effect on journalists covering Uber. Was any disciplinary action taken as a result of Mr. Michael’s statements?

3.      Where in your privacy policy do you address the “limited set of legitimate business purposes” that may justify employees’ access to riders’ and drivers’ data, including sensitive geolocation data?

4.      To whom is the so-called “God view” tool made available and why? What steps are you taking to limit access?

5.      Your privacy policy states that you may share customers’ personal information and usage information with your “parent, subsidiaries and affiliates for internal reasons.” On what basis do you determine what constitutes legitimate “internal reasons”? Why aren’t these standards set out for customers?

6.      Your privacy policy states that you may share “non-personally identifiable information” with third parties for “business purposes.” What does that mean exactly? Why aren’t customers asked to affirmatively consent to this use of their information? At a minimum, may they opt out of this information sharing?

7.      Your policies suggest that customers’ personal information and usage information, including geolocation data, is maintained indefinitely—indeed even after an account is terminated. Why? What limits are you considering imposing? In particular, when an account is terminated, why isn’t this information deleted as soon as pending charges or other transactional disputes are resolved?

8.      What training is provided to employees, as well as contractors and affiliates, to ensure that your company’s policies, as well as relevant state and federal laws, are being followed? In light of Mr. Michael’s recent comments, how do you plan to improve this training?

9.      Your spokeswoman has represented that your “policy is … clear that access to data is monitored and audited by data security specialists on an ongoing basis.” Where in your company policies is this discussed? How is this monitoring conducted? How frequently are audits completed? Are customers informed if their information has been inappropriately accessed?

10. Under what circumstances would an employee face discipline for a violation of Uber’s privacy policies? Have any disciplinary actions been taken on this basis?

It will be interesting to see how Uber responds and how federal agencies will follow-up on these alleged privacy issues

Leave a Reply

Your email address will not be published. Required fields are marked *