Skip to main content
For Indian SaaS, IT services, BPO and healthtech companies

GDPR Compliance Services for Indian companies serving the EU

No authority hands out a GDPR licence. What your EU customer, their auditor and a supervisory authority ask for is evidence: the records, contracts, transfer files and breach process behind your claim. We build that evidence pack.

  • Article 3 applicability tested and written down
  • Article 30 records, DPAs and sub-processor terms
  • SCC module plus a transfer impact assessment
  • Breach and rights procedures drilled, not filed
Reviewed by Industry Experts & Startup Specialists.
Last Updated: 
FREE Consultation Get Started @ ₹299 ₹0

Get Expert Consultation

Share Your Business Requirement

Instant Response 100% Confidential Expert Advice

Encrypted in transit We do not sell your data

EU and EEA countries covered
30
Breach notification clock
72 hrs
Maximum fine, global turnover
4%
Weeks to a defensible programme
4 to 8

Our partners & associations

Client RatingRazorpay TrustedZoho Partner
FAQs

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.

The scope test
The GDPR reaches companies with no office, entity or server in Europe. Article 3(2) applies it to any organisation that offers goods or services to people in the EU or EEA, or monitors their behaviour. Separately, Article 28(3) forces every EU client to push its obligations down to you by contract, which is how most Indian IT services and BPO companies first meet the Regulation. The first route makes you directly accountable to a supervisory authority. The second makes you accountable to your customer, whose own fine exposure sits behind every clause they ask you to sign.
  • Direct routeArticle 3(2): you target or monitor people in the EU
  • Contract routeArticle 28(3): your EU client passes obligations down
  • RepresentativeArticle 27 appointment, unless an exemption applies
Common Indian business models and how the GDPR reaches them
Your businessTypical roleHow the GDPR reaches youFirst thing to build
SaaS product sold to EU businessesProcessor for customer data, controller for your ownArticle 28(3) flow-down from every EU client, plus Article 3(2) if you market into the EUDPA, sub-processor list and processor-side Article 30 record
IT services, BPO or KPO for EU clientsProcessorContract flow-down; client audits and security questionnairesDPA, SCC module Two or Three and a transfer impact assessment
D2C e-commerce shipping to the EUControllerArticle 3(2): goods offered to people in the EULawful basis review, privacy notice and Article 27 representative
App or website with EU users and analyticsControllerArticle 3(2) monitoring limb, plus national ePrivacy rules on cookiesConsent layer, cookie audit and controller-side Article 30 record
Healthtech handling EU patient dataUsually processor, sometimes controllerArticle 9 special category data raises the risk profile sharplyDPIA under Article 35 and encryption and access controls
Recruitment or staffing into the EUController for candidatesArticle 3(2) services offered to people in the EURetention schedule, candidate notice and rights procedure
Indian company with an EU subsidiaryGroup: both rolesArticle 3(1) establishment limb applies to the EU entity directlyIntra-group agreement and a single group-wide record

Two exemptions people rely on that usually do not hold

The Article 30(5) exemption for organisations under 250 employees falls away when processing is not occasional, is likely to result in a risk, or involves special category data, which covers most continuous SaaS and BPO work. The Article 27(2) exemption from appointing an EU representative requires processing that is occasional and low risk and not large-scale special category data. Recurring, systematic processing does not qualify on either count.

Why ProTax

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.

Scope decided first

The Article 3 test is run and written down before any work starts, so you are not paying to comply with obligations that were never yours.

Evidence, not templates

Records, notices and contracts drafted against how your product actually processes data, because a generic template fails on the first follow-up question.

The whole vendor chain

Your obligations flow down to every sub-processor. We check that the terms you sign with clients are ones your own vendors can support.

Drilled, not filed

A breach procedure nobody has rehearsed fails at hour three of a 72 hour clock. We run the drill and fix what the drill breaks.

FAQs

Frequently asked questions about GDPR compliance in India, side by side

Key takeaway
The General Data Protection Regulation (EU) 2016/679 has applied since 25 May 2018 across the EU and the EEA. It is a regulation, not a certification scheme: no authority inspects you, licences you, or hands you a certificate. Compliance is a state you evidence on demand, through a record of what you process, a lawful basis for each purpose, contracts down your vendor chain, a documented transfer safeguard, security proportionate to the risk, and procedures that work when a data subject writes in or a laptop goes missing. Fines run to 20 million euro or 4 percent of global annual turnover, whichever is higher, but for most Indian vendors the sharper risk is commercial: failing due diligence and losing the contract.
  • 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.

ProTax privacy expert reviewing an EU data processing agreement with an Indian technology team 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
FAQs

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.

Controller and processor duties compared, GDPR
ObligationAs controllerAs processor
Decides purpose and means of processing Yes No
Keeps an Article 30 recordYes, full record of its own processingYes, of processing carried out for each controller
Needs a documented lawful basis (Article 6) YesNo, acts on the controller instructions
Publishes a privacy notice (Articles 13 and 14) YesOnly for its own data, such as employees
Answers data subject requestsYes, within one month under Article 12(3)Assists the controller on the DPA timeline
Notifies the supervisory authority of a breachYes, within 72 hours under Article 33Notifies the controller without undue delay
Carries out DPIAs (Article 35) YesAssists the controller
Signs an Article 28(3) contractYes, as the imposing partyYes, and mirrors it to sub-processors
Appoints an Article 27 representative if in scope Yes Yes
Direct fine exposure under Article 83Full rangeLimited 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.

FAQs

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.

FAQs

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.

GDPR evidence pack for an Indian controller or processor
DocumentAnchored inWho asks for itRefresh cycle
Data map and system inventoryFoundation for Article 30Internal, and auditors during scopingOn every product or vendor change
Record of processing activitiesArticle 30Supervisory authority, first requestAnnually and on change
Privacy notice and cookie policyArticles 13 and 14Public, regulators, customersAnnually and on change
Lawful basis register and balancing testsArticles 6(1)(f) and 9Regulators, enterprise buyersAnnually
Data processing agreementArticle 28(3)Every EU customerPer contract
Sub-processor list and notification commitmentArticle 28(2) and (4)Customers, continuouslyOn every addition
SCC package with the correct moduleChapter V, Decision (EU) 2021/914Customers and their counselOn relationship change
Transfer impact assessmentSchrems II, Case C-311/18Customers, regulatorsWhen the legal position moves
Security statement mapped to Article 32Article 32Security questionnairesAnnually, with test evidence
Data subject rights procedureArticles 12 to 22Regulators after a complaintAnnually
Breach response runbook and drill recordArticles 33 and 34Customers, regulators after an incidentAnnually, drilled
Retention schedule and deletion evidenceArticle 5(1)(e)Customers at terminationAnnually
DPIA reports where triggeredArticle 35Regulators for high-risk processingPer project
Article 27 representative appointment letterArticle 27Published in the noticeOn appointment change
Training recordArticle 39(1)(b) and accountabilityCustomers and auditorsAnnually
FAQs

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.

01

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.

02

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.

03

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.

04

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.

05

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.

06

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.

07

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.

08

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.

09

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.

10

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.

FAQs

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.

Standard Contractual Clauses modules, Commission Implementing Decision (EU) 2021/914
ModuleRelationshipTypical Indian scenario
Module OneController to controllerAn EU partner sends you customer data you then use for your own purposes
Module TwoController to processorThe common case: an EU client sends data to your Indian SaaS or services team
Module ThreeProcessor to processorYour EU client is itself a processor and you act as its sub-processor
Module FourProcessor to controllerAn 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.

FAQs

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.

GDPR response deadlines that apply to Indian controllers and processors
TriggerWho actsDeadlineAnchor
Personal data breach detected by a processorProcessor tells its controllerWithout undue delay, usually 24 to 48 hours by contractArticle 33(2)
Breach likely to risk individual rightsController tells the supervisory authority72 hours from becoming awareArticle 33(1)
Breach likely to result in high riskController tells the individualsWithout undue delayArticle 34(1)
Data subject access or erasure requestController respondsOne month, extendable by two for complex requestsArticle 12(3)
Request received by a processorProcessor forwards and assistsOn the DPA timeline, typically 3 to 5 working daysArticle 28(3)(e)
High-risk processing plannedController completes a DPIABefore processing beginsArticle 35(1)
DPIA shows unmitigated high riskController consults the supervisory authorityBefore processing beginsArticle 36(1)
Sub-processor changeProcessor notifies the controllerOn the notice period in the DPA, commonly 30 daysArticle 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.

FAQs

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.

GDPR administrative fine tiers under Article 83
FailureFine tierCeiling
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.

FAQs

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.

GDPR compared with the Indian DPDP framework
DimensionGDPRDPDP Act, 2023 and Rules, 2025
InstrumentRegulation (EU) 2016/679, applicable 25 May 2018Act of 2023, Rules notified 13 November 2025, phased to 13 May 2027
Terms usedController, processor, data subjectData Fiduciary, Data Processor, Data Principal
Lawful basesSix under Article 6, including legitimate interestsConsent, plus specified legitimate uses; no legitimate interests test
NoticeArticles 13 and 14 information dutiesItemised notice, with a right to a notice in the Eighth Schedule languages
Cross-border transfersChapter V safeguards; India has no adequacy decisionPermitted except to countries restricted by the Central Government
Breach reporting72 hours to the supervisory authority under Article 33Intimation to the Board and affected Data Principals, per the Rules
RegulatorNational supervisory authority in each member state, coordinated by the EDPBData Protection Board of India
Maximum penalty20 million euro or 4 percent of worldwide turnoverUp to 250 crore rupees per instance of breach
Extra duties for large processorsDPO, DPIA and records where thresholds are metSignificant 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.

FAQs

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
FAQs

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.
FAQs

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.

FAQs

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.

Yes, when the company is caught by Article 3(2) of the GDPR: it offers goods or services to people in the EU or EEA, or monitors their behaviour, even with no office or server in Europe. It also applies indirectly through contract when an Indian company processes personal data on behalf of an EU client, because Article 28(3) forces the client to pass the obligations down to you.
The General Data Protection Regulation (EU) 2016/679 is the European Union's data protection law, applicable since 25 May 2018, which sets out how personal data of people in the EU and EEA must be collected, used, secured, transferred and deleted, and what rights those people can exercise against the organisation holding their data.
There is no government-issued GDPR licence or registration. Article 42 allows approved certification schemes, and Europrivacy is the first scheme approved as a European Data Protection Seal, but most EU buyers do not ask for it. What they ask for is evidence: your records of processing, your data processing agreement, your transfer documentation, your security measures and your breach process.
Three parties in practice. Your EU customer checks it in vendor due diligence and security questionnaires. Their auditor checks it when the customer is itself audited. A supervisory authority checks it after a complaint or a breach, and it can act against a non-EU company through the Article 27 representative and through the EU controller you work for.
An Article 27 representative is a person or firm established in an EU member state, appointed in writing, who acts as the local contact point for data subjects and supervisory authorities. A controller or processor outside the EU that is caught by Article 3(2) must appoint one, unless the processing is occasional, low risk, and does not involve special category data on a large scale, or the organisation is a public authority.
If your processing is limited to acting for an EU controller and you do not target EU individuals yourself, the Article 3(2) test is usually not met on your own account, and no representative is required. Where you also sell directly to EU customers, run EU-facing websites, or profile EU visitors, the test can be met independently and the appointment obligation is yours.
A controller decides the purposes and means of processing. A processor processes personal data only on the controller's documented instructions. An Indian IT services or BPO company is normally a processor for client data and a controller for its own employee, marketing and website data. The same company can be both, on different data sets, at the same time.
The Article 30 record is an internal inventory of what personal data you handle: purposes, categories of data subjects and data, recipients, transfers outside the EU, retention periods and a general description of your security measures. It is the first document a supervisory authority asks for, and processors keep their own version listing processing carried out for each controller.

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.

FROM THE PROTAX LIBRARY

Recent Articles & Guides

Practical reading on business records, tax filings and the decisions that come with running a company.

Newsletter

Stay ahead on compliance, tax & business updates

Get selected business and compliance updates by email. Once a month, no spam.

  • 100% privacy
  • 1 email / month
  • Unsubscribe anytime
Contact ProTax
Chosen by individuals and businesses

Get Help With Your Business

Tell us what you need help with. Our team will review your enquiry and explain the next steps.

Free Consultation No Obligations Expert Advice
FREE Consultation Get Started @ ₹299 ₹0

Talk To ProTax

Share Your Business Requirement

Instant Response 100% Confidential Expert Advice
FREE Consultation Get Started @ ₹299 ₹0

Request a Free Quote

Share Your Business Requirement

Instant Response 100% Confidential Expert Advice
Make your EU data handling defensible 4 to 8 weeks Article 30 records