Shared Definitions & Cross-Document Glossary

This file is the single source of truth for terminology, model decisions, and cross-references across all legal documents. Every document in docs/legal/final/ must use these terms exactly as defined here.

Effective date: 2026-03-14 Last updated: 2026-03-14

1. Canonical Defined Terms

2. Contract Model Decision

Model: Intermediary Marketplace

The Operator acts as the platform, moderation, and distribution layer. The Operator is not the seller-of-record for Buyer-facing transactions involving third-party Seller content.

• The Operator controls platform access, moderation, checkout surface, delivery rails, and policy enforcement.
• Sellers are independent providers responsible for the legality, accuracy, and support commitments of their Listings, subject to Marketplace rules.
• The Operator may still make Buyer-facing decisions on takedowns, refunds, trust and safety, and abuse.
• The Buyer's primary contractual relationship for content-specific matters is with the Seller; the Buyer's relationship with the Operator covers platform access, delivery infrastructure, and policy enforcement.

3. Document Hierarchy

When documents conflict, the following priority order applies (highest first):

1. Terms of Service — marketplace-wide rules (highest priority)
2. Refund Policy — purchase disputes and refund eligibility
3. Buyer License — how purchased Skills may be used
4. Seller Terms — Seller obligations to the Operator
5. Listing-specific terms — may supplement only if approved by the Marketplace and shown before purchase (lowest priority; cannot override Terms or Buyer License)

The Privacy Policy, Acceptable Use Policy, and IP/Takedown Policy apply alongside the hierarchy above and are incorporated by reference into the Terms of Service.

4. Cross-Reference Format

When referencing other documents, use this format:

• "See the Privacy Policy for details on data handling."
• "As described in Section [X] of the Terms of Service."
• "Subject to the Refund Policy."

5. Operator Identity Block

Use this template in all documents that require operator identification:

For full contact and business details, see the Legal & Contact Information page.

6. Contact Channels

All documents must reference these contact paths consistently:

At launch, some of these may route to the same inbox. The labels must still be listed separately in each document for clarity and future routing.

7. Retention Periods

All documents referencing data retention must use these periods consistently:

8. Common Clause: Telegram Dependency

All documents that discuss service availability, delivery, or payment should include or reference this language:

The Marketplace relies on Telegram for account authentication, messaging, payment processing (Stars), and delivery channels. The Operator does not control Telegram's infrastructure, terms, or availability. Service disruptions, API changes, Stars rule changes, or bot suspension by Telegram may affect Marketplace operations, including purchase processing, delivery, refund timing, and account access. The Operator will use reasonable efforts to maintain service continuity but cannot guarantee uninterrupted operation of features that depend on Telegram.

9. Style and Formatting Rules

• Use plain, direct language. These are startup launch documents, not corporate legal boilerplate.
• Use "you" for the reader (Buyer/Seller/User) and "we" or "the Operator" for the Marketplace operator.
• Use markdown formatting with clear section numbering.
• Each document starts with: title, effective date, and a one-paragraph plain-language summary.
• Each document ends with: contact information and last-updated date.
• Flag unresolved decisions with > **OPEN QUESTION:** callouts.
• Flag launch blockers with > **LAUNCH BLOCKER:** callouts.