1. Who these rules apply to
This policy is part of the Terms of Service. It applies to everyone who uses Frazer: the console, the CLI, the API, the MCP server, the Frazer app and editor extensions, Fir repositories and the public hub, Frazer CI, Frazer Runners and GitHub runners, agents and squads, the LLM gateway, GPUs, Frazer Mail, servers and everything else Frazer provides (“the Services”).
Agents count as you. An agent, a bot, an app or an automation acting with your credentials or in your organization is bound by the same rules as a person, and you are responsible for what it does.
2. Illegal and harmful content
You may not use the Services to store, send, publish or generate:
- child sexual abuse material, or anything that sexualizes minors. We remove it, preserve what the law requires, and report it to the National Center for Missing and Exploited Children;
- intimate images of a person shared without their consent, including realistic synthetic ones. We remove reported images within 48 hours of a valid request;
- content that promotes, supports or directs terrorism or violent extremism;
- threats of violence, or content that incites violence against a person or a group;
- content that infringes someone else’s copyright, trademark or other rights (see the Copyright and DMCA Policy);
- personal data of others published to harm them, such as home addresses, identity documents or financial details (“doxxing”);
- anything else that is illegal where you or Frazer operate.
Public content must also follow the Community Guidelines.
3. Fraud, deception and impersonation
You may not:
- phish, or collect passwords, keys or payment details under false pretenses;
- impersonate a person, a company or Frazer, or imply an endorsement you do not have;
- run scams, pyramid schemes, or sell counterfeit or stolen goods;
- create accounts with false information, or create many accounts to get around limits, prices, free plans or a suspension;
- present AI-generated content as human-made where that deceives people about something that matters, or remove the provenance Frazer attaches to agents’ work in order to mislead.
4. Security and networks
You may not use the Services to:
- break into, scan, probe or test systems you do not own or have written permission to test;
- distribute malware, or run command-and-control infrastructure, botnets or phishing kits against people who have not agreed to it;
- launch or help launch denial-of-service attacks, or flood any system with traffic;
- run open proxies, open mail relays, open recursive DNS resolvers or anonymizing exit relays, or send traffic with forged source addresses;
- get around the security, isolation, quotas, metering or billing of the Services, or reach data that is not yours.
Security research is allowed. You may host proof-of-concept exploits, malware samples and security tools in repositories for research, defense and teaching, if they are labeled as such and are not delivered against anyone without consent. You may test Frazer itself only under our Vulnerability Disclosure Policy.
5. Compute: CI, runners, devboxes, agents and GPUs
Frazer-run compute is for building, testing, running and serving your own software and models. You may not:
- mine cryptocurrency, or run proof-of-work or proof-of-space jobs, on Frazer-run compute: Frazer CI and Frazer Runners, GitHub runners, devboxes, agents, serverless, the Frazer fleet, rented Frazer servers, GPUs and any free plan. Security Center stops mining processes it finds;
- use CI runners as general-purpose compute unrelated to the repository being built, to serve production traffic, or to run work for third parties as a resale service, unless we agree in writing;
- split one workload across many accounts or organizations to stay under free allowances or limits;
- leave abandoned workloads running to keep capacity you do not use, where a plan forbids it;
- train or run models for a purpose this policy forbids.
Use that far exceeds what other customers of the same feature and plan use, in a way that harms the service for others, may be throttled until we have talked with you. On paid plans we contact you before we act, unless the harm cannot wait.
Public repositories run outside contributions in sandboxes, and free plans have limits. Abuse of them, for example a contribution that only exists to mine or to attack, is removed and its author’s account is restricted.
6. Agents and AI
When you run agents or use models through Frazer, you must not:
- use them to do anything this policy forbids, or to evade it;
- turn off, bypass or trick guardrails, approvals, budgets or kill switches in order to cause harm, or to act beyond what a person has approved;
- point them at third-party services in ways those services forbid, such as mass account creation, mass scraping against a site’s terms, or automated posting that pretends to be people;
- use them to make decisions with legal or similarly significant effects on people, such as about credit, employment, housing, insurance, education or access to essential services, without meaningful human review;
- generate content that a model provider’s usage policy forbids, when you use that provider’s models;
- deploy a chatbot or agent that talks to the public and hides that it is an AI when someone sincerely asks, or where the law requires disclosure.
The AI Terms say more about agents, models and outputs.
7. Frazer Mail
Mail you send through Frazer must be mail its recipients asked for. You must:
- send only to people who gave you their address and agreed to hear from you, or with whom you have a relationship the law treats as consent;
- never use purchased, rented, harvested or scraped lists, or send “lead generation” or affiliate mail to people who did not opt in;
- identify yourself truthfully, with accurate headers, a working unsubscribe link and, in commercial mail, a valid postal address;
- honor unsubscribes at once (Frazer’s one-click unsubscribe does this for broadcast streams);
- follow the laws that apply to your mail, including CAN-SPAM, the GDPR and the ePrivacy rules, and Canada’s anti-spam law;
- never send phishing, malware, or mail that impersonates another sender.
Frazer scans outgoing mail for abuse, holds suspicious messages for review, and pauses a stream automatically when its complaints, bounces or spam-trap hits pass published limits. Reports to abuse@frazer.ai are acknowledged automatically and acted on within one business day, and within four hours for phishing.
8. Public repositories, models and the hub
Public content on Frazer is for software, models, datasets and their documentation and discussion. You may not:
- use public repositories, releases, packages or pages as a general file host, a content delivery network for unrelated content, or storage for media that has nothing to do with a project;
- push, star, follow, open proposals or comment through automation in order to fake popularity or spam other people;
- publish secrets or personal data of others. Fir’s push protection blocks known secret formats, and you must remove anything that gets through;
- upload a model or dataset that you have no right to share, or that is built to do something this policy forbids.
9. Your servers and domains
On servers you bring, you are responsible for what runs on them and for following your provider’s rules. These rules still apply to anything you do through Frazer, including mail, DNS and agents that act from those servers. A domain you add to Frazer must be one you own or control.
10. What happens when a rule is broken
We choose the lightest action that stops the harm, and we act faster when people are at risk. Depending on the case, we may:
- remove or hide the content, or redact it from a repository while keeping the rest of the history intact;
- pause the resource, the mail stream, the agent or the workload;
- restrict a feature, such as public visibility or sending mail;
- suspend or close the account or the organization;
- keep records and report to authorities when the law requires it, or when someone’s life or safety is in danger.
Automated checks act on their own only where waiting does more harm than acting: a cryptocurrency miner is stopped, a destination known to be malicious is blocked, and a mail stream past its limits pauses. Everything else is decided by a person.
We tell you what we did and why, which rule and which content it concerns, how long the action lasts, whether it was automated, and how to appeal, unless the law forbids it or telling you would put someone at risk. A pause never deletes your data. If we close an account for a serious violation, we give you a reasonable chance to export lawful data first, except where the content itself is illegal.
11. Appeals
If you think we got it wrong, reply to our notice or write to abuse@frazer.ai within six months, with what you think we missed. A person who was not involved in the first decision reviews it, and we tell you the result and the reason. If we were wrong, we restore what we removed.
12. Reporting abuse
Report abuse of Frazer, or abuse that comes from Frazer, to abuse@frazer.ai. Include where you saw it (a link, a repository, an IP address, or the full headers of an email), what is wrong, and how to reach you. Copyright claims follow the Copyright and DMCA Policy. Security issues in Frazer itself go to security@frazer.ai.
13. Changes
We update this policy as Frazer and the ways it can be abused change. When a change restricts what you may do, we email account owners 30 days ahead, unless we must act sooner to stop harm or follow the law.