RINGSIDE · LEGAL

Developer Addendum

Version 2026-06-25

This applies once you switch on developer features and start creating accounts for other people. It sits on top of the Ringside Terms of Service and Privacy Policy, and on developer-specific matters it wins. The binding text is below. Above it is a summary in ordinary English so you know what you are agreeing to before you read it properly.

The accounts you create are yours to answer for

You vouch for the people you provision for and for what they do with the account. If you created it, it is on your side of the line.

Grants, vouchers and linked billing are real money

A grant or a voucher debits your wallet the moment you make it. Linked billing sends every call that account makes to your wallet, with no cap unless you set one. Set one.

Wallet funds are non-refundable

Except where the law says otherwise. Developer features are not a route for moving chargeback risk onto us or onto your customers.

You can resell the work, not the platform as your own

Associated accounts are full Ringside accounts. Building on top of them is the point. Passing Ringside off as your own undisclosed infrastructure is not.

Limits exist and we can pull the key

There is a cap on live associated accounts, and raising it is a conversation. Suspected abuse, non-payment or platform risk can cost you the provisioning key.

The summary above is for orientation only and has no legal effect. Where it differs from the text below, the text below governs.

The Addendum

This Addendum applies when you enable developer features on your Ringside account and provision accounts for other people ("associated accounts"). It is in addition to, and incorporates, the Ringside Terms of Service and Privacy Policy. If there is a conflict on a developer-specific matter, this Addendum controls.

1. Your responsibility for associated accounts

You are responsible for every associated account you create and for everything done through it, including its usage, content, and the accuracy of the details you provide when creating it. You confirm you are authorised to create an account on behalf of each end user and to share their sign-in details with them.

2. Money changes hands

Developer features move funds. When you fund an associated account by grant or by minting a voucher, the amount is debited from your wallet at that time. When you choose linked billing, that account's API usage is charged to your wallet with no per-account limit unless you set one. You are solely responsible for the cost of all usage you fund, for setting any limits you need, and for any amounts you charge your own customers. We are not a party to, and take no responsibility for, your billing arrangements with your customers.

3. No chargeback shifting

Funds you add to your wallet are non-refundable except as required by law or expressly stated. You will not use associated accounts, vouchers, grants, or linked billing to launder funds, evade fees, or shift chargeback liability to us or to your customers.

4. Acceptable use and resale

Associated accounts are full Ringside accounts, not a licence to resell Ringside as your own undisclosed platform. You will not misrepresent Ringside as your own infrastructure, remove or obscure required notices, or use the platform to provision accounts in bulk for abuse, spam, or circumvention of rate or spend controls. Your customers' use must comply with the Ringside acceptable-use terms.

5. Limits and suspension

Developer accounts may create a limited number of active associated accounts; raising that limit is at our discretion. We may suspend or revoke your provisioning key, your developer status, or specific associated accounts at any time for suspected abuse, non-payment, or risk to the platform or other users.

6. Data and privacy

For associated accounts you create, you act as the controller of the end-user details you supply and are responsible for having a lawful basis to provide them and for informing those end users. We process that data as described in the Privacy Policy.

7. Changes

We may update this Addendum. Material changes take effect on the version date shown above, and continued use of developer features after that date is acceptance. Your acceptance is recorded with the version in effect at enrolment.

Happy with all that?

Accepting this Addendum is part of enrolling. It takes one click, and the rsk_ key is waiting on the other side of it.