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
| Term | Definition |
|---|---|
| Operator | The legal entity or sole proprietor that operates the Marketplace, identified on the Legal/Contact page. At launch, this is ФОП Крючков Костянтин Андрійович, registered/operating in Ukraine. |
| Marketplace | The digital platform operated by the Operator for listing, discovering, purchasing, and delivering Skill Bundles, accessible through the Website, Telegram Bot, and Mini App. |
| Website | The Operator's public web application at forgedemy.org. |
| Telegram Bot | The Operator's Telegram bot at @forgedemy_bot, used for purchases, delivery, support, and account linking. |
| Mini App | The Telegram Mini App interface embedded within the Telegram Bot. |
| Seller (also "Publisher") | A person or entity that uploads, publishes, and distributes Listings through the Marketplace under the Seller Terms. |
| Buyer | A person or entity that browses, purchases, downloads, or uses Skill Bundles through the Marketplace. |
| User | Any person who accesses or uses the Marketplace, including Buyers, Sellers, and visitors. |
| Listing | A published entry on the Marketplace describing a Skill Bundle, including its title, description, screenshots, metadata, pricing, compatibility claims, and license type. |
| Skill Bundle (also "Skill") | A digital package distributed through the Marketplace, which may include code, prompts, manifests, configuration files, installation instructions, documentation, and related operational materials. |
| Entitlement | A record in the Marketplace system confirming that a Buyer has acquired lawful access to a specific Listing and its associated Skill Bundle. |
| Delivery | The process by which a Buyer receives access to a purchased Skill Bundle. Delivery is considered complete when the Entitlement is created and the Buyer has been provided with a working download link, archive, or installation instructions. |
| Telegram Stars (also "Stars" or "XTR") | The virtual currency used within Telegram for digital goods purchases. Stars are purchased through Telegram and governed by Telegram's own terms. |
| Refund | The return of Telegram Stars to a Buyer's account through the Telegram refundStarPayment API, subject to the Refund Policy and Telegram's technical constraints. |
| Third-Party Materials | Any code, libraries, assets, prompts, documentation, or other materials included in a Skill Bundle that are owned by parties other than the Seller, including open-source components. |
| Open-Source Components | Third-Party Materials distributed under recognized open-source licenses (e.g., MIT, Apache 2.0, GPL, AGPL, MPL). |
| Modification | Altering, adapting, reconfiguring, or extending a Skill Bundle so that the result still depends on a substantial portion of the original Bundle to function. |
| Derivative Work | A new, independently functional skill or product that was partly derived from a purchased Skill Bundle but can function without any substantial portion of the original. |
| Output | Work product (text, code, reports, images, etc.) generated by a Buyer using a Skill Bundle as a tool, as distinct from the Skill Bundle itself. |
| Internal Use | Use by the Buyer (or the Buyer's single employing/owning legal entity) for its own internal personal or business workflows, excluding public redistribution, resale, or sublicensing. |
| Manifest | A structured file within a Skill Bundle listing its components, dependencies, required permissions, and third-party license information. |
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):
- Terms of Service — marketplace-wide rules (highest priority)
- Refund Policy — purchase disputes and refund eligibility
- Buyer License — how purchased Skills may be used
- Seller Terms — Seller obligations to the Operator
- 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:
| Field | Detail |
|---|---|
| Operator | ФОП Крючков Костянтин Андрійович (trading as Forgedemy) |
| Operating form | FOP (sole proprietorship under Ukrainian law) |
| Country | Ukraine |
| Registration number / ІПН / ЄДРПОУ | 3478909918 |
| Address | Odesa, Ukraine |
| Website | forgedemy.org |
| Telegram Bot | @forgedemy_bot |
| IBAN | UA673220010000026001310045384 |
For full contact and business details, see the Legal & Contact Information page.
6. Contact Channels
All documents must reference these contact paths consistently:
| Purpose | Channel | Label in documents |
|---|---|---|
| General support | [email protected] | "Support" or "General Support" |
| Payment/refund issues | [email protected] (subject: Payment) | "Payment Support" |
| Privacy/data requests | [email protected] | "Privacy Contact" |
| Abuse/IP/takedown | [email protected] | "Abuse/IP Contact" |
| Legal notices | [email protected] | "Legal Contact" |
| Telegram support | t.me/latand | "Telegram Support" |
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:
| Data category | Retention period |
|---|---|
| Interest/onboarding requests | Until handled + up to 12 months for follow-up |
| Account and entitlement data | While active + 3 years after account closure |
| Payment and purchase records | Longer of 5 years or applicable statutory limitation period |
| Reviews and listing history | While listing is live + 12 months after removal |
| Seller uploads and moderation records | While listing is active + 12 months after removal/closure |
| Logs and security data | 90-day rolling window (unless extended for investigation/legal hold) |
| Device-side storage (localStorage token) | Until user clears browser storage or token is overwritten |
| Evidence from IP/takedown complaints | 3 years after final resolution |
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.