Privacy

Privacy Policy

This policy explains, at a working-product level, how Shori handles account, team, viewer, sponsor, and content data across the current platform.

Last updated June 6, 2026

These pages are a working policy and terms set for the current Shori pilot. They are meant to give users a clear baseline for how the service works today and should be reviewed again before a broader public launch, especially if Shori expands payments, sponsorship transactions, or multi-user team operations.

What this policy covers

This Privacy Policy explains how Shori collects, uses, stores, and shares information when people use the Shori website, create a team account, manage game coverage, view public team or game pages, join a viewer list, or interact with sponsorship surfaces.

Shori is currently an early-stage product and operating pilot. The services described here may change as the platform expands, but this policy is intended to describe the current baseline in plain language.

Information Shori collects

  • Account information, such as name, email address, login credentials, and role-based access details.
  • Team information, such as team name, sport, city, league, logos, branding choices, public descriptions, schedules, and broadcast details.
  • Viewer and contact information that team operators choose to store, such as names, email addresses, and phone numbers.
  • Sponsor and sponsorship information, such as sponsor names, website links, inquiry details, offer details, and sponsorship workflow status.
  • Content and media information, such as uploaded logos, replay files, clip links, and other assets submitted through the product.
  • Technical and usage information, such as pages visited, browser/device information, IP-based security and anti-abuse logs, and product events needed to operate and improve the service.
  • Third-party integration data, such as connected YouTube channel metadata and tokens needed to create or manage streaming workflows.

How Shori uses information

  • To create, host, and display public team pages, game pages, replay pages, clips, and related coverage surfaces.
  • To operate team dashboards, user accounts, sponsorship workflows, and viewer list tools.
  • To support YouTube and streaming integrations, including connected channel workflows.
  • To communicate with users about account access, product updates, support, security, and operational issues.
  • To maintain security, detect abuse, troubleshoot issues, and improve product performance and reliability.
  • To support sponsorship and community-visibility workflows, including sponsor pages, sponsor inquiries, and related reporting within the product.

How public information works

Some information in Shori is intended to be public by design. If a team chooses to publish a public team page, game page, replay, clip, or sponsor surface, the related public-facing content may be visible to viewers, supporters, sponsors, and search engines.

Team operators are responsible for reviewing public-facing content before publishing it and for making sure they have the right to publish the names, logos, descriptions, schedules, media, and sponsor materials they submit.

Third-party services

Shori relies on third-party services to operate parts of the product. These may include hosting, analytics, media storage, video/streaming services, and account or communications infrastructure.

If a team connects a YouTube channel or uses Shori with YouTube streaming workflows, Google and YouTube will also process information according to their own terms and privacy practices.

How information is shared

  • With the public, when a team chooses to publish public pages, clips, replays, or sponsor surfaces.
  • With service providers and infrastructure partners that help run the product.
  • With integration partners such as YouTube when a user authorizes those connections.
  • When required by law, legal process, or to protect the rights, safety, or security of Shori, its users, or the public.
  • As part of a business transition if the product, company, or related assets are reorganized, financed, or transferred.

Data retention

Shori keeps information for as long as it is reasonably needed to operate the product, maintain records, support active accounts, preserve published pages, comply with legal obligations, resolve disputes, and protect the platform.

Different information may be kept for different periods depending on whether it is tied to published team content, account access, sponsor workflows, support history, or system security.

Your choices

  • Team operators can update or remove team details, sponsor details, viewer list entries, and related content through the product where those controls exist.
  • Users can choose not to connect third-party services such as YouTube, although some streaming features may then be limited.
  • Users can request account or data help through the contact method made available by the operator of the service.

Security

Shori uses reasonable administrative, technical, and operational measures intended to protect account information, tokens, and stored content. No method of storage, transmission, or internet-connected service can be guaranteed to be perfectly secure.

Users are responsible for protecting their own devices, account credentials, and any third-party services they connect through the platform.

Children and team participants

Shori may be used to publish coverage involving school-age and youth athletes. Team operators are responsible for making sure they have the appropriate authority, permissions, and internal policies in place before publishing names, photos, video, schedules, or related content involving minors.

Shori is intended for team operators, schools, organizations, clubs, and other responsible adults managing team coverage rather than for unsupervised direct use by children.

Changes to this policy

Shori may update this Privacy Policy from time to time as the product evolves. When practical, material changes will be reflected by updating the date on this page and by publishing the revised version here.

Related pages