# Marketing Compliance Framework {% hint style="warning" %} **MANDATORY COMPLIANCE REQUIRED** This framework establishes mandatory guidelines for all Key Opinion Leaders, content creators, and marketing partners to ensure accurate representation of Tharwa and maintain professional standards. {% endhint %} *** ## 1. Fundamental Principle {% hint style="danger" %} **CRITICAL RULE: Only communicate information that has been officially published by Tharwa.** {% endhint %} If Tharwa has not made an official public statement about a partnership, integration, funding round, or business relationship, it does not exist for communication purposes. *** ## 2. Authorized Information Sources All content must reference only these verified sources: ### Official Channels * **Tharwa Twitter/X:** [@TharwaUAE](https://x.com/TharwaUAE) * **Official Documentation:** [tharwa.gitbook.io](https://tharwa.gitbook.io/) * **Founder Communications:** Saeed Al-Fahim's verified posts * **Head of Community:** Raqib's official communications * **Company Website:** tharwa.finance * **Official Press Releases:** Distributed through authorized channels ### Verification Process Before referencing any information: 1. Confirm it appears on an official Tharwa channel 2. Link directly to the original source 3. Quote accurately without interpretation 4. Maintain full context *** ## 3. Prohibited Communications ### Absolute Prohibitions **Partnership Claims:** * Never announce, imply, or suggest partnerships unless officially confirmed by Tharwa * Do not reference meetings, discussions, or negotiations as partnerships * Avoid language that implies formal business relationships **Institutional Relationships:** * Never claim endorsements from financial institutions, regulators, or government entities * Do not reference meetings as public partnerships * Avoid implying institutional backing or support without official confirmation **Financial Information:** * Do not speculate about funding rounds, valuations, or investment details * Never reference private investor information or funding sources * Avoid claims about financial backing or capital commitments **Product Development:** * Do not announce features, integrations, or launches unless officially confirmed * Avoid speculation about technical partnerships or protocol integrations * Never reference internal roadmaps or development timelines as confirmed plans ### Language Guidelines **Simple Rule:** Only use language that Tharwa has officially used. If Tharwa hasn't said it, you cannot say it. | Phrase | ✅ When You Can Use It | ❌ When You Cannot Use It | | ------------------------------ | ---------------------------------- | ------------------------------------------ | | "Tharwa has partnered with..." | Tharwa announced a partnership | Tharwa has not announced a partnership | | "In collaboration with..." | Tharwa announced collaboration | Tharwa has not announced collaboration | | "Backed by..." | Tharwa announced backing | Tharwa has not announced backing | | "Coming soon..." | Tharwa announced upcoming features | Tharwa has not announced upcoming features | | "Met with..." | Tharwa shared meeting details | Tharwa has not shared meeting details | ### Individual vs. Corporate Meetings {% hint style="danger" %} **CRITICAL DISTINCTION:** Meeting with an individual who works at a company is NOT the same as meeting with the company itself. {% endhint %} | Wrong | Correct | | ------------------------------- | ------------------------------------------------------- | | "Tharwa met with JPMorgan" | "Tharwa met with \[Individual Name]" | | "Tharwa met with Goldman Sachs" | "Tharwa met with \[Individual Name] from Goldman Sachs" | | "Tharwa met with the SEC" | "Tharwa met with \[Individual Name] from the SEC" | **Key Principle:** Always specify the individual's name when referencing meetings. Never imply corporate-level relationships from individual meetings. *** ## 4. Approved Communication Framework ### Factual Reporting Use Tharwa's exact language when available, or "Tharwa has announced/published/stated..." **Example:** "Tharwa has announced plans to integrate LayerZero technology for cross-chain functionality, as detailed in their latest X post." ### Commentary and Analysis Personal analysis clearly separated from facts **Example:** "Based on Tharwa's published roadmap, this development could potentially impact... \[personal opinion clearly marked]" ### Content Amplification Direct sharing with proper attribution **Example:** Reposting official Tharwa content with original context intact and proper source links *** ## 5. Institutional Relationship Guidelines ### All Institutional Entities This applies to any financial institution, corporation, government body, or regulatory entity: **Strict Requirements:** * Never reference meetings or discussions as partnerships * Do not imply institutional endorsement or backing * Avoid suggesting formal business relationships without official confirmation * Never use third-party logos or branding alongside Tharwa content (e.g., don't use JPMorgan logo with Tharwa logo without confirmed partnership) * Do not claim or imply investment, funding, or financial backing from any entity **Approved References:** * Only discuss publicly announced collaborations or relationships * Reference official press releases or joint statements only * Maintain professional distance in language * Focus on Tharwa's technology and value proposition independently * Use factual language: "Tharwa announced..." rather than "partnered with..." ### Government and Regulatory Bodies * Never claim regulatory approval unless officially announced by both parties * Avoid implying government backing, endorsement, or support * Do not reference regulatory discussions or meetings * Focus on Tharwa's compliance-ready approach without claiming official endorsement * Never suggest regulatory partnerships or special relationships *** ## 6. Content Review Requirements ### Pre-Publication Checklist Before publishing any content about Tharwa: **Source Verification:** * [ ] Information sourced from official Tharwa channels only * [ ] Direct links to original sources included * [ ] No speculation or interpretation presented as fact * [ ] No unauthorized partnership or relationship claims **Language Review:** * [ ] Professional, factual tone maintained * [ ] No prohibited language used * [ ] Clear distinction between facts and personal opinion * [ ] Proper attribution and disclaimers included **Institutional Sensitivity:** * [ ] No unauthorized institutional references * [ ] No partnership implications without confirmation * [ ] No use of third-party branding or logos * [ ] Professional boundaries maintained ### Optional Review Service **Content Review:** We offer optional content review for creators who want to ensure their content meets our guidelines before publication. **Contact for Review:** * **Email:** * **Discord:** Submit ticket in [Tharwa Discord](https://discord.gg/gn9htPaF9v) * **Response Time:** 24-48 hours for standard content, 4-6 hours for time-sensitive material *** ## 7. Violation Consequences {% hint style="warning" %} **Simple Process:** If unauthorized claims are made, we will ask the content creator to remove or amend the content. If they fail to do so, we may seek legal action for misrepresentation. {% endhint %} ### Required Actions If unauthorized claims are made: 1. **Remove or Amend:** Content must be corrected or removed immediately upon notification 2. **Compliance:** Failure to comply may result in legal action for misrepresentation *** ## 8. Emergency Communication Protocol ### Crisis Situations If you become aware of misrepresentation or false claims about Tharwa: **Immediate Response (Within 1 Hour):** * Contact Tharwa team immediately * Do not engage with or amplify the misinformation * Document the source and extent of misinformation * Await official response guidance **Contact Information:** * **Standard Reporting:** or [Discord ticket](https://discord.gg/gn9htPaF9v) * **Emergency Escalation:** DM [@alfahimsa](https://x.com/alfahimsa) on X/Twitter or LinkedIn ### Damage Control * Follow official Tharwa response guidance only * Do not attempt independent damage control * Coordinate all responses through official channels * Maintain professional communication standards *** ## 9. Key Contacts ### Primary Contacts * **General Inquiries & Content Review:** * **Partnerships & Compliance:** * **Community Management:** [@Raqib\_Tharwa](https://x.com/Raqib_Tharwa) ([Discord](https://discord.gg/gn9htPaF9v)) * **Technical Questions:** Reference GitBook documentation first * **Emergency/Compliance Issues:** [@alfahimsa](https://x.com/alfahimsa) (Founder Saeed Al-Fahim) ### Response Times * **Standard Inquiries:** 24-48 hours * **Content Review:** 4-24 hours depending on complexity * **Emergency Issues:** 1-4 hours * **Compliance Concerns:** Immediate escalation *** ## 10. Summary Checklist **Before Every Post About Tharwa:** * [ ] Information verified from official sources only * [ ] No partnership or institutional claims without confirmation * [ ] Professional language without speculation * [ ] Proper attribution and source links included * [ ] No prohibited language or implications used * [ ] Content reviewed if high-risk or institutional-related **Remember:** Your role is to accurately amplify Tharwa's official communications, not to create new narratives or make unauthorized claims. When in doubt, ask for clarification rather than risk misrepresentation. *** **Document Version:** 1.0\ **Last Updated:** October 5, 2025\ **Next Review:** Quarterly\ **Mandatory Compliance:** All KOLs and marketing partners For questions or clarifications: --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://tharwa.gitbook.io/tharwa/brand-and-compliance/marketing-compliance-framework.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.