Privacy Policy

What we collect

Core app data is local-first. CourtsideView stores roster, match, stat, rotation, color, and app preference data on your device so you can score games without creating a visible account.

User-selected photos and files. CourtsideView uses the native photo picker when you choose team or opponent logos. It uses the native document/file picker when you import roster or scout files, including CSV, XLS, XLSX, and PDF workflows where available. These photos and files are selected by you. The app reads selected files to create roster or scouting data and does not upload the raw import file in the normal import flow. Selected logo images and imported roster/scout data may become part of shared content if you later publish a FanView link or Team Scout session that includes that information.

Optional FanView sharing. When you tap FANVIEW and publish a live view, CourtsideView sends a match snapshot to Supabase so family and fans can open a read-only web link. FanView publishing is user-initiated and optional.

Optional Team Scout sharing. When you create or share a Team Scout session, CourtsideView can sync that session through Supabase so coaches and contributors can review and combine observations.

Website updates. If you choose to receive CourtsideView updates on our website, we store the email address you submit and the date it was submitted so we can send occasional product updates. Joining the list is optional and separate from using the app.

What stays on your device

• Roster details you enter (player names, jersey numbers, positions).
• User-selected roster import files after they are parsed into app data.
• User-selected logo images unless included in a published/shared view.
• Match results: scores, sets, rotations, timeouts, and the events you log (kills, digs, blocks, errors, etc.).
• Solo Scout sessions and local Coach Hub data unless you use Team Scout sharing.
• App preferences: theme choice, team colors, dismissed coaching tips.

Core app data is stored locally on your device using app storage. You can wipe local app data at any time from Settings → Wipe All Data.

What FanView stores when you publish

If you publish FanView, CourtsideView stores the information needed to show the live scoreboard and match context on a public-but-unlisted web link. This can include:

• Team names, colors, format, set scores, match state, and whether the match is complete.
• Team logos if you added logos and publish a FanView display that uses them.
• Player names, jersey numbers, positions, tracked-player status, stats, rotation/court data, and live activity feed items.
• A generated share ID used in the FanView URL.
• An anonymous Supabase user/session identifier used to publish and update the FanView row.
• Optional live-video status metadata if the broadcaster starts FanView live video.

FanView links are stable for the match share ID and are intended for people you share them with. They are not indexed by CourtsideView, but anyone with the link may be able to view the live match while it is available.

What Team Scout stores when you share

If you create or share a Team Scout session, CourtsideView may store the information needed for team scouting, contributor sync, shared tracking, and report review. This can include:

• Session ID, scout mode, opponent or team name, match context, timestamps, and ended-at state.
• Opponent player names, jersey numbers, positions, and player IDs.
• Scouting observations, notes, zones, directions, results, set targets, and block-related fields.
• Contributor IDs, contributor labels, selected player IDs, and coach/contributor status.

Team Scout links are hosted on CourtsideView-owned web URLs, such as courtsideviewapp.com/scout/..., and are intended for the coaches and contributors you share them with. Anyone with the shared link may be able to view or contribute while the session remains available.

What we don't do

• We don't run analytics or telemetry on your usage.
• We don't display ads or share data with advertisers.
• We don't sell, rent, or trade your information to third parties.
• We don't make website signup email addresses publicly visible.
• We don't access native contacts or location in the current mobile app.
• We don't use the native app camera or microphone for capture in the current mobile app.
• We don't record or store FanView live video.

Permissions you may see

The iOS and Android app may ask for photo library or media-picker access when you choose a team or opponent logo. The app may also open the system document/file picker when you import rosters or opponent scout files. These flows are initiated by you and are used only for the selected photo or file.

The FanView broadcaster web page may ask your browser for camera and microphone access when you choose to start live video. Camera and microphone access is used only to send the live stream while the broadcaster keeps it running. CourtsideView does not record or store the video or audio. If microphone access is unavailable or declined, the web broadcaster may fall back to video-only where the browser allows it.

Retention and deletion

• Local app data: remove it in the app with Settings → Wipe All Data.
• FanView data: FanView links close 15 minutes after the match is marked complete. Some FanView rows or operational records may remain in Supabase unless removed by request.
• Team Scout data: shared Team Scout sessions and contributor records may remain in Supabase unless removed by request.
• Website signup data: we keep your email until you ask us to remove it or we no longer need it for CourtsideView update communications.

To request deletion of FanView data, Team Scout data, anonymous session data associated with a published share, or website signup email data, email teagan@courtsideviewapp.com. Include the FanView link, Team Scout link/session, or the email address you used so we can locate the data.

Service providers

CourtsideView uses service providers to operate the app and website, including Supabase for optional FanView publishing, Team Scout sharing/sync, anonymous session support, realtime updates, and website signup forms; Expo for app updates; Vercel for website hosting; and Cloudflare for the optional live-video relay. These providers process data only to provide CourtsideView functionality.

Security

We use HTTPS, app-store platform controls, and database access rules to protect CourtsideView data. No system is perfect, so avoid sharing FanView links with people who should not see the match.

Updates over the air

To deliver bug fixes quickly, CourtsideView uses Expo's update service to download new application bundles. The update service receives version, build, runtime, and device/update identifiers needed to deliver the right bundle.

Children's privacy

CourtsideView is designed for use by adult parents and youth coaches. We do not knowingly collect information directly from children. Adults may enter youth athlete names, jersey numbers, positions, stats, logos, roster imports, scouting notes, and opponent information. Users should only enter information they are authorized to share. That information stays local unless the adult user chooses to publish FanView or Team Scout sharing. Parents or guardians can wipe local data in the app or contact us to request deletion of shared FanView or Team Scout data.

Changes to this policy

We will update this page if our practices change. The "Last updated" date at the top will reflect the most recent revision. Material changes will be summarized in the app's release notes.

Contact

Questions, feedback, or a request to delete your data? Email teagan@courtsideviewapp.com.