Byga API Terms of Service

Thank you for using Byga, Inc. ("Byga") APIs, related software, and development services (collectively, the "APIs"). By accessing or using the APIs, you agree to these API Terms of Service ("Terms"), including the accompanying documentation, policies, and guidelines.

1. Eligibility and registration

a. Acceptance of Terms

You may not use the APIs if:

  • You are not legally permitted to enter a binding agreement; or
  • You are barred from accessing the APIs under applicable laws.

b. Club-sponsored integrations only

The APIs are provided for integrations that a club or organization using the Byga platform ("Client") owns and manages. They are not provided for personal or individual projects. Byga may decline or revoke access for any integration that is not sponsored by a Client, or that a Client does not accept responsibility for.

c. Use on behalf of an entity

If you use the APIs on behalf of an entity, you represent that you are authorized to bind that entity. All references to "you" refer to that entity.

d. Registration

You may be required to provide accurate and up-to-date information. You must promptly update any changes.

2. Use of the APIs

a. Authorized users

You are responsible for your authorized users' compliance with these Terms and applicable law.

b. Legal compliance

You will comply with all applicable laws and third-party rights.

c. Access and credentials

Access must occur only via documented methods. Credentials must be kept confidential.

d. Supported and experimental capabilities

Byga publishes which API capabilities are supported and which are experimental. Supported capabilities carry the documentation, change notice, and deprecation commitments in section 14. Experimental capabilities are offered for evaluation, may change or be withdrawn without the notice period in section 14, and should not be relied on in production. Where the published documentation does not state which a capability is, treat it as experimental.

e. Usage limits, pricing, and future charges

Byga may impose usage limits, including limits on request volume. The APIs are not charged for today. Access is not unlimited, and Byga may introduce fees for API access in the future. Byga will give notice before any charge applies to an existing integration.

f. Client authorization, scope of access, and read-only default

Access to data through the APIs is controlled by the applicable Client. You may access and process data made available through the APIs ("Client Data") only as:

  • authorized by the applicable Client; and
  • made available through the Byga platform.

The Client determines the permitted scope of the integration, including which teams, which other Client Data, and which API endpoints are enabled. You may not access, use, or process any data outside of the authorization mechanisms provided by Byga.

The APIs are read-only by default. Any capability that creates, modifies, or deletes data in the Byga platform is enabled only where Byga has granted it expressly and in writing for your integration, and only with the authorization of the applicable Client. A request for write access is not granted by implication, by the absence of a refusal, or by the presence of an endpoint in the documentation.

3. API Clients

a. Monitoring

Byga may monitor API use to ensure compliance and service quality.

b. Security

You must implement commercially reasonable administrative, technical, and physical safeguards to protect Client Data, including multi-factor authentication on any account or system used to access or store Client Data.

c. Ownership

Byga retains all rights, title, and interest in and to the APIs and all associated content. You retain ownership of your applications that use the APIs ("API Clients"). All Client Data remains subject to the applicable Byga Client Terms of Service, available at [INSERT LINK], and nothing in these Terms grants you ownership rights in Client Data.

d. Privacy obligations

You must:

  • comply with applicable privacy and data protection laws;
  • maintain a privacy policy that accurately describes your data practices; and
  • process Client Data solely for the purposes authorized by the applicable Client and permitted by these Terms.

You may not use Client Data for advertising, marketing, profiling, resale, or any purpose unrelated to the authorized integration.

e. Sensitive personal information

Client Data may include personal information about minors, including dates of birth. You will process that information only for the purposes authorized by the applicable Client, will not disclose it to any third party not authorized by the Client, and will apply the safeguards required by section 3(b) to every system on which it is stored.

f. User consent (limited cases)

In limited cases, Byga may enable functionality that allows individual users (such as athletes or their parents or guardians) to authorize the sharing of certain data directly with your application.

In such cases:

  • you may access such data only where such access is enabled through the Byga platform and authorized by the applicable Client and, where applicable, the relevant user;
  • you must obtain and maintain any required consents in accordance with applicable law; and
  • your use of such data must remain within the scope of the applicable authorization.

You may not use user consent or any other mechanism to expand access beyond what is made available through the Byga platform.

g. Breach and credential exposure notification

You will notify Byga within 72 hours of becoming aware of any known or suspected unauthorized access to, or loss of, Client Data. You will notify Byga immediately if credentials Byga issued to you are exposed, whether or not you believe they were misused, so that they can be rotated. You will reasonably cooperate with Byga's response in either case.

4. Restrictions and confidentiality

a. Prohibited uses

You will not:

  • sublicense or redistribute the APIs;
  • reverse engineer, decompile, or attempt to extract source code;
  • introduce harmful code;
  • interfere with the APIs or related systems; or
  • use the APIs for unlawful or unauthorized purposes.

b. Additional data restrictions

You will not:

  • aggregate Client Data across multiple Clients to create independent datasets, analytics products, or services;
  • use Client Data to build or enhance competing products or services;
  • use Client Data outside the scope of the applicable Client authorization; or
  • attempt to re-identify anonymized or aggregated data.

c. No access by user credentials

You may not access the APIs or the Byga platform using another person's login credentials, and you may not collect, store, request, or transmit a Byga user's password, whether persistently or transiently. Access must use only the credentials Byga issues to you. This applies to automated and AI-driven access on a user's behalf as it does to any other access.

For the avoidance of doubt, this section restricts how Client Data is retrieved, not what you may lawfully do with it once retrieved. Client Data obtained through credentials Byga issued to you may be stored and processed in your own systems, including by automated and AI-assisted tools, subject to the authorization of the applicable Client and to sections 3, 4(b), and 5(c).

d. No circumvention

You may not use user consent, direct relationships, scraping, or any other mechanism to access data that is not made available through the Byga platform or authorized by the applicable Client.

e. Security of credentials

Credentials must remain confidential and must not be exposed in public code or shared.

f. Confidential information

You will not disclose Byga's confidential information without prior written consent, except as required by law.

5. Content

a. API content

Content and data made available through the APIs may originate from Clients or third parties. Such content remains the responsibility of the party that provided it. Byga does not independently verify such content and disclaims responsibility for its accuracy or completeness.

b. Submitted content

By submitting content through the APIs, you grant Byga a non-exclusive, worldwide, royalty-free license solely to operate, maintain, secure, and improve the APIs and related services. This license does not grant Byga rights to use Client Data for advertising or unrelated purposes.

c. Data use and disclosure

You may not disclose Client Data except:

  • as authorized by the applicable Client;
  • as necessary to provide your API Client; or
  • as required by law.

You must ensure that any third parties receiving Client Data comply with obligations consistent with these Terms.

d. Content restrictions

You may not scrape, modify, republish, or misrepresent content accessed via the APIs except as permitted by law and these Terms.

6. Branding and attribution

a. Brand features

Neither party grants the other rights to its trademarks except as expressly permitted.

b. Attribution

You must comply with Byga's attribution requirements.

c. Public statements

You may not imply partnership, endorsement, or sponsorship without written approval.

d. Marketing use

Byga may use your name or publicly available materials to describe integrations with the APIs.

7. Privacy and data protection

a. Byga Privacy Policy

By using the APIs, you acknowledge the Byga Privacy Policy: https://www.byga.net/privacy. You must not process personal information obtained through the APIs in a manner that conflicts with the Byga Privacy Policy.

b. Your privacy policy

You must:

  • disclose your use of the Byga APIs; and
  • clearly describe how you access, use, and share Client Data.

8. Relationship to Byga Client Terms

These Terms do not modify or supersede the Byga Client Terms of Service. In the event of any conflict between these Terms and the Byga Client Terms of Service with respect to Client Data, the Byga Client Terms of Service control.

9. Suspension and revocation

Byga may suspend or terminate your API access at any time, including:

  • to protect Client Data;
  • to enforce these Terms; or
  • at the request of the applicable Client.

10. Termination

You may stop using the APIs at any time. Byga may terminate your access at any time. Upon termination, you must cease use of the APIs and delete or return all copies of Client Data within 10 business days, unless retention is required by law, and confirm deletion in writing if Byga asks.

11. Disclaimers and liability

The APIs are provided "as is" without warranties of any kind. To the fullest extent permitted by law, Byga disclaims all implied warranties, including merchantability, fitness for a particular purpose, and non-infringement.

12. Indemnification

You will indemnify and defend Byga from claims arising from:

  • your use of the APIs;
  • your API Client;
  • your violation of these Terms; or
  • your misuse of Client Data.

13. Changes to the APIs, versioning, and deprecation

Byga may add, change, or withdraw API capabilities.

For supported capabilities, Byga will give at least 60 days' notice before a backward-incompatible change takes effect or a capability is deprecated, and will publish the change in the API change history. A backward-incompatible change is one that removes a field or endpoint, changes the type or meaning of an existing field, or changes the conditions under which a request succeeds.

Where a capability is deprecated, Byga will state the date on which it stops functioning and, where a replacement exists, identify it.

Byga may make a change without the notice period above where it is required to address a security vulnerability, a privacy obligation, or unlawful use. Byga will notify affected integrations as soon as practicable in that case.

Experimental capabilities, as described in section 2(d), are not covered by this section.

14. Changes to these Terms

Byga may revise these Terms. Where a revision materially changes your obligations, Byga will notify you and may require you, and the Client that authorizes your integration, to accept the revised Terms. Byga may suspend access if the revised Terms are not accepted within a reasonable period.

15. General terms

a. Governing law

These Terms are governed by the laws of the State of California. The exclusive venue for disputes is Santa Clara County, California.

b. Related agreements and order of precedence

These Terms, the Byga Data Access Waiver signed for your integration, and any written agreement Byga has signed with you or with the applicable Client covering API access together form the complete agreement regarding the APIs, and supersede any prior understanding on that subject. Where they conflict:

  1. the Byga Client Terms of Service control with respect to Client Data, as stated in section 8;
  2. a written agreement signed by Byga and naming your integration controls over these Terms and over the Waiver;
  3. these Terms control over the Waiver, except where the Waiver states a more specific obligation for your particular grant of access, in which case the Waiver controls for that grant.

c. Severability

If any provision is unenforceable, the remainder remains in effect.