Version: 2026-11-13
Transfer Impact Assessment: OpenAI API
This document is a reusable transfer impact assessment ("TIA") support note for Connection Game customers. It describes the current transfer of personal data to OpenAI when Connection Game uses OpenAI's standard API endpoint.
The customer's own TIA may need to include customer-specific factors, such as the customer's sector, risk tolerance, categories of employees, internal policies, and whether the customer uploads meetings that contain sensitive information.
1. Scope
Importer / sub-processor: OpenAI, including OpenAI Ireland Ltd. for EEA and Swiss data under OpenAI's DPA and relevant OpenAI affiliates involved in providing the API service.
Exporter: Connection Game AS, acting as processor for the customer where the customer is the controller.
Service: OpenAI API used by Connection Game for language model processing.
Current endpoint: api.openai.com for accounts that have not been switched to Azure.
Transfer destination: This OpenAI path may involve processing outside the EU/EEA, including in the United States.
Azure alternative: Accounts with use_azure_llm enabled do not use this OpenAI transfer for text analysis. Those calls go to a Microsoft Foundry resource in Sweden Central, deployment type Data Zone Standard. Inference stays in the EU data zone, and data stored at rest stays in Sweden. That path is outside the scope of this OpenAI TIA.
Transfer mechanism: OpenAI Data Processing Addendum and EU Standard Contractual Clauses (SCCs) for transfers of EEA and Swiss data, as described in OpenAI's DPA.
2. Processing Activity
Connection Game uses OpenAI to provide:
- meeting transcript analysis;
- speaker name tagging;
- meeting summaries;
- team and individual analysis generation;
- profile and insight generation;
- AI coach responses;
- short overviews of uploaded team strategy documents (PDF);
- other text-based analysis features in the service.
Meeting analyses typically use OpenAI's Responses API with background processing enabled. Team strategy PDF ingest uses a synchronous Responses API call with a file attachment. The uploaded file is deleted after the overview is returned and is not stored by Connection Game. The implementation does not currently use OpenAI's EU data residency endpoint.
3. Personal Data Transferred
Depending on the feature used, OpenAI may receive:
- meeting transcriptions and speaker labels;
- participant names or display names;
- team name, roles, titles, and team context;
- meeting agenda text (titles, purpose, owner, duration, and notes, or free-form text) when a prepared meeting is analysed. PDF documents attached to the preparation are stored by Connection Game and are not sent to OpenAI;
- user-provided text such as reflections or user manual answers;
- Big Five high-level profile information or related analysis context where the user has given the required consent;
- AI coach chat messages and generated responses;
- uploaded team strategy documents (PDF) processed to produce a short stored text overview (the PDF is not retained);
- technical metadata needed to route and reconcile analysis jobs.
Connection Game does not intentionally send raw audio files to OpenAI in the current main workflow. Raw audio is processed by speech-to-text and diarization providers before text analysis.
4. Data Sensitivity
The transferred data is generally work-related personal data. It may include:
- identifiable statements from meetings;
- opinions, communication style, collaboration patterns, and profile-derived insights;
- names and organizational context;
- personality-related profile data where the relevant feature is enabled.
Customers should avoid uploading special category data unless this has been clearly assessed and a separate legal basis and safeguards are in place. Meeting recordings may accidentally contain sensitive information if participants discuss health, union membership, religion, political opinions, or other protected topics.
5. OpenAI Contractual Safeguards
Connection Game relies on OpenAI's data processing terms for API processing. Based on OpenAI's public documentation:
- OpenAI provides a Data Processing Addendum for business/API customers.
- For customers based in the EEA or Switzerland, the DPA is entered into with OpenAI Ireland Ltd. for relevant processing.
- OpenAI states that transfers of EEA and Swiss data outside the EEA/Switzerland are protected by SCCs or an adequacy decision where applicable.
- OpenAI states that API customer content is not used to train OpenAI models by default.
Connection Game should keep a copy or reference to the applicable OpenAI DPA and terms with the customer contract file.
6. Technical and Organizational Safeguards
Connection Game applies the following supplementary measures:
- Data minimization: Requests are scoped to the analysis being performed. Raw audio is not sent to OpenAI in the main workflow.
- Purpose limitation: OpenAI is used only to generate the requested analyses, summaries, profiles, and coach responses.
- Access control: Access to customer data in the service is controlled through authenticated accounts and role-based application access.
- Encryption in transit: API communication uses HTTPS/TLS.
- Provider controls: OpenAI states that API content is not used for model training by default.
- Retention controls: Connection Game applies internal retention rules, including deletion of audio within 24 hours and transcriptions within 180 days.
- Sub-processor documentation: OpenAI is listed in the maintained sub-processor list.
- No sale or marketing sharing: Connection Game does not sell customer personal data or share it with providers for their own marketing purposes.
OpenAI's standard API may retain limited abuse-monitoring logs unless separate zero data retention controls are approved and enabled. The current implementation should therefore be documented as a US transfer with SCCs and supplementary measures, not as EU-only processing or zero data retention.
7. Legal Environment Assessment
The United States does not provide a general EU adequacy decision for all transfers. Transfers to US providers therefore require a valid transfer mechanism, such as SCCs, unless the specific recipient and processing are covered by another valid mechanism.
Potential risks include:
- access requests by US public authorities under applicable US law;
- limits on notification or redress in some circumstances;
- difficulty for EU data subjects to exercise rights directly against foreign authorities.
Relevant mitigating factors in this specific processing:
- OpenAI acts as a processor under contractual commitments.
- The transfer is limited to text and analysis context needed for service delivery; raw audio is not intentionally sent to OpenAI in the main workflow.
- The data is primarily work-context collaboration data, although it can include identifiable and profile-related information.
- The service is not used for automated decisions that grant or remove legal rights or employment status.
- Internal retention and access-control measures reduce the amount and duration of data held in Connection Game systems.
8. Risk Assessment
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| Provider retention of prompts/responses for abuse monitoring | Medium | Medium | OpenAI API no-training default; document retention terms; minimize prompt content; consider ZDR/EU residency as future improvement |
| Government access request in third country | Low to medium | Medium | SCCs; OpenAI DPA; data minimization; avoid special category data; customer information and policies |
| Excessive personal data in prompts | Medium | Medium | Prompt design, analysis-specific payloads, avoid raw audio, retention policy |
| Sensitive data accidentally included in meeting transcript | Medium | High | Customer recording policy, participant notice, avoid recording sensitive meetings, customer LIA/DPIA where needed |
| Misuse of generated insights internally by customer | Medium | Medium to high | Customer controller responsibility; role-based access; terms prohibit surveillance or unlawful control; explain intended development purpose |
Overall residual risk is assessed as moderate for ordinary leadership/team-development use, provided the customer does not intentionally upload sensitive meeting content and the contractual/SCC safeguards are in place.
9. Conclusion
For current use of OpenAI in Connection Game, the transfer can be documented as:
- a necessary sub-processing activity for AI-generated analysis and coach functionality;
- a transfer to OpenAI's standard API infrastructure that may include the United States;
- governed by OpenAI's DPA and SCCs for EEA data;
- supported by supplementary measures including minimization, access control, encryption in transit, retention controls, and no use of API content for model training by default.
Customers should include this information in their own TIA and assess whether their planned use introduces higher risk. Higher-risk use may require stricter internal controls, avoiding sensitive meetings, a DPIA, or a move to an EU-resident LLM setup.
10. Future Improvement Option
OpenAI offers EU data residency for eligible API customers through region-specific projects and the eu.api.openai.com endpoint, subject to OpenAI approval and contractual requirements such as zero data retention amendments.
Connection Game does not currently document the service as using OpenAI EU data residency. A migration would require separate commercial approval from OpenAI and technical changes because the current implementation uses background OpenAI Responses API jobs.