API Terms

1. Introduction

The Sail Club API lets a club, or a third party it authorises (its own website, or a results partner), read that club's public event and results data server-to-server. These API Terms apply to anyone using API credentials issued for a club — whether the club administrator itself or an integrator the club has handed credentials to — together with our Terms of Service and Privacy Policy.

2. Permitted Use

API access may be used only to display or process the club's own public event, race and results data, for the club's own events, in ways consistent with how that data already appears on the club's public results pages. You may not use the API to build a competing results platform, to aggregate data across clubs without our written permission, or for any purpose other than showing the club's own results.

3. Attribution

Any public display of data obtained through the API must credit Sail Club with visible attribution (for example, "Results by Sail Club") linking to sailracing.club, placed near the displayed data.

4. Caching and Freshness

Our API caches data for at least one hour before refreshing it; every response tells you how fresh the data is. Do not present cached data as more current than the age we report, and do not poll the API more often than needed to keep your own cache within that same window — repeated requests for the same data inside the cache window will not return newer results.

5. Credential Security

The client secret shown when a credential is created is shown once and is never stored by us in a retrievable form. You are responsible for keeping it secret — store it only on your own server, never in client-side code, a mobile app, or a public repository — and for rotating it if you suspect it has been exposed. Any request made with your credentials is treated as made by you.

6. Personal Data

Data returned by the API is limited to what already appears on the club's public results pages (see our Privacy Policy, Section 8): never a participant's email address, phone number, live location, or internal account identifiers.

You may only display this data as public results information — you may not use it to build a profile of, market to, or otherwise contact a participant. If a participant's data is corrected or anonymised on our platform (for example, after their account is deleted), you must apply the same change to any copy you have kept within a reasonable time, and remove data at our request or the participant's.

7. Rate Limits and Availability

Requests are rate-limited per credential; if you exceed the limit we may return a 429 response with a Retry-After header. We do not guarantee a particular level of availability, response time, or continued support for any API version, though we aim to give advance notice before retiring one (see Section 9).

8. Suspension and Revocation

We may suspend or revoke API credentials at any time, with or without notice, if we believe these Terms are being violated, the credentials are compromised, or continued access poses a risk to the platform, a club, or its members. A club administrator may also disable or delete their own credentials at any time from the panel.

9. Changes and Versioning

We may change these Terms, and we may change or retire an API version. Where practical, we will give advance notice through the developer documentation or the panel. Continued use of the API after a change takes effect means you accept the updated Terms.

10. No Warranty

The API and the data it returns are provided "as is", without warranty of any kind, express or implied, including as to accuracy, completeness, or fitness for a particular purpose.

11. Governing Law

These API Terms are governed by and construed in accordance with the laws of the Republic of Turkiye, without regard to its conflict of law provisions, the same as our Terms of Service.