> For the complete documentation index, see [llms.txt](https://partnership-voxel-eng.gitbook.io/partnership-voxel-eng-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://partnership-voxel-eng.gitbook.io/partnership-voxel-eng-docs/content-policy.md). # Content Policy The Content Policy defines the requirements for video materials submitted by participants in the VOXEL Partner Program. All creators must comply with these rules, as well as with the policies of the platforms where the content is published. Violation of this Policy may result in reward denial, temporary suspension, or complete removal from the Program. *** ## **1. General Content Requirements** #### **1.1. Originality** All content must be original and created by the participant. #### **1.2. Relevance** Videos must be related to VOXEL products and the VOXEL ecosystem. #### **1.3. Legal Compliance** All content must comply with the laws and regulations of the participant’s country. #### **1.4. Intellectual Property** Publishing materials that violate third-party rights is strictly prohibited. #### **1.5. VOXEL Mention** Each video must include an explicit VOXEL mention, such as: * logo, * app interface, * verbal mention, * on-screen text reference. *** ## **2. Prohibited Content** The following categories of content are strictly prohibited: ### **2.1. NSFW and Adult Material** * pornography, sexual acts, erotic content; * explicit or revealing imagery; * fetish content. ### **2.2. Violence and Harmful Behavior** * real scenes of violence; * threats of physical harm; * promotion of weapons, terrorism, or dangerous actions. ### **2.3. Political and Ideological Content** * support of political parties, candidates, or elections; * discussion of political conflicts; * activism, propaganda, or calls for political participation. ### **2.4. Toxicity and Harmful Conduct** * insults, humiliation, bullying; * discrimination (race, gender, religion, etc.); * provocation, hate speech; * misleading or manipulative information. ### **2.5. Fraud, Scams, and Manipulation** * “get-rich-quick” schemes, pyramids, HYIP; * false or exaggerated earning claims; * selling or advertising illegal goods/services; * impersonating official VOXEL channels. ### **2.6. Use of Third-Party Content** * reuploads of existing videos; * uploading content without permission from the owner; * copyrighted materials (music, movies, streams) without proper rights. *** ## **3. Acceptable Content Conditions** #### **3.1. Allowed Content Types** The following are acceptable when compliant with this Policy: * gameplay demonstrations; * reviews, guides, tutorials; * IRL content; * challenges, reactions, comparisons. #### **3.2. Accuracy** Content must accurately and truthfully represent VOXEL features. #### **3.3. Use of Third-Party Materials** Music, photos, or videos may be used only if the participant holds the rights or if the materials are royalty-free. #### **3.4. Integrations** Third-party integrations are allowed as long as they do not violate platform policies. *** ## **4. Transparency & Disclosure Requirements** #### **4.1. Disclosure of Partnership** Where required by law, creators must indicate the nature of the partnership (e.g., “Partner Content”). #### **4.2. Accuracy of Information** It is prohibited to distort information about VOXEL, VCOIN, mechanics, or in-game features. #### **4.3. Income Claims** Any earning-related messaging must be honest, balanced, and non-manipulative. **Example of an acceptable disclaimer:** > “Earnings depend on user activity and are not guaranteed.” *** ## **5. Content Quality Requirements** #### **5.1. Technical Standards** Content must meet the following minimum standards: * clear, understandable audio; * no aggressive flashing effects (for epilepsy safety); * correct aspect ratio. #### **5.2. Minimum Duration** If applicable: * Shorts / Reels / TikTok: **minimum 3 seconds**; * YouTube Videos: **minimum 10 seconds**. *** ## **6. Anti-Fraud & Artificial Traffic Policy** #### **6.1. Prohibited Practices** * buying views, likes, or followers; * device farms and automated tools; * VPN usage to manipulate geolocation; * participation in engagement groups. #### **6.2. VOXEL Rights** VOXEL may: * request analytics screenshots; * conduct manual traffic verification; * reduce or cancel rewards in cases of suspicious activity. *** ## **7. VOXEL Moderation Rights** #### **7.1. VOXEL Reserves the Right to:** * hide, restrict, or reject content; * request corrections or re-uploads; * pause the participant’s access to the Program. #### **7.2. Final Decision** All moderation decisions are final. *** ## **8. Participant Responsibilities** The participant bears full responsibility for: * the content they publish; * compliance with local laws; * adherence to platform policies; * correct and lawful use of the VOXEL brand; * accuracy and honesty of information presented. *** ## **9. Policy Updates** VOXEL may update the Content Policy to comply with platform rules, legal requirements, or internal standards. All updates take effect upon publication as of **28.11.2025**. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://partnership-voxel-eng.gitbook.io/partnership-voxel-eng-docs/content-policy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.