Step 8 of 23
personal data, consent, right to deletion, breach notification, fines
GDPR, PDPA — ข้อมูลส่วนบุคคลคืออะไร เก็บได้แค่ไหน ลบเมื่อไหร่ ค่าปรับเท่าไหร่
Data privacy is not just a legal checkbox. It is a matter of trust, reputation, and survival.
Fines for non-compliance can reach tens of millions of dollars or a percentage of global revenue, whichever is higher. But the real cost is often reputational. When customers learn their data was mishandled, they leave. When partners learn you are non-compliant, they stop sharing data with you.
Three forces drive data privacy:
| Force | What It Means |
|---|---|
| Legal | Regulations like GDPR (Europe) and PDPA (Southeast Asia) impose specific obligations |
| Ethical | People have a right to know how their information is used |
| Business | Trust is a competitive advantage. Handling data well builds it; mishandling destroys it |
"Personal data" is any information that can identify a person, directly or indirectly:
| Direct Identifiers | Indirect Identifiers |
|---|---|
| Full name | IP address |
| Email address | Location data |
| Phone number | Device fingerprint |
| National ID number | Purchase history (combined) |
| Passport number | Date of birth + zip code |
Even if a single data point does not identify someone, combining several often can. This is why "we only collect anonymous data" is sometimes misleading -- true anonymization is harder than it sounds.
Consent. Individuals must know what data is being collected and why, and they must agree to it. Pre-checked boxes and hidden clauses do not count.
Purpose limitation. You collected an email address to send order confirmations. You cannot decide later to sell it to a marketing company.
Data minimization. Collect only what you need. If you do not need a customer's date of birth, do not ask for it.
Right to access and deletion. Individuals can ask what data you hold about them and request it be deleted.
Breach notification. If data is leaked or stolen, you must notify affected individuals and regulators -- often within 72 hours.
Compliance is not a one-time project. It is an operational practice:
If you collect, store, or use customer data (you almost certainly do), you have compliance obligations. The specifics vary by region and industry, but the principles are universal: be transparent, collect only what you need, protect it, and respect individuals' rights.
When engineers propose a new feature, ask: "What data does this collect? Where is it stored? Who has access? Are we compliant?" If they cannot answer, the feature should not ship until they can.
