An enterprise must be able to prove the data subject’s consent if a dispute arises. The article helps it design consent on websites, apps, calls and paper so that the evidence is kept.

About this article

Consent is valid only if it meets three conditions: the data subject consents voluntarily; the data subject knows clearly what they are agreeing to; the consent is expressed in a verifiable way. The enterprise must keep the consent and bears the burden of proving it in a dispute. If the enterprise has only a tick box and does not record the time and content of consent, that evidence is usually not enough.

The content is for general information and does not replace legal advice on a specific case.

An enterprise can check each form, screen or call script with six questions:

  1. Has the data subject been given enough information? This covers the types of data, the purpose of processing, the name of the controller or the controller and processor, and the data subject's rights and obligations.
  2. Is consent separated by purpose? Buying goods, receiving promotions and sharing with partners are three different purposes.
  3. Is consent tied to a condition? An enterprise may not make use of the service conditional on the data subject consenting to purposes beyond the agreement.
  4. Does the data subject have to act positively to consent? Silence or no response is not consent. The enterprise may not set consent as the default.
  5. Are the options to consent and to refuse equally clear? The law prohibits the enterprise from giving unclear or misleading instructions between consent and refusal.
  6. Can the enterprise verify who consented, when, and to what?

When processing sensitive data, the enterprise must meet a seventh test: it must inform the data subject that the data is sensitive personal data. In some sectors, the notice must contain additional information. For example, finance and banking institutions must state clearly any credit scoring, the sources of data, the retention period and how to withdraw consent. An enterprise that uses data for advertising must tell customers clearly the content, method, form and frequency of product promotion.

Whatever method is used, the enterprise must be able to verify three things: who consented, when, and to what. The law lists the following methods:

MethodEvidence to keep
Paper documentThe signed copy, the date of signature and the version of the notice attached
Recorded callThe recording, including the notice read out and the answer of consent, with the calling number and the time
Text message syntaxThe message log, with the phone number, the syntax sent, the time and the invitation message that was sent
Email, website, platform or app with a technical consent settingA record of the account or device identifier, the time, the options chosen and the version of the text displayed
Other methods that can be printed or copied, including in electronic or verifiable formDepends on the method, but all three elements must be provable

An e-commerce site uses analytics and behavioural advertising code. Its current banner has a large "Accept" button and a small "Customise" link. Tracking code runs as soon as the page loads.

Conclusion: this does not meet the requirements. Data from tracking a person's behaviour online is sensitive data. The enterprise may collect data through website tracking for behavioural advertising only with the user's consent. The enterprise should do four things: block tracking code until the user consents; place a "Refuse" button at the same level as "Accept"; allow a separate choice for each group of purposes; keep a record of the choice together with the banner version.

A food delivery app asks for location access through the operating system dialog. The enterprise treats the user's tap on "Allow" as consent to every use of location data, including advertising suggestions.

Conclusion: the operating system dialog only lets the app read the location. The dialog does not state the purpose, the controller or the data subject's rights. Location determined through location services is sensitive data. The app should have its own consent screen. The screen states that location data is used for delivery and, if applicable, for advertising. The user gets a separate choice for each purpose and a notice that the data is sensitive.

3.3. Calls: the script must give the full information before asking for consent

An insurer calls prospective customers and asks, "Do you agree to let us advise you?". The call is recorded.

Conclusion: this question does not tell the customer the types of data, the purpose or the name of the controller. The script should include a short passage covering those points and how to withdraw consent. Only then should the agent ask for consent for each purpose. Health information is sensitive data. If the agent asks about health for insurance advice, the agent must tell the customer that this is sensitive data. The insurer must store the recording with the customer code so that it can be retrieved when needed.

A gym uses a membership form with a single signature at the bottom, under the small print "I agree that the gym may use my information for business purposes and share it with partners".

Conclusion: this bundled consent does not meet the requirement of consent for each purpose. The gym should split the form into separate, unticked boxes for each purpose: receiving promotions, and sharing with named partners. The gym needs no additional consent to perform the membership contract. For the other purposes, the gym needs consent. The gym must keep the paper or scanned copy as proof.

The controller and the controller and processor must keep records of consent. In a dispute, they bear the burden of proving it. A consent record sufficient as proof should include:

  • The identity of the data subject, or of the account, device or phone number.
  • The time of consent.
  • What was consented to, including the version of the notice at that time.
  • The channel and method of consent.
  • The change history, including the time of any withdrawal.

Each time the notice changes or a new purpose is added, the enterprise should keep the new version and obtain consent for the new part. If the enterprise validly obtained consent under the previous rules before 1 January 2026, it may continue to use that consent for ongoing processing without obtaining it again. For a new purpose arising afterwards, the enterprise needs new consent.

5. Withdrawal requests must be handled within the statutory time limits

Data subjects may withdraw consent in writing, including in electronic or verifiable form. On receiving a request made in accordance with the procedure, the enterprise must:

  • Respond within 2 working days and inform the data subject of the procedure for stopping processing.
  • Stop processing within 15 days. This period is 20 days if the enterprise must ask a processor or third party to stop processing as well.
  • If an extension is needed, extend only once and by no more than 15 days. The enterprise must give reasons for the extension and be able to show that it is necessary and reasonable.

Withdrawal does not affect processing carried out before it. Nor does the right of withdrawal apply to activities within the no-consent cases. The enterprise should place an unsubscribe link in every promotional message and a consent management section in the user account, so that withdrawing is no harder than consenting.

Under the GDPR, withdrawing consent must be as easy as giving it. Vietnamese law has no direct rule of this kind. However, it requires agencies, organisations and individuals to facilitate, and not to obstruct or hinder, the exercise of data subjects' rights, including the right to withdraw consent. Enterprises should therefore make sure that withdrawing is no harder than consenting.

In Planet49 (C-673/17, judgment of 1 October 2019), the Court of Justice of the European Union examined an online lottery with a pre-ticked box permitting cookies. The Court reached two conclusions:

  • A pre-ticked box, that is, a box the user must untick to refuse, does not create valid consent. This applies whether or not the data collected through the cookies is personal data.
  • Users must be told how long the cookies will operate and whether third parties may have access to them.

The Court applied the EU rules on privacy in electronic communications together with the GDPR.

IssueVietnamEuropean Union
Pre-ticked boxes, consent by defaultProhibitedNot valid, under Planet49 and the GDPR
Silence, no responseNot consentNot consent
Consent by purposeMust be given for each purposeMust be specific; where there are several purposes, consent must be given for each of them
Specific cookie rulesNo specific rules; tracking for behavioural advertising requires consent and behavioural data is sensitiveSpecific rules on storing and accessing information on the user's device, covering information that is not personal data
Methods of expressionThe law lists specific verifiable methodsNo fixed methods, but there must be a clear affirmative act
Burden of proofOn the controller and the controller and processorOn the controller

The conclusion in Planet49 is consistent with Vietnam's prohibition on default consent. Enterprises using a cookie management solution built to European standards can continue to use it. Even so, they need to add a notice on sensitive data. They also need to make sure that consent records meet the verification requirements of Vietnamese law.

  • Bundling every purpose into one consent box in the terms of use.
  • Pre-ticking the promotions box or running tracking code before the user chooses.
  • Recording only "yes" or "no" without the time and the version of the content.
  • Making withdrawal harder than consent, for example by accepting requests only in person.

8. What enterprises should do

  • List every data collection point: web forms, app screens, call scripts, paper forms.
  • Rewrite consent wording against the six tests, separated by purpose, with a notice where sensitive data is involved.
  • Remove every pre-ticked box and block tracking code until the user consents.
  • Set up a consent register with identifiers, times, content versions and change history.
  • Build a procedure for handling withdrawal requests, with internal deadlines shorter than the statutory ones. The procedure includes passing requests on to processors.
  • Review consents obtained before 2026 to identify which consents may still be used, and for which purposes.

Read on in the Personal data protection series