Skip to main content
CodeSignal logo

CodeSignal

GDPR evidence

Discover the agentic skills intelligence platform that helps teams see, measure, develop, and grow skills clearly with

codesignal.comResearch and data providersLast verified 21 Sep 2026
Request the report Are you CodeSignal?

Regulation (EU) 2016/679

CodeSignal against GDPR’s vendor requirements

5 provisions of GDPR reach the vendors you rely on. For each, the public evidence from CodeSignal that may support it, with its date and source.

3 evidence found1 available on request1 no public evidence
Article 28(1)

Use processors that provide sufficient guarantees

A controller shall use only processors "providing sufficient guarantees to implement appropriate technical and organisational measures" so that processing meets the Regulation and protects data subjects’ rights.

Evidence found

  • Independent security assurance

    Evidence found

    A current SOC 2 report or ISO/IEC 27001 certificate is the usual evidence that a supplier operates appropriate security measures.

    • SOC 2Vendor states SOC 2 Type II on its trust centreas of 21 Sep 2026
    • SOC 2 report"CodeSignal SOC 2 Report" on the trust centreas of 21 Sep 2026
    • SOC 2 report"SOC2 Report" on the trust centreas of 21 Sep 2026

  • Security testing and documentation

    Evidence found

    A penetration test report, a completed standard questionnaire (SIG, CAIQ, HECVAT) or security documentation shows how the supplier tests and runs its controls.

    • Penetration test report"Web Application Penetration Test" on the trust centreas of 21 Sep 2026
    • Penetration testing"Does CodeSignal conduct regular penetration testing?" Yes. Independent third-party penetration tests are conducted annually on our APIs, web applications, and network infrastructure.as of 21 Sep 2026
    • Penetration testingPenetration testing: report availableas of 21 Sep 2026
    • Penetration test report"AI Penetration Test" on the trust centreas of 21 Sep 2026
    • and 16 more
Article 28(3)

Put processing under a written contract

Processing by a processor must be governed by a contract that sets out the subject matter, duration, nature and purpose of processing, and binds the processor to act on documented instructions, keep data confidential, secure it, assist the controller and make available the information needed to demonstrate compliance.

No public evidence

  • Data processing agreement

    No public evidence

    The DPA is where processing instructions, confidentiality, security, sub-processing and audit rights are written down.

Article 28(2) and (4)

Know and control sub-processors

A processor may engage another processor only with the controller’s prior authorisation, must inform the controller of intended changes so it can object, and must flow the same data protection obligations down by contract.

Evidence found

  • Published subprocessor list

    Evidence found

    A current list of subprocessors, with purpose and location, is how a customer knows who else touches its data.

Article 33(2)

Be told of breaches without undue delay

The processor shall notify the controller "without undue delay after becoming aware of a personal data breach".

Available on request

  • Incident response and notification

    Available on request

    An incident response plan or a published notification commitment shows how and when the supplier tells customers about incidents.

Articles 44 to 46

Transfer data outside the EU lawfully

Transfers of personal data to a third country need an adequacy decision or appropriate safeguards such as standard contractual clauses, and the controller needs to know where the data goes.

Evidence found

  • Transfer mechanism

    Evidence found

    Transfers outside the EU or UK need a basis such as an adequacy decision (including the EU-US Data Privacy Framework) or standard contractual clauses.

  • Where data is hosted and processed

    Evidence found

    The regions or countries where the service runs and data is stored, from the vendor or its subprocessor list.

    • Where data is hosted or processed"Where is CodeSignal hosted?" Our infrastructure is hosted on Amazon Web Services (AWS). All deployments use virtual private cloud (VPC) configurations with firewalls and isolation mechanisms.as of 21 Sep 2026
    • Where data is hosted or processed"Where is customer data stored?" Data is hosted on AWS in the following U.S. regions: us-east-1 (primary), us-west-2, and us-east-2.as of 21 Sep 2026
    • Hosting regionsHosting regions stated: USas of 21 Sep 2026
    • Subprocessor locations26 of 26 subprocessors list a locationas of 21 Sep 2026

Questions buyers ask

Is CodeSignal GDPR compliant?

CertReports does not decide that. It shows the public evidence that may support each GDPR requirement that reaches vendors: evidence was found or is available on request for use processors that provide sufficient guarantees (Article 28(1)), know and control sub-processors (Article 28(2) and (4)), be told of breaches without undue delay (Article 33(2)), transfer data outside the eu lawfully (Articles 44 to 46), and nothing public was found for put processing under a written contract.

What should I ask CodeSignal for?

Request incident response and notification, data processing agreement, and confirm each is current.

Reading for GDPR reviews

All articles

This maps third-party obligations to the vendor evidence that may support them. It is not legal advice and never a statement that a vendor or its customers comply; confirm scope and sufficiency with your counsel or auditor. “No public evidence” means nothing public was found at the last check. Citations link to the official text.

Requirements reviewed 21 Sep 2026. The vendor lists the evidence on its trust centre behind a request or NDA; ask for it.