The Terms Checkbox on Your Sign-up Form: Can You Prove the User Agreed?
Most Vietnamese websites have a small line under the sign-up form: "I agree to the terms and privacy policy". The harder question: six months later, can you show which version this person agreed to, and when?
This article is for information only and is not legal advice. Check the primary text, or ask a lawyer about your specific case.
What the law asks of consent
Article 9 of the Personal Data Protection Law No. 91/2025/QH15 (in force since January 1, 2026) sets the main conditions:
- Voluntary and informed — the user knows what data, for what purpose, by whom (clause 2)
- Clear, specific and verifiable — expressible in writing, including electronic form (clause 3)
- Separate for each purpose — no forcing extra purposes beyond what was agreed (clause 4 a, b)
- Silence is not consent (clause 4 d)
Sign-up form checklist
- Never pre-tick the box. The user must tick it themselves.
- Separate the purposes. Agreeing to create an account is not agreeing to marketing messages. Don't bundle them.
- Say what they agree to, linking the exact terms and privacy policy.
- Don't make marketing consent a condition of using the service.
- Make withdrawal as easy as giving consent.
Evidence: the part people forget
A checkbox is not enough. In a dispute you must be able to prove it. A good consent record usually holds:
- When the user agreed
- The terms/policy version at that moment (hash or version number) — so you know which text they agreed to
- The specific purpose agreed to
- A lookup identifier (such as a user ID or email in your own system)
The record is itself personal data: keep only what you need, limit who can read it, and never publish it.
When the terms change
If you edit your terms, old consent is tied to the old text. A tidy approach: compare the version the user agreed to with the current one, and ask again when they differ.
How Widget.vn helps
Widget.vn's terms-consent widget is free: it adds a checkbox to your existing form with one snippet, blocks the submit button until ticked, and stores a server-side consent record (time, text version). It helps you keep evidence; it does not make a site compliant on its own — you still need the right policies and data-handling processes.
Sources: Personal Data Protection Law No. 91/2025/QH15 (Article 9); Decree 356/2025/ND-CP.