Trust
Data Processing Agreement
Last updated: April 26, 2026
A2Go offers a standard Data Processing Agreement (DPA) for customers who require one under GDPR, CCPA, or other data protection regulations. Our DPA covers the processing of personal data in connection with the A2Go Decision Intelligence Platform (ADIP) and related services.
What's Covered
Our standard DPA addresses the following areas:
-
Scope and purpose of processing
Defines the categories of processing activities performed by A2Go, the nature and purpose of processing, and the duration of processing in relation to your service agreement.
-
Data categories and data subjects
Specifies the types of personal data processed and the categories of data subjects whose data may be included in Platform inputs or outputs.
-
Sub-processor obligations
Details our obligations when engaging sub-processors, including prior notification, contractual requirements, and your right to object to new sub-processors.
-
Security measures
Describes the technical and organizational measures A2Go implements to protect personal data, including encryption, access controls, and incident management.
-
Data breach notification procedures
Establishes notification timelines and procedures in the event of a personal data breach, including the information we will provide and our cooperation obligations.
-
Data subject rights assistance
Outlines how A2Go will assist you in responding to data subject requests for access, rectification, erasure, portability, and other rights under applicable law.
-
Data deletion and return
Defines procedures for returning or securely deleting personal data upon termination of the service agreement, with written confirmation provided.
Sub-processors
A current list of sub-processors that may process customer personal data is available on request. Material changes to the sub-processor list are communicated to customers under the terms of their executed DPA.
[COUNSEL REVIEW: Decide whether to publish the sub-processor list as a separate page (GDPR Art. 28 transparency expectation) or keep it gated behind email request. Published is friendlier to procurement.]