If I have concurrent user consents then can I combine these consents?
<p>I have an app that supports concurrent user consents.</p>
<p>Assume that I have:</p>
<ol>
<li><code>Consent A</code> that gives access to <code>https://example.com/resources/a</code></li>
<li><code>Consent B</code> that gives access to <code>https://example.com/resources/b</code>.</li>
</ol>
<p>But at some point my app needs access to these both: <code>https://example.com/resources/a</code> and <code>https://example.com/resources/b</code>. In a such situation, is it legal to combine these two consents and get access to these 2 resources or I need to get consent which immediately says that user has consented these 2?</p>
<p>I know it seems trivial: user gave consent so you have legal access.</p>
<p>But remember: these consents could be given independently of each other, they can refer to different resources (e.g. health and payment service), and could be given at completely different time.</p>

<p>GDPR consent does not apply to resources or activities, but to <em>processing purposes</em> – to the reason why you are using some data. Also, while consent must be specific, it is not necessary to tire the user with technical details – as long as they are able to consent to one purpose while being able to decline consent for unrelated purposes. And in many cases, no consent is needed at all. In particular, you won't need GDPR consent for processing activities that are strictly necessary to fulfil a contract. (But you do likely need explicit consent for dealing with health data.)</p>
<p>Here, I would think about what those separate and combined processing purposes are, whether they even need consent, and if so when and how you should seek that consent. In particular, an authorization grant for a health data endpoint does not equate GDPR-consent for using this health data for another purpose, and consent for a specific processing purpose could imply authorization for multiple endpoints.</p>
<p>In this sense, yes, it <em>can</em> be legal to “combine consent”, but it massively depends on the specific context of this app – and taking that context into account would be lega advice that can't be given here.</p>

gdpr consent