Data Processing Agreement
Last updated: 19 November 2026 · Sub-processors
This Data Processing Agreement ("DPA") forms part of the agreement between the parties under clause 2 of the Commercial Terms, or of another written agreement between them that refers to it, and is entered into between:
- The Customer named in the signed proposal, as data controller ("Controller"); and
- GTAIM AB, org.nr 559604-9972, as data processor ("Processor").
In respect of Customer Personal Data (clause 1), the Controller determines the purposes and means of the processing and the Processor processes it only on the Controller's behalf (GDPR Article 4(7) and 4(8)). This DPA sets out the terms required by Article 28(3) GDPR. Where this DPA and the Commercial Terms conflict on data protection, this DPA prevails, as clause 2 of the Commercial Terms states.
Dual capacity. The Processor acts as processor of Customer Personal Data under clauses 1 to 13, and separately as controller in its own right of Usage Data under clause 14. The two capacities are distinct, and clauses 1 to 13 apply to Customer Personal Data only.
1. Subject-matter and scope
The Processor processes Customer Personal Data on behalf of the Controller only to provide the services described in the signed proposal and in any further proposal the parties sign under the Commercial Terms (the "Services"), and only to the extent necessary for that purpose. The subject-matter, duration, nature and purpose of the processing, the types of personal data, and the categories of data subjects are set out in Annex 1. This DPA applies to all such processing from the date it takes effect, including personal data already held for the Services on that date.
Customer Personal Data means personal data, as defined in Article 4(1) GDPR, relating to the data subjects described in Annex 1, that the Controller supplies to the Processor or that is created on the Controller's behalf in the course of the Services. Its categories are set out in Annex 1.
Usage Data means data about how the Services are used and how they perform, such as usage logs, user behaviour metrics, progress and results, the answers, feedback and ratings the Controller's personnel give to questions the Services ask, and the measurements derived from them. It does not include other material they write or upload themselves. Personal data about persons other than the user, and special-category data (Article 9 GDPR), that a written answer contains is not Usage Data; the Processor processes it only on the Controller's behalf under this DPA. Usage Data is governed by clause 14 and is not processed on the Controller's behalf.
A single record may be Customer Personal Data in the Controller's hands and Usage Data in the Processor's, processed in parallel for different purposes on different lawful bases. Where that is so, both this DPA and clause 14 apply to it, each in its own capacity.
2. Processing on documented instructions (Art 28(3)(a))
The Processor processes the personal data only on the Controller's documented instructions, including as to transfers to a third country, unless required to do otherwise by Union or Member State law; in that case the Processor informs the Controller of that legal requirement before processing, unless the law prohibits it. The Processor immediately informs the Controller if, in its opinion, an instruction infringes the GDPR or other data-protection law.
The signed proposal and this DPA are the Controller's complete documented instructions, including on sub-processors (clause 5) and on transfers to a third country (clause 11). The Controller's use of the functions of the Services is an instruction within them. The Processor follows a further documented instruction to restrict or stop processing; where it prevents the Services as specified, fees paid or due remain payable. Any other change to the instructions is agreed in writing between the parties.
Instructions operate within the specified Services. The Services are those set out in the signed proposal and Annex 1. Delivery of the Services requires a persistent per-participant identifier, without which the Processor cannot provide an individual their own learning record, apply progress gating and completion, support that individual's rights under Articles 15 and 20 GDPR, or maintain enrolment integrity.
3. Confidentiality (Art 28(3)(b))
The Processor ensures that persons authorised to process the personal data are bound by an obligation of confidentiality or are under an appropriate statutory obligation of confidentiality.
4. Security of processing (Art 28(3)(c) / Art 32)
The Processor implements appropriate technical and organisational measures to ensure a level of security appropriate to the risk, taking into account the state of the art, the costs of implementation, and the nature, scope, context, and purposes of the processing as well as the risk of varying likelihood and severity for the rights and freedoms of data subjects (GDPR Article 32). The measures in force are set out in Annex 2. The measures are proportionate to the risk of the processing described in Annex 1.
5. Sub-processors (Art 28(2) and 28(4))
The Controller gives the Processor general written authorisation to engage sub-processors for hosting and infrastructure, e-mail delivery, monitoring, AI services, and business productivity and collaboration tools. The current list of sub-processors is published at academy.gotoaimarket.com/legal/sub-processors.
Each sub-processor is bound by a written agreement, which may be the sub-processor's own standard data processing terms, that meets the requirements of Article 28(4) GDPR. The Processor remains liable to the Controller for the performance of each sub-processor's obligations as Article 28(4) GDPR provides.
The Processor informs the Controller of an intended addition or replacement of a sub-processor by updating the published list. The Controller may object on reasonable data-protection grounds within thirty (30) days of the update. If the objection is not resolved, the Controller's sole remedy is to terminate the affected Services by written notice. Fees paid or due are not refunded.
6. Assistance with data-subject rights (Art 28(3)(e))
Taking into account the nature of the processing, the Processor assists the Controller by appropriate technical and organisational measures, insofar as this is possible, in fulfilling the Controller's obligation to respond to requests to exercise data-subject rights under Chapter III GDPR (Articles 12 to 23).
The Processor provides this assistance through the functions of the Services and its established procedures. Assistance beyond these is provided on the Controller's written request and at the Controller's cost, at the hourly rate stated in the signed proposal. A request the Processor receives directly from a data subject is forwarded to the Controller without undue delay. A data subject's request for their own individual responses is answered by the Processor to that data subject directly.
7. Assistance with security, breach, and impact assessment (Art 28(3)(f))
Taking into account the nature of the processing and the information available to the Processor, the Processor assists the Controller in ensuring compliance with its obligations under Articles 32 to 36 GDPR (security of processing, personal-data-breach notification, and data protection impact assessment / prior consultation). Assistance beyond the Processor's written security and data-protection documentation (clause 10) is provided on the Controller's written request and at its cost, at the hourly rate stated in the signed proposal, except assistance with a personal data breach of the Processor's own systems.
8. Personal data breach (Art 33(2))
The Processor notifies the Controller without undue delay after becoming aware of a personal data breach affecting the personal data processed under this DPA, and provides the information the Controller reasonably needs to meet its own notification obligations under Articles 33 and 34 GDPR.
9. Return or deletion at end of processing (Art 28(3)(g))
After the end of the Services, the Processor, at the Controller's choice, deletes or returns all the Customer Personal Data and deletes existing copies, unless Union or Member State law requires storage of the personal data. By entering into the agreement, the Controller makes the following choices:
(a) Identity and contact data of the Controller's personnel, and the Usage Data linked to it: the Controller instructs the Processor to make them available to the Processor as controller under clause 14 at the end of the Services, and chooses their deletion for the processing on its behalf. The Processor holds them for twelve (12) months after the end of the Services, then erases the identity and contact data, except records the law requires or legal claims need, and irreversibly anonymises the Usage Data.
(b) Material exchanged with the Controller's personnel in the course of the Services, and the personal data in it: the Processor stores it on the Controller's behalf for three (3) years after the end of the Services to support a later engagement, returns it on the Controller's request, and deletes it, together with any copies, at the end of that period.
(c) All other Customer Personal Data: the Controller chooses deletion, and the Processor deletes it, together with any copies, after the end of the Services.
9a. End of the engagement
Before the engagement ends, the Processor may inform each enrolled user of the end date and of the option to keep a personal GTAIM account. Where a user accepts before the end date, or within thirty (30) days after it, the account continues under GTAIM's Terms of Service with the Processor as controller, and clause 9 does not apply to the user's own identity and contact data and the Usage Data in it; material exchanged with the Controller's personnel stays under clause 9.
10. Audit and information (Art 28(3)(h))
The Processor makes available to the Controller, on request, the information necessary to demonstrate compliance with Article 28 GDPR, in the form of its written security and data-protection documentation. The Controller may also send the Processor one security questionnaire in any twelve (12) month period, which the Processor answers in writing.
The Processor allows for and contributes to an audit, including an inspection, by the Controller or an independent auditor it mandates, where that information does not enable the Controller to verify the Processor's compliance with this DPA and the Controller states in writing which information is missing, or where a supervisory authority requires it. Such an audit takes place no more than once in any twelve (12) month period, except where a supervisory authority requires it, on at least sixty (60) days' written notice, with scope, timing and duration agreed in advance, under a duty of confidentiality, and at the Controller's cost, including the Processor's time at the hourly rate stated in the signed proposal. The audit is limited to the processing under this DPA and gives no access to other customers' data. The auditor may not be a competitor of the Processor.
11. International transfers (Art 44–49)
The Controller authorises transfers of personal data to a third country where Chapter V GDPR permits them: under an adequacy decision of the European Commission, including the EU-US Data Privacy Framework for a recipient certified under it, or under the EU Standard Contractual Clauses in the recipient's agreement with the Processor.
12. Liability and relationship to the Commercial Terms
Liability between the parties arising out of or in connection with this DPA or the processing under it, whether in contract, under Article 82(5) GDPR or on any other ground, is subject to clauses 7 and 7a of the Commercial Terms. Each party bears any administrative fine imposed on it. Nothing in this DPA limits either party's liability towards data subjects under Article 82 GDPR.
13. Term
This DPA takes effect when the agreement under clause 2 of the Commercial Terms is concluded or, if earlier, when processing under a signed proposal starts, and remains in force for as long as the Processor processes personal data on the Controller's behalf. Clauses 3, 9, 9a, 10, 12, 14 and 15 survive termination.
14. Usage Data (the Processor acting as controller)
The Processor collects and generates Usage Data in the course of providing the Services. The Processor is the controller of Usage Data and determines the purposes and means of its processing, independently of the Controller. Usage Data is not processed on the Controller's behalf; where a record is also Customer Personal Data, clause 1 applies. By entering into the agreement, the Controller authorises the Processor to use the records it processes under this DPA also for the Processor's own purposes in this clause, as their controller. This authorisation is part of the Services as specified. An instruction under clause 2 that withdraws it applies only to records created after the instruction, and prevents the Services as specified.
The Processor processes Usage Data to operate, secure and improve the Services; to develop new products, features and technologies; and to produce aggregate insight and benchmarks. The lawful basis is Article 6(1)(f) GDPR (legitimate interests).
Identified Usage Data is retained for the period set out in clause 9, after which it is irreversibly anonymised and retained indefinitely in that form as the Processor's own data. Aggregate insight derived from anonymised Usage Data, including benchmarks spanning multiple customers, is the Processor's, and may be produced and published in a form that identifies neither the Controller nor any data subject.
The Processor may also, as controller in its own right, anonymise the data processed in the Services, including Customer Personal Data and what users write or upload but not special-category data, and use the anonymised data for the purposes in this clause, including benchmarks spanning customers. Anonymised data does not relate to an identified or identifiable natural person (GDPR Recital 26). The Processor makes it available to others only as clause 10 of the Commercial Terms states. The lawful basis for the anonymisation is Article 6(1)(f) GDPR.
Where Usage Data relates to an identified natural person, that person retains their rights under Chapter III GDPR against the Processor as controller. The Processor answers an erasure or objection request in respect of Usage Data by irreversible anonymisation rather than destruction; once irreversibly anonymised, the data is no longer personal data (GDPR Recital 26).
Exposure of Usage Data to the Controller is governed by the Processor's exposure policy: participation is reported at individual level, performance only in aggregate and only at or above a minimum cohort size, and individual response detail is never disclosed to the Controller.
15. Information to the Controller's personnel
The Controller informs its personnel that the Services are provided by the Processor and that the Processor processes Usage Data as controller as described in clause 14 and in the Processor's published Privacy Policy.
The Processor also makes that information available directly to data subjects, through the Services and its published Privacy Policy. The two are complementary; neither relieves the other, and the Processor's own transparency duty as controller under Article 13 GDPR is not discharged by this clause.
Annex 1 — Details of the processing (Art 28(3))
| Item | Detail |
|---|---|
| Controller | The Customer named in the signed proposal |
| Processor | GTAIM AB |
| Subject-matter | Delivery of the Services described in the signed proposal to the Controller's personnel |
| Duration | The term of the engagement, including any further signed proposal that continues it |
| Nature and purpose | Hosting and delivering the Services; issuing invitations and notices; recording enrolment and participation; reporting to the Controller |
| Categories of data subjects | The Controller's personnel invited to or enrolled in the Services; other natural persons whose personal data the Controller's personnel include in what they write or upload |
| Categories of personal data | Identity and contact data, such as name, contact details, title and role; data on enrolment in, use of and participation in the Services, including progress and completion; content the data subjects submit through the Services, other than answers given to questions the Services ask, which are Usage Data (clause 14); personal data about persons other than the user, and special-category data, contained in those answers |
| Special categories (Art 9) | The Services do not ask for special-category data and the Controller does not instruct its collection. Where a data subject includes it in free text, the Processor processes it only on the Controller's behalf, for delivering the Services, and for no other purpose. |
| National identifiers | None. The Processor does not process personnummer or samordningsnummer. If this changes, lag (2018:218) 3 kap. 10 § applies and this Annex is updated. |
Annex 2 — Technical and organisational measures (Art 32)
Proportionate to the risk of the processing described in Annex 1. The Processor maintains measures in each of the following areas and adapts them to the state of the art.
- Access control: access limited by role and scoped to the owning organisation; least-privilege administrative access; multi-factor authentication for administrative access.
- Encryption: personal data encrypted in transit and at rest.
- Confidentiality of responses: individual answers are not disclosed to the Controller (clause 14).
- Minimisation: only the data necessary for the Services is collected.
- Resilience and recovery: regular backups and the ability to restore availability and access to personal data after an incident.
- Detection and logging: error monitoring and logging of administrative actions.
- Sub-processor governance: written agreements meeting Article 28(4) GDPR (clause 5).
- Retention and deletion: retention, return and deletion as clause 9 sets out, and irreversible anonymisation of Usage Data (clause 14). Deleted data is removed from production systems without undue delay. Residual copies in encrypted backups expire with the backup rotation cycle and are restored only for disaster recovery and to test that recovery works.