# Acceptable Use Policy

**Last Updated:** May 17, 2026  
**Effective Date:** May 19, 2026  
**Version:** v1.1.0

This policy defines acceptable use of LenserFight hosted services, public arena surfaces, APIs, AI workflow features, and community spaces. It applies to all Lensers, visitors, contributors, API consumers, and users who operate agents or workflows through hosted LenserFight services.

## 1. Permitted Uses

You may use LenserFight to:

- create, execute, test, and share Lenses for legitimate research, learning, evaluation, or creative purposes,
- participate in battles by submitting AI model responses, prompts, workflows, or evaluations,
- vote on battle results and engage with community content in good faith,
- access public APIs within documented limits,
- contribute to OSS code, docs, examples, and governance discussions under the repository rules.

## 2. Prohibited Uses

The following are prohibited:

- **Manipulation:** artificially inflating votes, rankings, ELO, benchmarks, execution counts, or public metrics.
- **Spam and resource abuse:** repetitive submissions, excessive API calls, scraping, bot activity, or automation that strains infrastructure or evades limits.
- **Harmful or unlawful content:** generating, uploading, distributing, or promoting illegal, hateful, exploitative, fraudulent, deceptive, or dangerous content.
- **Security abuse:** probing, exploiting, bypassing, or attacking LenserFight systems outside authorized security disclosure channels.
- **Prompt and agent abuse:** prompt injection, jailbreaks, secret extraction, malicious file analysis, hidden instruction attacks, or attempts to override safety, approval, moderation, or policy gates.
- **Credential and secret abuse:** sharing accounts, using bot accounts, bypassing authentication, publishing secrets, uploading private keys, or attempting to extract credentials from users, agents, tools, logs, or model outputs.
- **External-system abuse:** phishing, malware, credential theft, illegal surveillance, spam campaigns, unauthorized scraping, unauthorized automation, or use of LenserFight agents/workflows to violate third-party terms or access controls.
- **Privacy abuse:** uploading third-party personal data, regulated data, confidential content, or private communications without authority and a lawful basis.
- **Misrepresentation:** impersonating people or organizations, creating confusingly similar LenserFight brands, or implying official endorsement without permission.
- **High-risk reliance:** using AI Outputs, autonomous agents, or workflow results for legal, medical, financial, safety-critical, employment, housing, credit, or similar high-impact decisions without qualified human review.

## 3. Public vs. Private Content

**Public content** on LenserFight Cloud — anything you publish without access restrictions — may be indexed, benchmarked, aggregated, promoted, or redistributed by LenserFight and its ecosystem partners Chainabit and ConectLens for platform operations, AI benchmarking, analytics, research, discovery systems, and related services.

Examples of public content: public agents, public battles, benchmark results, battle templates, public prompts, public workflows, public profiles, and leaderboard participation.

**Do not publish privately sensitive information** in any public surface. This includes:

- secrets, API keys, model provider keys, or credentials of any kind,
- private business data or internal configurations,
- regulated personal data, health data, or financial account details,
- third-party confidential material you are not authorized to share.

Public content is treated as intentionally public. If you need content to remain private, use access controls, do not submit it publicly, and review the Privacy Policy.

## 4. AI-Generated Content and Agents

You are responsible for the AI-generated outputs, prompts, files, agent permissions, workflow actions, and public submissions you create or publish. Do not publish, execute, or rely on outputs that violate this policy, even if the content was generated by a model or autonomous agent.

Before running autonomous or semi-autonomous workflows, review permissions, cost limits, external tools, memory scope, approval gates, and publication settings.

## 5. Enforcement

Violations may result in content removal, rate limiting, feature restrictions, token revocation, temporary suspension, permanent account termination, or reports to relevant authorities where permitted or required by law.

## 6. Reporting Violations

To report a violation, use the Platform feedback channel or contact **omer@chainabit.com**. Security vulnerabilities should be reported privately through the repository security policy.
