gdpr
Legal aspects of Firebase Crashlytics SDK
<p>Let's say we have a mobile app, where every user is associated with app-generated unique user id (ex. <code>57d2ef8b391277001aad7784</code>). </p>

<ul>
<li>Having the uuid itself that's not possible to identify a user. </li>
<li>Having the uuid and access to the app backend infrastructure that becomes possible (by querying users by uuid).</li>
<li>During sign-up to our service every user accepts Privacy Policy and allows us to store personal information on our backend infrastructure.</li>
</ul>

<p>What're legal aspects of usage <a href="https://firebase.google.com/docs/crashlytics/customize-crash-reports#set_user_ids" rel="noreferrer">Crashlytics.setUserIdentifier</a> method in such case? Is it safe to use considering GDPR changes?</p>

<p>I believe the answer depends on the jurisdiction user belongs to. I'd like to find a rock-solid legal answer at least for the US, the EU (GDPR), and Russia (152-FL).</p>

<p>[I'm not so well-versed on US and Russian law, thus I will limit my answer to EU law.]</p>

<p>Your specific use of a user identifier, as I understood from your question, can be classified as personal data, so in your case, the GDPR seems to apply. </p>

<p>This means that you need to have a) <em>legitimate purposes</em> to process that personal data (e.g. crash reporting) and b) <em>a legal justification for each purpose</em> of processing: it could be based on consent or another legitimate purpose (inc. your own legitimate interests). Consent might not be the best option for you, but it's up to you to decide.</p>

<p>In any case, you need to assess the risks to the data subjects (your users) before you decide. How likely is it that you will get breached, and what potential harm will that cause to your users?</p>

<p>These are some guidelines; my recommendation is that you read the law and the guidelines by the Article 29 Working Group and European Data Protection Board, or hire some good experts on this. There is no easy answer, or one size fits all solution. </p>

<p>The GDPR isn't so hard to understand or implement, but it does require some <strong>change in mindset</strong>. With the new law, processing personal data carries a higher risk of penalties, so you should do it only when it's absolutely necessary, and with respect to the rights of your users.</p>
