Prior consent for storing or accessing information in terminal equipment (cookies and SDKs)
Storing information, or gaining access to information already stored, in the terminal equipment of a subscriber or user is allowed only on condition that the subscriber or user has given consent, having been provided with clear and comprehensive information in accordance with data protection law, in particular about the purposes of the processing. There are only two exceptions: technical storage or access for the sole purpose of carrying out the transmission of a communication over an electronic communications network, and storage or access strictly necessary to provide an information society service explicitly requested by the subscriber or user. Analytics, advertising attribution, A/B testing and personalised recommendation therefore all require prior consent, with a refusal path as easy as acceptance.
- Applies when
- Chinese AI companies operating websites, apps or embedded SDKs for EU users. Common failures: treating analytics SDKs and crash reporting as "strictly necessary" and skipping consent; loading third-party SDKs before consent; and relying on the implied-consent-by-continued-browsing pattern common in China, which is not accepted in the EU.
- Deadline: Consent must be obtained before storing or accessing information in terminal equipment.
- Evidence to retain
- · Cookie and SDK inventory covering purpose, category, lifetime and third-party recipients
- · Consent management platform configuration and consent and refusal logs
- · Technical verification that non-essential scripts do not load before consent
- · Item-by-item justification for any "strictly necessary" exemption claimed
Estimated first-time effort: 5–15 person-days (estimate, not a commitment)