Repository navigation
docs(legal): add the Terms of Service and Payment Terms, make the license a license only - #2392
Merged
Merged
Conversation
…s, make the license a license only [preview:none] TERMS.md is the agreement for the hosted service, OpenMSP and the website. PAYMENT-TERMS.md is the payment terms draft with the owner's decisions applied. LICENSE.md v1.1 drops the acceptable use, OpenMSP and website clauses, which now live in the Terms. The three files carry no effective date yet, so the website does not publish them: the date is set when billing matches what the Payment Terms promise. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s in the terms [preview:none] Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
HELD: do not merge until billing matches what the Payment Terms promise
What
TERMS.md(new): the Terms of Service for OpenFrame SaaS, OpenMSP and the website: accounts, the services and AI features, acceptable use, customer data, community content, confidentiality, liability cap, suspension and termination, governing law.PAYMENT-TERMS.md(new): the payment terms draft as its own document, with the owner's decisions applied: saved card charged automatically, purchased tokens kept on cancel until their 12-month expiry, cancel at period end on every plan, suspension 30 days overdue and termination 60 days later, optional monthly limit on automatic top-up, no notice when a model is added or removed.LICENSE.mdv1.1: a license only. The acceptable use, OpenMSP and website clauses (5.4, 6.2, 6.3) move to the Terms, and "it serves as both the License and the Terms of Use" is removed. The README badge and the introduction name v1.1.Why it is held
The Payment Terms describe the target product. Not built yet: suspension and termination, billing emails, the 12-month token expiry (config unset), the auto top-up monthly limit, refund and chargeback handling, card-on-file collection, pay-as-you-go cancel at period end.
Safety
The three files carry an empty
**Effective date:**. The website publishes a legal file only when it states its version and effective date, so these are not published even if this is merged by accident. Publishing them is one edit: set the dates.Before merging
Change-Set: feat-legal-docs-pipeline
Depends-On: #2391
ClickUp task: CU-17tkuw5x9wh Legal documents: split license from Terms of Service, add payment terms, review privacy policy, one pipeline for all legal files
🤖 Generated with Claude Code
Change set
flamingo-stack/openframe-oss-lib#2665: these pull requests are one change, reviewed together.Linked work
Linked by the
Depends-On/Change-Setlines in these descriptions; this block is maintained by the hub.