Developer pilot

Pilot terms & acceptable use

These terms govern access to the current SportsFoundry pre-release developer pilot. They are intentionally narrower than the final paid-commercial Terms of Service.

Effective date: 21 September 2026. Operator: Matters Digital Ltd (SC874434).

1. Pilot purpose

The pilot is for evaluation, development, integration testing and product feedback. It is not a production service-level commitment. Features, coverage, limits and implementation details may change as pilot evidence is incorporated.

2. Accounts and API credentials

  • Keep account and API credentials confidential and use separate API clients where appropriate for applications/environments.
  • Do not share API secrets publicly or place them in client-side/public repositories.
  • Revoke a credential promptly if you believe it has been exposed.
  • You are responsible for activity performed using credentials issued to your workspace, subject to our security controls.

3. Acceptable use

You must not:

  • bypass or attempt to bypass authentication, authorisation, quotas, rate limits, resource limits or other security controls;
  • probe or exploit vulnerabilities except through a separately agreed security-testing arrangement;
  • use the service to interfere with SportsFoundry, its providers or other users;
  • send deliberately abusive, unlawful or disproportionate automated load;
  • use anonymous/public demonstration surfaces as a bulk-data export mechanism;
  • redistribute or resell SportsFoundry data except where the product or a separate written agreement expressly permits it;
  • use the service in a way that infringes law or third-party rights.

4. Coverage, data and corrections

The public Coverage surface is the current product truth for what SportsFoundry publishes. Sports data can be delayed, incomplete, corrected or withdrawn. Pilot applications should tolerate corrections, unavailable fields and degraded periods rather than assume every field or competition is permanently available.

5. Limits and service protection

Pilot entitlements, request limits and concurrency/resource controls apply. We may throttle or reject requests that exceed the applicable limits and may suspend pilot access where reasonably necessary to protect the service, investigate abuse/security issues or comply with law.

6. Pilot pricing and billing

Live self-service payment is not enabled for the current developer pilot. Public plan prices, allowances, billing cadence, overage treatment and paid service commitments remain TBC until explicitly offered and accepted. Participation in the pilot does not create a promise of future price protection unless SportsFoundry later says so in writing.

7. Feedback

You can choose to provide feedback about usability, coverage, missing data, reliability and value. We may use that feedback to improve SportsFoundry. Do not include confidential third-party information or unnecessary personal information in feedback.

8. Availability and responsibility

The pilot is provided without a production SLA and should not be the sole dependency for safety-critical, regulated or business-critical production use. Nothing in these pilot terms excludes or limits liability that cannot lawfully be excluded or limited.

9. Privacy

Personal information used for the pilot is handled as described in the SportsFoundry Privacy Notice.

10. Ending pilot access

You may stop using the pilot at any time. We may suspend or end pilot access where the pilot ends, the service changes, these terms are materially breached, security/service protection requires it, or law requires it. Where practical, material pilot changes will be reflected in the customer surface.

11. Governing law

These pilot terms are governed by the law of Scotland, subject to any mandatory rights that apply by law.

Contact and status

SportsFoundry is operated by Matters Digital Ltd, 49 Harlequin Court, Hamilton, Scotland, ML3 8SW.

These pilot terms do not replace the final commercial Terms of Service, billing/refund terms, data-redistribution terms or service-level schedules that may be required before paid general availability.