Why an Indian enterprise should care
If you offer goods or services to people abroad, process their data for a foreign client, or share data across a global group, someone else's data protection law may sit alongside India's. You do not need to master every regime. You need to know which ones can reach you and what they broadly demand.
The reference framework: Europe's GDPR
The world's most influential data protection law. Its ideas shaped most later laws, including India's: defined lawful bases for processing, individual rights, breach notification, data protection officers and impact assessments for risky processing, and records of processing as an explicit legal duty. Its fines are the headline: up to 20 million euros or 4 percent of worldwide annual turnover, whichever is higher, enforced by national authorities in each member state. If your enterprise touches European customers or European clients' data, GDPR is the regime to understand first.
The short profiles
| Regime | One-line character | What matters for an Indian enterprise |
|---|---|---|
| European Union, GDPR | The strict, influential baseline | Applies to offering goods or services to people in the EU; expect client contracts that pass GDPR duties down to you |
| United Kingdom, UK GDPR and Data Protection Act | GDPR's near-twin after separation | Similar obligations, separate authority; treat like the EU for planning |
| United States, state laws (California's CCPA/CPRA leads) | No single federal law; a patchwork of state regimes | Consumer rights and opt-outs; matters if you serve California residents or build for US clients |
| Brazil, LGPD | GDPR-style, broad national law | Similar structure and rights; relevant for LatAm business |
| Singapore, PDPA | Established, business-pragmatic regime | A common hub for Asian operations; clear consent and transfer rules |
| Canada, PIPEDA | Long-standing federal privacy law | Consent-centred; relevant for North American clients |
| Australia, Privacy Act | Established principles-based law | Reforms are tightening it; watch if you serve Australian customers |
| Japan, APPI | Mature law with transfer rules | Cross-border transfers need care and consent or equivalent safeguards |
| South Korea, PIPA | Strict, actively enforced | Strong consent and localisation-flavoured practice |
| South Africa, POPIA | GDPR-style, fully in force | Relevant for African operations |
| UAE and Saudi Arabia, PDPLs | Newer, fast-developing Gulf regimes | Growing requirements with localisation elements; check before Gulf expansion |
Each of these deserves its own verified profile before you rely on it for a decision; this table is orientation, not advice.
India in this company
India's law shares the family resemblance: consent and notice, individual rights, breach duties, a dedicated authority. It is narrower in some places (no general portability or objection rights) and distinctive in others (a small set of permitted non-consent bases, penalties as fixed rupee caps rather than turnover percentages). Indian enterprises used to GDPR-style client contracts will find the concepts familiar; Indian enterprises new to all of this should learn the Indian framework first, since it is the one that applies at home.
How to use this page in planning
- Map where your customers, employees, vendors and group entities are. Each geography on that list is a candidate regime.
- For any country where you have real business, get a verified profile before signing commitments: scope, rights, regulator, penalties, transfer rules.
- When a foreign client's contract passes its home-law duties to you, treat those clauses as obligations, not boilerplate.
Next step
A resource many enterprises underuse until after an incident: cyber insurance.