internet gdpr
How to handle account deletion of user with financial information and/or otherwise liability related information
<p>So, I read a post on reddit the other day about a user unhappy with Binance (crypto currency exchange company) for only being able to &quot;disable&quot; his account but not &quot;delete&quot; it.</p>
<p>Binance is used in Europe which means they must abide by the GDPR. Which states that a user may request information deletion.</p>
<p>However, this information is related to financials. Meaning if they delete it and some government comes after them they could be liable. So which takes precedence in this situation?</p>
<p>If they(government entity) prefer you to hold the financial information, couldn't any company argue that they can't delete user information for fear of be liable for.something?</p>

<p>The GDPR will probably not allow a successful demand for erasure in these circumstances. The company does not need to argue &quot;that they can't delete user information for fear of be liable for.something&quot; because GDPR art 17 1(c), 3(b), and 3(e) already make that case for the company.</p>
<p>Lets look at the relevant law.</p>
<p><a href="https://gdpr-info.eu/art-17-gdpr/" rel="nofollow noreferrer">GDPR Article 17</a> reads in relevant part:</p>
<blockquote>
<p>(1) The data subject shall have the right to obtain from the controller the erasure of personal data concerning him or her without undue delay and the controller shall have the obligation to erase personal data without undue delay where one of the following grounds applies:</p>
<p>(1) (a) the personal data are no longer necessary in relation to the purposes for which they were collected or otherwise processed;</p>
<p>(1) (b) the data subject withdraws consent on which the processing is based according to point (a) of Article 6(1), or point (a) of Article 9(2), and where there is no other legal ground for the processing;</p>
<p>(1) (c) the data subject objects to the processing pursuant to Article 21(1) and there are no overriding legitimate grounds for the processing, or the data subject objects to the processing pursuant to Article 21(2);</p>
<p>...</p>
<p>(3) Paragraphs 1 and 2 shall not apply to the extent that processing is necessary:</p>
</blockquote>
<blockquote>
<p>(3) (a) for exercising the right of freedom of expression and information;</p>
<p>(3) (b) for compliance with a legal obligation which requires processing by Union or Member State law to which the controller is subject or for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller;</p>
<p>...</p>
<p>(3) (e)  for the establishment, exercise or defence of legal claims.</p>
</blockquote>
<p>Art 17  Par 1 (a) only allows erasure when data are
&quot;no longer necessary&quot;. But depending on how the purposes were worded by the Controller, they may well still be necessary</p>
<p>Art 17  Par 1 (b) only allows erasure when  consent is withdrawn <strong>and</strong> consent was the legal basis for processing. But a contract with the user is a much more likely basis for processing for a financial service.</p>
<p>Art 17  Par 1 (c) requires erasure if the user objects and there is no &quot;overriding legitimate grounds for the processing&quot; but the needs to maintain financial records of a transaction is probably an &quot;overriding legitimate ground&quot;.</p>
<p>In any case par 3 alloys erasure to be refused &quot;for compliance with a legal obligation&quot; or &quot;for the establishment, exercise or defence of legal claims&quot;. Financial records may well fall into one or both of these categories, at least as regards transaction data.</p>
<p>In short it is far from clear that the GDPR will require erasure in these circumstances.</p>

<blockquote>
<p>couldn't any company argue that they can't delete user information for fear of be liable for.something?</p>
</blockquote>
<p>In most contexts, yes. The merit of that argument is premised on article 17(3)(b), (e) of the GDPR for as long as the potential claims have not prescribed.</p>
<p>In the context you outline, the exchange has to comply with regulations for purposes including, but not limited to, fiscal and anti-money laundering matters. The exchange knows or should know that the possibility that authorities may audit the exchange are not far-fetched. That imposes on the exchange the obligation to preserve records in the event that it is audited or investigated.</p>
<p>Additionally, the records might contain material evidence for ongoing, prospective/imminent, or potential litigation. Compliance with a deletion request could equitably forfeit the user's potential claims, but that does not imply that the controller must also waive the possibility of pursuing its own claims that could be proved by means of those records. To defeat the controller's premise, the user would need to prove that the records at issue cannot reasonably involve &quot;<em>the establishment, exercise or defence of legal claims</em>&quot; (article 17(3)(e)).</p>
