Exhibit a Filed Under Seal  🔗 **Source:** [Exhibit a Filed Under Seal](https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.295.2.pdf) > [!note]+ Document Notes > tags: [wordpress-governance, trademark-infringement, silver-lake-control, discovery-responses, nominative-fair-use, consumer-confusion, wordpress-foundation] > author: Automattic Inc. / Matthew Charles Mullenweg > source: CourtListener RECAP - N.D. Cal. 4:24-cv-06917-AMO > filing_type: exhibit > docket: 295.2 > > # 🏷️ Defendants' Sealed Discovery Responses on WP Engine Trademark "Misuse" Claims > > # 🧭 Table of Contents > - [References](#-references) > - [Summary](#-summary) > - [Main Content](#-main-content) > - [Governance Digest](#-governance-digest) > - [Hypotheses](#-hypotheses) > - [Questions](#-questions) > - [Future Research](#-future-research) > - [Implications](#-implications) > - [Conclusion](#-conclusion) > > # 🔗 References > **Dockets:** 295.2 (sealed exhibit), 51-1 (September 23, 2024 demand letter) > **Rules:** Fed. R. Civ. P. 33(d) (document production in lieu of interrogatory answers) > **Parties:** Automattic Inc., Matthew Charles Mullenweg (responding); WP Engine (propounding) > **Key Date:** February 17, 2026 (counterclaims filing) > > # 📝 Summary > This sealed exhibit contains Automattic and Mullenweg's detailed interrogatory responses explaining their trademark infringement claims against WP Engine. The responses allege that Silver Lake's 2020 takeover triggered WP Engine's shift to more aggressive use of WordPress/WooCommerce marks, including product naming violations and consumer confusion tactics. For WordPress governance, this reveals how trademark enforcement intersects with community platform control and the WordPress Foundation's policy framework. The filing includes extensive document citations and Mullenweg's comprehensive digital footprint disclosure across social media and communication platforms. > > # 📖 Main Content > <!-- deep-read:sections start --> ## 🗒️ Notes **Trademark Infringement Timeline** - Early 2020: Silver Lake assumes control of WP Engine - Alleged immediate shift to calling itself "The WordPress Technology Company" - Partners permitted to use "WordPress Engine" designation - 2021: Product line launches with WordPress in names ("Headless WordPress," "Managed WordPress," "Core WordPress," "Essential WordPress") - Claimed violation of WordPress Foundation Trademark Policy prohibiting WordPress in product names **Consumer Confusion Allegations** - WordPress displayed in near-identical font to WordPress.com - Increased keyword density for search manipulation - Aggressive SEO targeting WordPress/WooCommerce marks - No user-facing disclaimers of non-affiliation - Claims of "frequent and pervasive actual consumer confusion" **Mullenweg Digital Presence Disclosure (Interrogatory 10)** - Social media: X/Twitter (@photomatt), Reddit (u/photomatt), LinkedIn, Bluesky (@ma.tt), Mastodon, Facebook - Email addresses: [email protected], [email protected], [email protected], [email protected], [email protected] - Messaging platforms: X DMs, Telegram, Signal, WhatsApp, iMessage, Facebook Messenger - Slack instances: Automattic Slack, WordPress.org Slack **Document Production** - 80+ documents cited (A8C prefixed identifiers) - Range from A8C00027985 to A8C00680569 - Produced under Fed. R. Civ. P. 33(d) in lieu of detailed answers # 📚 References - WordPress Foundation Trademark Policy - September 23, 2024 Automattic demand letter (Dkt. 51-1) - February 17, 2026 counterclaims filing - Am. Bankers Ins. Co. of Fla. v. Nat'l Fire Ins. Co. of Hartford, 2020 WL 8996760 (N.D. Cal. July 9, 2020) # 🗣️ Paraphrase Automattic and Mullenweg claim that when Silver Lake bought WP Engine in 2020, WP Engine immediately started using WordPress trademarks more aggressively. They say WP Engine began calling itself "The WordPress Technology Company" and let partners call it "WordPress Engine," suggesting official endorsement that didn't exist. By 2021, WP Engine allegedly put "WordPress" directly in product names like "Managed WordPress," which they claim violates the WordPress Foundation's trademark rules. They also accuse WP Engine of making its website look like WordPress.com and stuffing keywords to confuse search engines and customers. Mullenweg disclosed his extensive online presence across major platforms and confirmed he uses multiple email addresses and messaging apps for WordPress-related communications. # 📰 Governance Digest The WordPress trademark dispute reveals deep tensions over who controls the WordPress brand versus the open-source project. Automattic claims WP Engine crossed the line from legitimate use to trademark infringement when Silver Lake took control, suggesting private equity ownership changed WP Engine's relationship with WordPress community norms. The WordPress Foundation's trademark policy becomes a key battleground—can hosting companies use "WordPress" in product names, or does that suggest false endorsement? Mullenweg's digital omnipresence across platforms shows how WordPress leadership operates in the social media age, while the sealed nature of these responses hints at sensitive competitive intelligence. Bottom line: this fight is about whether WordPress trademarks protect an open ecosystem or create barriers to entry. # 🧪 Hypotheses 1. **Silver Lake Trigger Theory**: Private equity control fundamentally altered WP Engine's trademark strategy in measurable ways post-2020 2. **Consumer Confusion Evidence**: Automattic has documented instances of actual customer confusion between WP Engine and WordPress.com services 3. **Foundation Policy Enforcement**: The WordPress Foundation trademark policy serves as enforceable legal boundary, not just guidelines 4. **Search Manipulation Claims**: WP Engine's SEO strategy deliberately targets WordPress brand recognition for competitive advantage 5. **Digital Governance Pattern**: Mullenweg's multi-platform presence reflects modern open-source leadership requiring constant community engagement 6. **Document Scope Theory**: The 80+ cited documents contain quantifiable evidence of WP Engine's trademark strategy evolution # 📊 Methodology The filing's evidentiary basis relies on Fed. R. Civ. P. 33(d) document production strategy, incorporating 80+ specific documents by identifier rather than detailed narrative responses. Mullenweg's responses appear based on personal knowledge of his own digital activities and business observations. The temporal framing around Silver Lake's 2020 investment suggests defendants tracked WP Engine's marketing evolution systematically. Sealed status indicates commercially sensitive competitive intelligence or confidential business information warranting protection from public disclosure. # ❓ Questions - What specific consumer confusion evidence exists in the 80+ cited documents? - How does the WordPress Foundation trademark policy actually define permissible vs. prohibited uses? - Why did Silver Lake's investment allegedly trigger immediate trademark strategy changes at WP Engine? - What role does Audrey Capital (mentioned in case context) play in Mullenweg's financial interests? - How do WordPress.org governance decisions intersect with trademark enforcement priorities? - What constitutes "nominative fair use" boundaries for WordPress hosting companies? # 🔮 Future Research **Litigation Threads**: Consumer survey evidence, WordPress Foundation policy interpretation, Silver Lake due diligence records, comparative analysis of other hosting companies' trademark practices **WordPress Governance**: Trademark policy revision processes, WordPress Foundation independence from Automattic, community input on enforcement priorities, hosting partner program guidelines, plugin directory trademark requirements # 💡 Implications **Practice**: WordPress hosting companies must audit trademark usage against Foundation policies and nominative fair use standards **Policy**: WordPress Foundation faces pressure to clarify trademark boundaries while maintaining open-source accessibility **Security**: Trademark enforcement becomes tool for platform control and competitor exclusion **Education**: WordPress community needs clearer guidance on permissible commercial uses of trademarks **Funding**: Private equity investment in WordPress ecosystem companies may trigger heightened trademark scrutiny and enforcement # 🧠 Learning Styles Assessment **Visual**: Document identifier lists, trademark policy citations **Aural**: Not applicable to written filing **Verbal**: Detailed written responses, legal terminology **Kinesthetic**: Platform-specific username formats, hands-on social media usage **Logical**: Chronological timeline, cause-effect claims about Silver Lake impact **Social**: Multi-platform community engagement, WordPress.org Slack participation **Solitary**: Individual interrogatory responses, personal account disclosures **Naturalistic**: Pattern recognition in trademark usage evolution **Reading Level**: Graduate/professional (legal terminology, complex sentence structure) # 📊 Accessibility Assessment **Text Quality**: Fully text-extractable legal document with clear structure **Organization**: Standard interrogatory response format with numbered questions and detailed answers **Barriers**: Legal terminology, sealed status limits public access, extensive document identifier lists challenging for screen readers **WCAG 2.2 AA**: Meets contrast and structure requirements in digital format, though complex legal language poses comprehension barriers # 🌍 DEIB Assessment **Cultural Breadth**: US legal system context, Silicon Valley private equity dynamics **Inclusive Language**: Standard legal terminology without obvious bias **Neurodiversity Support**: Structured format aids processing, but complex legal concepts create accessibility challenges **Representation**: Corporate litigation between well-resourced technology companies **Psychological Safety**: Adversarial legal context inherently creates defensive positioning # ✅ Logical Validity **Strong Reasoning**: Clear temporal causation claims linking Silver Lake investment to trademark strategy changes, systematic document production approach **Fallacies**: *Post hoc ergo propter hoc* - assuming Silver Lake caused trademark changes without establishing direct causal mechanism; *False dichotomy* - framing trademark use as either completely permissible or completely infringing without acknowledging gray areas **Fixes**: Provide evidence of Silver Lake's explicit directions regarding trademark strategy; acknowledge spectrum of trademark uses and identify specific crossing points **Tone**: Professional legal advocacy with underlying competitive tension # 🛡️ DARVO Analysis **Potential DARVO Elements**: Defendants deny trademark "misuse" terminology while pivoting to accuse WP Engine of infringement (reverse victim-offender); attack WP Engine's private equity ownership as corrupting influence **Counterargument**: Legitimate trademark enforcement and factual timeline documentation rather than manipulation tactics **Assessment**: Mixed - contains defensive denials combined with affirmative infringement claims, but grounded in specific factual allegations rather than pure deflection # 🎯 Conclusion This sealed filing reveals the factual foundation for Automattic's trademark infringement claims, centering on Silver Lake's 2020 investment as the inflection point for WP Engine's allegedly improper trademark usage. The detailed timeline and extensive document production suggest substantial evidence gathering around consumer confusion and WordPress Foundation policy violations. For WordPress governance, this establishes trademark enforcement as a critical lever for platform control, with the WordPress Foundation's policies serving as enforceable boundaries rather than mere guidelines. **Watch next**: Consumer confusion evidence in the cited documents, WordPress Foundation's response to policy interpretation questions, and Silver Lake's role in WP Engine's strategic decisions. # 🧱 Refactor Appendix ## 📚 Literature Atoms > [!quote] "In early 2020, following Silver Lake Technology Management L.L.C.'s ('Silver Lake') assumption of control over WP Engine, WP Engine began to progressively shift how it uses the WordPress and WooCommerce Marks." > [!quote] "In 2021, WP Engine began including WordPress in the names of its product offering with its product lines 'Headless WordPress,' 'Managed WordPress,' 'Core WordPress,' and 'Essential WordPress,' violating the express terms of the WordPress Foundation Trademark Policy, which prohibits the use of the WordPress trademarks in product names." > [!quote] "WP Engine's use of the WordPress and WooCommerce Marks has led to frequent and pervasive actual consumer confusion." > [!quote] "WP Engine's use of the WordPress and WooCommerce Marks goes well beyond the recognized limits of nominative fair use and creates a strong likelihood of confusion." ### 🧠 Permanent Candidates - **Silver Lake Catalyst Theory**: Private equity investment as trigger for trademark strategy changes - **WordPress Foundation Policy Enforcement**: Trademark policies as legally enforceable boundaries - **Consumer Confusion Documentation**: Systematic evidence gathering of marketplace confusion - **Nominative Fair Use Boundaries**: Legal limits on competitor trademark usage - **Digital Governance Footprint**: Multi-platform presence requirements for open-source leadership ## ✏️ Fleeting Queue - Connection between Audrey Capital and trademark enforcement motivations - WordPress.org Slack governance implications - Sealed document commercial sensitivity thresholds - Private equity due diligence and trademark compliance - WordPress Foundation independence questions raised by enforcement patterns <!-- deep-read:sections end --> 📄 **Full text:** ![[Full Document Contents/Articles/Exhibit a Filed Under Seal.md|Exhibit a Filed Under Seal by storage.courtlistener.com]] ## Highlights - Subject to and without waiver of the foregoing objections, WooCommerce responds as follows: WooCommerce maintains a trademark policy for the WooCommerce Marks that authorizes use of the trademark in plain, non-stylized text to "[t]ruthfully and accurately refer to or describe Automattic's WooCommerce products and services and the WooCommerce open-source software project"; "[r]efer to WooCommerce or Automattic in news and articles"; "[l]ink to [Automattic's] sites"; or "[d]escribe [] compatibility with or support for WooCommerce in certain circumstances." The trademark policy explains that absent a trademark license agreement with Automattic, third parties are not authorized to use the WooCommerce Marks "[i]n a way that suggests that Automattic or WooCommerce has somehow sponsored, endorsed, or is otherwise affiliated with you or your products or services"; "[i]n a way that maligns, disparages or tarnishes Automattic, WooCommerce or their products and services, even if your products and services also happen to be compatible with WooCommerce"; "[i]n a way that trades on the goodwill of the Woo Marks"; or "[i]n advertising and marketing materials." The trademark policy is publicly available at the following webpage: https://woocommerce.com/trademarkguidelines/. ([View Highlight](https://read.readwise.io/read/01ksfvckgs381rsv45h1xamvbz)) - Note: Docket 295.2: WooCommerce trademark policy — permitted nominative uses and prohibitions. - Tags: wp-engine-automattic, legal