QuickSide

Privacy Policy

This Privacy Policy describes how Quickside, LLC. (“Quickside,” “we,” “us,” or “our”) collects, uses, discloses, and protects personal information when you access or use the QuickSide websites, applications (including our mobile companion apps), and related services (collectively, the “Service”). By using the Service, you agree to this Privacy Policy.

If you have questions about this policy or our privacy practices, contact us at [email protected]. For general product or account help, contact [email protected].

1. Scope

This policy applies to personal information we process in connection with the Service. It does not apply to third-party websites, applications, or services that we do not control, even if they are linked from the Service.

Organizations (such as sports leagues, clubs, schools, or associations) and their authorized administrators may submit information about their members, participants, staff, and families to operate on the Service. Where those organizations act as independent controllers of personal information, their own notices and practices may also apply.

2. Information we collect

We collect information that you and your organization provide, that is generated through your use of the Service, and that we receive from service providers and integrations as described below.

2.1 Account and profile information

  • Name, email address, and authentication data: for email-and-password accounts we store a password hash (we do not store your password in plain text). If you use Sign in with Google, Sign in with Apple, or Facebook Login, authentication is handled in part by those providers; we receive limited information such as a stable provider identifier, and where available name, email address, and whether the provider treats the email as verified. We store provider identifiers and linkage to your QuickSide account so you can sign in again; we do not receive or store your password for those third-party accounts. If you use Apple’s Hide My Email, the address we see may be a private relay address that forwards to your personal inbox.
  • Optional multi-factor authentication data: if you enable TOTP authenticators or passkeys / WebAuthn, we store the credentials and related security metadata needed to verify those factors (we do not receive the biometric image from your device when you use a platform passkey or biometric unlock).
  • Display name, role, organization or league affiliations, and preferences you set in your account.
  • Communications you send to us (for example, support or helpdesk requests).

2.2 Organization, league, and team data

Organizations and their administrators may provide roster, scheduling, division, facility, volunteer, tournament, and related operational data. This may include:

  • Participant or player information (such as names, jersey numbers, positions, date of birth or age-related fields used for program eligibility and safety features, attendance, evaluations, tryout or placement notes, coach or family reports, and similar program data).
  • Contact information for guardians, coaches, staff, or volunteers when supplied to the Service.
  • Content you upload or post in league, team, or tournament areas (for example, posts, comments, attachments, announcements, and moderation records).

Date of birth and age. Where date of birth or age is provided, we may use it to enforce product safety rules (for example, messaging limits for users under 13), to support program eligibility, and as instructed by the organization. Platform safety features do not replace an organization’s duty to obtain parental or guardian consent where required by law.

2.3 Medical and emergency information

Where an organization or guardian chooses to use medical or emergency features, we may process:

  • Medical and health-related information you or your organization enter (for example, conditions, allergies, medications, notes, or related fields used for participant safety).
  • Emergency contact names and contact details.
  • Date of birth associated with a medical or participant record when provided.

This information is treated as sensitive. We encrypt medical and related fields at rest where implemented, and access is limited according to roles and permissions configured in the Service (for example, staff or co-guardians who need it for program operations). Quickside is not a covered entity or business associate under HIPAA and does not provide medical advice. Organizations and guardians are responsible for collecting only what they are legally permitted to collect and for obtaining any required consents.

2.4 Messaging, notifications, and communications

When you use team messaging, inbox or direct messages, announcements, or notification features, we process:

  • Message content and metadata (for example, thread membership, timestamps, and delivery state). Where the Service provides end-to-end encryption for certain team messages, message bodies are encrypted so that Quickside cannot read plaintext content on our servers for those messages; we still process metadata needed to deliver and secure the feature.
  • Push notification tokens for mobile devices (for example, tokens used with Apple Push Notification service or Firebase Cloud Messaging) so we can deliver alerts you or your organization enable.
  • Transactional email addresses and any content we include when we send notices through our email provider (such as Resend) — for example, invites, magic links, billing receipts, and security alerts. Where possible we send notify-only messages (a short notice plus a link) so message bodies and similar content stay in the Service rather than in email.

Under-13 and guardian privacy settings may restrict direct messaging or related visibility; those controls are described in the product and do not replace legal consent obligations.

2.5 Documents, waivers, and electronic signatures

If your organization uses the Document Center or similar features, we may process:

  • Uploaded documents (such as waivers, eligibility forms, or program PDFs).
  • Signature and acknowledgment records, including typed-name or other electronic signature evidence, timestamps, and related audit metadata.

Organizations control which documents they require and how long they retain them for their programs. Quickside stores and delivers these materials as instructed by account settings and permissions; organizations remain responsible for the legal sufficiency of any waiver or consent form.

2.6 Usage, device, log, and analytics data

We automatically collect certain technical information when you use the Service, which may include:

  • IP address, device or browser type, operating system, general location derived from IP, timestamps, and referring URLs.
  • Diagnostic and security logs, crash data, and performance metrics needed to operate and protect the Service.
  • On our marketing website and web app, we may use Google Analytics (GA4) when configured, to understand aggregate traffic and improve the Service. Analytics cookies and similar identifiers are used for this purpose; we do not use Google Analytics to sell your personal information for money. You can control many cookies through your browser settings; some features may not work if you disable certain cookies.

We may use cookies, local storage, and similar technologies to keep you signed in, remember preferences, prevent fraud (including Cloudflare Turnstile bot checks on certain forms), and understand how the Service is used.

2.7 Mobile companion apps

When you use our iOS or Android companion apps, we may also process:

  • Camera and microphone access when you capture photos, media, or live video/audio for streaming or uploads you initiate.
  • Push notification tokens as described in Section 2.4.
  • Optional biometric app lock settings; biometric templates stay on your device and are not uploaded to Quickside.
  • Limited crash or diagnostic information that may be used to improve stability or, if you choose, to open a support ticket.

2.8 Payments, billing, merchandise, and in-app purchases

When you purchase subscriptions, licenses, registrations, facility slot marketplace purchases, merchandise, stream entitlements, or other paid features, our payment processors collect and process payment information:

  • Stripe, including Stripe Connect where organizations, facility managers, or sellers receive payments for certain programs, events, or marketplace listings. We generally receive limited payment-related information (for example, confirmation of payment, partial card or account identifiers, billing address elements, and transaction metadata) rather than your full payment card number.
  • App Store / Google Play billing when you buy certain entitlements (such as stream-related in-app purchases). We receive limited receipt and entitlement data from Apple or Google; card numbers for those purchases are handled by the store, not by Quickside.
  • Merchandise / fulfillment partners (such as Printful or a similar provider) may receive shipping name, address, and order details needed to produce and ship apparel or goods you order.
  • QuickSide Exchange / POS (in-person register sales): we process sale amounts, tax, tender type, register and shift identifiers, and payment-rail data via Stripe or Clover as applicable. Guest registration names and emails, event titles and notes, order labels, and similar free-text fields are intended to be end-to-end encrypted under Path 2 so Quickside cannot read that content on our servers once cut over; org owners and entitled staff decrypt on their devices. Until a given field is cut over, treat it as encrypted at rest where implemented, not as zero-knowledge.

2.9 Facility slot marketplace

If you browse, list, buy, trade, or inquire about facility time through the facility slot marketplace, we may collect:

  • Search and lead information (for example, email, optional phone, sport, and preferred days) when you ask to be notified about nearby availability.
  • Listing and transaction details (sport, venue, schedule window, price, listing mode, order status, and transfer history).
  • Facility and venue information (facility name, address elements, and approximate location) associated with listings.
  • Buyer–seller contact exchanged through marketplace inquiry threads when you choose to message another user about a slot.

We encrypt contact information collected for marketplace leads and inquiries at rest. We use this information to operate discovery, reservations, payments, transfers of booked time, reminders, and fraud prevention. We do not sell personal information from marketplace leads.

2.10 Live streaming connections and content

If you connect a streaming destination (such as YouTube or Facebook) to broadcast through QuickSide, we collect and process the information needed to operate that broadcast:

  • Authorization credentials: OAuth access and refresh tokens (and, for Facebook, Page access tokens) issued by the provider when you connect your account. These tokens are encrypted at rest and are used only to create and manage broadcasts you initiate.
  • Connected account identifiers: your YouTube channel id and title, or your Facebook user and Page ids and names, so we can show you which destination you are broadcasting to.
  • Broadcast and stream configuration: the broadcast title and description, privacy setting (for example, unlisted or public), and the provider's broadcast/stream identifiers. The YouTube stream key (RTMP ingest credential) is retrieved live from the provider when needed and is not stored at rest by QuickSide.
  • Real-time stream content and metadata: when you broadcast, we process the real-time audio and video feed and related stream metadata (such as scoreboard state, game clock, and event details) needed to produce and publish the broadcast.

See Section 5 ("Live streaming and third-party broadcast platforms") for how this data is shared with YouTube and Facebook and how you can disconnect or revoke access.

2.11 Third-party roster and calendar imports

Organizations may connect or import data from third-party systems (for example, DaySmart, TeamSnap, or similar roster/calendar tools). When an organization initiates an import or sync, we may receive player, guardian, contact, and schedule information from that source as supplied by the organization. We process that information to populate the Service as instructed by the organization. The organization is responsible for ensuring it has the legal right to import and use that data.

2.12 Public registration and public pages

Organizations may publish public registration forms, vanity organization or team pages, tournament hubs, or similar pages that are accessible without signing in. Those pages may collect information you submit (for example, registrant name, contact details, and program selections) and may display limited information the organization chooses to make public (for example, schedules, team names, or publicly enabled roster elements). We may use bot-protection tools such as Cloudflare Turnstile on public forms. Organizations control what appears on public pages and are responsible for that publication.

3. How we use information

We use personal information to:

  • Provide, operate, maintain, secure, and improve the Service.
  • Authenticate users, enforce permissions and age-related safety rules, and prevent fraud or abuse.
  • Communicate with you about the Service, including transactional notices, support responses, push and email notifications you or your organization enable, and (where permitted) product updates.
  • Process payments, fulfill orders (including merchandise), complete facility slot transfers, and comply with tax, accounting, or regulatory obligations.
  • Host documents and signature records, deliver messaging, and support live streaming as you or your organization configure.
  • Analyze usage in aggregate or de-identified form (including via Google Analytics when configured) to improve features and reliability.
  • Comply with law, respond to lawful requests, and protect our rights and the rights of others.

We do not sell your personal information for money. We may share personal information with service providers, integrations, and as described in Section 4.

4. How we share information

We may disclose personal information to:

  • Service providers who assist us with hosting, infrastructure, email delivery, analytics, security, customer support, push delivery, object storage, merchandise fulfillment, and similar functions, subject to appropriate confidentiality and security obligations.
  • Payment processors (such as Stripe) to process payments, refunds, and fraud prevention, and to facilitate connected accounts or similar arrangements where an organization, facility manager, or seller receives funds for registrations, events, or marketplace listings and the platform may retain fees as configured for that transaction. For in-app purchases, Apple or Google process payment according to their terms.
  • Fulfillment partners (such as Printful or a similar provider) to produce and ship merchandise orders.
  • Buyers and sellers involved in a facility slot purchase or accepted trade, to the extent needed to fulfill the booking transfer and provide limited contact context for the transaction.
  • Organizations and their administrators you are affiliated with, consistent with roles and permissions in the Service (for example, league directors may access roster, schedule, document, or medical data their roles allow for their programs).
  • Other users where you or your organization choose to make information visible (for example, team feeds, tournament pages, shared schedules, or public vanity pages).
  • Third-party platforms you connect (for example, YouTube or Facebook for broadcasting, or roster/calendar tools an organization connects for import).
  • Professional advisers (such as lawyers or accountants) when necessary.
  • Law enforcement or other third parties when we believe disclosure is required by law, regulation, legal process, or governmental request, or to protect the safety, rights, or property of Quickside, our users, or the public.

We may also share information in connection with a merger, acquisition, financing, or sale of assets, subject to appropriate confidentiality and continuity commitments.

5. Live streaming and third-party broadcast platforms

QuickSide lets organizations and authorized users broadcast events to third-party platforms. When you connect a destination, we share the broadcast audio/video and the configuration described in Section 2.10 with that platform so the stream can be published. Your use of those platforms is also governed by their own terms and privacy policies.

5.1 YouTube API Services

QuickSide uses YouTube API Services to let you stream to your YouTube channel. By connecting YouTube, you also agree to the YouTube Terms of Service, and your data is handled in accordance with the Google Privacy Policy.

  • Permission requested: when you connect, we request the YouTube scope that allows QuickSide to create and manage live broadcasts on your channel on your behalf.
  • Data we handle: OAuth access and refresh tokens (encrypted at rest), your channel id and title, and the broadcast/stream configuration (title, description, privacy setting, and the provider's broadcast/stream identifiers). We use this solely to start, manage, and end the broadcasts you initiate.
  • Revoking access: you can disconnect YouTube at any time from within QuickSide, which deletes the stored tokens and connection from our systems. You can also review and revoke QuickSide's access directly through the Google security settings page at https://security.google.com/settings/security/permissions.

5.2 Facebook Live API

QuickSide integrates with the Facebook Live API so you can broadcast to Facebook destinations (Pages) you manage.

  • Permissions requested: we request authentication and publishing permissions (\`pages_show_list\`, \`pages_read_engagement\`, \`pages_manage_posts\`, and \`publish_video\`) solely to enumerate the Pages you manage and to broadcast real-time audio and video to the Facebook destination you choose. We do not use these permissions to post other content on your behalf.
  • Data we handle: an encrypted long-lived user token and per-Page access tokens (encrypted at rest), your Facebook user and Page ids and names, and the broadcast configuration for the live video you create.
  • Revoking access and deleting data: you can disconnect Facebook at any time from within QuickSide, which deletes the stored tokens and connection from our systems. You can also remove QuickSide from your Facebook Settings → Business Integrations. For full instructions on deleting the data associated with your QuickSide–Facebook connection, see our [Data Deletion Instructions](/app-support/help/data-deletion-instructions).

5.3 Live stream content, overlays, and metadata

When you broadcast through QuickSide, we capture and process real-time audio and video feeds and stream metadata to produce and publish the stream. Data overlays may be rendered into or alongside the stream, including team names, scores and game clock, player and roster information, and live evaluation scoring. Broadcast titles and descriptions sent to the platform may include event details such as team, opponent, location, date, time, and event name. Once published to a third-party platform, the broadcast is also subject to that platform's audience, retention, and visibility settings.

6. Children and schools

The Service is often used in connection with youth sports and similar programs. Organizations that submit information about minors are responsible for obtaining any legally required parental or guardian consent and for the accuracy and lawfulness of that information. Quickside processes such information on behalf of those organizations and to provide the Service as instructed by account settings and permissions.

Product safety features. We may use date of birth or age-related data to restrict certain features for users under 13 (for example, direct messaging) and to support guardian privacy controls. Those features are safety tools; they do not themselves constitute verifiable parental consent under COPPA or replace the organization’s consent obligations.

Live broadcasts involving minors. Before a league operator, organization, or other authorized user initiates a public broadcast that may capture, name, or otherwise identify youth athletes (minors) — including through live audio/video or data overlays such as rosters or live evaluation scoring — that operator is responsible for obtaining any verifiable parental or guardian consent required by the Children's Online Privacy Protection Act (COPPA) and other applicable laws. Quickside provides the streaming tools and acts on the operator's instructions; it does not independently obtain this consent on the operator's behalf. Operators should not broadcast minors where the required consent has not been obtained.

If you believe a child has provided us personal information directly in a way that violates applicable law, contact us at [email protected] and we will take appropriate steps.

7. Retention

We retain personal information for as long as necessary to provide the Service, fulfill the purposes described in this policy, comply with legal obligations, resolve disputes, and enforce our agreements. Retention periods may vary depending on the type of information and the context in which it was collected (for example, billing records, document/signature records retained by an organization, or backups that may persist for a limited period after deletion).

8. Security

We implement technical and organizational measures designed to protect personal information against unauthorized access, loss, or alteration. Where implemented, we encrypt sensitive fields at rest (including account contact and player personal information, medical and emergency fields, OAuth streaming tokens, marketplace lead contact information, and certain user-generated content) and protect data in transit with industry-standard transport security. Access is limited by authentication, roles, and permissions. No method of transmission over the Internet or electronic storage is completely secure; we cannot guarantee absolute security.

9. Your choices and rights

Depending on your location, you may have rights regarding your personal information, which can include:

  • Access to certain personal information we hold about you.
  • Correction of inaccurate or incomplete information.
  • Deletion of certain information, subject to legal exceptions.
  • Objection or restriction of certain processing.
  • Portability of certain information you provided, where technically feasible.

How to exercise rights in the product. Signed-in users can open Profile → Privacy (or the mobile Privacy & your data screen) to export a copy of personal data we make available and to delete their account, subject to verification. Step-by-step instructions, including disconnecting YouTube or Facebook, are in our [Data Deletion Instructions](/app-support/help/data-deletion-instructions). You may also contact support or our helpdesk for privacy-related requests, or email [email protected].

California residents: California law may provide you with specific rights regarding personal information, including rights to know, delete, correct, and opt out of certain “sales” or “sharing” of personal information (including targeted advertising) as those terms are defined under California law. We do not “sell” personal information as traditionally understood. If you wish to exercise California privacy rights, email [email protected] with your request and enough information for us to verify your identity, or use the in-app export/delete tools where available.

Other U.S. states: Several states have enacted consumer privacy laws that may grant similar rights. If you are a resident of such a state and wish to exercise available rights, contact [email protected] or use the in-app tools described above. We will not discriminate against you for exercising privacy rights where prohibited by law.

We may need to verify your identity before fulfilling certain requests. We aim to respond to verified deletion and similar requests within 30 days, unless a longer period is permitted by law.

10. International users

If you access the Service from outside the United States, you understand that your information may be transferred to, stored in, and processed in the United States and other countries where we or our service providers operate, which may have different data protection rules than your country.

11. Changes to this policy

We may update this Privacy Policy from time to time. We will post the updated version on the Service and update the “Last updated” date. If changes are material, we will provide additional notice as appropriate.

12. Contact