Pilot privacy notice
Updated October 19, 2026
Courtside is an independent student-led campus sports pilot awaiting campus approval. This notice describes the pilot as implemented; it is not a statement of school endorsement or a legal compliance certification.
Information the pilot uses
Courtside stores your account ID, verified email, display name, campus and role; posts and replies, including your posting preference; saved events and team interest; check-in names, attendance reviews and reward records; reports, blocks, staff activity records, and support, event correction or deletion requests. Supabase handles authentication and password credentials. Never send passwords in posts or support requests.
If you enable notifications, Courtside stores your email preference and device push subscription details, including delivery endpoint and keys. Delivery queues and results support reminders and updates. Text messaging is not enabled for this pilot; do not submit a phone number for texts.
How information is used
The pilot uses this information to provide campus access, discussions, events, saved plans, attendance and proposed rewards; deliver requested notifications; handle support requests; and investigate abuse. Hosting and service providers may process network and technical logs to operate their services.
Who can see it
Other signed-in campus members can see visible posts and replies and their displayed names, team listings, and team interest counts. They cannot see other students' private saved-plan or attendance lists through the student interface.
Authorized owners, admins and moderators can review campus attendance and discussion reports. Event staff can manage events according to their role. Anonymous posting hides your display name from students on that post or reply; it does not hide your identity from the system or moderators reviewing reports.
Private app support and account deletion requests, including your account name and email, are available in the support inbox only to Cooper and David Langston while they hold their authorized roles. Authorized infrastructure administrators may also access stored data through the hosting/database systems.
Service providers and external links
Cloudflare hosts the site. Supabase provides authentication, database and server functions. Resend delivers account and event emails. Your browser/device push provider processes push delivery if you enable alerts. The site loads fonts from Google Fonts and a Supabase browser library from jsDelivr. These services receive the technical information needed to respond to their requests. IMLeagues and calendar links open separate services with their own policies.
The pilot starts with Cooper and David as staff; they can authorize additional staff using verified campus emails. All staff access requires authenticator verification. A restricted staff activity log records changes, the acting account, timestamps and changed field names; it does not store passwords, authenticator setup keys or verification codes.
Your choices
In Settings you can change your display name or default posting preference, turn event emails on or off, and enable or disable alerts on each device. Changing your name or posting preference does not rewrite old posts. Your browser and phone settings also control notification permission and lock-screen previews. Push and email reminders can show event titles, locations and times outside the app.
Calendar downloads are separate from email and device subscriptions; they do not automatically update. A saved plan is not official event registration.
Deletion requests and retention
Use Settings → Request account deletion to send a private request to the pilot support team. Requests are reviewed manually; submitting one does not immediately delete your account or stop alerts. The team will follow up using your verified account email about the request, the records involved and any records that must be retained. You may also use App support for privacy questions or correction requests. If you cannot access your account, contact the pilot organizer through the person who introduced you to the pilot.
The pilot has not yet adopted a fixed retention schedule or automated account deletion. Records, including archived events, attendance, reports, support requests and notification delivery records, may remain stored until they are reviewed and removed. Infrastructure logs and backups have provider-specific retention. A deletion review must address those limits rather than promise immediate removal from every backup. Retention and school responsibilities need to be agreed before a broader launch.
Reports and safety
Use Report on a post or Report reply in a conversation to send concerns to campus moderators. App support and discussion reports are not monitored continuously and are not emergency services. For immediate danger, contact emergency services or campus safety directly. Avoid posting sensitive health, financial, disciplinary or other private information.
Changes to the pilot
Material changes to data handling should be reflected in this notice and communicated before they take effect. Questions can be submitted privately through App support.