caft

Acceptable Use Policy

Last updated 21 October 2026

This policy is part of the Terms of Service and applies to everything you do through the API.

Everything on this list is here for one of three reasons: it is unlawful, it causes harm, or it puts the service at risk for everyone else.

What is not on this list matters too. We do not restrict what you build, who you sell it to, or what you do with the output. Section 6 says so explicitly. This policy is about conduct and content, not commerce.

1. Illegal and harmful use

You must not use the service to:

2. Decisions about people, and things that must not fail

Model output is a statistical prediction. Two kinds of use ask more of it than it can carry: decisions that land on a person, and jobs that must not fail.

3. No personal data

Do not submit personal data through the API. Not names or contact details, government identifiers, financial account numbers, health information, biometric data, precise location, or anything at all about a child.

This is an outright prohibition rather than a duty to have a lawful basis, and the reason is structural: we retain nothing of a request, so if you send personal data we cannot find it, produce it, or delete it, and we cannot tell you what an upstream provider did with it. Section 8 of the Terms and Section 3 of the Privacy Policy say the same thing from their own angles.

4. Model integrity

5. Technical abuse

6. What this policy does not restrict

We sell capacity. What you build on it is your business, and we would rather say so than leave you to infer it:

One thing comes back the other way. If you resell or otherwise give others access through your account, their use is your use. This policy travels with the access: you are responsible for what your customers do as if you had done it yourself, and it is on you to bind them to terms at least as strict as these.

7. Enforcement

Where a breach is serious or unlawful we may suspend or terminate without notice, and may report it to law enforcement and to the upstream provider involved. Otherwise we will tell you what the problem is and give you a chance to fix it, where the circumstances allow.

Where throttling or a rate limit would solve the problem, we would rather do that than close an account.

Termination for breach forfeits any remaining credit balance — Section 6 of the Terms. That is the consequence of a breach, so it does not apply to a suspension we later determine was mistaken: if we get it wrong, we restore the account and the balance. If you think we have, write to support@caft.dev and we will look again.

8. Reporting misuse

Report misuse of the API, or content generated through it, to abuse@caft.dev. Report security vulnerabilities to security@caft.dev. Both are monitored.

Tell us what you saw and when, and how you came across it. We cannot search request content — we do not keep any — so what you can show us is usually all there is to go on.

9. Changes to this policy

We may update this policy. The date it was last updated appears at the top of this page, and a change is notified by publishing it here and nowhere else, on the same terms as Section 16 of the Terms.