Lyra Social Group — Legal & Community Hub (LSC-TOS)
Welcome to the central governance and legal repository for Lyra Social Group (LSG). This repository serves as the definitive, single-source-of-truth for all binding Terms of Service, privacy disclosures, operational frameworks, and community conduct standards governing our digital footprint.
All policies maintained within this repository apply universally across all digital assets, community spaces, and software tools operated under the Lyra Social Group umbrella—including, but not limited to, the Lyra Community Hub / Lyra Cuck HQ (LCH) Discord infrastructure, virtual reality instances (such as VRChat community worlds and groups), dedicated multiplayer game servers, custom automation utilities (e.g., HOLY MOLY BOT), and web applications—unless explicitly superseded by a domain-specific policy document.
🏛 Framework & Governance Overview
Our documentation ecosystem is constructed to provide legal transparency, operational clarity, and robust safety protections for our community members, creators, staff members, and third-party contributors.
Every policy in this repository operates under a unified hierarchy:
| Level | Authority | Responsibility |
|---|---|---|
| 1 | Administrative Parent | Lyra Social Group Administration acts as the primary governing entity, license holder, and legal maintainer. |
| 2 | Operational Community Environments | Lyra Community Hub / LCH represents the core user-facing digital spaces where these policies are actively enforced day-to-day. |
| 3 | Automated Infrastructure | Integrated bots, API endpoints, and monitoring services process minimal telemetry strictly in service of enforcing these policies and maintaining service availability. |
📜 Complete Document Index & Directory Structure
LSC-TOS/
├── tos/ # Binding legal terms and user service agreements
├── privacy/ # Telemetry disclosures, retention rules, and privacy policies
├── community/ # Member conduct guidelines, moderation standards, and appeals
├── governance/ # Ethical frameworks and operational mandates for staff
└── [root] # Administrative guidelines, security protocols, and repo metadata
1. Terms of Service (tos/)
Legal agreements defining the contractual relationship, service limitations, and intellectual property conditions between users and Lyra Social Group.
Discord Terms of Service
Comprehensive terms governing:
- Account access
- Code of conduct
- Service usage across Discord servers
- Connected community hubs
HOLY MOLY BOT Terms of Service
Operational rules governing:
- Command rate-limits
- Data access scope
- Acceptable use mandates
- Proprietary automation bot usage
Contributor Agreement
Defines:
- Intellectual property rights
- Code submission terms
- Art submission terms
- Documentation contribution rules
- Licensing frameworks for contributors
2. Privacy & Data Protection (privacy/)
Disclosures outlining how user data is:
- Collected
- Processed
- Minimized
- Stored
- Deleted
Across all platforms.
Global Privacy Policy
High-level privacy notice detailing:
- Data collection practices
- User rights
- Access requests
- Data erasure requests
- Third-party data handlers
Data Retention Policy
Defines:
- Operational data lifecycles
- Automated log rotation intervals (14–30 days)
- Telemetry purge routines
- Formal data deletion request channels
3. Community Standards & Operational Rules (community/)
Public-facing standards establishing:
- Expected member behavior
- Event protocols
- Safety enforcement mechanisms
Community Guidelines
Defines:
- Core behavioral expectations
- Harassment prohibition
- Age-gating requirements
- Decorum rules
- Text channel standards
- Voice channel standards
- VR interaction standards
Moderation Policy
Defines:
- Progressive discipline framework
- Warning tier thresholds
- Emergency intervention protocols
- Staff enforcement boundaries
Appeals Policy
Defines:
- Eligibility windows
- Mandatory 14-day post-action waiting period
- Non-appealable zero-tolerance violations
- Formal review procedures
Event Policy
Defines:
- Safety guidelines
- Host responsibilities
- Streaming permissions
- Participant etiquette
- Public event requirements
- Private event requirements
Verification Policy
Defines:
- Access tier requirements
- Age screening protocols
- Identity screening protocols
- Automated raid-defense mechanisms
- Manual vetting processes
Creator Guidelines
Defines:
- Streamer standards
- Video producer requirements
- Artist expectations
- Influencer standards
- Media capture requirements within LSG spaces
4. Governance & Staff Standards (governance/)
Internal operational codes ensuring:
- Transparency
- Accountability
- Ethical conduct
Among leadership and moderation team members.
Staff Code of Conduct
Defines:
- Staff neutrality
- Conflict of interest handling
- Privacy obligations
- Administrative transparency
- Disciplinary measures for staff abuse
📌 Document Metadata Standard
Every Markdown document contained within this repository must include the following YAML front matter block:
---
Document: <Document Title>
Version: 1.0.0
Effective Date: 2026-08-05
Last Updated: 2026-08-05
Maintainer: Lyra Social Group Administration
Contact: LEGAL@LYRAFOXWOOD.APP
---
Metadata Field Specifications
| Field | Description |
|---|---|
| Document | The formal title of the policy or specification. |
| Version | Semantic versioning code (MAJOR.MINOR.PATCH). |
| Effective Date | The calendar date (YYYY-MM-DD) on which the policy version actively takes effect. |
| Last Updated | The calendar date (YYYY-MM-DD) of the most recent revision. |
| Maintainer | The internal body or department responsible for updating and reviewing the document. |
| Contact | The designated email address or channel for inquiries related specifically to that document. |
Semantic Versioning Rules
MAJOR
Used for:
- Structural policy overhauls
- Fundamental legal changes
MINOR
Used for:
- Operational updates
- Clarified rules
- Added sections
PATCH
Used for:
- Typo corrections
- Formatting adjustments
- Link fixes
🛠 Amendment & Revision Lifecycle
Policy updates within this repository follow a structured revision lifecycle to prevent arbitrary enforcement changes.
1. Proposal
Proposed updates or amendments are drafted through Pull Requests following repository contribution guidelines.
2. Administrative & Legal Review
Proposed changes undergo review by the Lyra Social Group Administration to verify:
- Legal soundness
- Operational feasibility
- Community impact
3. Version Bump & Log
Upon approval:
- Document metadata is updated
- Version numbers are increased
- A detailed summary of changes is recorded
4. Community Notice
Major policy updates:
- MAJOR version changes
- MINOR version changes
will be announced through designated community notification channels:
#announcements
At least 7 days prior to taking full effect, except in cases involving:
- Urgent safety concerns
- Legal compliance requirements
- Security emergencies
5. Archive & Legacy Policies (old-tos/)
Historical policy versions retained for audit transparency and legacy references.
- Legacy LCH Terms of Service — Archival terms of service governing historical Lyra Community Hub instances.
- Legacy HOLY MOLY BOT TOS — Prior operational terms and data policies for legacy bot builds.
📧 Central Contact & Support Points
For:
- Legal notices
- Data privacy requests
- Staff conduct escalations
- General inquiries
Please use the appropriate contact point below.
| Purpose | Contact |
|---|---|
| Legal & Privacy Enquiries | LEGAL@LYRAFOXWOOD.APP |
| General Administrative Inquiries | lsg@lyrafoxwood.app |
| Community Support & Tickets | Submit an official administrative ticket through the primary Lyra Community Hub Discord server |