Terms of Service
Feature Detail
Description
The Terms of Service page defines the contractual framework governing organizations' use of the Meander platform. Published on the Sales Website as a pre-sales reference, it allows legal and procurement reviewers to evaluate usage terms, liability limitations, IP ownership, and termination conditions before entering a subscription. The page is a static versioned document with a visible effective date and revision summary, linked from the footer and all commercial call-to-action touchpoints across the Sales Website.
Sources & reasoning
'Vilkår' in the Fase 1 MVP scope for the Sales Website translates directly to Terms of Service. Also listed explicitly in the Product 4 description. Both references confirm MVP target release mapping via phase 1 ordinal position.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
Terms of Service create the enforceable legal framework for platform use before any subscription agreement is signed. For prospective organizations with formal procurement workflows - typical of Norwegian non-profits receiving Bufdir funding - the ability to review standard terms asynchronously before a sales call eliminates last-minute contract surprises and reduces cycle length. Published ToS also signal commercial maturity and institutional readiness, which is critical when selling to regulated organizations that must justify technology expenditures to boards and government funders.
Implemented as a static page on the Sales Website with no backend dependency. Content authored offline by legal counsel and integrated as markdown or MDX at build time. The page must carry a visible version date and brief change-log summary so organizations can track revisions. Linked from the global footer, demo booking confirmation page, and any pricing or sign-up call-to-action. Norwegian Bokmål primary; English translation is optional for Phase 1. Updates require legal sign-off followed by a new static build. No authentication, no database, no shared runtime with operational products.
Components (45)
Shared Components
These components are reused across multiple features
Service Layer (11)
Data Layer (23)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.