License Disclosure | ScripTreeApps

---
title: "License Disclosure Policy"
slug: "license-disclosure"
---

**Effective Date:** 2026-05-09
**Last Updated:** 2026-05-09

> **Not legal advice.** This policy describes how the platform requires producers to disclose what they are selling, and how buyers may rely on those disclosures. It is not a substitute for legal counsel. Producers and buyers should consult their own lawyers about how this policy applies to their specific situation and jurisdiction.

This License Disclosure Policy ("Policy") forms part of the Terms of Service between the platform operator (the "Platform") and producers and buyers using the platform. The Platform reads brand identifiers, support contact, and legal entity information from `branding/branding.config.json`; references in this Policy to "the Platform," "we," and "us" mean the legal entity identified there.

---

## 1. Producer obligation to disclose

Every producer who lists a paid app on the Platform must complete a License Disclosure for each version of the app, before that version can be published.

A complete License Disclosure consists of:

**1.1 Section 1 — What the buyer is paying for.** A one-sentence plain-language statement of what the purchase covers, accompanied by the producer's license selection. The producer must select a license from the curated SPDX list, choose "Custom (proprietary)" and supply the full text of the proprietary terms, or otherwise specify the license that governs the producer-authored code.

**1.2 Section 2 — Bundled software under separate licenses.** A list of every open-source, third-party, or otherwise externally-licensed component that travels inside the app's distribution bundle and that the buyer should be made aware of. Each row must identify the component name, version (where known), license, and (where reasonably available) the license URL and source URL.

**1.3 Auto-fill from bundle metadata.** Where the producer's bundle contains canonical metadata files (`LICENSE`, `LICENSE.md`, `LICENSE.txt`, `COPYING`, `NOTICE`, `THIRD_PARTY_NOTICES.md`, `BUNDLED.md`, or equivalent), the Platform's bundle-scan service will populate the form from those files. The producer is responsible for reviewing and confirming each auto-filled row before publishing the version. The Platform records both the auto-detected value and any subsequent producer edit as part of the disclosure audit trail.

**1.4 Accuracy and good faith.** The producer represents that, to the best of the producer's knowledge after reasonable inquiry, the License Disclosure is accurate at the time of publication. Knowingly false or misleading disclosures may result in listing removal, account suspension, refund liability to affected buyers, and referral to authorities under the laws cross-referenced in §5.

**1.5 Version-locking.** The License Disclosure is bound to a specific app version. Where a new version of the app introduces, removes, or changes a bundled component or the producer's own license, the producer must update the disclosure for that version. Disclosures from prior versions remain available to buyers who purchased those versions.

**1.6 Failure to disclose.** A version of an app whose License Disclosure has not been completed and confirmed cannot be published. The Platform will not enable a "Buy" or "Get free" action on the listing until disclosure is complete.

---

## 2. Buyer rights upon purchase

When a buyer purchases or acquires an app, the buyer is entitled to:

**2.1 Pre-purchase visibility.** A "What you're buying" panel must render on the listing page above the purchase action, presenting both Section 1 and Section 2 in a clear, intelligible form, before the buyer commits to the transaction.

**2.2 Post-purchase persistence.** A copy of the License Disclosure that was in effect at the moment of purchase remains visible to the buyer on the order receipt and the order detail page (under "My Apps") for the lifetime of the order record. Subsequent edits to the disclosure on later versions do not retroactively alter the buyer's record.

**2.3 The licenses themselves.** Where a license is identified by SPDX identifier or URL, the buyer is entitled to read the full text of that license. Where the producer has selected a custom proprietary license, the producer must supply the full text of the proprietary terms, and the buyer is entitled to read the full text before the purchase action is enabled.

**2.4 Bundled-component license texts.** Where Section 2 identifies a bundled component under a copyleft license (or any license whose terms require the license text to travel with the component), the producer must include the license text inside the distribution bundle. The Platform's bundle-scan service flags missing license texts to the producer prior to publication.

**2.5 Right to refund where the disclosure was materially inaccurate.** A buyer who, after purchase, identifies a material discrepancy between the License Disclosure and the actual contents of the bundle (for example: a bundled component not disclosed; a producer-claimed license that differs from the license the bundled component actually carries upstream) may request a refund. The refund-eligibility tie-in is described in §6.

**2.6 No additional rights to bundled OSS.** Purchase of an app does not, on its own, grant the buyer any rights to bundled open-source components beyond what those components' own licenses already provide. Most permissive open-source licenses already permit personal and internal-business use; if the buyer intends to redistribute, fork, or commercialize a bundled component, the buyer must comply with the bundled component's license terms.

---

## 3. Bundled OSS — buyer must comply with each separately licensed component

**3.1 Each bundled component is governed by its own license.** The producer's license (Section 1) covers the producer-authored code only. Every component listed in Section 2 is governed by its own license, as identified in that row. The buyer is responsible for understanding and complying with the terms of each separately licensed component if the buyer's use exceeds what the producer's license alone would authorize.

**3.2 Common scenarios where the bundled-component license matters.** These include, without limitation:

- **Redistribution.** Most copyleft licenses (GPL, LGPL, MPL, AGPL) impose obligations when the buyer distributes the component or a derivative work, including source-code disclosure or attribution requirements.
- **Modification.** Some licenses require the buyer to mark modified versions as such or to release modifications under the same license.
- **Commercial integration.** Some licenses (notably AGPL) impose source-disclosure obligations on network-accessible deployments.
- **Patent and trademark.** Some licenses include explicit grants or reservations of patent and trademark rights; the buyer should not assume those rights extend automatically.

**3.3 The Platform does not provide license-compatibility analysis.** The Platform surfaces what the producer disclosed and what the bundle-scan service detected. The Platform does not warrant that the combination of bundled components and the producer's own license is internally consistent for any particular buyer use. Where the buyer's intended use raises a license-compatibility question, the buyer should consult counsel.

---

## 4. Producer warranty and limitation

**4.1 Producer warranty of accuracy.** The producer warrants to the buyer that the License Disclosure is, to the best of the producer's knowledge after reasonable inquiry, accurate at the time of publication. The producer warrants that the bundled components identified in Section 2 are present in the bundle in the form described, and that the licenses identified are the licenses under which the producer is entitled to redistribute those components.

**4.2 Platform role.** The Platform provides the disclosure surface, the bundle-scan service, the curated SPDX list, and the audit trail. The Platform is not a party to the producer's warranty in §4.1 and does not independently verify the accuracy of every producer disclosure. Where the Platform receives a credible report of a materially inaccurate disclosure, the Platform will investigate under its takedown and dispute-resolution procedures and may remove the listing pending resolution.

**4.3 Limitation.** Except for the warranty in §4.1 and any non-disclaimable statutory warranty (see §5), the producer's License Disclosure is provided "as is" with respect to forward-looking accuracy. License texts referenced by URL are maintained by the upstream license stewards (for example, GNU, Apache Software Foundation, OSI); the producer and the Platform are not responsible for upstream changes to those license texts.

**4.4 Audit trail.** The Platform retains the disclosure entries (auto-detected values, producer edits, and the timestamp of each) for the period specified in the platform Records Retention policy. This audit trail is available to law-enforcement, regulators, and counsel under the conditions described in the Privacy Policy and the Records Retention policy.

---

## 5. Cross-references — applicable law

This Policy is designed to align with the following frameworks. Producers and buyers should consult counsel for jurisdiction-specific applicability.

**5.1 EU Digital Services Act, Article 27 (Recommender system transparency) and Article 14 (Terms-and-conditions transparency).** The Platform must present terms governing the buyer's use of digital content in a clear, plain, intelligible, user-friendly, and unambiguous manner. The pre-purchase visibility requirement in §2.1 and the post-purchase persistence requirement in §2.2 are designed to meet this standard. Article 27 transparency obligations applicable to recommender systems are addressed separately in the Sponsored Placement Policy.

**5.2 EU Digital Content Directive (Directive (EU) 2019/770), Article 8.** For digital content supplied to consumers in the European Union, traders must disclose pre-contractually the main characteristics of the digital content, its functionality (including any technical-protection measures), and any relevant interoperability with hardware and software. Section 1 addresses main characteristics. Cross-references to host-software compatibility on the listing page address interoperability. Where an app ships with no technical-protection measure, the listing states so explicitly; where an app does ship with such a measure, the producer must declare it.

**5.3 Canadian Competition Act, R.S.C. 1985, c. C-34, §52.** A material representation about a product made knowingly or recklessly that is false or misleading in a material respect is an offence. The producer's warranty in §4.1, combined with the audit trail in §4.4, creates a defensible record of the representations made at the time of sale and the basis for those representations.

**5.4 United States Federal Trade Commission Act, §5 (15 U.S.C. §45).** Unfair or deceptive acts or practices in or affecting commerce are unlawful. The auto-detected versus producer-edited distinction surfaced on the buyer-facing disclosure panel is a deception-prevention design choice: a buyer acting reasonably can see whether a disclosure row was extracted from the bundle's own metadata or typed by the producer. The Platform will not soften or remove this distinction for visual-design reasons.

**5.5 Other jurisdictions.** Where the Platform's MVP scope expands to additional jurisdictions, this Policy will be reviewed and (where required) supplemented for local consumer-protection laws. The current jurisdictional matrix is maintained internally by the Platform's compliance team and is reflected in the Terms of Service for each launch market.

---

## 6. Refund eligibility tie-in

A material inaccuracy in a License Disclosure may give the buyer a basis for a refund under the platform Refund Policy. The relationship between this Policy and the Refund Policy is as follows:

**6.1 Self-serve refund window.** During the self-serve refund window described in the Refund Policy (currently 14 days from purchase, sourced from `pricing.config.json`), a buyer may obtain a refund without invoking this Policy. No discrepancy needs to be alleged.

**6.2 Disclosure-based refund after the self-serve window.** Where the self-serve window has expired and the buyer alleges a material discrepancy between the License Disclosure and the bundle as delivered, the buyer may contact support at the address in `branding.config.json` and request a refund under §2.5 of this Policy. The Platform will investigate using the audit trail (§4.4) and the bundle-scan record. Where the discrepancy is verified, the buyer is entitled to a refund regardless of the self-serve window having lapsed.

**6.3 Statutory rights preserved.** Nothing in this Policy or in the Refund Policy purports to limit any non-disclaimable statutory consumer-protection right available to the buyer in the buyer's jurisdiction (including, where applicable, rights under the Ontario *Consumer Protection Act, 2002*, the British Columbia *Business Practices and Consumer Protection Act*, the Quebec *Consumer Protection Act*, the EU Consumer Rights Directive, the US Magnuson–Moss Warranty Act, and equivalents).

The full Refund Policy is available at `/legal/refund` on the storefront.

---

## 7. Changes to this Policy

The Platform may update this Policy from time to time to reflect changes in law, in the disclosure mechanics, or in the curated SPDX list. Material changes will be announced on the storefront and, where the buyer has opted in to such notifications, by email. The "Effective Date" and "Last Updated" fields above record the version of this Policy currently in force; prior versions are retained in the Platform's records-retention archive.

---

## 8. Contact

Questions about this Policy, or reports of suspected disclosure inaccuracies, may be sent to the support address in `branding/branding.config.json`. The Platform maintains an internal triage SLA for license-disclosure reports under its Trust and Safety procedures.

---

## See also

- **Producer Agreement** at `/legal/producer-agreement` — the producer-facing contract that incorporates this Policy as a publishing prerequisite (§3 of that Agreement).
- **Terms of Service** at `/legal/terms` — the buyer-facing contract that recognises producer-published licenses and bundled-OSS obligations (§5 of those Terms).
- **Refund Policy** at `/legal/refund` — how a material disclosure inaccuracy interacts with the refund window.
- **Producer License Disclosure how-to** at `/help/license-disclosure` — practical walkthrough of the form with good and bad examples.

--- title: "License Disclosure Policy" slug: "license-disclosure" --- **Effective Date:** 2026-05-09 **Last Updated:** 2026-05-09 > **Not legal advice.** This policy describes how the platform requires producers to disclose what they are selling, and how buyers may rely on those disclosures. It is not a substitute for legal counsel. Producers and buyers should consult their own lawyers about how this policy applies to their specific situation and jurisdiction. This License Disclosure Policy ("Policy") forms part of the Terms of Service between the platform operator (the "Platform") and producers and buyers using the platform. The Platform reads brand identifiers, support contact, and legal entity information from `branding/branding.config.json`; references in this Policy to "the Platform," "we," and "us" mean the legal entity identified there. --- ## 1. Producer obligation to disclose Every producer who lists a paid app on the Platform must complete a License Disclosure for each version of the app, before that version can be published. A complete License Disclosure consists of: **1.1 Section 1 — What the buyer is paying for.** A one-sentence plain-language statement of what the purchase covers, accompanied by the producer's license selection. The producer must select a license from the curated SPDX list, choose "Custom (proprietary)" and supply the full text of the proprietary terms, or otherwise specify the license that governs the producer-authored code. **1.2 Section 2 — Bundled software under separate licenses.** A list of every open-source, third-party, or otherwise externally-licensed component that travels inside the app's distribution bundle and that the buyer should be made aware of. Each row must identify the component name, version (where known), license, and (where reasonably available) the license URL and source URL. **1.3 Auto-fill from bundle metadata.** Where the producer's bundle contains canonical metadata files (`LICENSE`, `LICENSE.md`, `LICENSE.txt`, `COPYING`, `NOTICE`, `THIRD_PARTY_NOTICES.md`, `BUNDLED.md`, or equivalent), the Platform's bundle-scan service will populate the form from those files. The producer is responsible for reviewing and confirming each auto-filled row before publishing the version. The Platform records both the auto-detected value and any subsequent producer edit as part of the disclosure audit trail. **1.4 Accuracy and good faith.** The producer represents that, to the best of the producer's knowledge after reasonable inquiry, the License Disclosure is accurate at the time of publication. Knowingly false or misleading disclosures may result in listing removal, account suspension, refund liability to affected buyers, and referral to authorities under the laws cross-referenced in §5. **1.5 Version-locking.** The License Disclosure is bound to a specific app version. Where a new version of the app introduces, removes, or changes a bundled component or the producer's own license, the producer must update the disclosure for that version. Disclosures from prior versions remain available to buyers who purchased those versions. **1.6 Failure to disclose.** A version of an app whose License Disclosure has not been completed and confirmed cannot be published. The Platform will not enable a "Buy" or "Get free" action on the listing until disclosure is complete. --- ## 2. Buyer rights upon purchase When a buyer purchases or acquires an app, the buyer is entitled to: **2.1 Pre-purchase visibility.** A "What you're buying" panel must render on the listing page above the purchase action, presenting both Section 1 and Section 2 in a clear, intelligible form, before the buyer commits to the transaction. **2.2 Post-purchase persistence.** A copy of the License Disclosure that was in effect at the moment of purchase remains visible to the buyer on the order receipt and the order detail page (under "My Apps") for the lifetime of the order record. Subsequent edits to the disclosure on later versions do not retroactively alter the buyer's record. **2.3 The licenses themselves.** Where a license is identified by SPDX identifier or URL, the buyer is entitled to read the full text of that license. Where the producer has selected a custom proprietary license, the producer must supply the full text of the proprietary terms, and the buyer is entitled to read the full text before the purchase action is enabled. **2.4 Bundled-component license texts.** Where Section 2 identifies a bundled component under a copyleft license (or any license whose terms require the license text to travel with the component), the producer must include the license text inside the distribution bundle. The Platform's bundle-scan service flags missing license texts to the producer prior to publication. **2.5 Right to refund where the disclosure was materially inaccurate.** A buyer who, after purchase, identifies a material discrepancy between the License Disclosure and the actual contents of the bundle (for example: a bundled component not disclosed; a producer-claimed license that differs from the license the bundled component actually carries upstream) may request a refund. The refund-eligibility tie-in is described in §6. **2.6 No additional rights to bundled OSS.** Purchase of an app does not, on its own, grant the buyer any rights to bundled open-source components beyond what those components' own licenses already provide. Most permissive open-source licenses already permit personal and internal-business use; if the buyer intends to redistribute, fork, or commercialize a bundled component, the buyer must comply with the bundled component's license terms. --- ## 3. Bundled OSS — buyer must comply with each separately licensed component **3.1 Each bundled component is governed by its own license.** The producer's license (Section 1) covers the producer-authored code only. Every component listed in Section 2 is governed by its own license, as identified in that row. The buyer is responsible for understanding and complying with the terms of each separately licensed component if the buyer's use exceeds what the producer's license alone would authorize. **3.2 Common scenarios where the bundled-component license matters.** These include, without limitation: - **Redistribution.** Most copyleft licenses (GPL, LGPL, MPL, AGPL) impose obligations when the buyer distributes the component or a derivative work, including source-code disclosure or attribution requirements. - **Modification.** Some licenses require the buyer to mark modified versions as such or to release modifications under the same license. - **Commercial integration.** Some licenses (notably AGPL) impose source-disclosure obligations on network-accessible deployments. - **Patent and trademark.** Some licenses include explicit grants or reservations of patent and trademark rights; the buyer should not assume those rights extend automatically. **3.3 The Platform does not provide license-compatibility analysis.** The Platform surfaces what the producer disclosed and what the bundle-scan service detected. The Platform does not warrant that the combination of bundled components and the producer's own license is internally consistent for any particular buyer use. Where the buyer's intended use raises a license-compatibility question, the buyer should consult counsel. --- ## 4. Producer warranty and limitation **4.1 Producer warranty of accuracy.** The producer warrants to the buyer that the License Disclosure is, to the best of the producer's knowledge after reasonable inquiry, accurate at the time of publication. The producer warrants that the bundled components identified in Section 2 are present in the bundle in the form described, and that the licenses identified are the licenses under which the producer is entitled to redistribute those components. **4.2 Platform role.** The Platform provides the disclosure surface, the bundle-scan service, the curated SPDX list, and the audit trail. The Platform is not a party to the producer's warranty in §4.1 and does not independently verify the accuracy of every producer disclosure. Where the Platform receives a credible report of a materially inaccurate disclosure, the Platform will investigate under its takedown and dispute-resolution procedures and may remove the listing pending resolution. **4.3 Limitation.** Except for the warranty in §4.1 and any non-disclaimable statutory warranty (see §5), the producer's License Disclosure is provided "as is" with respect to forward-looking accuracy. License texts referenced by URL are maintained by the upstream license stewards (for example, GNU, Apache Software Foundation, OSI); the producer and the Platform are not responsible for upstream changes to those license texts. **4.4 Audit trail.** The Platform retains the disclosure entries (auto-detected values, producer edits, and the timestamp of each) for the period specified in the platform Records Retention policy. This audit trail is available to law-enforcement, regulators, and counsel under the conditions described in the Privacy Policy and the Records Retention policy. --- ## 5. Cross-references — applicable law This Policy is designed to align with the following frameworks. Producers and buyers should consult counsel for jurisdiction-specific applicability. **5.1 EU Digital Services Act, Article 27 (Recommender system transparency) and Article 14 (Terms-and-conditions transparency).** The Platform must present terms governing the buyer's use of digital content in a clear, plain, intelligible, user-friendly, and unambiguous manner. The pre-purchase visibility requirement in §2.1 and the post-purchase persistence requirement in §2.2 are designed to meet this standard. Article 27 transparency obligations applicable to recommender systems are addressed separately in the Sponsored Placement Policy. **5.2 EU Digital Content Directive (Directive (EU) 2019/770), Article 8.** For digital content supplied to consumers in the European Union, traders must disclose pre-contractually the main characteristics of the digital content, its functionality (including any technical-protection measures), and any relevant interoperability with hardware and software. Section 1 addresses main characteristics. Cross-references to host-software compatibility on the listing page address interoperability. Where an app ships with no technical-protection measure, the listing states so explicitly; where an app does ship with such a measure, the producer must declare it. **5.3 Canadian Competition Act, R.S.C. 1985, c. C-34, §52.** A material representation about a product made knowingly or recklessly that is false or misleading in a material respect is an offence. The producer's warranty in §4.1, combined with the audit trail in §4.4, creates a defensible record of the representations made at the time of sale and the basis for those representations. **5.4 United States Federal Trade Commission Act, §5 (15 U.S.C. §45).** Unfair or deceptive acts or practices in or affecting commerce are unlawful. The auto-detected versus producer-edited distinction surfaced on the buyer-facing disclosure panel is a deception-prevention design choice: a buyer acting reasonably can see whether a disclosure row was extracted from the bundle's own metadata or typed by the producer. The Platform will not soften or remove this distinction for visual-design reasons. **5.5 Other jurisdictions.** Where the Platform's MVP scope expands to additional jurisdictions, this Policy will be reviewed and (where required) supplemented for local consumer-protection laws. The current jurisdictional matrix is maintained internally by the Platform's compliance team and is reflected in the Terms of Service for each launch market. --- ## 6. Refund eligibility tie-in A material inaccuracy in a License Disclosure may give the buyer a basis for a refund under the platform Refund Policy. The relationship between this Policy and the Refund Policy is as follows: **6.1 Self-serve refund window.** During the self-serve refund window described in the Refund Policy (currently 14 days from purchase, sourced from `pricing.config.json`), a buyer may obtain a refund without invoking this Policy. No discrepancy needs to be alleged. **6.2 Disclosure-based refund after the self-serve window.** Where the self-serve window has expired and the buyer alleges a material discrepancy between the License Disclosure and the bundle as delivered, the buyer may contact support at the address in `branding.config.json` and request a refund under §2.5 of this Policy. The Platform will investigate using the audit trail (§4.4) and the bundle-scan record. Where the discrepancy is verified, the buyer is entitled to a refund regardless of the self-serve window having lapsed. **6.3 Statutory rights preserved.** Nothing in this Policy or in the Refund Policy purports to limit any non-disclaimable statutory consumer-protection right available to the buyer in the buyer's jurisdiction (including, where applicable, rights under the Ontario *Consumer Protection Act, 2002*, the British Columbia *Business Practices and Consumer Protection Act*, the Quebec *Consumer Protection Act*, the EU Consumer Rights Directive, the US Magnuson–Moss Warranty Act, and equivalents). The full Refund Policy is available at `/legal/refund` on the storefront. --- ## 7. Changes to this Policy The Platform may update this Policy from time to time to reflect changes in law, in the disclosure mechanics, or in the curated SPDX list. Material changes will be announced on the storefront and, where the buyer has opted in to such notifications, by email. The "Effective Date" and "Last Updated" fields above record the version of this Policy currently in force; prior versions are retained in the Platform's records-retention archive. --- ## 8. Contact Questions about this Policy, or reports of suspected disclosure inaccuracies, may be sent to the support address in `branding/branding.config.json`. The Platform maintains an internal triage SLA for license-disclosure reports under its Trust and Safety procedures. --- ## See also - **Producer Agreement** at `/legal/producer-agreement` — the producer-facing contract that incorporates this Policy as a publishing prerequisite (§3 of that Agreement). - **Terms of Service** at `/legal/terms` — the buyer-facing contract that recognises producer-published licenses and bundled-OSS obligations (§5 of those Terms). - **Refund Policy** at `/legal/refund` — how a material disclosure inaccuracy interacts with the refund window. - **Producer License Disclosure how-to** at `/help/license-disclosure` — practical walkthrough of the form with good and bad examples.