Skip to main content
COOKIE NOTICECOOKIE CHOICE

We use cookies for analytics (Google Analytics) and ad measurement (Google Ads, including remarketing, and ChatGPT Ads by OpenAI). Strictly necessary cookies keep the site working. See our Cookie Policy for what each one does and how to opt out.

We’d like to use cookies for analytics (Google Analytics) and ad measurement (Google Ads, including remarketing, and ChatGPT Ads by OpenAI), and none of them is set unless you accept. Cookie Policy

EU Data Protection Regulation

GDPR Compliance Services

Achieve comprehensive compliance with the EU General Data Protection Regulation. Protect personal data, implement data subject rights, and avoid penalties up to €20 million or 4% of global revenue.

7 GDPR principles fully implemented across your organization

Complete data subject rights framework (Articles 15-22)

International data transfer mechanisms (BCRs, SCCs, adequacy decisions)

Explore 7 Principles

EU GDPR Compliance  ·  99 Articles  ·  Global Data Protection

99GDPR Articles11 Chapters
7Core PrinciplesArticle 5
8Data Subject RightsArticles 15-22
€20MMax Fineor 4% revenue
  • 21K School
  • Arali AI
  • Assemblage Health
  • Cargoflash
  • Data Alchemy
  • Dsider
  • Factor Avenue
  • GroundHog Apps
  • immiOne
  • IPPC Group
  • LiveMindz
  • Lyik
  • NPCI
  • Phyllo
  • Softsages
  • Surface Labs
  • Vault Infosec
  • Xonar
  • Harriman Global
  • Dune Dynamics
  • Aairo
  • Ardem
  • autoResilience
  • Citius Cloud
  • Datavi Cloud
  • eSolutions
  • Forsys
  • HighRadius
  • Intellify
  • Jarex
  • LookDeep Health
  • Mashreq
  • PayU
  • Provar
  • Soudah Development
  • TalentBridge
  • VisiLean
  • Zepic
  • Procedure
  • incep²t
  • American Express
  • Ascent Risk & Resilience
  • Auxanova
  • Cohivra
  • DollarTraq
  • Excers Technologies
  • Girmiti
  • IIIT Delhi
  • intelXIP
  • Komp AI
  • Loveinstore
  • Maxima
  • Personaify
  • Sebone Technologies
  • Spinny
  • Uni5
  • WyraAI
  • JudoNxt
  • BuyNxt · Green Receipt
Introduction

What is GDPR?

The General Data Protection Regulation (GDPR) is the European Union's data protection law that governs how any organisation collects, uses, and stores the personal data of people in the EU. It applies extraterritorially, so any company — whether based in India, the US, the UK, or anywhere else — that handles the data of EU residents (customers, employees, or website visitors) must comply. GDPR sets out 7 data-protection principles and 8 data subject rights, requires a lawful basis for every processing activity, mandates Data Protection Impact Assessments (DPIAs) for high-risk processing, and a 72-hour breach notification to the supervisory authority. Non-compliance can cost up to €20 million or 4% of global annual turnover, whichever is higher.

Key Takeaways

  • GDPR is an EU regulation with extraterritorial reach — firms that process EU residents’ personal data must comply, regardless of where in the world the company is based.
  • It is built on 7 principles (Article 5) and grants 8 data subject rights (Articles 15–22), including access, erasure, and data portability, each answerable within one month.
  • High-risk processing requires a DPIA (Article 35), and personal-data breaches must be reported to the supervisory authority within 72 hours (Article 33).
  • Fines reach up to €20 million or 4% of global annual turnover. International transfers out of the EU need safeguards such as Standard Contractual Clauses (SCCs) or Binding Corporate Rules (BCRs).

The General Data Protection Regulation (GDPR) is the world's most comprehensive data privacy and security law. Enacted by the European Union in May 2018, it replaced the 1995 Data Protection Directive and fundamentally transformed how organizations worldwide handle personal data of EU residents.

GDPR consists of 99 articles organized into 11 chapters, covering everything from lawful processing grounds to individual rights, data protection by design, breach notifications, and cross-border data transfers. It applies to any organization—regardless of location—that processes personal data of individuals in the EU.

The regulation introduces severe penalties for non-compliance: up to €20 million or 4% of global annual turnover, whichever is higher. Since enforcement began, regulators have issued billions in fines to companies including Google (€50M), Amazon (€746M), and Meta (€1.2B).

Who Must Comply with GDPR?

EU-Based Organizations Any company established in the EU, regardless of where data processing occurs.

Non-EU Organizations with EU Customers Companies offering goods/services to EU residents or monitoring their behavior (e.g., US SaaS companies with European users).

Data Controllers Organizations that determine the purposes and means of processing personal data (e.g., employers, e-commerce platforms).

Data Processors Organizations that process data on behalf of controllers (e.g., cloud providers, payroll services, marketing agencies).

Public Authorities Government bodies and public institutions processing personal data (except for law enforcement activities).

Key Insight: GDPR has extraterritorial reach. Even if your company is based in India, US, or anywhere else, you must comply if you process data of EU residents. Read the full regulation text at EUR-Lex or the practical guidance at gdpr.eu.

Core Framework

The 7 GDPR Principles

Article 5 establishes seven foundational principles that govern all personal data processing. Compliance with these principles is mandatory and forms the basis for GDPR enforcement.

1Article 5(1)(a)

Lawfulness, Fairness, and Transparency

Personal data must be processed lawfully, fairly, and in a transparent manner. Data subjects must be informed about how their data is collected and used.

2Article 5(1)(b)

Purpose Limitation

Data must be collected for specified, explicit, and legitimate purposes. Further processing must be compatible with the original purpose.

3Article 5(1)(c)

Data Minimisation

Only collect and process data that is adequate, relevant, and limited to what is necessary for the stated purpose.

4Article 5(1)(d)

Accuracy

Personal data must be accurate and kept up to date. Inaccurate data must be erased or rectified without delay.

5Article 5(1)(e)

Storage Limitation

Data should be kept in a form that permits identification of data subjects for no longer than necessary for the stated purpose.

6Article 5(1)(f)

Integrity and Confidentiality

Process data in a manner that ensures appropriate security, including protection against unauthorized processing, accidental loss, destruction, or damage.

7Article 5(2)

Accountability

The controller is responsible for and must be able to demonstrate compliance with all GDPR principles through documentation and evidence.

Accountability Principle

The 7th principle—Accountability—is critical: you must not only comply with principles 1-6 but also demonstrate compliance through documentation, policies, procedures, and evidence. This includes maintaining records of processing activities (Article 30), conducting Data Protection Impact Assessments (Article 35), and implementing data protection by design and by default (Article 25).

Article 6

Lawful Basis for Processing

Under GDPR Article 6, you must have at least one of six lawful bases to process personal data. You cannot switch to a different lawful basis after processing begins—choose carefully at the outset.

1. Consent

Article 6(1)(a)

The data subject has given clear, affirmative consent for specific processing purposes. Consent must be freely given, specific, informed, and unambiguous. Pre-ticked boxes do not constitute valid consent.

Examples:

Marketing emails, newsletter subscriptions, cookies (non-essential)

Requirements:

Must be withdrawable at any time, burden of proof is on controller, and consent requests must be separate from other terms

When to Use:

Best for optional activities like marketing. Avoid for employment or public services where power imbalance exists.

2. Contract

Article 6(1)(b)

Processing is necessary for the performance of a contract with the data subject, or to take steps at their request before entering into a contract.

Examples:

Processing customer orders, delivering products, providing services under contract

Requirements:

Must be objectively necessary—not just mentioned in terms of service

When to Use:

E-commerce transactions, SaaS service delivery, employment contracts

3. Legal Obligation

Article 6(1)(c)

Processing is necessary to comply with a legal obligation under EU or Member State law.

Examples:

Tax reporting, employment law compliance, anti-money laundering checks

Requirements:

Must cite specific legal provision requiring processing

When to Use:

Regulatory reporting, legal compliance (GDPR itself is NOT a legal obligation for this purpose)

4. Vital Interests

Article 6(1)(d)

Processing is necessary to protect someone's life or physical integrity. This is a narrow exception for emergency situations.

Examples:

Emergency medical treatment, disaster response, safeguarding children

Requirements:

Must be genuine life-or-death situation, and cannot be used if another lawful basis applies

When to Use:

Rarely used, and only for genuine emergencies where consent cannot be obtained

5. Public Task

Article 6(1)(e)

Processing is necessary for tasks carried out in the public interest or in the exercise of official authority vested in the controller.

Examples:

Public healthcare, education, government services

Requirements:

Must have clear basis in law, and controller must be public authority or private entity exercising public authority

When to Use:

Government bodies, public universities, healthcare providers acting under statutory obligations

6. Legitimate Interests

Article 6(1)(f)

Processing is necessary for the legitimate interests of the controller or third party, except where overridden by the interests, rights, or freedoms of the data subject (especially children).

Examples:

Fraud prevention, network security, direct marketing to existing customers, employee monitoring

Requirements:

Must conduct and document a Legitimate Interest Assessment (LIA) balancing controller interests against data subject rights

When to Use:

Business operations, cybersecurity, customer analytics—when consent is impractical and no other basis applies

Special Categories of Personal Data (Article 9)

Processing of sensitive data—racial/ethnic origin, political opinions, religious beliefs, trade union membership, genetic data, biometric data, health data, sex life, or sexual orientation—is generally prohibited unless you meet one of the Article 9 exceptions (e.g., explicit consent, vital interests, legitimate activities of non-profits, data manifestly made public by the data subject).

Criminal conviction data (Article 10) can only be processed under official authority or when authorized by Union/Member State law.

Article 35

Data Protection Impact Assessment (DPIA)

When processing is likely to result in high risk to individuals' rights and freedoms, you must conduct a DPIA before processing begins. This is mandatory for certain types of processing.

When DPIA is Mandatory:

Systematic and Extensive Profiling Automated processing including profiling that produces legal or similarly significant effects (e.g., credit scoring, algorithmic decision-making for employment/healthcare)

Large-Scale Processing of Special Categories Processing sensitive data (health, biometric, genetic, racial/ethnic origin, political opinions) or criminal conviction data at scale

Systematic Monitoring of Public Areas Large-scale systematic monitoring (e.g., CCTV surveillance, facial recognition in public spaces, location tracking)

New Technologies Use of new technological solutions that present high risk (e.g., AI/ML systems, IoT deployments, blockchain for personal data)

DPIA Must Include:

  • Systematic description of processing operations and purposes
  • Assessment of necessity and proportionality of processing
  • Assessment of risks to rights and freedoms of data subjects
  • Measures to address risks (technical and organizational)
  • Safeguards, security measures, and mechanisms to ensure data protection
  • Demonstration of compliance with GDPR
  • Consultation with data subjects or their representatives (where appropriate)
  • Consultation with DPO (if appointed)
  • Prior consultation with supervisory authority if high risk cannot be mitigated
Articles 33-34

Data Breach Notification

Personal data breaches must be reported to the supervisory authority within 72 hours—and to affected individuals if the breach poses high risk to their rights and freedoms.

1Immediately

Detect & Assess

  • Detect the breach
  • Contain the incident
  • Assess scope and severity
  • Determine if breach is likely to result in risk to individuals
2Within 72 hours

Notify Authority

  • Notify supervisory authority (ICO, CNIL, etc.)
  • Provide: nature of breach, categories/number of individuals affected, likely consequences, measures taken/proposed
  • If not notified within 72h, provide reasons for delay
3Without undue delay

Notify Individuals

  • Required if high risk to individuals
  • Describe breach in clear, plain language
  • Provide contact point for more information
  • Describe likely consequences and mitigation measures
  • Not required if: data encrypted, subsequent measures remove high risk, or disproportionate effort (use public communication instead)

Penalties for Non-Compliance

Failure to notify a breach to the supervisory authority or affected individuals can result in fines up to €10 million or 2% of global annual turnover (whichever is higher). In 2022, British Airways was fined £20M for a breach affecting 400,000 customers due to inadequate security and delayed notification.

What's Included

Comprehensive GDPR Compliance Services

End-to-end GDPR implementation from gap analysis to certification, audit support, and ongoing compliance management.

Gap Assessment

Current state analysis against GDPR requirements, data mapping, processing inventory (Article 30), identification of high-risk processing activities.

Policy & Documentation

Privacy policies, data processing agreements, consent mechanisms, data retention schedules, breach response plan, DPIA templates.

Lawful Basis Analysis

Identify appropriate lawful basis for each processing activity, conduct Legitimate Interest Assessments (LIAs), document basis selection.

DPIA Execution

Conduct Data Protection Impact Assessments for high-risk processing, risk mitigation strategies, supervisory authority consultation.

Data Subject Rights

Implement DSAR response procedures, automated request portals, identity verification, data discovery across systems.

International Transfers

Standard Contractual Clauses (SCCs), Binding Corporate Rules (BCRs), Transfer Impact Assessments (TIAs), adequacy decisions.

Breach Notification

72-hour breach notification procedures, incident response playbooks, supervisory authority templates, individual notification protocols.

Security Measures

Data protection by design and by default, encryption, pseudonymization, access controls, organizational security measures.

Training & Awareness

Staff GDPR training programs, DPO certification support, privacy champion networks, ongoing awareness campaigns.

Implementation Roadmap

GDPR Compliance Timeline

TYPICAL 5-6 MONTH TIMELINE

GDPR Implementation Roadmap

Here is how a typical engagement runs, week by week. Your scope sets the actual pace.

  1. Weeks 1-3

    Data Mapping & Gap Analysis

    Complete data inventory, map data flows, identify all processing activities, document Article 30 records, conduct gap assessment against GDPR requirements.

  2. Weeks 4-6

    Lawful Basis & Documentation

    Identify lawful basis for each processing activity, conduct Legitimate Interest Assessments, update privacy policies, create data processing agreements.

  3. Weeks 7-10

    Data Subject Rights Implementation

    Build DSAR response procedures, implement automated request portals, train staff on rights requests, test response workflows.

  4. Weeks 11-14

    DPIAs & High-Risk Processing

    Conduct DPIAs for high-risk activities, implement risk mitigation measures, consult supervisory authority if required.

  5. Weeks 15-18

    Security & Technical Controls

    Implement encryption, pseudonymization, access controls, breach notification procedures, security by design and by default.

  6. Weeks 19-22

    International Transfers & Final Audit

    Implement SCCs/BCRs, conduct Transfer Impact Assessments, final compliance audit, staff training, continuous monitoring setup.

Proof

In their words.

Quotes verbatim from G2. Company names added where the client confirmed them.

Verify on G2
They expertly mapped the overlapping controls between SOC 2 and ISO 27001, which saved us from duplicating work.
Jasreet Kaur B.Silicon Physical Design Engineer · Small-BusinessSOC 2 + ISO 27001 · August 2026
Instead of simply providing generic templates or checklists, their team took the time to understand our environment and requirements.
Anand .Market Risk Analyst · Mid-MarketCompliance readiness · September 2026
The team’s willingness to work with us and ease of communication.
sam v.CEO · Small-BusinessSOC 2 Type I + ISO 27001 · August 2026
They delivered the project with speed, accuracy, and cost-effectiveness.
Maneet P.Mid-MarketSOC 2 · August 2026
My only regret is that we didn’t engage them sooner in our compliance journey, which would have saved us even more time.
Mahesh Raju C. · XonarSmall-BusinessSOC 2 · GRC · August 2026
They were always responsive and willing to go the extra mile whenever we had questions or needed guidance.
Chandan J. · DsiderSmall-BusinessSOC 2 Type I · August 2026
Managing the auditor relationship on our behalf was especially valuable — it took a lot of pressure off our internal team.
Achyut B.Senior Software Engineer · Small-BusinessSOC 2 + ISO 27001 · September 2026
Their focus on ensuring that we were genuinely audit-ready rather than simply completing documentation.
Ravi V.Founder & CEO · Mid-MarketSOC 2 Type II · August 2026
The guidance was not generic or simply based on a standard checklist — they suggested practical approaches that made sense for our business.
Verified UserInternational Trade and Development · Small-BusinessSOC 2 + ISO 27001 · September 2026
What I like best is the hands-on support and clear guidance throughout the SOC 1 and SOC 2 process.
Sai Sudha S. · ExcersSmall-BusinessSOC 1 + SOC 2 · September 2026

Frequently Asked Questions

Does GDPR apply to my company if I'm not in the EU?
Yes, if you offer goods/services to EU residents or monitor their behavior. GDPR has extraterritorial reach—location of your company is irrelevant. Examples: a US SaaS company with European customers, an Indian outsourcing firm processing EU employee data, a Chinese e-commerce site shipping to the EU. Even a single EU customer can trigger GDPR obligations.
What's the difference between a Data Controller and Data Processor?
A Data Controller determines the purposes and means of processing (e.g., an employer deciding to process employee data for payroll). A Data Processor processes data on behalf of the controller (e.g., a payroll service provider). Controllers have primary GDPR responsibility, while processors have direct obligations under Article 28 including maintaining processing records, implementing security, and assisting with DPIAs and breach notifications. One entity can be both controller and processor for different processing activities.
Do I need to appoint a Data Protection Officer (DPO)?
A DPO appointment is mandatory if: (1) you are a public authority (except courts), (2) your core activities involve large-scale systematic monitoring (e.g., behavioural advertising, location tracking), or (3) your core activities involve large-scale processing of special categories or criminal data (e.g., hospitals, genetic testing companies). The DPO must have expert knowledge of data protection law, must be independent, and cannot be penalised for performing their duties. They can be an internal staff member or an external consultant.
What are the penalties for GDPR non-compliance?
GDPR has a two-tier penalty structure. Tier 1 (up to €10M or 2% of global annual turnover) covers violations of processor obligations, breach notification, and DPO requirements. Tier 2 (up to €20M or 4% of global annual turnover) covers violations of core principles, lawful basis, data subject rights, and international transfers. Supervisory authorities weigh the nature, gravity, and duration of the infringement, whether it was intentional or negligent, cooperation, and prior infringements. Since 2018, regulators have issued billions of euros in fines.
Can I transfer personal data outside the EU?
Yes, but only with appropriate safeguards: (1) an Adequacy Decision, where the EU Commission recognises that the destination country provides adequate protection (e.g., UK, Switzerland, Japan), (2) Standard Contractual Clauses (SCCs), the EU-approved contract templates between exporter and importer, which require a Transfer Impact Assessment (TIA), (3) Binding Corporate Rules (BCRs), internal policies for multinational groups approved by a supervisory authority, or (4) limited derogations such as explicit consent. Post–Schrems II, you must assess whether local laws in the destination undermine the SCCs.
How long can I keep personal data?
Only as long as necessary for the purpose (Article 5(1)(e) — Storage Limitation). Define retention periods based on the purpose of processing, legal obligations (e.g., tax records for 6–7 years), limitation periods for legal claims, industry standards, and data subject expectations. Implement automated deletion, regular reviews, and archiving procedures. Truly irreversible anonymised data is no longer personal data and falls outside GDPR.
What's the difference between GDPR and ISO 27001?
GDPR is a legal regulation focused on privacy and individual rights (lawful processing, consent, data subject rights, accountability). ISO 27001 is a voluntary security standard focused on protecting information assets (confidentiality, integrity, availability). GDPR is law with penalties for non-compliance, while ISO 27001 is a certification that confers a business advantage. GDPR applies only to personal data, while ISO 27001 covers all information. Many organisations pursue both — ISO 27001 for security controls and GDPR for privacy compliance — and ISO 27701 bridges the two as a privacy extension.
Do I need consent for all data processing?
No. Consent is just one of six lawful bases (Article 6). The others are contract (e.g., processing customer orders), legal obligation (e.g., tax reporting), vital interests (e.g., a medical emergency), public task (e.g., government services), and legitimate interests (e.g., fraud prevention). Consent should be a last resort when no other basis applies. Valid consent must be freely given, specific, informed, unambiguous, and easily withdrawn. Pre-ticked boxes and silence are not valid consent.
Working with Tranquility Cybersecurity

How TCSA supports your GDPR programme

Tranquility Cybersecurity helps organisations worldwide operationalise GDPR end to end — data mapping and Article 30 records, lawful-basis analysis, DPIAs, data subject request workflows, breach-response playbooks, and international-transfer mechanisms (SCCs/BCRs). Because GDPR overlaps heavily with security and privacy standards, we often run it alongside ISO 27701 (privacy) and ISO 27001 (security). For ongoing oversight, our vCISO & vDPO services provide a named Data Protection Officer. See the engagements behind this work on our proof & results page.

Serving people in California as well? Most of this work carries over to the CCPA as amended by the CPRA.

Written By Expert Auditors

Surendra Pal SinghChief Information Security Officer & Data Protection OfficerCISODPOCISAMCSEITILISO 27001 Lead AuditorISO 27701 Lead AuditorISO 42001 Lead Auditor
Saundhi ChauhanLead AuditorISO 27001 Lead AuditorISO 27701 Lead AuditorISO 42001 Lead Auditor
Last reviewed: June 2026 • Content verified by certified lead auditors

Get in touch

Book a free consultation or send us your requirements. We respond within 24 hours.

Send us your requirement.

01Your details
02What is it about?
GDPR
03Send
Asking about: GDPR