Terms of Service

1. Who we are

These terms are an agreement between you and the company that operates GridPort ("we", "us"). [The operating entity and its registered address — to be stated before these terms take effect]

They cover the website, the console and the API. The Service Level Agreement, the Acceptable Use Policy, the Refund Policy and, for personal data you send us, the Data Processing Addendum form part of them. An order form or written agreement signed by both sides prevails where it differs.

2. Your account

One person or organisation holds each account. You are responsible for what happens under it, including calls made with keys you or your members issue. Keep credentials out of client-side code and public repositories; a key that leaks is spent at your expense until you disable or rotate it.

You must be able to form a contract in your jurisdiction, and you must give an address we can reach you at. We may refuse or close an account that exists to evade a limit, a payment or a suspension, or that was opened to collect trial credit more than once.

3. The service

We route your requests to inference engines we operate and to third-party providers we have contracted with, and we meter what they return. Which engine serves a request can change. The console records the serving route and model version for every call, and that record is what we will discuss if you ask.

We do not publish which providers we use. Customers can obtain the current list of subprocessors, with their roles and locations, as described in the Data Processing Addendum.

Model availability changes. We announce a model retirement in the console and by email before it takes effect, with the replacement named where there is one. Features marked beta or preview may change or be withdrawn without that notice.

4. Acceptable use

Your use of the service must follow the Acceptable Use Policy, including the licence terms of each model you call, which are linked from its model page.

If you use the service to offer an AI product to your own users, you are responsible for the obligations that apply to you as that product's provider in the places where you offer it — for example registration or filing, labelling generated content, content moderation and handling user complaints.

5. Your content

Your prompts and the outputs you receive are yours. We do not use them to train models, and we do not sell them. We process them to serve the request, to meter it, and — only if you switch content logging on for a project — to store them for the retention window you chose.

You are responsible for having the rights to what you send, and for what you do with what comes back. Model output can be wrong, and outputs are not professional advice.

6. Credit, prices and payment

The service is prepaid unless we have agreed otherwise in writing. Credit is denominated in US dollars and spent oldest-expiring first. Trial and promotional credit expires on the date shown in the console and has no cash value.

Charges are made in US dollars. If you pay with a card or a wallet such as Alipay or WeChat Pay in another currency, its provider converts the amount at its own rate.

Prices are published in the console and on the pricing page. An increase to a published price takes effect no sooner than thirty days after we announce it; a decrease can take effect immediately. Each request is billed against the price in force when it ran, and the console shows which price row was used.

Prices exclude taxes. Taxes are your responsibility unless we are required to collect them. Receipts and monthly statements are available in the console. A failed or reversed payment may suspend inference until the balance is settled.

Refunds follow the Refund Policy.

7. Service levels and support

The serverless API is covered by the Service Level Agreement: 99.9% monthly uptime, with service credits when we miss it. Dedicated endpoints, fine-tuning, batch jobs and anything marked beta or preview are outside it unless an order form says otherwise. Beyond the SLA, the service is provided as available.

We publish component status and per-model availability on the status page. Support: [Support address — to be stated before these terms take effect]. Every request carries an identifier you can quote to us, with its tokens, price row and settlement state.

8. Suspension

We may suspend an account, a project or a key: for non-payment; to stop a breach of the Acceptable Use Policy or a security risk; or where the law requires it. Where we can, we tell you first and give you time to fix the problem; where the alternative is ongoing harm we act first and tell you straight after. We lift a suspension once its cause is resolved.

9. Export controls and sanctions

You may not use the service if you are, or act for, a person on a sanctions or restricted-party list maintained by the United States, or where providing the service to you would be prohibited by the export control or sanctions laws that apply to us. You are responsible for the export and import laws that apply to your own use of outputs.

10. Liability

Neither side is liable for indirect or consequential loss, or for lost profits or data. Our aggregate liability is limited to what you paid us in the three months before the event. Service credits under the SLA are the sole remedy for unavailability. Nothing here limits liability that cannot be limited by law.

You indemnify us against third-party claims arising from your content or your use of the service in breach of these terms.

11. Changes and ending the agreement

You can close your account at any time from the console. Unused paid credit is refunded on request as described in the Refund Policy; trial and promotional credit lapses.

We tell account holders at least fifteen days before a materially changed version of these terms takes effect, and the console records which version you accepted. Continuing to use the service after the effective date is acceptance of the new version; if you do not accept it, you can close the account before then and have unused paid credit refunded.

12. Governing law and disputes

[Governing law — to be stated before these terms take effect]

[Where disputes are decided — to be stated before these terms take effect]

Before starting formal proceedings, each side will first try in good faith to resolve the dispute by writing to the other.

13. Notices

We send notices to the email address of the account owner. Write to us at [Support address — to be stated before these terms take effect].