GDPR Compliance
Compliance · GDPR

GDPR Compliance

Overview

What it is & who needs it

The EU's General Data Protection Regulation applies to organisations anywhere in the world that offer goods or services to, or monitor, individuals in the EU. We assess your processing activities, run DPIAs and align your controls and documentation to the regulation.

Who needs it: Any organisation that handles the personal data of individuals in the EU.

What GDPR broadly requires

  • A lawful basis documented for every processing activity
  • Data subject rights (access, erasure, portability, objection) honored on time
  • Records of processing and DPIAs for higher-risk activities
  • Breach notification to supervisory authorities within 72 hours where required
  • Transfer safeguards for personal data leaving the EU

How Virtual Caim helps

  1. Map processing activities and confirm how GDPR applies to you
  2. Gap assessment against GDPR obligations
  3. Remediation covering notices, consent, rights workflows and documentation
  4. DPIAs for higher-risk processing
  5. Security review and testing of systems holding personal data
  6. Periodic reassessment and audit-ready documentation
GDPR FAQ

GDPR: reach, representatives, breach clock, fines and the Digital Omnibus

GDPR applies under Article 3(2) to a non-EU controller or processor that offers goods or services to people in the Union or monitors their behaviour there. Such an organisation must then designate an EU representative in writing under Article 27, established in a Member State where the data subjects are. The only exceptions are occasional processing that involves no large-scale special category or criminal conviction data and is unlikely to risk individuals' rights, and public authorities.

Article 33 requires the controller to notify the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of the breach, with reasons if it is late. No notice is needed where the breach is unlikely to result in a risk to individuals' rights and freedoms. A processor must inform the controller without undue delay after becoming aware of a breach.

Article 83 sets two tiers. Infringements of obligations such as those of controllers and processors can reach EUR 10 million or 2 percent of total worldwide annual turnover of the preceding financial year, whichever is higher. Infringements of the basic principles, data subjects' rights and international transfer rules can reach EUR 20 million or 4 percent, whichever is higher. These are ceilings, and regulators weigh the factors in Article 83(2).

As of November 2026 they are proposals, not law. The Council agreed its negotiating mandate on 21 October 2026. It keeps the current definition of personal data, adds a new Article 25a on when pseudonymised data counts as personal data, keeps a high-risk threshold for breach reporting and proposes to extend the reporting deadline to 96 hours. Talks with Parliament can start only once Parliament sets its position, and EU leaders aim to finish simplification packages by the end of 2027. The 72-hour rule continues to apply today.

Article 37 requires one where the processing is carried out by a public authority or body, where the core activities involve regular and systematic monitoring of data subjects on a large scale, or where the core activities involve large-scale processing of special category data or data on criminal convictions and offences. Where none applies, appointing one is optional, but a named privacy lead helps a regulator or customer find an owner.

Get GDPR-ready for global customers.

Give EU customers and partners a privacy program they can rely on.