← Back

Privacy Policy

Effective Date: July 19, 2026

Last Updated: July 31, 2026

This Privacy Policy explains how Court Coach AI collects, uses, discloses, stores, and otherwise processes personal information when you use the Court Coach AI mobile application, the website at courtcoachai.org, and related features and services (collectively, the “Services”).

Court Coach AI is owned and operated by Brandon Hornbeck.

Questions, privacy requests, or concerns may be sent to: courtcoachsupport@gmail.com.

1. Children's Privacy

Court Coach AI is a basketball-training application intended for general audiences. [CONFIRM: Verify the App Store age rating set in App Store Connect and whether the app is rated 4+, 9+, 12+, or 17+. Confirm whether users under 13 are permitted and whether age verification or parental consent is collected at sign-up.]

Court Coach AI does not knowingly collect personal information from children under 13 in the United States or from children under the applicable minimum age in other jurisdictions without verifiable parental or guardian consent, as required by the Children's Online Privacy Protection Act (COPPA) and similar laws. If we learn that a child under 13 has submitted personal information without appropriate consent, we will take reasonable steps to delete that information and close the associated account.

If you believe a child under 13 has created an account, contact us at courtcoachsupport@gmail.com. Users who are minors in their jurisdiction should use the Services only with the involvement and permission of a parent or legal guardian where required by applicable law.

2. Information We Collect

The table below identifies each category of information we collect, its source, its purpose, whether it is associated with your account, where it is stored, which service providers may receive it, how long we retain it, and what happens when you delete your account.

(a) Name and Email Address

  • What: Your display name and email address.
  • Source: Provided directly during account creation, or received from Apple or Google when you choose Sign in with Apple or Google Sign-In.
  • Purpose: Account creation and authentication, support communications, subscription verification, and service notices.
  • Linked to account: Yes.
  • Stored: [CONFIRM: Verify database provider — Supabase or other.] Server-side database.
  • Providers: [CONFIRM: Supabase or other backend provider]; Apple (if Sign in with Apple); Google (if Google Sign-In).
  • Retention: Retained while your account is active. Deleted or de-identified upon account deletion, subject to legal and operational retention exceptions described in Section 11.

(b) User ID and Account Identifiers

  • What: An internal user identifier assigned when your account is created. [CONFIRM: Identify the specific identifier format — e.g., Supabase UUID, internal database ID.] May also include authentication provider identifiers received from Apple or Google.
  • Source: Generated by the authentication and database system when your account is created; also received from Apple or Google.
  • Purpose: Uniquely identifying your account, linking workout data, linking subscription entitlements, and authenticating requests.
  • Linked to account: Yes.
  • Stored: [CONFIRM: Supabase or other backend database.]
  • Providers: [CONFIRM: Supabase or other backend]; RevenueCat (subscription linking); Apple; Google.
  • Retention: Retained while your account is active. Deleted or de-identified upon account deletion, subject to retention exceptions.

(c) Device ID and Installation Identifiers

  • What: Device-generated or application-generated identifiers, push-notification tokens, and installation identifiers. [CONFIRM: Identify which specific identifiers are collected — e.g., Expo installation ID, RevenueCat anonymous ID, Apple IDFV, push token.]
  • Source: Generated automatically by the device or by SDKs installed in the application.
  • Purpose: Sending push notifications, linking subscription entitlements before account creation, crash and error diagnosis, security, and fraud prevention.
  • Linked to account: May be linked to your account after you sign in.
  • Stored: [CONFIRM: Supabase or other backend] and with applicable SDK providers.
  • Providers: RevenueCat; [CONFIRM: Expo for push notifications, if used]; [CONFIRM: crash-reporting SDK, if any].
  • Retention: [CONFIRM: Specify retention period or criteria, e.g., retained until account deletion or until token expires.]

(d) Basketball Profile and Fitness Information

  • What: Skill level, position, training goals, strengths, weaknesses, self-rated abilities, available equipment, preferred workout duration, preferred training schedule, and other answers you provide during onboarding or profile updates.
  • Source: Provided directly by you.
  • Purpose: Personalizing workout plans, drill recommendations, and AI coaching responses.
  • Linked to account: Yes.
  • Stored: [CONFIRM: Supabase or other backend database.]
  • Providers: [CONFIRM: Supabase or other backend]; the AI provider (used as context when generating coaching responses — see Section 6).
  • Retention: Retained while your account is active. Deleted or de-identified upon account deletion.

(e) Workout and Performance Information

  • What: Generated workout plans, completed workouts, exercises, drills, sets, repetitions, makes, misses, attempts, workout durations, timer data, skipped exercises, difficulty ratings, notes, training history, progress metrics, analytics, streaks, achievements, badges, and ratings.
  • Source: Recorded by the application as you use it, or entered directly by you.
  • Purpose: Tracking your progress, displaying workout history and analytics, personalizing future workouts and coaching, and providing streak and achievement features.
  • Linked to account: Yes.
  • Stored: [CONFIRM: Supabase or other backend database.]
  • Providers: [CONFIRM: Supabase or other backend]; the AI provider (used as context — see Section 6).
  • Retention: Retained while your account is active. Deleted or de-identified upon account deletion.

(f) Voice and Audio Data

  • What: Microphone audio captured during active voice-coaching sessions.
  • Source: Captured from your device microphone when you activate a voice-coaching session.
  • Purpose: Interpreting your speech to provide real-time AI coaching responses.
  • Linked to account:Transcripts or summaries derived from audio may be linked to your account. [CONFIRM: Verify whether transcripts are saved to the user's account or workout history.]
  • Stored: [CONFIRM: Verify whether raw audio is stored server-side or only streamed/buffered locally and then discarded. Confirm whether transcripts are stored in Supabase or another database.]
  • Providers: [CONFIRM: Identify the AI provider. If OpenAI, confirm which API is used and whether audio is sent as raw audio or as a text transcript.] See Section 6 for full voice and AI processing details.
  • Retention: [CONFIRM: Specify raw audio retention, e.g., raw audio is not stored, or raw audio is deleted within X hours. Specify transcript retention period.]

(g) AI Conversations and Other User Content

  • What: Written messages, coaching questions, workout-editing requests, commands, voice-command transcripts, conversation summaries, AI-generated responses, and other content you submit to the AI coach.
  • Source: Provided directly by you during coaching sessions.
  • Purpose: Generating personalized coaching responses, personalizing future sessions, and maintaining coaching context.
  • Linked to account: [CONFIRM: Verify whether conversation history is saved and linked to the user account.]
  • Stored: [CONFIRM: Supabase or other backend database, if conversation history is saved.]
  • Providers: The AI provider; [CONFIRM: Supabase or other backend].
  • Retention: [CONFIRM: Specify retention period or confirm that conversation history is deleted with the account.]

(h) Customer Support Communications

  • What: Information you submit when contacting support, including your name, email address, account information, screenshots, purchase details, technical information, and the contents of your message or attachments.
  • Source: Provided directly by you when you contact us.
  • Purpose: Responding to your request, resolving billing or technical issues, and improving the Services.
  • Linked to account: May be linked to your account where you identify yourself.
  • Stored: [CONFIRM: Identify whether support tickets are stored in email, a helpdesk platform, or another system.]
  • Providers: [CONFIRM: Identify any helpdesk or email provider used for support.]
  • Retention: [CONFIRM: Specify retention period, e.g., retained for X years after resolution for dispute and legal purposes.]

(i) Subscription and Purchase History

  • What: Subscription product identifier, subscription status, trial and introductory-offer status, original transaction identifier, transaction identifier, purchase date, renewal date, expiration date, cancellation status, refund status, billing-issue status, offer eligibility, and entitlement status.
  • Payment card and billing details: App Store payments are processed entirely by Apple. Court Coach AI does not receive or store your payment-card number, bank-account information, or Apple ID password. We receive only the subscription and purchase metadata listed above.
  • Source: Received from Apple and from RevenueCat.
  • Purpose: Activating and verifying premium access, restoring purchases, determining offer eligibility, processing subscription events, and resolving billing-related support requests.
  • Linked to account: Yes.
  • Stored: [CONFIRM: Supabase or other backend database]; RevenueCat.
  • Providers: RevenueCat; Apple.
  • Retention: Purchase records may be retained after account deletion where required for accounting, refund processing, fraud prevention, dispute resolution, or legal compliance. [CONFIRM: Specify retention period, e.g., seven years for accounting records.]

(j) Product Interaction and Usage Data

  • What: App launches, feature taps, workout activity, AI-session activity, navigation patterns, and other interactions with the application. Also includes other usage data not listed above.
  • Source: Generated automatically as you use the application.
  • Purpose: Understanding how features are used, diagnosing errors, improving the Services, and internal analytics.
  • Linked to account:[CONFIRM: Verify whether usage events are linked to the user's account or stored anonymously.]
  • Stored: [CONFIRM: Identify analytics or logging provider, if any, e.g., Supabase, Expo, a third-party analytics SDK.]
  • Providers: [CONFIRM: Identify all analytics providers actually installed as SDKs or called via API.]
  • Retention: [CONFIRM: Specify retention period.]

(k) Crash Data, Performance Data, and Other Diagnostic Data

  • What: Crash reports, error logs, stack traces, performance measurements, network diagnostics, device type, operating-system version, app version, memory, and other technical device information.
  • Source: Generated automatically by the device or by the application when an error or performance event occurs.
  • Purpose: Diagnosing errors, monitoring performance, improving stability, and securing the Services.
  • Linked to account: Not linked to the user (consistent with App Store Connect declaration).
  • Stored: [CONFIRM: Identify crash-reporting provider, e.g., Sentry, Expo, Apple, or another SDK.]
  • Providers: [CONFIRM: Identify crash-reporting providers actually installed.]
  • Retention: [CONFIRM: Specify retention period, e.g., 90 days.]

3. How We Collect Information

  • Directly from you — when you create an account, complete onboarding, enter workout results, communicate with the AI coach, enable voice features, purchase a subscription, or contact support.
  • Automatically from your device — when you use the application, including crash reports, performance data, product interactions, and device identifiers.
  • From Apple or Google — when you choose Sign in with Apple or Google Sign-In, those providers share name, email, and an authentication token with us.
  • From Apple's App Store systems — when you make a purchase or your subscription status changes.
  • From RevenueCat — subscription status, entitlement, and purchase metadata derived from App Store purchase information.
  • From our AI provider — responses and, where applicable, conversation summaries returned by the AI service.

4. How We Use Your Information

  • Create, authenticate, and manage user accounts.
  • Generate and personalize workouts, drills, training plans, and coaching responses.
  • Provide written and voice-based AI coaching.
  • Save workout history, progress, achievements, ratings, and preferences.
  • Verify subscription purchases and determine whether premium access is active.
  • Restore purchases across supported devices and account sessions.
  • Determine trial, introductory-offer, or promotional-offer eligibility.
  • Process subscription events such as renewals, expirations, cancellations, billing issues, and refunds.
  • Send workout reminders, account notices, subscription-related messages, and other service communications, where you have enabled notifications.
  • Respond to support requests and troubleshoot technical or billing issues.
  • Detect fraud, abuse, unauthorized access, and violations of our Terms of Service.
  • Diagnose errors, monitor performance, secure the Services, and improve features.
  • Comply with legal obligations and enforce our agreements.

5. Legal Bases for Processing

Where applicable law requires a legal basis for processing personal information, we rely on the following:

  • Contract performance — processing necessary to create and maintain your account, provide the Services, process purchases, and handle support requests.
  • Legitimate interests — fraud prevention, security monitoring, service improvement, crash diagnosis, and analytics, where those interests are not overridden by your rights.
  • Legal obligation — retaining records required by applicable accounting, tax, or other laws.
  • Consent — microphone access and push notifications, where required by your device operating system or applicable law. You may withdraw consent at any time without affecting processing that occurred before withdrawal.

6. Voice and AI Processing

Overview

Court Coach AI provides live AI-powered coaching. The AI coach can respond to written messages and, where you grant microphone permission, to voice commands.

When microphone capture begins and ends

[CONFIRM: Describe exactly how voice sessions are started — e.g., the user taps a button to begin a voice session, or the app uses a wake word. Confirm when the microphone stops — e.g., the user taps a button to end the session, or capture ends automatically after a period of silence.]

Audio transmission

When a voice-coaching session is active, microphone audio is transmitted off the device to an AI provider for speech recognition and response generation. [CONFIRM: Identify the AI provider. If OpenAI, specify the API — e.g., Realtime API, Whisper API, or Chat Completions API with audio input.]

Raw audio storage

[CONFIRM: State clearly whether raw audio is (a) not stored — only streamed and discarded after processing, (b) temporarily buffered on the device and then deleted, or (c) stored server-side and for how long.]

Transcripts

[CONFIRM: State whether transcripts of voice input are created. If yes, confirm whether they are (a) saved to the user's account or workout history or (b) discarded after the session ends.]

AI model training

[CONFIRM: Verify the applicable API agreement and settings with your AI provider. Confirm whether audio, transcripts, prompts, or other data sent to the AI provider may be used by that provider to train or improve its models. If using OpenAI, verify the data-usage settings for the applicable API tier and whether zero-data-retention has been enabled. State the outcome clearly.]

What the AI provider receives

When you use AI coaching features, we may send the following to our AI provider: your basketball profile (skill level, position, goals, strengths, weaknesses), current workout context, workout history or summaries, your messages or voice audio, and other context needed to generate a coaching response. This may include personal information you speak or type. Do not submit information through the AI coach that you do not want processed as part of providing the feature.

OpenAI

[CONFIRM: Confirm whether Court Coach AI sends audio, transcripts, text prompts, workout data, user content, or other personal information to OpenAI. If yes, state what OpenAI receives, why it receives it, whether it retains it, and whether it may use it for model training. Refer to the OpenAI API data privacy documentation and applicable usage-policy commitments. If a different AI provider is used, name that provider instead.]

You can review OpenAI's privacy practices at openai.com/privacy. [CONFIRM: Add link to the correct AI provider's privacy policy.]

Using the app without microphone access

Microphone access is optional. You can use workout generation, drill tracking, workout history, analytics, and written coaching without granting microphone permission. Granting microphone access is required only to use voice-coaching features.

Revoking microphone permission

You may revoke microphone permission at any time through your device settings (iOS: Settings → Privacy & Security → Microphone → Court Coach AI). Revoking permission disables voice-coaching features but does not affect other features.

Requesting deletion of audio or transcripts

[CONFIRM: Describe the in-app or email mechanism for requesting deletion of saved audio recordings or transcripts, if any are stored.] You may also submit a deletion request by emailing courtcoachsupport@gmail.com.

Personal information spoken aloud

Information you speak during a voice-coaching session — including any personal information you choose to share — may be transmitted to our AI provider as part of providing the feature. You will be asked to grant microphone permission before voice features are enabled, and you may decline or revoke that permission at any time.

7. Service Providers and Data Sharing

We disclose personal information to service providers that perform services on our behalf. Service providers are permitted to use personal information only as necessary to perform those services and are required by contract or applicable law to protect it consistently with this Privacy Policy.

[CONFIRM: Supabase — Authentication, Database, and Backend Infrastructure]

[CONFIRM: Verify that Supabase is the actual backend and database provider. If yes, describe what it receives: account information, user IDs, workout data, subscription records, session tokens, and other data stored in the application database. Supabase acts as a service provider. Data may be processed in the United States. See supabase.com/privacy. If a different backend provider is used, describe it instead.]

[CONFIRM: OpenAI — AI Voice and Language Processing]

[CONFIRM: Confirm whether OpenAI is used. If yes: OpenAI receives the information described in Section 6 — including basketball profile, workout context, messages, voice audio or transcripts, and other context — to generate coaching responses. OpenAI acts as a service provider. Data is processed in the United States. Verify OpenAI's retention and training practices under the applicable API agreement. See openai.com/privacy. If a different AI provider is used, name it instead.]

RevenueCat — Subscription Management

RevenueCat receives an app user identifier (which may be your Court Coach AI account ID after sign-in, or an anonymous identifier before sign-in), subscription product identifiers, transaction identifiers, purchase dates, renewal and expiration dates, cancellation and refund events, trial and offer information, storefront information, and limited app or device information. RevenueCat uses this information to verify purchases, manage subscription entitlements, restore purchases, and deliver subscription status events to our backend. RevenueCat acts as a service provider. Data may be processed in the United States. See revenuecat.com/privacy.

Apple — Authentication, App Store, and Subscriptions

If you use Sign in with Apple, Apple shares your name, email address, and an authentication token with us. Apple processes all App Store payments and subscription billing independently. Apple may share purchase metadata and subscription events with our backend and with RevenueCat. Apple's practices are governed by its own privacy policy at apple.com/privacy.

Google — Google Sign-In

If you use Google Sign-In, Google shares your name, email address, and an authentication token with us. Google's practices are governed by the Google Privacy Policy at policies.google.com/privacy.

[CONFIRM: Expo — App Infrastructure and Push Notifications]

[CONFIRM: Verify whether Expo push notifications are implemented. If yes, describe that Expo may receive device push tokens and notification delivery information. If not used, remove this entry. See expo.dev/privacy.]

[CONFIRM: YouTube or Other Video Provider — Drill Demonstrations]

[CONFIRM: Verify whether drill demonstration videos are served from YouTube or another video platform. If yes, note that viewing those videos may send your IP address and device information to that provider, governed by their own privacy policy. If not used, remove this entry.]

[CONFIRM: Crash Reporting and Diagnostics Provider]

[CONFIRM: Identify any crash-reporting SDK installed (e.g., Sentry, Firebase Crashlytics, Expo error reporting). Describe what it receives: crash reports, error logs, stack traces, device information, and performance data. If no third-party crash-reporting SDK is used, remove this entry.]

Other disclosures

We may also disclose information:

  • When reasonably necessary to comply with law, legal process, or governmental requests.
  • To investigate fraud, abuse, security incidents, or violations of our agreements.
  • To protect the rights, safety, and property of users, Court Coach AI, or others.
  • In connection with a merger, acquisition, financing, reorganization, bankruptcy, or sale of all or part of the business.
  • With your consent or at your direction.

Court Coach AI does not sell personal information and does not use personal information for third-party targeted advertising. Court Coach AI does not share data with advertisers for the purpose of tracking users across apps and websites. [CONFIRM: Verify that no installed SDK — analytics, attribution, advertising, or otherwise — uses Court Coach AI data to track users across apps or websites owned by other parties. If any such SDK is installed, disclose it and update the App Store Connect “Tracking” declaration accordingly.]

8. Data Retention

We retain personal information for as long as necessary to operate the Services, maintain your account, verify subscription access, resolve disputes, prevent fraud, enforce agreements, and comply with legal obligations. The criteria for determining retention are described below.

  • Account and profile information: Retained while your account is active. Deleted or de-identified when you delete your account, subject to the exceptions below.
  • Workout and fitness information: Retained while your account is active. Deleted upon account deletion.
  • Raw audio data:[CONFIRM: Specify, e.g., “Raw audio is not stored on our servers” or “Retained for up to X days and then deleted.”]
  • Transcripts and AI conversations: [CONFIRM: Specify retention period or confirm deleted with account.]
  • Usage and analytics data: [CONFIRM: Specify retention period.]
  • Purchase and subscription records: May be retained after account deletion where required for accounting, refund processing, fraud prevention, dispute resolution, or legal compliance. [CONFIRM: Specify retention period, e.g., seven years.]
  • Customer-support messages: [CONFIRM: Specify retention period.]
  • Crash and diagnostic data: [CONFIRM: Specify retention period, e.g., 90 days.]
  • Server and request logs: [CONFIRM: Specify retention period.]
  • Backup copies: [CONFIRM: Specify backup retention and deletion cycle, e.g., backups are retained for up to X days after deletion and then permanently purged.]

We may retain information in aggregated or de-identified form where it no longer reasonably identifies you, and we may retain specific categories of information where required by applicable accounting, tax, fraud-prevention, or legal-compliance obligations.

9. Account and Data Deletion

You may request deletion of your account through the Profile screen in the application. [CONFIRM: Verify the exact in-app location of account deletion — e.g., Profile → Settings → Delete Account.] You may also request deletion by emailing courtcoachsupport@gmail.com.

Account deletion generally removes or de-identifies account information, basketball profile, workout history, analytics, achievements, preferences, and other information associated with your account, subject to applicable retention requirements described in Section 8.

Deleting your account does not cancel an active Apple subscription.

You must separately cancel any active subscription through your Apple ID subscription settings before or after deleting your account. Apple may continue billing an active subscription until it is separately canceled.

Some transaction identifiers and subscription records may remain with Apple, RevenueCat, or Court Coach AI where necessary to process refunds, restorations, accounting entries, fraud prevention, legal compliance, or disputes.

To withdraw consent for specific optional processing — such as microphone access or push notifications — you may adjust the relevant permissions in your device settings at any time without deleting your account.

10. Your Privacy Rights

Depending on your location and applicable law, you may have the right to:

  • Request access to personal information we hold about you.
  • Request correction of inaccurate information.
  • Request deletion of certain personal information.
  • Request a portable copy of certain information.
  • Restrict or object to certain processing.
  • Withdraw consent where processing is based on consent.
  • Appeal certain decisions concerning a privacy request, where applicable.
  • Lodge a complaint with an applicable data-protection authority.

To submit a request, contact courtcoachsupport@gmail.com. We may need to verify your identity before completing a request. Rights may be subject to exceptions under applicable law, including where information must be retained for legal, transactional, security, or fraud-prevention purposes.

11. Data Security

We use reasonable administrative, technical, and organizational safeguards designed to protect personal information against unauthorized access, loss, misuse, or disclosure — including encrypted network connections, authenticated access controls, and restricted service permissions.

No method of data transmission or storage is completely secure. We cannot guarantee that unauthorized access, loss, misuse, or disclosure will never occur. If you have reason to believe your account has been compromised, contact us immediately.

12. International Data Transfers

Court Coach AI and its service providers may process personal information in the United States and other countries. Those countries may have privacy and data-protection laws that differ from those in your jurisdiction.

Where required by applicable law, we and our service providers use appropriate safeguards for international transfers of personal information.

13. Notifications and Communications

If you enable notifications, we may send workout reminders, training-plan updates, streak reminders, account notices, security messages, and subscription-related information.

You may disable push notifications through your device settings at any time. We may still send essential account, security, transaction, or legal communications where permitted.

14. Third-Party Links and Services

The Services may contain links to or integrations with third-party websites, videos, authentication providers, stores, or other services. Their privacy practices are governed by their own policies, and this Privacy Policy does not apply to information they independently collect or control.

15. Changes to This Policy

We may update this Privacy Policy as Court Coach AI, its features, or applicable legal requirements change. The “Last Updated” date at the top of this page will be revised when changes are made.

Where required by law or where changes materially affect how we process personal information, we may provide additional notice or request consent before those changes take effect.

16. Contact Us

Court Coach AI
Owner and Operator: Brandon Hornbeck
Email: courtcoachsupport@gmail.com
Website: courtcoachai.org

Change Log (July 31, 2026 revision)

  • Added per-category data table in Section 2 covering all 14 App Store Connect declared data types, with source, purpose, account linkage, storage, providers, and retention for each.
  • Added dedicated Section 6 — Voice and AI Processing — with sub-sections on session start/end, audio transmission, raw audio storage, transcripts, AI model training, what the AI provider receives, using the app without microphone, revoking permission, transcript deletion, and personal information spoken aloud.
  • Named OpenAI as the likely AI provider; marked as [CONFIRM] pending developer verification of provider identity, API type, retention settings, and training practices.
  • Expanded Section 7 to name each provider individually (Supabase, OpenAI, RevenueCat, Apple, Google, Expo, YouTube/video, crash-reporting SDK) with categories shared, purpose, processor/controller status, and country of processing.
  • Distinguished payment-card data (processed by Apple only) from purchase history metadata (received by Court Coach AI and RevenueCat) in Section 2(i).
  • Added Section 5 — Legal Bases for Processing.
  • Expanded Section 8 — Data Retention — to include per-category retention criteria and backup retention.
  • Added withdrawal of consent mechanism to Section 9.
  • Added cross-tracking statement and [CONFIRM] to Section 7 regarding App Store “Tracking” declaration consistency.
  • Updated Children's Privacy in Section 1 to include COPPA reference and a [CONFIRM] for age rating and age-gate verification.
  • Added Effective Date and Last Updated date.
  • Updated support email to courtcoachsupport@gmail.com throughout.

[CONFIRM] Items Requiring Developer Verification

  • App Store age rating and whether users under 13 are permitted or blocked.
  • Database and backend provider identity (Supabase or other).
  • AI provider identity (OpenAI or other) and which specific API is used (Realtime, Whisper, Chat Completions, etc.).
  • Whether raw audio is stored server-side or discarded after processing.
  • Whether transcripts are saved to the user's account or workout history.
  • OpenAI (or other AI provider) data-retention settings and whether data may be used for model training under the applicable API tier agreement.
  • Whether voice sessions are started with a button tap or a wake word, and when microphone capture ends.
  • Whether Expo push notifications are implemented and whether Expo receives device tokens.
  • Whether YouTube or another video provider is used for drill demonstrations.
  • Whether any crash-reporting SDK (e.g., Sentry) is installed.
  • Whether any analytics SDK is installed and whether usage data is linked to user accounts.
  • Whether any third-party SDK uses Court Coach AI data for cross-app tracking. If yes, update App Store Connect Tracking declaration.
  • Specific retention periods for audio, transcripts, usage data, support messages, crash data, server logs, and backups.
  • Exact in-app location for account deletion.
  • Whether conversation history is saved and linked to the user account.

Potential App Store Connect Declaration Issues

  • Verify that “Crash Data,” “Performance Data,” and “Other Diagnostic Data” are truly not linked to the user in the actual implementation, consistent with the current App Store Connect declaration.
  • If conversation history or AI transcripts are saved and linked to the user account, confirm that “Other User Content” is declared correctly in App Store Connect.
  • If any third-party SDK performs cross-app tracking, add a “Tracking” declaration in App Store Connect.

© 2026 Brandon Hornbeck