The terms of using Jean.

This is between Jean Technologies and your organisation. An owner accepts it on the organisation's behalf, and we record which version was accepted, by whom, and when.

Using the API or the console means these terms apply to you.

Every account belongs to an organisation, and so does every API key — a key is the organisation's, not the property of whoever created it.

A key is shown once and afterwards stored only as a hash, so keep it somewhere safe. Anything done with your organisation's key is treated as done by your organisation. If a key leaks, revoke it.

Plainly:

• Submit only work you have the right to submit.
• Do not use the platform to break the law, or to harm, harass or deceive people.
• Do not try to reach another organisation's data, work around quotas, or degrade the service for anyone else.
• Do not share keys outside your organisation.
• Reselling access to the API as though it were your own service is something to talk to us about first, not something to assume.

If we see use of that kind we will contact you. If it continues, or if it is serious, we may suspend the organisation's keys.

The default is scoring_only: your submissions are used to compute the score you asked for and to return a result and a trace, and for nothing else. An owner can change the setting to aggregate_ok or training_ok, and can change it back.

The privacy page sets out what each setting means, what we store, and for how long.

A score is the output of a model. It is a measurement, and measurements can be wrong.

We do not warrant that any score is fit for a particular purpose. Whether a score is good enough for yours is your judgement to make, and we would rather you treated it as evidence than as a verdict. In particular, do not make a score the sole basis of a decision that materially affects a person.

The service is provided as is. We do not promise uptime, and we do not promise that a feature here this month will be here the next.

We will try to warn you before a change breaks something you depend on, but early access is early access, and you should treat it that way.

The API is described by a versioned OpenAPI contract, and that contract is the thing to build against.

We may change the API. When we do, the change arrives with notice through that contract and its version, rather than as a surprise in production.

Usage is metered per request, and that meter is the record we bill and apply quotas from.

Pricing during early access is agreed with you directly. Nothing on this page sets a price.

Either party may end the relationship at any time. Tell us by email, or we will tell you.

When it ends, keys stop working. Deletion of the organisation's data works as the privacy page describes, and the billing usage records and the audit log are kept as business records.

Liability, indemnity and confidentiality are not settled on this page. Those belong in a signed agreement, and this draft does not pretend to have them. If you need them now, email us and we will work them out.

Jean Technologies — jonathan@jeantechnologies.com