What this covers

This policy applies to the Jatevo service at jatevo.ai: the front page, the console under /app, the API under /v1 together with the other request formats it accepts, and the documentation. It is written for the people who sign in and for the tools that hold their keys.

Jatevo is open-source software. If you run it on your own server, this page describes what the software does; the operator of that deployment is responsible for its own policy.

Personal and team use only

Every endpoint Jatevo exposes, and every key it mints, is provided for your own personal use or for use within your own team. A key identifies one person, or one workload that person or their team runs. A provider connection an administrator adds is for the members of that team. Nothing here is offered as capacity to resell, or to build a service for third parties on.

Not a custodian, not a merchant

Jatevo holds nothing of yours in custody. Your provider accounts, subscriptions, credits and payment methods stay with the provider, under the provider’s own terms. Jatevo takes no deposits, holds no funds and moves no money.

Jatevo is not a merchant. It does not sell or resell model access, does not price requests, and does not take payment for the requests that pass through it. The commercial relationship for any model you use exists separately, between you or your team and that provider, under the provider’s terms. That remains so when the provider is a service Jatevo operates elsewhere under its own terms.

Sharing, resale and reuse

A key, a connection or an account is for the person or team it was issued to. Reselling it, renting it out, sharing it with, or reusing it on behalf of anyone outside your team is not what the service is for.

Whoever does so carries the risk alone. Most providers forbid it in their terms, and it can end in a suspended account, a lost subscription, unexpected charges or blocked keys, none of which Jatevo can prevent or undo. Jatevo bears no responsibility for such use and may revoke keys or connections used that way. Where a provider’s own terms expressly permit sharing or resale, that is a matter between you and that provider.

Each person is responsible for their own accounts, their own keys, and what is sent through them.

What Jatevo stores

• Account. Your email address, when you give one or accept an invitation; a scrypt hash of your password, never the password itself; and your role.
• Sessions. For each sign-in, when it was created and last seen, and the IP address and browser identifier it came from, so you can review and revoke sessions from Settings.
• Keys. A key’s name, its prefix, a SHA-256 hash of it, its permissions and allowances, and when it was created, rotated, revoked and last used. The full key is shown once when it is minted and is not stored in readable form.
• Connections. The provider, its address, the model IDs it may serve, and the credential an administrator entered, encrypted with AES-256-GCM under a secret kept outside the database. Credentials never appear in a page or an API response.
• Requests. For every request a key serves: the key, the provider, the model, the request format, the outcome, when it started and finished, the HTTP status and the token counts the provider reported. Not the content: prompts, messages, files and model output are forwarded to the provider and are not written to the database or to any log.
• History. Who created, rotated or revoked what, sign-ins, and the notifications the console shows you.

Request records are kept 90 days and history 180 days. Accounts, keys and connections are kept for as long as they exist. A session expires after seven days without use, or when you revoke it.

Where a request goes

When a key sends a request, Jatevo checks the key, its permissions and its allowance, then forwards the request to the provider whose model it names, with that provider’s credential. The provider receives the content of the request and handles it under its own privacy terms, on its own servers, wherever it runs them.

Jatevo sends nothing to anyone else. There are no analytics, no advertising, no tracking pixels, and no third-party scripts or fonts on any page. The deployment may be reached through a reverse proxy or content delivery network, which terminates the connection and sees connection metadata such as your IP address and the requested path in transit.

Nothing that passes through Jatevo is used to train anything. Jatevo keeps no message content, so it could not.

Cookies and browser storage

One cookie, jatevo_session, holds your session after you sign in. It is HttpOnly, Secure, SameSite=Lax, scoped to this host alone, and expires after seven days without use. There are no other cookies, no local storage and no cross-site identifiers. Signing out clears it.

Security

Passwords are stored as scrypt hashes. Keys are stored as SHA-256 hashes. Provider credentials are encrypted with AES-256-GCM under a secret kept in a separate file. Session cookies carry a keyed signature. Every page ships a content security policy that allows no inline script and no third-party source. Please report a vulnerability privately, not in a public issue.

Your choices

From the console you can review and revoke your sessions and rotate or revoke your keys at any time, and an administrator can remove a connection or a member. Revoking a key or removing a connection stops its use at once; the request records about it remain for the retention period above and then drop out. To have an account and everything recorded about it removed sooner, ask the operator.

Changes and contact

This page changes when the software or the service does; the date at the top is the date of the current text. Questions about it, or requests about your data, go to the operator of this deployment.

Jatevo 0.1.0. About. Documentation.