Frequently asked questions about GDPR compliance in India, side by side
- InstrumentRegulation (EU) 2016/679, applicable 25 May 2018
- Reach27 EU member states plus Iceland, Liechtenstein and Norway
- CertificationVoluntary under Article 42; no mandatory licence
- Top fine tier20 million euro or 4 percent of worldwide turnover
Indian companies meet the Regulation from an unusual angle. Most do not sell to European consumers at all; they build or run systems for European businesses. That makes them processors, and a processor's duties are narrower than a controller's but far more visible, because they arrive as contract clauses with an audit right attached. The work is therefore less about grand privacy strategy and more about producing a specific set of artefacts that hold up when someone reads them closely.
The Regulation is also deliberately outcome-based. It rarely tells you which tool to buy or which retention period to set. It tells you to decide, document the decision, and be able to defend it. That is why two companies with identical stacks can produce very different compliance postures, and why a data map built from a real system inventory beats any template on the market.
Evidence pack What we produce, in the order buyers ask for it
Every artefact below has been asked for by an EU customer at some point in a vendor review. They are built in dependency order, because a data processing agreement written before the data map is a promise you have not checked you can keep.
- Data map and Article 30 record, split by controller and processor role
- Privacy notice, cookie and consent layer, retention schedule
- Article 28(3) DPA, sub-processor list and flow-down terms
- SCC module, transfer impact assessment and supplementary measures
- Security statement mapped to Article 32, with testing evidence
- Rights and breach procedures, plus the drill record behind them
One legal point worth being precise about
Nobody can make you "GDPR certified". Article 42 allows certification schemes approved by supervisory authorities, and Europrivacy is the first scheme approved as a European Data Protection Seal, but no EU authority issues a general compliance certificate, and no consultant can. Any provider promising one is selling something the Regulation does not contain. What genuinely moves a deal forward is a complete, internally consistent evidence pack, which is what this service produces.
Frequently asked questions about GDPR compliance in India
39 questions taken from real search queries, EU customer security questionnaires, EDPB guidance and the Regulation itself.
| Obligation | As controller | As processor |
|---|---|---|
| Decides purpose and means of processing | Yes | No |
| Keeps an Article 30 record | Yes, full record of its own processing | Yes, of processing carried out for each controller |
| Needs a documented lawful basis (Article 6) | Yes | No, acts on the controller instructions |
| Publishes a privacy notice (Articles 13 and 14) | Yes | Only for its own data, such as employees |
| Answers data subject requests | Yes, within one month under Article 12(3) | Assists the controller on the DPA timeline |
| Notifies the supervisory authority of a breach | Yes, within 72 hours under Article 33 | Notifies the controller without undue delay |
| Carries out DPIAs (Article 35) | Yes | Assists the controller |
| Signs an Article 28(3) contract | Yes, as the imposing party | Yes, and mirrors it to sub-processors |
| Appoints an Article 27 representative if in scope | Yes | Yes |
| Direct fine exposure under Article 83 | Full range | Limited to processor-specific duties, plus contractual liability |
The label is not chosen; it follows the facts. If you decide what happens to the data, you are the controller, whatever the contract says. A support tool that you configure, a model you train on client data for your own product improvement, or an analytics feature you switch on by default can quietly move you from processor to controller for that slice of processing, and with it comes a lawful basis you now need to justify.
Where the line usually moves without anyone noticing
Three moments turn a processor into a controller: using client data to train or improve your own product, running your own analytics over client environments, and retaining data after termination for your own purposes. Each is defensible if you decide it deliberately, disclose it, and pick a lawful basis. None of them survives a customer audit if it happened by default in a product decision nobody wrote down.
Frequently asked questions about GDPR compliance in India, side by side
39 questions taken from real search queries, EU customer security questionnaires, EDPB guidance and the Regulation itself.
Article 30 records
The processing inventory, kept separately for your controller and processor roles. Asked for first in almost every regulatory contact.
Articles 6 and 9 lawful basis
A documented basis for every controller purpose, with a balancing test where you rely on legitimate interests and a condition for special category data.
Articles 13 and 14 notices
Privacy information given at collection, and within a month where data came from somewhere else, matching what the record says you do.
Article 28 contracts
The mandatory processor terms, mirrored down to every sub-processor, with a sub-processor list and a change notification commitment.
Article 32 security
Measures appropriate to the risk, including encryption, resilience, restoration and a process for regularly testing effectiveness.
Articles 33 and 34 breach duties
Supervisory authority notified within 72 hours where required, individuals told without undue delay where the risk is high.
Chapter III rights
Access, rectification, erasure, restriction, portability, objection and automated decision safeguards, answered within one month.
Chapter V transfers
A valid safeguard for every export to India, currently the Standard Contractual Clauses plus a transfer impact assessment.
The obligation most often missed by Indian vendors
Not security. It is retention. Contracts promise deletion at termination, records list retention periods, and then backups, logs, ticketing systems and analytics warehouses keep the data anyway. Deletion is the one commitment a customer can test cheaply, by asking you to prove that an account deleted eighteen months ago is actually gone from every system on your own sub-processor list.
Frequently asked questions about GDPR compliance in India, side by side
39 questions taken from real search queries, EU customer security questionnaires, EDPB guidance and the Regulation itself.
| Document | Anchored in | Who asks for it | Refresh cycle |
|---|---|---|---|
| Data map and system inventory | Foundation for Article 30 | Internal, and auditors during scoping | On every product or vendor change |
| Record of processing activities | Article 30 | Supervisory authority, first request | Annually and on change |
| Privacy notice and cookie policy | Articles 13 and 14 | Public, regulators, customers | Annually and on change |
| Lawful basis register and balancing tests | Articles 6(1)(f) and 9 | Regulators, enterprise buyers | Annually |
| Data processing agreement | Article 28(3) | Every EU customer | Per contract |
| Sub-processor list and notification commitment | Article 28(2) and (4) | Customers, continuously | On every addition |
| SCC package with the correct module | Chapter V, Decision (EU) 2021/914 | Customers and their counsel | On relationship change |
| Transfer impact assessment | Schrems II, Case C-311/18 | Customers, regulators | When the legal position moves |
| Security statement mapped to Article 32 | Article 32 | Security questionnaires | Annually, with test evidence |
| Data subject rights procedure | Articles 12 to 22 | Regulators after a complaint | Annually |
| Breach response runbook and drill record | Articles 33 and 34 | Customers, regulators after an incident | Annually, drilled |
| Retention schedule and deletion evidence | Article 5(1)(e) | Customers at termination | Annually |
| DPIA reports where triggered | Article 35 | Regulators for high-risk processing | Per project |
| Article 27 representative appointment letter | Article 27 | Published in the notice | On appointment change |
| Training record | Article 39(1)(b) and accountability | Customers and auditors | Annually |
Frequently asked questions about GDPR compliance in India
39 questions taken from real search queries, EU customer security questionnaires, EDPB guidance and the Regulation itself.
Establish whether the GDPR applies to you
Run the Article 3 test and write down the conclusion. Offering goods or services to people in the EU or EEA, or monitoring their behaviour, puts you in scope directly. Working for an EU client puts you in scope through Article 28(3). The answer sets the scope of everything after it.
Map the data and decide your role
Inventory every system, feature, vendor and spreadsheet touching EU personal data, then fix your role per data set: controller for employee, website and marketing data, processor for client data. Same company, different roles, different duties.
Build the Article 30 record
Turn the map into the formal record: purposes, data and data subject categories, recipients, transfers, retention and a description of security measures. Processors keep a separate record per controller. Expect this to be the first document ever requested.
Fix the lawful basis and rewrite the notices
Select and document an Article 6 basis for each controller purpose, add an Article 9 condition for special category data, and record the balancing test wherever legitimate interests are used. Then rewrite the notice against Articles 13 and 14 to match.
Put the contracts in order
Sign an Article 28(3) DPA with every EU client, mirror the terms to every sub-processor, and publish a sub-processor list with a change notification commitment. Check that the audit, security and liability terms you accept are ones your vendor chain supports.
Build the transfer file
India has no adequacy decision. Document the Chapter V safeguard: the right SCC module from Decision (EU) 2021/914, a transfer impact assessment following Schrems II, and supplementary measures such as encryption, key control and a government access response procedure.
Harden security against Article 32
Encryption in transit and at rest, access control with joiner-mover-leaver discipline, logging and monitoring, patching, backup and restore testing, and vendor security review. Record what you implemented and how you test it, because Article 32 asks for regular testing.
Write the operational procedures
A rights procedure that meets the one-month deadline in Article 12(3), a breach procedure that notifies a controller without undue delay and a supervisory authority within 72 hours under Article 33, and a retention schedule that actually deletes when the period ends.
Appoint a representative or DPO where required
Appoint an Article 27 EU representative in writing where Article 3(2) catches you and no exemption applies, and name them in the privacy notice. Appoint a DPO where Article 37 requires one, publish the contact details and notify the supervisory authority.
Test it, then keep it alive
Run a breach drill against the 72 hour clock and a mock access request end to end. Then set the rhythm: refresh records on product and vendor change, revisit transfer assessments when the legal position moves, and repeat drills and training annually.
Not sure whether the GDPR reaches your company at all?
The Article 3 test takes one conversation. We will tell you if you are out of scope, in scope through contract only, or directly accountable, and what each answer costs to act on.
Frequently asked questions about GDPR compliance in India
39 questions taken from real search queries, EU customer security questionnaires, EDPB guidance and the Regulation itself.
| Module | Relationship | Typical Indian scenario |
|---|---|---|
| Module One | Controller to controller | An EU partner sends you customer data you then use for your own purposes |
| Module Two | Controller to processor | The common case: an EU client sends data to your Indian SaaS or services team |
| Module Three | Processor to processor | Your EU client is itself a processor and you act as its sub-processor |
| Module Four | Processor to controller | An EU processor returns data to a non-EU controller, such as a global group parent |
The clauses alone are not the safeguard. After the Court of Justice's judgment in Schrems II (Case C-311/18, 16 July 2020), the exporter has to assess whether the destination country's law and practice would undermine what the clauses promise, and add supplementary measures where it would. For India that assessment usually turns on government access powers, the routes through which access can be compelled, and what your architecture does about it: encryption with keys held outside the destination, strict access segregation, and a documented procedure for responding to any access demand.
Two neighbouring facts get confused with this. The EU-US Data Privacy Framework, whose challenge the General Court dismissed in Case T-553/23 on 3 September 2025, only helps for the US leg of a chain where your sub-processor is certified under it. And the UK route is separate: the European Commission renewed UK adequacy on 19 December 2025 for six years, to 27 December 2031, after assessing the Data (Use and Access) Act 2025, while UK to India transfers use the UK International Data Transfer Agreement or the UK Addendum.
What a usable transfer impact assessment contains
Four parts: a description of the transfer including the data, purpose and onward recipients; an assessment of the destination law and practice relevant to government access; the supplementary technical, contractual and organisational measures you apply; and the conclusion, with the review trigger that will bring you back to it. Customers increasingly ask for this by name, and the ones who do not ask still expect you to have it when their own regulator asks them.
Frequently asked questions about GDPR compliance in India, side by side
39 questions taken from real search queries, EU customer security questionnaires, EDPB guidance and the Regulation itself.
| Trigger | Who acts | Deadline | Anchor |
|---|---|---|---|
| Personal data breach detected by a processor | Processor tells its controller | Without undue delay, usually 24 to 48 hours by contract | Article 33(2) |
| Breach likely to risk individual rights | Controller tells the supervisory authority | 72 hours from becoming aware | Article 33(1) |
| Breach likely to result in high risk | Controller tells the individuals | Without undue delay | Article 34(1) |
| Data subject access or erasure request | Controller responds | One month, extendable by two for complex requests | Article 12(3) |
| Request received by a processor | Processor forwards and assists | On the DPA timeline, typically 3 to 5 working days | Article 28(3)(e) |
| High-risk processing planned | Controller completes a DPIA | Before processing begins | Article 35(1) |
| DPIA shows unmitigated high risk | Controller consults the supervisory authority | Before processing begins | Article 36(1) |
| Sub-processor change | Processor notifies the controller | On the notice period in the DPA, commonly 30 days | Article 28(2) |
Where the 72 hours actually goes
The clock starts when you become aware, not when you finish investigating. In real incidents the first day is spent deciding whether personal data was involved at all, the second collecting scope, and the notification is drafted in what is left. Companies that meet the deadline are the ones that decided in advance who declares an incident, which contacts get called, what a holding notification looks like, and that a supervisory authority accepts a phased notification under Article 33(4) when the full picture is not yet available.
Frequently asked questions about GDPR compliance in India, side by side
39 questions taken from real search queries, EU customer security questionnaires, EDPB guidance and the Regulation itself.
| Failure | Fine tier | Ceiling |
|---|---|---|
| Processor duties, records, security, breach notification (Articles 8, 11, 25 to 39, 42, 43) | Lower tier, Article 83(4) | 10 million euro or 2 percent of worldwide annual turnover, whichever is higher |
| Principles, lawful basis and consent (Articles 5, 6, 7 and 9) | Upper tier, Article 83(5) | 20 million euro or 4 percent of worldwide annual turnover, whichever is higher |
| Data subject rights (Articles 12 to 22) | Upper tier, Article 83(5) | 20 million euro or 4 percent of worldwide annual turnover, whichever is higher |
| Transfers to a third country without a valid safeguard (Chapter V) | Upper tier, Article 83(5) | 20 million euro or 4 percent of worldwide annual turnover, whichever is higher |
| Ignoring a supervisory authority order or refusing access (Article 58) | Upper tier, Article 83(5) | 20 million euro or 4 percent of worldwide annual turnover, whichever is higher |
For a vendor in India, the statutory ceiling is rarely the operative risk. The operative risk is the chain of consequences that starts earlier: a security questionnaire you cannot answer, a deal that stalls in procurement, a customer whose own regulator asks about its vendors, an indemnity clause that transfers their exposure to you, and a termination right that triggers on a material breach of the DPA. Every one of those arrives years before a supervisory authority would.
Frequently asked questions about GDPR compliance in India, side by side
39 questions taken from real search queries, EU customer security questionnaires, EDPB guidance and the Regulation itself.
| Dimension | GDPR | DPDP Act, 2023 and Rules, 2025 |
|---|---|---|
| Instrument | Regulation (EU) 2016/679, applicable 25 May 2018 | Act of 2023, Rules notified 13 November 2025, phased to 13 May 2027 |
| Terms used | Controller, processor, data subject | Data Fiduciary, Data Processor, Data Principal |
| Lawful bases | Six under Article 6, including legitimate interests | Consent, plus specified legitimate uses; no legitimate interests test |
| Notice | Articles 13 and 14 information duties | Itemised notice, with a right to a notice in the Eighth Schedule languages |
| Cross-border transfers | Chapter V safeguards; India has no adequacy decision | Permitted except to countries restricted by the Central Government |
| Breach reporting | 72 hours to the supervisory authority under Article 33 | Intimation to the Board and affected Data Principals, per the Rules |
| Regulator | National supervisory authority in each member state, coordinated by the EDPB | Data Protection Board of India |
| Maximum penalty | 20 million euro or 4 percent of worldwide turnover | Up to 250 crore rupees per instance of breach |
| Extra duties for large processors | DPO, DPIA and records where thresholds are met | Significant Data Fiduciary duties, including DPIA, audit and a DPO in India |
The overlap is large enough that running two programmes is waste. One data map, one notice and consent layer, one vendor contract set and one breach process serve both; what differs is the paperwork layered on top. Under the DPDP framework, the dates are now fixed: the Rules were notified on 13 November 2025, consent manager provisions take effect from 13 November 2026, and the substantive Data Fiduciary obligations from 13 May 2027. Any GDPR work done this year should be built so those additions drop in without a rebuild.
Frequently asked questions about GDPR compliance in India
39 questions taken from real search queries, EU customer security questionnaires, EDPB guidance and the Regulation itself.
Holds up under review
- A record of processing built from a real system inventory, where every row names an owner and a retention period
- A DPA whose sub-processor list matches the vendors your engineers actually use in production
- A transfer impact assessment that names the Indian access powers it considered and the measures that answer them
- Retention periods that are enforced by a job, with deletion evidence you can produce for a named account
- A breach runbook with named roles, a declared decision-maker and a rehearsal date within the last twelve months
- Security claims that map one to one onto Article 32 and onto whatever certification you hold
Falls over on the follow-up question
- A template record with generic categories, no owners, and retention marked "as required"
- A sub-processor list that omits the analytics, support and AI tools added after the list was written
- SCCs signed with the wrong module, or with the annexes left as unfilled placeholders
- A transfer impact assessment that concludes "no risk identified" without naming a single legal provision
- Deletion promised in the contract while backups, logs and warehouses keep the data indefinitely
- A breach procedure nobody has run, where the 72 hour clock is discovered mid-incident
- A privacy notice describing processing the product stopped doing two releases ago
Frequently asked questions about GDPR compliance in India
39 questions taken from real search queries, EU customer security questionnaires, EDPB guidance and the Regulation itself.
- Personal data
- Any information relating to an identified or identifiable natural person, under Article 4(1). Device identifiers, IP addresses, support-ticket contents and pseudonymised records are included where a person can still be singled out.
- Processing
- Any operation performed on personal data, from collection and storage to consultation, transmission, erasure and destruction. Merely hosting data is processing, which is why infrastructure vendors sit inside the chain.
- Special category data
- Data revealing racial or ethnic origin, political opinions, religious beliefs, trade union membership, genetic or biometric data used for identification, health, sex life or sexual orientation. Article 9 prohibits processing it unless a listed condition applies.
- Pseudonymisation
- Processing personal data so it can no longer be attributed to a person without additional information kept separately and secured. It reduces risk and is named in Article 32, but pseudonymised data is still personal data.
- Sub-processor
- Any vendor a processor engages to carry out part of the processing, from cloud hosting to a support desk or an AI feature. Article 28(4) requires the same data protection terms to be imposed down the chain.
- Adequacy decision
- A European Commission finding that a country ensures an essentially equivalent level of protection, allowing transfers without further safeguards. India does not hold one, so Indian transfers rely on Chapter V tools.
- Supervisory authority
- The independent public authority in each member state that enforces the GDPR, investigates complaints and issues fines. Cross-border cases run through the lead authority mechanism coordinated by the European Data Protection Board.
- Accountability
- The Article 5(2) principle that a controller must not only comply but be able to demonstrate compliance. It is the reason evidence, and not intention, is what an audit or an investigation actually measures.
Frequently asked questions about GDPR compliance in India
39 questions taken from real search queries, EU customer security questionnaires, EDPB guidance and the Regulation itself.
Frequently asked questions about GDPR compliance in India
39 questions taken from real search queries, EU customer security questionnaires, EDPB guidance and the Regulation itself.
Start with the question that decides everything else
Does the GDPR apply to you, and in which role? Our privacy experts run the Article 3 test, review your contracts and data flows, and give you a scoped plan for the evidence pack your buyers keep asking for.


