<!– wp:table {“className”:”purposes-table”} –>
<figure id=”table-6303″ class=”wp-block-table purposes-table”><table><tbody><tr><td>Name</td><td>Store and/or access information on a device</td></tr><tr><td>Legal text</td><td>Vendors can:<br>● Store and access information on the device such as cookies and device identifiers for the purposes presented to a user.</td></tr><tr><td>User-friendly text</td><td>Cookies, device identifiers, or other information can be stored or accessed on your device for the purposes presented to you.</td></tr><tr><td>Vendor guidance</td><td>● Allowable Lawful Basis: Consent.<br>● Purpose 1 is meant to signal whether the condition for lawful storing and/or accessing information on a user’s device is met where this is required. It is not a purpose for personal data processing in itself, unlike all other Purposes the Framework covers. Purpose 1 corresponds to the obligation of Article 5(3) of the ePrivacy Directive. While Purpose 1 is not a data processing purpose, is technically treated the same way for signalling purposes.<br>● Purpose 1 does not apply to processing identifiers or client information, etc. that is not accessed on a user device. For example, reading a device’s IDFA falls within Purpose 1, however processing an IDFA outside of reading it from a device, e.g. when receiving it as part of information sent through an ad request is not covered by Purpose 1.<br>● If information stored or accessed falls within the information covered by Special Feature 2 or Feature 3, Vendors must make sure to adhere to the opt in requirement of Special Feature 2 and the disclosure requirement of Feature 3 respectively in addition to the consent requirement of Purpose 1.<br>● Any personal data stored and/or accessed via Purpose 1 still requires another Purpose to actually be processed. For example, reading a user identifier from a stored cookie cannot be used to create a personalised ads profile without having obtained consent or met requirements for processing under a legitimate interest for the Purpose 3.</td></tr></tbody></table></figure>
<!– /wp:table –>
<!– wp:paragraph –>
<p>source: <a href=”https://iabeurope.eu/iab-europe-transparency-consent-framework-policies/” data-type=”URL” data-id=”https://iabeurope.eu/iab-europe-transparency-consent-framework-policies/”>IAB Europe</a></p>
<!– /wp:paragraph –>
