Courtside HD is developed by Dalton Schwentker. This policy describes the current pre-release app and this website. Contact support@courtsidehd.com with privacy questions or requests. The app is not yet publicly available on the App Store.
Information on your device
Courtside stores teams, player names, selected headshots, session details, chosen covers, highlight flags, and settings locally. Selected photos are processed locally. Local recordings, imported footage, and highlight clips are kept inside the app. We do not operate a developer-hosted server that receives your roster, session records, or local footage.
Saved sessions may retain their own lineup snapshots and photo references independently of changes to a team roster. Local information remains until you remove it using available app controls or delete the app. Device backups and exported copies are controlled by your device settings and chosen destination.
YouTube and Google authorization
Courtside uses YouTube API Services. Google handles sign-in; Courtside does not collect your Google password. Your authorization permits the app to identify the selected channel and create, configure, and manage broadcasts on your behalf.
Courtside sends the broadcast title, description, visibility, and settings you choose to Google. When streaming starts, composed camera video and optional microphone audio are sent to YouTube. Record-only capture does not create or transmit a YouTube broadcast.
Selected channel information, broadcast identifiers, event references, and last verified visibility can be stored locally with your sessions. Google Sign-In manages authorization credentials on your device. Manual stream keys and managed ingest credentials use the iPhone Keychain.
Google and YouTube process information under the Google Privacy Policy and YouTube Terms of Service. YouTube playback opens externally and follows the broadcast’s current access controls.
Sharing and broadcast visibility
New managed broadcasts default to Private. Selecting Public requires a separate confirmation before Start. With a manual stream key, visibility is determined by the event configured in YouTube Studio.
Exporting to Photos or using the system Share action creates a copy at the destination you select. That destination handles information under its own practices. Deleting footage inside Courtside does not remove exported copies or videos on YouTube. Highlight clips do not overwrite your source footage.
Connection checks and technical details
An upload-speed check sends generated test bytes to Cloudflare, up to 20 MB per test. It does not send your camera footage or saved videos. Providers may process network information such as your IP address to deliver these services. See Cloudflare’s Privacy Policy.
Some pre-release versions may keep technical recording error codes, requested recording quality, available storage, and thermal state locally with a recording. These details are not automatically uploaded to us. They exclude raw error descriptions, file paths, and stream keys. If you choose to share a diagnostic screenshot with support, it becomes part of that support conversation.
Website and support messages
This website uses Vercel hosting. Vercel may process request information such as IP addresses, requested URLs, and browser information for hosting, security, and delivery under the Vercel Privacy Policy. We have not added advertising, analytics scripts, tracking cookies, embedded video players, or contact forms to this website.
If you email support, we receive your email address, message, and any attachments you choose to send. ImprovMX forwards support mail to the developer’s Gmail inbox. See ImprovMX’s Privacy Policy and the Google Privacy Policy linked above. Support correspondence may remain in that inbox until resolved or deleted. Please do not include passwords, stream keys, or authorization codes. Contact us to request deletion of support correspondence.
Permissions, revocation, and deletion
Manage camera, microphone, and photo access through iPhone Settings. You can disconnect YouTube in the app or revoke access through Google account permissions. Disconnect clears the connected-channel and managed-ingest cache; remove a manual stream key separately.
In the current pre-release implementation, disconnecting does not remove all API-derived metadata in local session history. That history may remain until the associated local session data is removed or the app is deleted. There is not yet an automatic age-based refresh/deletion schedule for all stored YouTube metadata. This is being addressed before public release; this policy does not claim it is already implemented.
Deleting the app removes its local files and session storage. iOS Keychain values may survive uninstalling, so clear credentials and revoke Google access first. To delete a YouTube broadcast, use YouTube’s own controls. For help removing locally stored information or other privacy requests, contact support@courtsidehd.com. We do not have remote access to your phone’s app storage.
Policy updates and contact
When practices change, we will update this page and its version/date. The public-release app and policy must agree before launch. Privacy questions, complaints, and requests can be sent to support@courtsidehd.com.
Developer: Dalton Schwentker
Website: courtsidehd.com