Legal
Data Processing Addendum
Draft for legal review. This Data Processing Addendum (DPA) forms part of the agreement between GinfoCloud (the Processor, we) and the organisation that subscribes to a Team plan or a Schools plan (the Customer). It applies automatically when the Customer accepts the Terms of Service for a Team, and it meets Article 28 GDPR, the UK GDPR, Burkina Faso Law No. 001-2021/AN on the obligations of a processor (sous-traitant), and the service-provider requirements of US state privacy laws.
Last updated: [date] · Version: [1.0]
1. Scope and roles
1.1 This DPA applies to the personal data we process on the Customer's behalf: the Team's membership, roles, invitations and seats, and the progress figures about members that the Customer views on the manager dashboard, in CSV exports and in AI-literacy reports (Customer Personal Data).
1.2 For Customer Personal Data, the Customer is the controller and we are its processor. For each member's own learning content (prompts, Feedback, work profile, library, Community activity) and for Account management, we act as an independent controller under our Privacy Policy, and the Customer has no access to that content.
1.3 Annex 1 describes the processing (subject matter, duration, nature, purpose, types of data and categories of data subjects).
2. Customer's obligations
2.1 The Customer is responsible for: (a) having a lawful basis for viewing members' figures; (b) informing members, before inviting them, of what managers can see and why; (c) consulting employee representatives where the law or a collective agreement requires it; (d) carrying out any data protection impact assessment it needs; (e) the accuracy of the email addresses it invites; and (f) not using Customer Personal Data to make decisions prohibited by section 13.5 of the Terms.
2.2 The Customer's instructions to us are this DPA, the Terms, and the Customer's use of the Service's settings. Additional instructions must be in writing and consistent with the Service; if they create extra cost, we may charge for them after agreeing a quote.
3. Our obligations as processor
3.1 Instructions. We process Customer Personal Data only on the Customer's documented instructions, including for international transfers, unless a law that applies to us requires otherwise; in that case we will inform the Customer before processing, unless that law prohibits it. We will tell the Customer if we believe an instruction breaks data protection law.
3.2 Confidentiality. Everyone authorised to process Customer Personal Data is bound by confidentiality.
3.3 Security. We implement the technical and organisational measures in Annex 2, appropriate to the risk, and may update them provided the overall level of security is not reduced.
3.4 Sub-processors. The Customer gives a general authorisation to use the sub-processors listed in Annex 3 and on our sub-processors page. We will inform the Customer at least 30 days before adding or replacing a sub-processor (by email to the Team owner and on that page). The Customer may object on reasonable data protection grounds within that period; if we cannot reasonably accommodate the objection, the Customer may terminate the affected Team subscription and receive a refund of prepaid fees for the remaining period. We impose on each sub-processor data protection obligations equivalent to this DPA and remain responsible for its performance.
3.5 Assistance. Taking into account the nature of the processing, we assist the Customer by appropriate technical and organisational measures in responding to requests from data subjects, and in complying with its obligations on security, breach notification, impact assessments and prior consultation. If we receive a request from a data subject about Customer Personal Data, we will forward it to the Customer without undue delay and will not answer it ourselves except to confirm it was forwarded.
3.6 Personal data breaches. We will notify the Customer without undue delay, and in any event within 48 hours, after becoming aware of a personal data breach affecting Customer Personal Data, with the information then available (nature of the breach, categories and approximate number of people and records concerned, likely consequences, measures taken or proposed, and a contact point), and will supplement it as information becomes available. Notification is not an admission of fault.
3.7 Deletion or return. When the Team subscription ends or the Team is deleted, we delete Customer Personal Data within [30 days], except where the law requires us to keep it. Before that, the Customer can export members' figures as CSV. Members keep their own Accounts and learning content, which remain governed by our Privacy Policy.
3.8 Records and audits. We make available to the Customer all information reasonably necessary to demonstrate compliance with this DPA, including summaries of our security measures and any certifications or audit reports. Where that information is not sufficient, the Customer may, at its own cost, with at least 30 days' notice, no more than once in any 12-month period (unless required by an authority or after a breach), and subject to confidentiality, carry out or commission an audit by an independent auditor, in a way that does not disrupt the Service or compromise other customers' data.
4. International transfers
4.1 We are established in Burkina Faso and some sub-processors are in the United States. Where Customer Personal Data subject to the GDPR is transferred to a country without an adequacy decision, the Standard Contractual Clauses adopted by Commission Implementing Decision (EU) 2021/914 apply and are incorporated by reference: Module 2 (controller to processor) between the Customer and us, and Module 3 (processor to processor) between us and our sub-processors. For the Clauses: clause 7 (docking) applies; clause 9 option 2 (general authorisation, 30 days); clause 11 optional language does not apply; clause 17 governing law is [the law of Ireland]; clause 18 forum is [the courts of Ireland]; Annexes I to III are Annexes 1 to 3 of this DPA. For UK data, the UK International Data Transfer Addendum applies; for Swiss data, the Clauses apply with references to the Swiss Federal Act on Data Protection.
4.2 Transfers of data subject to the law of Burkina Faso or of another ECOWAS or African Union state take place under the safeguards and authorisations required by that law.
5. US state privacy laws
Where the CCPA or a similar US state law applies, we act as a service provider or processor and we: (a) do not sell or share Customer Personal Data; (b) do not retain, use or disclose it for any purpose other than providing the Service under the agreement, or outside the direct business relationship with the Customer; (c) do not combine it with personal data received from other sources, except as the law permits; (d) comply with the applicable law and provide the same level of protection; (e) notify the Customer if we can no longer meet our obligations; and (f) allow the Customer to take reasonable steps to stop and remedy unauthorised use. We certify that we understand and will comply with these restrictions.
6. Liability and precedence
6.1 Each party's liability under this DPA is subject to the limitations in the Terms, except where the law does not allow such limitation (including the liability of each party to data subjects under Article 82 GDPR).
6.2 In case of conflict, the Standard Contractual Clauses prevail over this DPA, and this DPA prevails over the Terms for the processing of Customer Personal Data.
6.3 This DPA ends when we no longer process Customer Personal Data.
Annex 1 — Description of the processing
| Item | Description |
|---|---|
| Categories of data subjects | Members, admins and owners of the Customer's Team; people invited to join it |
| Types of personal data | Names, email addresses, roles, invitation status and expiry, seat usage; per member: number of evaluations, activity dates, average scores per criterion, missions passed, start and end test scores, certificate status, number of exercises reported as used at work |
| Special categories | None. The Customer must not invite members to submit them. |
| Nature of processing | Storage, organisation, aggregation, display on the dashboard, CSV export, report generation, deletion |
| Purpose | Enabling the Customer to organise and follow AI-literacy training for its members |
| Duration | The term of the Team subscription, then deletion under section 3.7 |
| Frequency of transfer | Continuous, while the Service is used |
Annex 2 — Technical and organisational security measures
- Encryption of data in transit (TLS) and [at rest — to be confirmed with the hosting provider].
- Passwords stored only as salted hashes; password reset links expire after 60 minutes.
- Email verification before use of the Service; invitations restricted to the invited address and valid 7 days.
- Role-based access: only owners and admins see dashboards and reports; members cannot manage the Team; enforced on the server.
- Managers never see prompts, Feedback, work profiles, libraries or Community activity.
- Rate limiting on authentication, AI features and sharing.
- Secrets and API keys kept in server configuration outside the code repository.
- Protection against cross-site request forgery and cross-site scripting; AI outputs rendered as plain text.
- Signed verification of payment webhooks.
- Daily backups retained [30 days], with restore tests [quarterly].
- Logging of administrative access; access limited to authorised staff under confidentiality obligations.
- Incident response procedure with notification as in section 3.6.
- Data minimisation: no special categories requested; visitor data deleted after 30 days.
Annex 3 — Authorised sub-processors
See the sub-processors page, which is part of this Annex.