> ## Documentation Index
> Fetch the complete documentation index at: https://docs.openpage.fun/llms.txt
> Use this file to discover all available pages before exploring further.

# Official Community Guidelines

> To maintain trust, clarity, and authenticity across our platform, we have established the following guidelines for what qualifies as an **Official Community**. 

## 1. Definition of an Official Community

An **Official Community** is any page or domain that represents:

* A real-world organization, company, or public figure.
* A widely recognized product, initiative, or community.
* A project directly affiliated with or endorsed by the actual entity it claims to represent.

***

## 2. Name and Domain Restrictions

* Users **may not claim domain names or page titles** that could mislead others into believing they represent an official project unless they have **rightful affiliation or permission**.
* This includes names of major brands, government organizations, popular open-source projects, and other high-profile entities.

> **Examples of restricted names** (unless verified):\
> `/google`, `/nasa`, `/python`, `/microsoft`, `/unicef`

***

## 3. No Name Squatting

* We **do not allow squatting** on official-sounding names with the intent to block others, resell access, or impersonate.
* Creating a page with a well-known name without legitimate ties to that name may result in the **removal or reassignment** of that domain/path.

***

## 4. Community Pages Must Be Clearly Labeled

* If you are building an **unofficial fan or community page**, you must make this **clear in both the name and description**.
* Avoid using logos, branding, or names that could be confused with the official project.

### ✅ Acceptable:

* `/python-community`
* `/fans-of-nasa`
* `/unofficial-minecraft`

### ❌ Not acceptable:

* `/python`
* `/nasa`
* `/minecraft`\
  *(unless officially affiliated)*

***

## 5. We Reserve the Right to Reclaim Domains

* We reserve the right to **reclaim or reassign any page or domain name** that conflicts with these guidelines.
* This includes situations where a verified or official representative requests control over their rightful domain.

***

## 6. Verification

* Official projects may request **verification status** to distinguish themselves from unofficial communities.
* Verification may require documentation, a domain-based email, or other proof of affiliation.

### Verified Subscription Tier

We offer a **"verified" subscription tier** for communities that meet our official status criteria:

* **Official Badge**: Verified communities receive a distinctive badge that clearly identifies them as officially recognized.
* **Internal Review Process**: All verification requests undergo thorough internal review based on these community guidelines.
* **Eligibility Requirements**: Applicants must demonstrate legitimate affiliation with the entity they represent and comply with all guidelines outlined above.
* **Ongoing Compliance**: Verified status may be revoked if a community no longer meets our guidelines or misrepresents their official status.

To apply for verified status, communities must provide appropriate documentation and evidence of their official standing.

***

By following these guidelines, we aim to foster a platform that is trustworthy, transparent, and fair to everyone—official and community creators alike.

<Note>
  If you're unsure whether your project qualifies as official, or how to represent your community appropriately, feel free to contact us.
</Note>