5 mistakes businesses make when obtaining consent to process personal data: GDPR, CCPA and Ukraine compared

Consent is in place. But is that enough? Most companies have probably added a checkbox on their website asking users to consent to the processing of their personal data at some point. It is not difficult to do. What is much harder is making sure that consent is actually needed, that its wording meets legal requirements, and that the company can use it for exactly the purposes it has in mind.

Consider this example: a customer provides their phone number to place an order. Does that give the company the right to send them marketing messages? And if a user agreed to the processing of their data when registering, can the company use that data for entirely different purposes a year later? In situations like these, a checkbox alone may not be enough.

It is also important to remember that different jurisdictions take different approaches. The GDPR, the US-based CCPA/CPRA and Ukraine’s Law on Personal Data Protection have different requirements when it comes to consent and other legal bases for processing. As a result, a practice that seems perfectly normal to a business may not necessarily be lawful.

We have put together five common mistakes businesses make when obtaining consent. We recommend checking your forms, contracts and internal processes against them. You may find that some things need to be reviewed sooner rather than later.

Mistake 1. Treating consent as a universal legal basis for processing personal data

When a company handles personal data, asking users to consent to its processing may seem like the easiest option. You have probably seen a consent statement under a registration form or a separate checkbox at checkout. The logic seems straightforward: the person has agreed, so the company has permission to use their data. But data protection law is not quite that simple. In fact, this approach can sometimes create unnecessary restrictions for the business.

Under the GDPR, consent is just one of six legal bases for processing personal data. For example:

  1. To accept an order, arrange delivery or take other steps necessary to perform a contract with a customer, a company may rely on the necessity of performing that contract.
  2. If processing is required to comply with a legal requirement, the company may rely on a legal obligation.
  3. In certain circumstances, a company may also rely on legitimate interests, provided that the processing is genuinely necessary and the individual’s rights and interests do not override those interests.

Read more: Legitimate interest in marketing: a lawful basis or a shortcut to complaints? 

Important: before asking for consent, determine whether you actually need it.

If a company chooses to rely on consent, it must ensure that consent is freely given, specific, informed and unambiguous. It must also allow individuals to withdraw it at any time. If they do, the company must stop any further processing based on that consent unless another valid legal basis applies.

That is why asking for consent when it is not actually needed is not always a safe strategy. By doing so, the company ties its processing to a legal basis that comes with additional requirements and gives individuals the right to withdraw their consent at any time. And if the company intends to continue processing the data even after consent has been withdrawn, another question arises: did it choose the right legal basis in the first place?

The UK Information Commissioner’s Office (ICO) also addresses this issue in its guidance on consent.The ICO gives the example of a credit card company that asks customers to consent to sharing their data with credit reference agencies, but would in fact continue sharing that data even if a customer refused or withdrew consent, relying instead on legitimate interests. According to the ICO, asking for consent in this situation is inappropriate: the individual does not have a genuine choice, and the company creates the misleading impression that it would stop processing the data if consent were withdrawn. If legitimate interests are the appropriate legal basis, the company should identify and justify that basis rather than ask for consent as a formality.

Ukrainian law does not make consent the only basis for processing either. Under Articles 6 and 11 of Ukraine’s Law on Personal Data Protection, processing may rely on several legal grounds, including consent, compliance with a legal obligation, the need to perform a transaction, the protection of vital interests or the controller’s legitimate interests. Ukrainian businesses should therefore first determine the legal basis on which they process personal data and only then decide whether a consent checkbox is necessary.

California takes a somewhat different approach from Europe. The CCPA/CPRA does not require businesses to obtain prior consent for every collection of personal information. Instead, the law focuses on informing consumers and giving them the right to opt out of the sale or sharing of their personal information for cross-context behavioural advertising. There are, of course, exceptions where opt-in consent is required. For example, specific rules apply to the sale or sharing of personal information belonging to minors: businesses generally need affirmative authorisation for consumers aged 13 to 15, and parental or guardian consent for children under 13.

This means that the same consent form will not necessarily work for customers in the EU, Ukraine and California. The starting point should be a much more important question: what is the legal basis for processing these particular data for this particular purpose? Once that is clear, it becomes much easier to determine whether consent is needed, what information must be provided to the individual and how their rights should be protected.

Mistake 2. Treating a Privacy Policy as a substitute for informed consent

A company launches a website and publishes a privacy policy. The document explains what personal data is collected, why it is needed and who it may be shared with. The team assumes that this is enough because users have been informed and are therefore aware of the company’s practices. But there is an important difference between informing someone about data processing and obtaining their consent to it.

A privacy policy is primarily an information document. It explains who processes the data, for what purposes, on which legal basis, how long the information will be retained and what rights the individual has. But publishing this document on your website does not mean that users have automatically agreed to every activity described in it. Nor does a statement such as “by continuing to use this website, you agree to this privacy policy” work where the law requires a clear and unambiguous expression of consent.

The GDPR draws a fairly clear distinction between these obligations. Articles 13 and 14 set out the information that a controller must provide to data subjects, while Articles 4(11) and 7 establish the requirements for valid consent. For example, a company may state in its privacy policy that it uses personal data for personalised advertising. That statement alone does not mean that the user has given valid consent to such processing.

Important: fulfilling the obligation to inform individuals does not replace obtaining consent where consent is the legal basis for a particular processing activity.

Ukrainian law also distinguishes between informing individuals and establishing a legal basis for processing. Article 12 regulates the information that must be provided to data subjects, including details about the controller, the personal data collected, their rights, the purpose of collection and the parties to whom the data may be transferred. Article 11 sets out the legal bases for processing, including consent. Therefore, having a privacy policy that describes the company’s practices does not, by itself, prove that a user has consented where consent is required for a particular activity.

In California, the CCPA/CPRA likewise does not treat a notice about data practices as consent. Businesses must inform consumers about how their personal information is used and provide them with rights such as the right to opt out of its sale or sharing. Simply mentioning this right in a privacy policy is not enough if there is no actual mechanism through which consumers can exercise it.

A company may have a privacy policy that is legally sound, yet still have a completely inadequate consent or opt-out process. The reverse is also true: a well-drafted consent form does not release a business from its obligation to provide proper privacy information. These are two separate responsibilities, and both need to work together.

Mistake 3. Combining different processing purposes into a single consent

Imagine that a company opens registration for a free webinar. To receive the access link, users need to provide their name and email address. But there is another condition: by clicking the registration button, they automatically agree to receive marketing emails, have their data used for personalised advertising and share their details with the company’s partners. Without accepting all these terms, they cannot register.

From the company’s perspective, this seems convenient: one checkbox covers several things at once. But for an ordinary user, registering for a webinar and agreeing to receive marketing messages are two entirely different matters. Someone may want to attend the webinar but have no interest in receiving advertising or sharing their contact details with other companies. If they cannot opt out of marketing, it raises the question of whether their choice was genuinely voluntary.

Under the GDPR, consent must relate to a specific purpose. If a company intends to use personal data for several different purposes and relies on consent as its legal basis, it must clearly explain each purpose so that individuals can make an informed choice. This does not mean that a separate checkbox is always required for every individual processing operation. However, a company cannot hide several different purposes behind one vague statement that leaves users unsure what they are actually agreeing to.

CNIL case: sharing data with a social network for advertising purposes – €3.5 million fineAt the end of 2025, the French data protection authority, CNIL, fined a company €3.5 million for transferring customers’ contact details to a social network for targeted advertising without valid consent. The company used the email addresses and phone numbers of loyalty programme members for advertising targeting on a social network. It relied on consent that customers had given when joining the loyalty programme and agreeing to receive marketing messages by email or SMS.However, CNIL emphasised that consent to receive marketing messages does not automatically mean consent to transfer contact details to a social network for advertising targeting. Customers had not been properly informed about this transfer when joining the loyalty programme, and the company’s documents did not explain its purpose clearly enough. The regulator therefore found that the consent was not sufficiently informed. The infringement affected more than 10.5 million people.

Ukrainian law also requires businesses to distinguish between processing purposes and the scope of data collected. Article 6 of Ukraine’s Law on Personal Data Protection requires the purpose of processing to be clear and lawful, and the data itself to be adequate and not excessive in relation to that purpose. Companies should therefore assess separately which data is needed for registration, which is needed for marketing and which may be required for sharing with partners. If consent is necessary for a particular activity, it should relate to that specific purpose rather than serve as a general permission for any future use of the information.

The CCPA/CPRA follows a different model. Businesses covered by the law must inform consumers about the personal information they collect and how they use it, and must provide the rights established by the law. For example, in certain circumstances, individuals can opt out of the sale or sharing of their personal information for targeted advertising. However, not every transfer of data to a partner qualifies as a sale or sharing under the CCPA/CPRA, and not every new purpose requires prior consent. It all depends on the nature of the processing and the specific legal requirements.

In other words, problems arise when a company combines different purposes in a way that leaves users unsure what they are agreeing to or prevents them from refusing optional services. A broad, all-in-one consent may seem like a simple solution, but in practice it often conceals a lack of transparency about how personal data is used.

Mistake 4. Assuming that a checkbox or signature automatically proves consent

A company obtains consent to process personal data when entering into a contract. The customer signs the paperwork, their details are entered into the CRM system, and the company considers the matter settled: consent has been obtained. But later, a dispute arises. The customer says they never agreed to having their identity documents copied, receiving marketing messages or having their data shared with third parties. Can the company defend its position by relying solely on the signature under the contract?

Under the GDPR, the controller must be able to demonstrate that consent was obtained. Article 7(1) requires the company to show that the individual has consented to the processing of their personal data.

Article 4(11), in turn, defines consent through four essential elements: it must be freely given, specific, informed and unambiguous.

In other words, the evidence must show more than the fact that someone clicked or signed something. It must demonstrate that the person understood what they were agreeing to.

It is important to note that the GDPR does not prohibit obtaining consent through a checkbox, electronic confirmation or written signature. On the contrary, Recital 32 expressly recognises ticking a box on a website as one way of expressing consent. The problem arises when the box is pre-ticked, consent is buried among other contractual terms or the company cannot demonstrate that the individual received sufficient information.

In Planet49 (C-673/17), a company organised an advertising lottery for which users had to complete a registration form. The checkbox for consent to the use of cookies for advertising purposes had already been ticked. The Court of Justice of the European Union ruled that this did not meet the requirements for valid consent: a user does not actively express their wishes if they can consent simply by doing nothing. The Court also made clear that clicking the button to enter the lottery could not automatically be treated as consent to the use of cookies.

Another relevant example is Orange România (C-61/19).

The Romanian telecom operator collected and stored copies of customers’ identity documents. Its contracts contained a provision on consent to storing those copies, and the relevant checkbox had already been ticked by company employees before customers signed the documents. Customers who did not want to give consent had to submit a separate written refusal. The national data protection authority fined the operator because it had failed to demonstrate that valid consent had been obtained. The Court of Justice of the European Union drew attention to several circumstances:Customers had not ticked the relevant box themselves.The consent provision was not clearly separated from the other contractual terms.The wording could give customers the impression that the service would not be provided without consent to copying their identity documents, even though the operator could in fact enter into the contract without it.The Court emphasised that a signature on a document containing a pre-ticked box does not, by itself, prove that valid consent was given.

In Ukraine, Article 2 of the Law on Personal Data Protection defines consent as a voluntary expression of an individual’s will to grant permission for the processing of their personal data in accordance with a specified purpose. It is therefore important to distinguish between the formal presence of a signature and the individual’s actual willingness to consent. Although Ukrainian law does not contain an express equivalent of the GDPR’s Article 7(1) requirement to demonstrate consent, being able to substantiate the circumstances in which consent was obtained remains important when establishing the lawfulness of processing.

As mentioned earlier, California follows a different model. The CCPA/CPRA does not require prior consent for every collection of personal information, so there is no general obligation to prove consent for every such collection. Instead, the law identifies specific situations in which consent is required, such as the sale or sharing of personal information belonging to minors and certain uses of financial incentives. Businesses must also provide a way for consumers to opt out of the sale of their personal information where the law applies. This makes it important to keep records showing how relevant consumer requests have been handled.

The practical takeaway for businesses is that evidence of consent should make it possible to reconstruct the circumstances in which it was obtained. For an online form, keep the date and time of the user’s action, the wording or version of the consent notice, the processing purpose and the method used to confirm consent. For a paper contract, make sure the relevant provision is clear and separate from other terms, and that the signature or other action genuinely demonstrates the individual’s choice.

Mistake 5. Failing to provide a real opportunity to withdraw consent

A company launches a newsletter, sets up advertising campaigns and transfers contact details to its CRM and email marketing platforms. The first results are coming in, and every email contains an unsubscribe link. But after clicking it, users continue receiving messages. Why does this happen? Perhaps their email address is still on another mailing list, the data has already been synced to another platform, or the marketing team has simply created a new audience using the old database. Formally, the unsubscribe button exists, but in practice it does not work as users expect.

Under the GDPR, individuals have the right to withdraw their consent at any time (Article 7(3)). The process must be as easy as giving consent in the first place.

If a user agreed to everything with a single click, the company cannot then require them to submit paper applications, make phone calls or complete complicated forms to withdraw it. It is also important to understand that withdrawing consent does not make processing that took place lawfully before the withdrawal unlawful.

Once consent has been withdrawn, the company must stop processing the data where that processing relied on the withdrawn consent. However, this does not always mean that all data must be deleted immediately. For example, certain information may need to be retained to comply with legal obligations or to establish, exercise or defend legal claims. In such cases, the company must have another valid legal basis for retaining that information. What it cannot do is continue using the data for the purposes to which the individual has withdrawn consent.

Important: GDPR gives individuals the right to object to the processing of their personal data for direct marketing purposes (Articles 21(2)-(3)). This right applies regardless of whether the company relies on consent or another legal basis. An individual can object at any time to the use of their data for direct marketing, including related profiling. Once they do, the company must stop processing the data for those purposes. This means that the “Unsubscribe” link in a marketing email must work regardless of the legal basis on which the company originally built its mailing list.Read more: ​​Marketing compliance. How to sell without violating privacy

In Ukraine, Article 8 of the Law on Personal Data Protection gives data subjects the right to withdraw their consent where consent is the basis for processing. However, withdrawing consent should not automatically be treated as a request to delete all data. What happens next depends on whether other lawful grounds for processing and retaining the information exist, as well as on the circumstances of the particular case. Companies should take this into account when designing their opt-out procedures: they need to identify which processing activities must stop, which data can no longer be used for the relevant purpose and whether there are grounds for retaining certain information in their systems.

The CCPA/CPRA does not provide a general right to withdraw consent for any processing in the same way as the European framework. Instead, consumers have the right to opt out of the sale of their personal information and its sharing for cross-context behavioural advertising. Businesses must provide an appropriate opt-out mechanism and honour applicable signals, such as Global Privacy Control. A request to withdraw consent under the GDPR and an opt-out request under the CCPA/CPRA are therefore different legal mechanisms, even though both may require changes to how advertising systems operate.

Whatever the legal framework, the conclusion is the same: a company’s promise to respect users’ choices must work in practice, not just appear in the wording of a settings page. If data is synced between a website, CRM, email marketing services and advertising platforms, the opt-out process must cover the entire chain. Otherwise, the company risks continuing to process personal data even after the individual has clearly said no.

GDPR, CCPA and Ukrainian Law: key differences

As you can see, another common mistake is using the same consent model across all jurisdictions. The GDPR provides several legal bases for processing; the CCPA/CPRA focuses on consumer notices and specific rights relating to personal information; and Ukrainian law establishes its own rules on processing purposes, legal bases and consent.

QuestionGDPRCCPA/CPRAUkrainian Law
Is consent required for every processing activity?No. Article 6 provides six legal bases for processing, and consent is only one of them.No. The law does not establish a universal requirement to obtain prior consent for every collection of personal information.No. Article 11 provides several legal bases for processing, including consent and other circumstances established by law.
What makes consent valid?It must be freely given, specific, informed and unambiguous, and involve a clear affirmative action.Consent is not a universal prerequisite for collection. Specific requirements apply to certain activities and categories of consumers.Consent must be a voluntary expression of an individual’s will to allow the processing of personal data for a specified purpose.
Can several purposes be combined into one consent?Different purposes must not be concealed behind vague, general wording. Consent must cover specific purposes.Businesses must provide appropriate notice about the categories of personal information collected and the purposes for which it is used. Separate consent for every purpose is not a general CCPA/CPRA requirement.The purpose must be defined, and the data must be relevant to it. Where the purpose changes, the law provides for consent to processing in accordance with the changed purpose.
How must consent be demonstrated?Where processing is based on consent, the controller must be able to demonstrate that it was given (Article 7(1)).There is no universal equivalent of the GDPR’s Article 7(1) requirement for every collection. Businesses should document compliance with applicable requirements and consumer requests.Businesses should retain evidence of the individual’s expression of will and the circumstances in which consent was obtained.
What happens when an individual withdraws or opts out?Consent can be withdrawn. For direct marketing, individuals have a separate and unconditional right to object to processing for that purpose.Consumers can opt out of the sale or sharing of their personal information as defined by the law. Where applicable, businesses must honour Global Privacy Control signals.Individuals can withdraw consent where processing is based on it. Further action depends on whether another lawful basis exists.

Read more: Marketing compliance: TOP-5 mistakes that can lead to GDPR fines

Conclusion

Consent to process personal data is not just a formality that can be quickly added to a contract or registration form. Companies need to understand why they collect information, which legal basis they rely on and how they actually protect users’ rights. If the purposes of processing change, or an individual decides to withdraw consent or restrict the use of their data, this must be reflected not only in the documentation but also across the company’s internal systems.

The GDPR, CCPA/CPRA and Ukrainian legislation take different approaches to obtaining consent, informing individuals and giving them the opportunity to opt out. So, if your business operates across several markets, it is not a good idea to rely on one universal form or simply copy the rules of one jurisdiction for another. A much safer approach is to assess each data processing activity separately, identify the appropriate legal basis, take local requirements into account and regularly review your procedures whenever your product or business processes change.

If you need help reviewing your consent mechanisms, drafting consent forms and notices, configuring cookie banners or setting up consent withdrawal procedures, get in touch with the privacy experts at Legal IT Group!

Do you have any questions for the lawyers?
up to 500 characters
An error occurred
The request has been sent Thank you for your message! We will process it as soon as possible.

Articles on the topic

Go to the blog