Skip to Main Content
Connection Game
Log in →
NO | EN
Home How it works Pricing Privacy
Home How it works Pricing Privacy
Log in →

← Privacy

Version: 2026-11-12

Technical and Organizational Measures

This document summarizes the technical and organizational measures ("TOMs") Connection Game AS applies to protect personal data processed in the Connection Game service.

The measures are proportionate to the current service: an AI-powered SaaS product for leadership and team development that may process account data, meeting audio, transcriptions, profile data, AI coach messages, and analysis outputs.


1. Governance and Responsibility

  • Connection Game assigns responsibility for privacy and security follow-up internally.
  • Legal and compliance documentation is maintained in docs/legal/ with Norwegian mirrors in docs/GDPR/.
  • Provider and sub-processor changes must be reflected in the sub-processor list, Privacy Policy, DPA, TIA, and related documents.
  • Material changes to data categories, AI providers, transfer regions, or retention must trigger a legal documentation review.

2. Access Control

  • User access requires authenticated accounts.
  • Access is scoped by organization, team, role, and feature permissions where implemented.
  • Administrative access should be limited to personnel with a business need.
  • Users must not share accounts or credentials.
  • Customer administrators are responsible for assigning and removing user access in line with their internal policies.

3. Data Minimization and Purpose Limitation

  • The service processes data needed to provide leadership and team-development insights.
  • Meeting audio is used to create transcriptions and analysis outputs, then deleted according to retention rules.
  • OpenAI receives text and context needed for the relevant analysis, not raw audio in the main workflow.
  • Product analytics should use coarse usage metadata and should not intentionally include full meeting transcripts or coach chat content.
  • Optional Big Five processing requires explicit consent.
  • Optional voiceprint identification requires explicit consent under GDPR Article 9(2)(a). The enrollment recording is not kept after the biometric profile is stored.

4. Encryption and Transmission Security

  • Application traffic and API calls to external providers use HTTPS/TLS.
  • Database and infrastructure providers apply encryption and platform security controls according to their service terms.
  • Secrets and API keys are stored in environment variables or configured secret storage, not hardcoded in application code.

5. Retention and Deletion

Connection Game applies purpose-limited retention:

  • audio recordings: deleted within 24 hours after upload;
  • transcriptions and meeting text: deleted within 180 days after transcription;
  • meeting preparation (agenda, notes, participants, and PDF documents in a private storage bucket): deleted when the preparation or the meeting is deleted, or when the team is deleted. The PDF files are not sent to AI providers. Agenda text may be sent as meeting context when the meeting is analysed;
  • Big Five data: retained only while consent applies and as needed for the purpose;
  • Voiceprint embeddings: retained until the user withdraws consent, deletes the voiceprint, or deletes the account;
  • AI coach history: retained while the user is active, subject to deletion/anonymization after termination and applicable legal retention;
  • technical and security logs: retained as needed for security, troubleshooting, and legal compliance;
  • account, profile, and analysis data: retained while the customer agreement is active and for a limited period afterward for support, documentation, complaints, and legal obligations.

The backend includes a retention routine for old audio files and related metadata. Retention rules should be reviewed whenever data storage or workflow behavior changes.


6. Sub-processor Management

  • Sub-processors are listed in docs/legal/sub-processors.md.
  • New providers must be reviewed for purpose, data categories, processing region, DPA terms, international transfer mechanism, retention, and security posture before production use.
  • Existing providers must be reviewed when their terms, regions, or processing purposes materially change.
  • Where possible, Connection Game uses EU/EEA processing regions and configurations that minimize provider retention.

7. AI-Specific Controls

  • AI outputs are used as decision support and insight generation, not as automated decisions with legal or similarly significant effect.
  • Customer terms prohibit misuse of the service for harassment, surveillance, unlawful control, or manipulation of analysis results.
  • OpenAI API content is not used to train OpenAI models by default according to OpenAI's published API data controls.
  • Prompts and payloads should be scoped to the analysis task and avoid unnecessary personal data.
  • High-risk or sensitive customer use cases should be separately assessed before launch.

8. Recording and Meeting Controls

  • Customers are responsible for informing meeting participants and establishing a legal basis for recording or uploading meetings.
  • The service documentation states that audio is temporary and deleted within 24 hours.
  • Customers should avoid recording sensitive meetings unless they have completed a separate assessment and implemented additional safeguards.
  • Meeting analysis should be used for development and reflection, not disciplinary monitoring.

9. Incident Handling

  • Security or privacy incidents must be assessed without undue delay.
  • If a personal data breach affects customer personal data, Connection Game will notify the affected customer without undue delay and provide available information needed for the customer's GDPR assessment.
  • Incident response should include containment, impact assessment, remediation, documentation, and communication.

10. Data Subject Rights Support

Connection Game supports customers with data subject requests where the customer is the controller, including requests for:

  • access;
  • rectification;
  • erasure;
  • restriction;
  • portability;
  • objection;
  • withdrawal of consent for consent-based features.

Requests should be handled within the legal deadlines, normally one month under GDPR.


11. Backup, Availability, and Recovery

  • Production data is stored with managed infrastructure providers that provide platform-level availability and resilience controls.
  • Service availability depends on the cloud infrastructure, database provider, and external AI/transcription providers.
  • Recovery and continuity procedures should be reviewed as the service matures and customer requirements increase.

12. Review Cadence

These measures should be reviewed:

  • before onboarding customers with stricter compliance requirements;
  • when adding or replacing AI, transcription, analytics, hosting, database, payment, or email providers;
  • when changing retention rules;
  • after material security incidents;
  • when GDPR, AI Act, regulator guidance, or provider terms materially change;
  • at least annually for customer-facing legal documentation.
Read in Norwegian Customer packPrivacy PolicyConsentTerms of ServiceData processing agreement (template)Sub-processorsTIA, transfer impact assessmentLIA, legitimate interest assessment

Get in touch

+47 98646541

hei@connectiongame.ai

About us

Terms of Service · Privacy ·

Made in Norway

Connection Game AS

Gaustadveien 12b

0372 Oslo

NORWAY

VAT.nr: 935 814 030

Partners

  • Motivation Branding Motivation. Branding
  • Sammen med Innovasjon Norge Sammen med Innovasjon Norge
  • NAST
  • MishMash ved UiO

  • Toppledercoach Thor-Philip Hauge

© 2026 Connection Game™ AS. All rights reserved.

Cookies and analytics

We use PostHog to understand how this site is used. Analytics starts only if you accept. Your language preference still works either way. Read the Privacy Policy