Privacy Policy
Your season contains personal information. This policy explains how information is used when you visit our website or take part in the CompeteLab beta.
About this policy
CompeteLab is a sports-performance coaching and reflection product for competitive teams. This policy covers our website and the CompeteLab beta features made available to you. Features and the information they require can differ between beta versions.
This service is operated under the CompeteLab name from Alberta, Canada. Our privacy contact can answer questions about the operator and our practices using the contact details below. Last updated: October 14, 2026.
Information you provide
When you express interest in the beta, we collect your name, email, sport, optional team name and competitive level, and the performance goals you choose to share. Support requests include your contact details and the information you send us.
When you use account and team features, information can include your name, email, account identifier and team membership. Sport-performance features use the competition information, goals, athlete ratings, preparation responses, post-event and practice reflections, and performance observations you enter.
AI Coach features process your messages and generated responses, together with relevant context and derived memories or insights. If you use recording features, the content includes voice or meeting recordings and transcripts, including speaker labels where supported.
You may voluntarily mention readiness, soreness, injury concerns, stress, confidence or other personal concerns. Share only what is needed for your sport-performance reflection. CompeteLab is not a healthcare service and does not diagnose or treat injuries or mental-health conditions.
Technical information
Website hosting involves processing technical request information such as IP address, browser information, requested page and request time to serve pages, protect the service and investigate errors. This website does not include advertising trackers or optional analytics scripts.
Where you enable app notifications, delivery requires a device push token and your time zone. Operational records can include error details, AI model usage, processing times and generated analysis. Support may ask you for app and device versions and error details. The technical information collected by a beta feature depends on the features you use and the permissions you allow.
How information is used
- Operate accounts, team access, preparation, reviews and meetings.
- Provide AI coaching and personalize it using relevant season context.
- Identify longitudinal performance patterns and maintain athlete or team memory.
- Help teams test interventions and review progress.
- Manage beta applications, send requested notifications and provide support.
- Protect the service, troubleshoot errors and maintain reliability.
Where applicable law requires a legal basis, processing depends on the purpose: providing the service you request, consent for optional activities, legitimate interests in security and support, or compliance with legal obligations. You can withdraw consent for optional processing by contacting us; this does not undo processing already lawfully completed.
AI processing
AI features use the content you submit and relevant team or athlete context to generate responses, summaries, patterns and suggested interventions. Information needed for those tasks may be sent to OpenAI to generate coaching and analysis, transcribe personal reflection audio and create numerical representations of text used to find relevant season context. Generated insights and conversation history are stored in our backend. Provider retention depends on the applicable service and account settings; we do not promise that AI requests are processed without retention.
AI outputs can be inaccurate or infer something you did not intend. Review outputs before relying on them or sharing them with others. You can ask us to review inaccurate personal information or derived insights. Avoid sending unnecessary sensitive information or another person’s private information.
Audio and transcripts
Recording features require microphone access. Only record a meeting or another person after obtaining appropriate consent from everyone involved. Explain the purpose of the recording and that transcription and AI processing may be involved.
Meeting audio passes through Firebase and Google Cloud to Speechmatics’s US service for live transcription and speaker identification. The live relay does not store raw audio in Cloud Storage. Final transcripts are saved and shared with the team, and OpenAI processes the transcripts to produce meeting insights. Temporary live captions are not persisted.
Recordings and transcripts are used for the recording or review feature you choose, including preserving lessons and decisions. Transcription and speaker labels can be inaccurate. Revoking microphone permission prevents future microphone access but does not itself delete content already submitted.
Optional voice setup
With your separate, explicit consent, voice setup stores a short recording and a voice identifier privately to help recognize you in later meetings for that team. These may constitute biometric data. Speechmatics processes setup audio and voice identifiers; we do not send participant names to Speechmatics. Your saved setup sample and identifier are not shared with teammates.
Saved samples may be reused to refresh your voice identifier after a Speechmatics model update. Voice identification is optional and is not identity verification. You can delete your saved voice setup from a meeting or from Account → Saved meeting voices, including when AI permission or billing access is off. Deleting it does not delete existing team meeting transcripts.
Service providers and disclosure
Firebase and Google Cloud provide account authentication, database and audio storage, and backend processing. Speechmatics processes meeting audio, optional voice setup audio and voice identifiers in its US service for transcription and speaker identification. OpenAI processes meeting transcripts and other content needed for AI coaching, analysis, personal reflection transcription and text embeddings. Expo delivers enabled push notifications through the device notification infrastructure, including Apple’s push service on iOS; notification requests include a delivery token and notification content. Vercel hosts this website and processes the technical requests needed to deliver it.
We may disclose information when required by law, to respond to valid legal requests, or to protect users and the service. A business reorganization may require transfer of service records, subject to applicable privacy requirements.
Retention and deletion
Information is retained for the purposes for which it is collected, including providing the service, maintaining useful season history, addressing support requests and meeting applicable legal obligations. Retention depends on the data type, whether your account is active, shared team context and legal requirements. The following periods describe our own storage and cleanup, rather than a guarantee of provider-side retention.
- Uploaded raw recordings: deleted as soon as their transcript is saved, with a daily cleanup backstop for remaining audio older than seven days, whether or not transcription succeeded. Saved voice setup samples are the exception described below.
- Transcripts and personal coaching records: retained for the life of the account, or until the associated session is deleted. Shared team meeting records remain for the life of the team; one member deleting their account does not erase them. Team data is deleted when its last member deletes their account.
- Optional voice profiles and setup samples: retained privately while you opt in for that team, deleted on request or account deletion, and removed after you leave the team by the daily cleanup. Incomplete setups expire after seven days.
- Speechmatics processing jobs: we request deletion after the transcript is saved and retry daily if the provider is unavailable. Abandoned jobs are cancelled after seven days. Our cached Speechmatics results are kept for up to seven days plus the daily cleanup interval and removed on account deletion. Voice setup result caches are also cleared when the voice profile is deleted.
- Temporary recovery audio on the recording device: removed after server-confirmed completion or explicit use of the saved transcript, and cleared on sign-out or account deletion. Files older than 35 minutes are purged on the next app launch or recording setup. A closed app cannot perform this cleanup.
- Notifications: 90 days. Invitation codes: 14 days to redeem, followed by deletion. Scheduled processing failures can delay cleanup.
Provider-side retention depends on the applicable service, account agreement and settings. Model-training sharing is disabled for our Speechmatics account. Requesting deletion of a Speechmatics processing job does not establish that its live service keeps no operational logs.
You can delete your account in the app or contact us to request deletion of information. We may need to verify your identity. Shared records involving other athletes need separate review; deleting your account should not be understood as automatically deleting every team record. Some information may need to be retained for legal obligations or resolving disputes. Backup copies may persist until their normal expiry, including managed database backups and point-in-time recovery snapshots. Those copies are not accessible through the app or to other users and are not restored to the live database.
See account deletion help for request guidance. We will explain applicable exceptions when responding to a request.
Security and international processing
We use safeguards appropriate to the information and service, including access restrictions and secure transmission where supported. No storage or transmission method can guarantee complete security.
Backend functions are configured to run in the United States. Providers may also process information in other countries, outside Canada, where privacy laws and government access rules differ. The purposes are hosting, authentication, storage, AI processing and notification delivery described above. Contact our privacy contact below to request information about our policies for providers outside Canada, processing locations and safeguards relevant to your account.
Your choices and rights
Depending on your location, you may have rights to access, correct, export or delete personal information, object to or restrict certain processing, or withdraw consent. Contact us using the details below. We may verify your identity before responding and will respond within applicable legal time limits.
You may also contact your local privacy regulator. Manage device notifications and optional permissions in iOS Settings. See Privacy Choices for more information.
Children’s privacy
CompeteLab is not directed to children under 13, or a higher minimum age where local law requires it. Young athletes who are not legally able to agree to the service need parent or guardian approval. Each team member must accept the updated meeting processing disclosure, and junior players also require their guardian’s updated approval. Optional voice setup requires separate explicit consent. If you believe a child has submitted information without the required authorization, contact us so we can review and address it.
Policy changes
We may update this policy as the service develops. The date above identifies the current version. When changes materially affect how personal information is handled, we will provide notice through an appropriate channel, as required by applicable law.
Contact
CompeteLab — Privacy and support contact
support@competelab.app ↗