1. What these terms cover
These AI Terms are part of the Terms of Service and apply when you use Frazer’s AI services: agents and squads, the LLM gateway, models Frazer serves on its own GPUs, the Reviewer, Knowledge, the console assistant and AI features in the Frazer app and editor extensions (together, the “AI Services”). Where these terms and the Terms of Service differ about the AI Services, these terms apply.
Inputs are what you or your agents send to the AI Services: prompts, code, files, documents, tool results and context. Outputs are what the AI Services return: text, code, proposals, reviews, plans and actions. Inputs and Outputs are part of Your Content under the Terms.
2. You own your inputs and outputs
As between you and Frazer, you own your Inputs and your Outputs. To the extent Frazer has any rights in Outputs, we assign them to you. We use Inputs and Outputs only to provide the AI Services to you, to keep them secure, to prevent abuse, and as the law requires.
Outputs may be similar to what others receive, because models produce similar answers to similar questions. Your ownership does not extend to someone else’s similar output. The law on copyright in AI-generated material differs between countries and is still developing, so we do not promise that Outputs can be protected by copyright.
3. No training on your content
- Frazer does not train or fine-tune any model on your Inputs, your Outputs or any other Your Content, and does not use them to improve models, ours or anyone else’s. This includes the code in your repositories, your agent sessions, your reviews, your Knowledge sources and the mail you send.
- Routes Frazer bills for go only to model providers whose terms with us forbid training on what we send them. A route’s data policy, such as zero data retention or no training, is enforced on every request: a request that would break it is refused, not sent.
- With your own key, a request goes to the provider under your agreement with them, and their terms decide what they keep and whether they train on it. The gateway still enforces the data policy you set on the route.
- You can train your own models on Frazer, with your own data, on your own instructions. The result is yours.
The only exception is if you tell us in writing that you want us to use specific content for a purpose you choose. We will not ask for that as a condition of anything.
4. What we keep
| AI Service | Default | What you can choose |
|---|---|---|
| LLM gateway | Request metadata: model, route, tokens, cost, timing and guardrail results, for 30 days. No prompts or outputs | Masked bodies for 7 days, full bodies for 7 to 30 days where your organization’s policy allows it, a time-boxed capture of up to 24 hours, or zero data retention mode, which keeps metadata only and blocks every feature that would store a body |
| Reviewer | Code is read in a sandbox that is deleted when the review ends. Findings text is kept for 180 days. The code index is encrypted per organization and can be deleted | Zero retention: counts and fingerprints only, and no index |
| Agents | Sessions, transcripts and memory as you configure them. A person’s agent sessions are readable by that person and the people they share them with; organization admins see only the list, unless an organization policy shown to members says otherwise | Retention per agent and per memory store; erase on offboarding |
| Knowledge | Your sources’ text and vectors, encrypted, for as long as the source is connected | Deleting a source deletes it from every index |
| Console assistant | Nothing beyond your organization’s audit log | Your organization can turn it off |
Deleting a project, an organization or your account deletes the data above as the Terms describe.
5. Model providers
Some AI Services use models from other companies. When a request goes to one of them:
- on a route Frazer bills for, the provider processes it for Frazer, as a sub-processor. Every such provider is named on the sub-processors list before it receives any request;
- with your own key, the provider works for you, and is not Frazer’s sub-processor;
- the provider’s usage policy, and its list of countries it serves, apply to what you send it, in addition to our Acceptable Use Policy. We show which provider a route uses before you send anything through it;
- providers change and retire models. We tell you ahead when a model a route uses is being retired, as early as the provider tells us.
6. Open models Frazer serves
Models Frazer serves on its own GPUs, and models you deploy from the hub, come with their own licenses, such as Apache 2.0 or a model developer’s community license. The license is shown on the model’s page. You must follow it, including any use restrictions it contains. Frazer does not grant you more rights in a model than its license does.
7. Agents act for you
Agents on Frazer work under their own identity, with the permissions, credentials, budgets and approval rules you or your organization give them. Every action they take is recorded in your audit log.
- You are responsible for your agents’ actions, as if you had taken them yourself, within the permissions you granted. That includes changes they make, mail they send, money they spend and messages they post on other services. An agent acting with your credentials is your electronic agent, and what it does in the Services binds you.
- Give the least access that does the job. Frazer’s defaults ask for approval before risky actions, and our guardrails, budgets and kill switches limit damage, but no control can stop every mistake. Review what agents propose before it reaches production, customers or the public.
- An agent never approves. Approvals on Frazer are made by people. An agent may prepare a change, never approve its own or another agent’s.
- Content from outside can be hostile. Pages, issues, emails and tool results that agents read can contain instructions meant to mislead them. Frazer labels untrusted input and switches risky tools to ask for approval after it, but you should not give agents that read untrusted content access they do not need.
- Third-party services. When an agent uses another service for you, that service’s terms apply, and you must have the right to use it that way.
8. Outputs can be wrong
Outputs come from statistical models. They can be incorrect, incomplete, insecure or out of date, even when they sound certain, and the same input can give different outputs. The Reviewer’s findings are suggestions, not a guarantee that code is correct or safe. You must evaluate Outputs before you rely on them, especially for security, money, health, legal matters or anything that affects people. Do not use the AI Services to make decisions with legal or similarly significant effects on people without meaningful human review.
9. Provenance and disclosure
Frazer records which agent made a change, for whom and from which session, on every pull request it merges in Fir, and carries that record into exports. You must not remove or falsify it to mislead others about who or what made something. If you use AI Services to build a product that talks to people or produces content for them, you are responsible for telling them they are dealing with AI where the law requires it.
10. Restrictions
You must not use the AI Services to do anything the Acceptable Use Policy forbids, to get around a guardrail or a provider’s safety measures in order to cause harm, or to extract a model’s weights or system instructions in breach of its license or its provider’s terms.
11. Changes to these terms
We change these terms as the AI Services and the law change. When a change matters to you, we email owners and billing contacts 30 days ahead, as the Terms of Service describe.