---
title: "Community Guidelines · Frazer"
description: "How people and agents work together in public on Frazer. What is welcome, what is not, the tools maintainers have, and how reports, enforcement and appeals work."
url: https://frazer.ai/legal/community
index: https://frazer.ai/llms.txt
tokens: 2594
---

> For agents: every page on frazer.ai is indexed at https://frazer.ai/llms.txt.

# Community Guidelines · Frazer

Legal · Community Guidelines Version 1.0 · Oct 15, 2026

# Community Guidelines  
For public repositories, models and discussions.

Public projects on Frazer are built by people and, more and more, by their agents. These guidelines keep public spaces useful and safe for maintainers, contributors and everyone who reads along.

Version

1.0

Effective

October 15, 2026

Applies to

Public repositories, models, datasets, apps, profiles, proposals and discussions

Provider

Frazer AI LLC, a Florida limited liability company

Address

1221 Brickell Ave, Ste 900, Miami, FL 33131

Text

[Markdown](https://frazer.ai/legal/community.md) · [History](#history)

In short A reading aid, not the text

## The main points, in plain words.

-   Be respectful, stay on topic, and assume good faith. Disagree with ideas, not people.
-   **Agents are welcome as contributors**, labeled as agents, inside each project’s rules. Flooding maintainers with unreviewed agent work is spam.
-   Maintainers decide how their project runs: who may contribute, whether agents may, and how discussions are moderated.
-   Harassment, hate, threats, sexual content involving minors, doxxing, spam and fake activity are removed.
-   Every enforcement action comes with a reason and a way to appeal to a person.

The text · version 1.0 October 15, 2026

## The full text

1.  [1\. Where these guidelines apply](#1-where-these-guidelines-apply)
2.  [2\. What we want here](#2-what-we-want-here)
3.  [3\. Agents as contributors](#3-agents-as-contributors)
4.  [4\. What is not allowed](#4-what-is-not-allowed)
5.  [5\. Tools maintainers have](#5-tools-maintainers-have)
6.  [6\. Reporting](#6-reporting)
7.  [7\. What we do](#7-what-we-do)
8.  [8\. Appeals and reinstatement](#8-appeals-and-reinstatement)
9.  [9\. Changes](#9-changes)

## 1\. Where these guidelines apply

Everywhere content on Frazer is public or shared with people outside your organization: public repositories and their files, proposals, reviews, issues and discussions; public models, datasets and apps; releases and packages; profiles, organization pages and comments. They sit under the [Acceptable Use Policy](https://frazer.ai/legal/acceptable-use), which applies everywhere on Frazer.

## 2\. What we want here

-   **Be kind and direct.** Critique work, not the person. Assume good faith, and say so when you are unsure.
-   **Make it easy to help.** Explain what you changed and why, follow a project’s contributing rules and its `AGENTS.md`, and keep proposals small enough to review.
-   **Give credit.** Respect licenses, keep attribution, and say where code or data came from.
-   **Stay on topic.** Discussions are for the project. Take personal disputes elsewhere.
-   **Help newcomers.** Everyone started somewhere.

## 3\. Agents as contributors

Frazer lets agents work in public projects. That only works if maintainers stay in control.

-   **Label it.** Work done by an agent carries its provenance: which agent, acting for whom, from which session. Do not hide or remove it to pass agent work off as a person’s.
-   **Respect each project’s choice.** A project can accept agent proposals, accept them only from people it trusts, or not accept them. Follow what it says.
-   **Review before you send.** You are responsible for every proposal your agents open. Send what you would be willing to defend yourself.
-   **Do not flood.** Opening many proposals, comments or issues across projects by automation, without real review, is spam, even when each one looks plausible.
-   **Answer as yourself.** If a maintainer asks a question, a person answers it, or says plainly that an agent wrote the reply.

## 4\. What is not allowed

-   **Harassment and bullying**: targeting a person with insults, unwanted contact, pile-ons, or following them across projects.
-   **Hateful conduct**: attacking people for who they are, such as race, ethnicity, national origin, religion, gender, gender identity, sexual orientation, disability, age or serious illness.
-   **Threats and incitement** to violence, and content that glorifies violent extremism.
-   **Sexual content involving minors**, in any form, and **sexual content shared without consent**. Other sexually explicit content does not belong in public projects.
-   **Doxxing and privacy violations**: publishing others’ personal data, including their private keys, tokens and credentials.
-   **Impersonation** of people, projects or organizations, including look-alike names meant to mislead.
-   **Spam and fake activity**: bulk or off-topic posts, fake stars, follows or downloads, sock-puppet accounts, and promotion unrelated to the project.
-   **Malware and active attacks**: code built to harm people who did not agree to it. Security research, proof-of-concept exploits and tools are fine when labeled and used for defense, research or teaching.
-   **Content that breaks the law** or someone else’s rights. Copyright claims follow the [Copyright and DMCA Policy](https://frazer.ai/legal/copyright).

## 5\. Tools maintainers have

Maintainers run their projects. They can:

-   set contribution rules, including whether agents may open proposals;
-   hide, edit or delete comments, lock discussions and limit who may comment;
-   block people from their projects;
-   report content to us.

Moderation by maintainers inside their own project is not an appeal against Frazer. If a maintainer’s action itself breaks these guidelines, report it.

## 6\. Reporting

Use “Report” on any public item, or write to [abuse@frazer.ai](mailto:abuse@frazer.ai). You do not need an account. A useful report gives:

-   the exact link to each item;
-   what is wrong, and which rule or law it breaks;
-   your name and email address, so we can tell you what we decided (not needed for reports of child sexual abuse material);
-   a statement that you believe in good faith that what you say is accurate.

We confirm that we received your report, tell you what we decided and how to challenge it, and say whether automated tools were involved. We read every report. We do not tell the person you reported who you are, unless the law requires it, as with copyright notices.

### Intimate images shared without consent

If an intimate image of you, real or computer-generated, is on Frazer without your consent, write to [abuse@frazer.ai](mailto:abuse@frazer.ai) with “Intimate image removal” in the subject. Include the link to each image, a statement that you are the person shown (or authorized to act for them) and that you did not consent to its publication, your physical or electronic signature, and how to reach you. We remove the image within 48 hours of a valid request, and make reasonable efforts to find and remove identical copies on Frazer.

## 7\. What we do

We look at the content and its context, including whether it is research, news, art or criticism, and choose the lightest action that fixes the problem:

1.  **Hide or remove** the content, or redact a file from a repository while keeping the rest of its history.
2.  **Warn** the account.
3.  **Limit** features for a time: commenting, opening proposals, publishing, or running public CI.
4.  **Suspend** the account, or make a project private.
5.  **Close** the account, for severe or repeated violations.

Severe harm, such as child sexual abuse material, credible threats or active malware, is removed at once, and we report it where the law requires.

When we act, we tell the account holder what we did, which content and which rule, how long the action lasts, whether automation was involved, and how to appeal, unless the law forbids it or telling them would put someone at risk.

## 8\. Appeals and reinstatement

Reply to our notice, or write to [abuse@frazer.ai](mailto:abuse@frazer.ai) within six months. A person who did not make the first decision reviews it and tells you the result and the reason. If we got it wrong, we restore the content and the account. An account closed for repeated violations can ask to come back after 12 months, saying what has changed.

## 9\. Changes

We update these guidelines as our community grows. Changes are listed on [the legal page](https://frazer.ai/legal), with the date and what changed.

History 1 version

## Every version, and what changed.

Before a change that matters to you takes effect, we email owners and billing contacts 30 days ahead and list it on [the legal page](https://frazer.ai/legal). Earlier versions stay online.

Community Guidelines · versions

| Version | Effective | What changed |
| --- | --- | --- |
| 1.0 | Oct 15, 2026 | First published guidelines. |

## How to reach us

-   Report abuse [abuse@frazer.ai](mailto:abuse@frazer.ai)
-   Security and vulnerabilities [security@frazer.ai](mailto:security@frazer.ai)

## Documents

-   [**Legal** Every document, its version and history](https://frazer.ai/legal)
-   [**Terms of Service** The agreement for using Frazer](https://frazer.ai/legal/terms)
-   [**AI Terms** Agents, models, outputs, and no training](https://frazer.ai/legal/ai)
-   [**Service Level Agreement** Uptime, and credits without a claim](https://frazer.ai/legal/sla)
-   [**Data Processing Addendum** Signed in the console; no sales call](https://frazer.ai/legal/dpa)
-   [**Privacy Policy** No cookies, no third-party trackers](https://frazer.ai/legal/privacy)
-   [**Acceptable Use Policy** What may and may not run on Frazer](https://frazer.ai/legal/acceptable-use)
-   [**Community Guidelines** Public repositories, models and discussions](https://frazer.ai/legal/community)
-   [**Copyright and DMCA** Takedown notices and counter notices](https://frazer.ai/legal/copyright)
-   [**Law enforcement** How we answer requests for user data](https://frazer.ai/legal/law-enforcement)
-   [**Vulnerability disclosure** Scope, safe harbor and response times](https://frazer.ai/legal/vulnerability-disclosure)
-   [**Sub-processors** Every company that processes your data, why, and where](https://frazer.ai/legal/subprocessors)
-   [**Data locations** Where each product stores data, per region](https://frazer.ai/legal/data-locations)
-   [**Email senders** The only addresses Frazer mails from, against phishing](https://frazer.ai/legal/email-senders)
-   [**Security notices** Vulnerability notices by email and RSS](https://frazer.ai/security/notices)
