Version: 2026-11-19
Sub-processor List
This document lists the sub-processors Connection Game AS uses to deliver the Connection Game service. It is intended as an annex to customer data processing agreements and as supporting material for customer privacy documentation, records of processing, legitimate interest assessments, and transfer impact assessments.
iOS note (2026-08-12): Distributing the iOS app via Apple does not add Apple as a content sub-processor for meeting audio or transcripts. Audio remains on-device until the user uploads it to Connection Game’s own backend; Apple does not receive meeting content for analysis. When the user enables push notifications, Apple’s APNs delivers notification payloads (which may include a meeting title) and processes device tokens for delivery.
Connection Game AS remains responsible for ensuring that sub-processors process personal data only on documented instructions and under appropriate contractual, technical, and organizational safeguards.
Summary
| Sub-processor | Purpose | Main data categories | Processing region / endpoint | Transfer mechanism |
|---|---|---|---|---|
| Supabase | PostgreSQL database, authentication, and private file storage | Account data, organization/team data, profiles, analyses, transcriptions, consent logs, meeting preparation (agenda, notes, and PDF documents in the private meeting-documents bucket) |
EU-hosted where configured | DPA; SCCs if data is processed outside the EU/EEA |
| Render | Application hosting | Application data in transit, technical logs, temporary audio files during processing | EU region where configured | DPA; SCCs if data is processed outside the EU/EEA |
| OpenAI | Language model analysis, AI coach, profile and meeting analysis for accounts that are not switched to Azure | Meeting transcripts, names, team context, meeting agenda text when a prepared meeting is analysed (PDF attachments are not sent), analysis inputs/outputs, Big Five summaries where used, coach chat messages, uploaded team strategy PDFs (not retained) | Default path uses OpenAI API at api.openai.com |
OpenAI DPA; EU SCCs via OpenAI Ireland Ltd.; supplementary measures described in the TIA |
| Microsoft (Azure / Microsoft Foundry) | The same text-analysis purposes, only for accounts with Azure enabled | The same text categories as OpenAI. Audio is not sent | Sweden Central resource, Data Zone Standard (EU data zone). Data at rest stays in Sweden | Microsoft DPA / Product Terms |
| Soniox | Speech-to-text transcription | Audio recordings, transcription metadata, and optional meeting-context text, including an agenda when the meeting was prepared | EU API endpoint api.eu.soniox.com |
DPA; EU/EEA processing where configured |
| pyannoteAI | Speaker diarization and voiceprint identification | Audio recordings, speaker labels, voiceprint embeddings where the user has enrolled | EU provider (France), API endpoint api.pyannote.ai |
DPA; EU/EEA processing where configured |
| Resend | Transactional email | Email addresses, names, invitation content, delivery metadata | Global email infrastructure | DPA; SCCs if data is processed outside the EU/EEA |
| Stripe | Payments for CG Transcript product where applicable | Payment metadata, customer/contact information, user ID in payment metadata | Stripe infrastructure | DPA; SCCs / approved transfer mechanisms |
| PostHog | Product analytics and diagnostics | User IDs, usage events, device/browser properties, server-side event metadata | EU PostHog project where configured | DPA; SCCs if data is processed outside the EU/EEA |
| Apple (APNs) | Delivery of optional iOS push notifications | Device push tokens; notification title/body (may include meeting title); delivery metadata | Apple push infrastructure (may include processing outside the EU/EEA) | Apple developer/service terms; SCCs / transfer mechanisms under Apple’s applicable terms where transfers occur |
Processing Details
Supabase
Purpose: Database, authentication, account administration, and private file storage.
Data: User account data, organization and team membership, profile data, consent records, analysis outputs, meeting transcription records, audio metadata, meeting preparation (agenda, notes, and PDF documents in the private meeting-documents bucket), and other application data stored by the service.
Region and safeguards: Connection Game configures Supabase for EU hosting where available. Supabase acts as a sub-processor under its data processing terms. If Supabase or its affiliates process data outside the EU/EEA, relevant transfer mechanisms such as SCCs apply.
Render
Purpose: Hosting for the backend and related application services.
Data: Application traffic, technical logs, environment-level service data, and temporary binary files during processing. Audio files may be temporarily stored on application servers before the retention policy deletes them.
Region and safeguards: Connection Game configures Render services in EU regions where available. Local filesystem storage on Render is treated as ephemeral and temporary; persistent application data is stored in the database or designated storage.
OpenAI
Purpose: Text analysis, meeting-data analysis, AI coach responses, profile generation, speaker name tagging, summaries, team/individual analysis generation, and short overviews of uploaded team strategy documents.
Data: Inputs can include meeting transcriptions, speaker names, team context, meeting agenda text when a prepared meeting is analysed, role/title information, user-provided manual answers, Big Five high-level profile information where relevant, analysis prompts, coach chat messages, uploaded team strategy documents (PDF) processed to produce a stored text overview, and generated outputs. Strategy PDFs are not retained after the overview is created. Meeting-preparation PDFs are stored by Connection Game and are not sent to OpenAI.
Region and safeguards: The default path uses OpenAI's standard API endpoint (api.openai.com). This may involve processing outside the EU/EEA, including in the United States. OpenAI processes API customer data under its DPA, with OpenAI Ireland Ltd. and EU SCCs for EEA and Swiss data transfers. OpenAI states that API content is not used to train OpenAI models by default. A separate transfer impact assessment is maintained in docs/legal/tia.md.
Accounts with Azure enabled do not use this OpenAI path for their text analysis. Those calls go to Microsoft Foundry, described below.
Microsoft (Azure / Microsoft Foundry)
Purpose: The same text-analysis purposes as OpenAI, for accounts an administrator has switched to Azure.
Data: The same text categories listed for OpenAI. Meeting audio is not sent.
Region and safeguards: The Foundry resource is in Sweden Central. Model deployments use Data Zone Standard, so prompts and responses are processed within the EU data zone. Data stored at rest remains in Sweden. Microsoft does not use customer content submitted through Azure OpenAI to train the foundation models. Microsoft's DPA and Product Terms apply.
Soniox
Purpose: Speech-to-text transcription.
Data: Audio recordings, metadata needed to create transcriptions, and optional meeting-context text. When a meeting was prepared, that context includes the agenda (titles, purpose, owner, duration, and notes, or free-form text). PDF attachments are not sent.
Region and safeguards: The current application configuration uses the EU API endpoint api.eu.soniox.com. Soniox is used in the default meeting transcription workflow together with pyannoteAI.
pyannoteAI
Purpose: Speaker diarization, and voiceprint identification where a user has enrolled.
Data: Meeting audio, speaker labels, diarization output, and the voiceprint embedding where a user enrolls. Connection Game stores the embedding and does not keep the enrollment recording after the profile is created. The sample is sent to pyannoteAI to create the embedding.
Region and safeguards: pyannoteAI is a France-based provider. The current API endpoint is api.pyannote.ai. Voiceprint identification is biometric data used to uniquely identify a person. The legal basis is the user's explicit consent (GDPR Art. 9(2)(a)). Use is limited to labelling that person in meeting recordings in their teams.
Resend
Purpose: Transactional email, including team invitations.
Data: Recipient email addresses, inviter names, team names, message content, and delivery metadata.
Region and safeguards: Resend processes email through global email infrastructure. Connection Game uses Resend as a service provider for transactional email only.
Stripe
Purpose: Payment processing for the CG Transcript product where applicable.
Data: Payment session data, customer/contact information handled by Stripe, payment status, and internal user ID metadata used to link purchases to accounts.
Region and safeguards: Stripe acts as an independent payment processor and sub-processor/service provider depending on the processing activity. Stripe uses approved transfer mechanisms for international transfers.
PostHog
Purpose: Product analytics, usage metrics, diagnostics, and improvement of the service.
Data: User IDs, event names, coarse usage properties, device/browser information, and technical event metadata. Connection Game should not intentionally send full meeting transcripts or coach chat content to PostHog.
Region and safeguards: The project is configured for the EU PostHog environment where available. PostHog processes data under its data processing terms.
Apple (APNs)
Purpose: Deliver optional push notifications to the Connection Game iPhone app when an analysis started by the user finishes or fails.
Data: APNs device tokens stored by Connection Game; notification payloads sent via APNs (alert title/body, which may include a meeting title); technical delivery responses from APNs.
Region and safeguards: Apple operates global push infrastructure. Connection Game does not send full transcripts or audio to APNs. Users can disable notifications in the app or in iOS Settings. Device tokens are deleted on account deletion and when a token is rejected by APNs.
Change Management
Connection Game reviews this list when:
- a new provider is added;
- a provider receives new categories of personal data;
- a provider's processing region changes;
- a provider's data processing terms, DPA, SCCs, or retention terms materially change;
- a feature changes the data sent to an existing provider.
When this document changes, update the Privacy Policy, DPA, TIA, customer compliance pack, Norwegian translations, and the served legal copies in frontend/public/legal/ where relevant.