Skip to main content

Guide

TISAX Data Protection vs. GDPR

TISAX data protection module explained: commissioned processing, special categories, and TOMs in the automotive context.

Julian Köhn
|Updated|Read time: 4 minutes

TISAX data protection module explained: commissioned processing, special categories, and TOMs in the automotive context.

TISAX data protection and GDPR: How do they relate?

The GDPR establishes legal duties. TISAX provides an assessment for selected data protection objectives in business relationships. A label records a result within the assessed scope; it is not blanket evidence of GDPR compliance or a data protection certification under GDPR Article 42.

The objectives are Data (AL2) and Special data (AL3). Both address processing on behalf of a controller under GDPR Article 28; Special data includes special categories under Article 9. Both ISA information security and data protection catalogues apply.

Who processes which data? · © 2026 Kopexa GmbH

Similarities Between TISAX and GDPR

Existing privacy work can support the assessment. First establish your role: controller, processor or another arrangement. Roles determine different duties and evidence.

  • Safeguards: Select and review appropriate technical and organisational measures according to risk.
  • Processing records: Maintain the Article 30 records required for your role.
  • Processor relationships: Review contracts and subprocessors under Article 28.
  • Individual rights: Establish responsibilities and support procedures.
  • Impact assessment: Check whether Article 35 requires an assessment and define responsibilities and support.

What the TISAX assessment examines

Data Protection Assessment Objective: What Exactly Is Assessed

The ISA data protection catalogue examines organisational and operational implementation, including:

  • Responsibilities, policies and trained staff.
  • Known processing activities and applicable safeguards.
  • Contracts, subprocessors and protected data transfers.
  • Handling instructions, individual-rights requests and personal data incidents.

Commissioned Processing (DPA) in the TISAX Context

When acting as a processor, you need a contract or another legal instrument under Article 28. Review specific customer requirements as well, particularly:

  • Instructions, purpose and scope of the commissioned processing.
  • Authorisation or agreed information and objection procedures for subprocessors.
  • Passing applicable duties to subprocessors and reviewing compliance.
  • Support for requests and incidents, plus return or deletion at the end of the engagement.

Special Categories of Personal Data

Special data concerns processing special categories under GDPR Article 9 on behalf of a controller. Examples include:

  • Health data.
  • Biometric data used to uniquely identify a person.
  • Trade union membership.
  • Data revealing ethnic origin or religious beliefs.

Not every photograph or personnel record automatically belongs to these categories. Review content, purpose and role. Special data uses AL3, generally including an on-site assessment.

Technical and organisational measures: Useful evidence

Describe safeguards so they can be checked against actual practice. These examples are aids, not universal technology requirements for every business:

AreaTraceable evidence
AccessApproved roles and documented access review
EncryptionSelected methods, configuration and key management
DeletionAgreed periods, procedure and recorded result
SubprocessingCurrent parties, authorisations and contract review
Personal data incidentsReporting channels, responsibilities and handling records

AL2 vs. AL3 for Data Protection Labels

The choice between data protection labels depends on the type of data being processed:

  • Data (AL2): Processing on behalf of a controller within the agreed objective.
  • Special data (AL3): Processing that includes special categories under Article 9.

Agree required labels with the customer. Running your own HR function does not automatically make you that customer’s processor. Conversely, particularly sensitive data in a commissioned service may require a different objective.

Practical Tips for Data Protection in the TISAX Assessment

  • Keep data flows and roles current; processing activities support this overview.
  • Compare contracts against the actual service and subprocessors used.
  • Assign notification duties correctly: the processor notifies the controller without undue delay. Where notification to the authority is required, the controller generally has 72 hours from awareness, where feasible.
  • Involve privacy owners early and document support procedures for requests.

More on scope definition and special requirements for IT service providers can be found on our TISAX for service providers page. The complete TISAX requirements are available on the corresponding overview page.

Connect data protection and TISAX efficiently

Where privacy work and TISAX preparation concern the same processing, suitable evidence can be reused. Check what it establishes for each purpose. Our TISAX page shows how Kopexa supports this work.

Sources and reference date

Reviewed on 13 November 2026 using the ENX participant handbook and ISA 6, including the transition to ISA 2027.

GDPR, particularly Articles 9, 28, 30, 32–35 and 42