WestCoast Charts Premium — Commercial Licence Terms

1. Seller, customer and order

The seller is WestCoast Software (Inh. Peter Kannengießer) (“WestCoast Software”, “we” or “us”).

• Business/postal address: Dorfstraße 19, 25764 Hellschen-Heringsand-Unterschaar, Germany
• Email: service@pekagi.io
• Terms version: 2026-10-27.2

This offer is exclusively for customers acquiring WestCoast Charts Premium in the course of their business or independent professional activities (“you” or “the Customer”), not consumers. Provide the purchasing business identity and billing details when ordering. The person placing the order must be authorised to act for that business. The purchasing organisation, selected plan, included developer seats, annual fee, paid term and, where relevant, the named licensed product are recorded in the order confirmation.

An individually agreed arrangement takes precedence over these standard terms, including where no written form is legally required. These terms do not cancel or narrow rights already granted under a licence that accompanied previously supplied code.

German and English versions are available. Before payment, choose the contractual language shown in Checkout. The selected language and terms version are recorded with your order. Both versions describe the same rights and obligations; changing the website display language later does not change an existing contract. Neither translation silently replaces the version accepted for an existing order. Statutory rules on interpretation and ambiguous standard terms remain unaffected.

2. What the licence covers

“Premium” means the commercially supplied distribution, additional licence rights, licence delivery, updates and support for the WestCoast Charts release identified in your order and its accompanying file-level licence manifest (premium/FILE-LICENSES.json). The exact commercially marked artifacts and their relationship to MIT source are described in premium/README.md. The initial offering covers the full Premium library: all thirteen chart families and their advanced compositions, including Quint Timeline, Quint Convergence, Vitals Clock and Practice Schedule.

The initial major-version scope is WestCoast Charts 1.x, as identified in the order and release documentation. During an active paid term, you may obtain and use updates that we make available within that scope. This is not a promise of a particular release schedule or of delivery of a future feature.

WestCoast Charts Free Core and components supplied under the MIT licence retain that licence, including its permission for commercial use. Their copyright and licence notices must be retained as required by the applicable licence. These commercial terms do not relicense MIT code or impose Premium fees on its independent use. All JavaScript sources under src/premium and types/premium.d.ts carry MIT notices, and their existing MIT grants remain in force, including when that code is included in a commercially marked bundle. A commercial banner does not extinguish those independent rights. The seat, product, term and redistribution limits below govern the additional purchased commercial rights and services only; they do not restrict independently licensed MIT use, modification or redistribution. Third-party components retain their accompanying licences.

The release contains nine families in the main Premium bundle, Quint Timeline and Quint Convergence in layers/quint, Vitals Clock in layers/vitals, and Practice Schedule in layers/schedule. The wave-ring, matrix-core and network-facet modules are included compositions. The manifest lists the three shipped Premium main formats and eighteen optional module formats; MIT declarations remain separate. A marketing family name does not change a file's existing licence.

3. Plans and permitted use

For the paid term, we grant you a non-exclusive licence to use and integrate Premium within the plan scope below, subject to the developer-seat allowance and named organisation/product recorded in your order.

Plan	Annual net fee	Included developer seats	Permitted scope
Premium Internal	€349	1	One organisation; unlimited internal applications. Each developer working directly with Premium needs a seat.
Premium SaaS	€990	3	One named customer-facing product hosted by one organisation. Includes internal use and unlimited tenants, end users, and production or staging domains for that product.
Standard OEM	€2,490	5	One named product distributed by one organisation for customers to install or host. Unlimited end-user installations within that product scope; no per-installation royalty.

A developer seat covers a person working directly with Premium in the licensed applications or product. Ordinary users of your finished application do not need developer seats. The included seat count does not limit the number of permitted end users.

Internal applications under the Internal plan are for use within the purchasing organisation. Hosting a customer-facing service requires SaaS scope; supplying a product for customers to install or host requires OEM scope.

SaaS scope permits serving the integrated Premium functionality to users of the named hosted product. Standard OEM scope permits supplying Premium as an integrated part of the named finished product and permitting those customers to run that product. It does not grant those customers an independent right to extract and reuse Premium as a chart library in their other products.

These standard plans do not include redistribution of Premium as a standalone library, SDK or chart-building toolkit. Third-party white-labelling, affiliate rights, broader sublicensing and other custom redistribution arrangements require an expressly agreed separate scope. This does not restrict rights independently available under MIT or another applicable licence.

Additional products, seats or custom rights must be confirmed in an order covering them. Contact us to discuss a separate arrangement before expanding beyond your recorded scope.

4. Price, payment and delivery

Prices are in euro, exclusive of VAT where applicable. The applicable tax and total payable amount are shown before payment. The plans are billed annually in advance.

The initial paid term and subsequent renewal periods are recorded in your order and invoices. By submitting the paid order in Checkout, you offer to conclude the displayed subscription. We accept by confirming the order or providing the paid entitlement after verified payment. An automatic acknowledgement that Checkout received a submission is not itself acceptance. A paid Premium entitlement is supplied after payment has been verified. We will assist with any payment or delivery problem at service@pekagi.io.

We provide access to the purchased licence and release through the order's delivery page. Keep your order confirmation and recovery link. If access is lost or delivery does not complete, contact service@pekagi.io for assistance.

The order confirmation must identify the purchased organisation and, for SaaS/OEM, the named product. A technical key alone is not the complete record of your commercial scope.

5. Annual renewal and cancellation

Each paid subscription renews automatically for another 12-month term unless cancelled before the renewal takes effect. The agreed annual fee and applicable taxes are charged for each renewal. Any proposed change to your commercial terms or price must be addressed separately; this clause does not authorise unspecified unilateral changes.

You can cancel future renewal through the billing portal linked to your order. Cancellation takes effect at the end of the already-paid term and does not shorten that term. If you cannot access the portal, contact service@pekagi.io for help with cancellation.

A failed renewal payment does not create a new paid period or extend development, deployment, support or update rights beyond the period already paid for. Any rights or remedies provided by applicable law remain unaffected.

6. Rights during and after the paid term

During an active paid term, you may develop with Premium, make new deployments within your plan scope, obtain available licensed updates and receive the support described below.

After ordinary expiry or cancellation at the end of the paid term, an existing deployment that was properly licensed and made during the paid term may continue to use its existing Premium version. Its permitted organisation/product scope remains the scope under which it was deployed. An end user's continued use of an existing OEM installation is not made dependent on that end user buying a developer seat.

Expiry does not grant rights to start new Premium development, create new deployments or install Premium updates. Those activities require a new active paid term or another expressly agreed licence. Continued operation of an existing deployment is distinct from an entitlement to future releases, new installations or new development work.

A runtime key may remain technically valid after the paid term so that an existing deployment can continue working. That technical behaviour does not extend the paid development, deployment, download or support entitlement. Commercial scope is determined by the applicable licence and order, not solely by whether a runtime accepts a key.

7. Integration support

An active paid term includes email assistance with library integration and reproducible bugs during the 12-month term, available at service@pekagi.io, within these annual allowances:

Plan	Included integration support
Premium Internal	2 hours per developer seat per year
Premium SaaS	4 hours per licensed product per year
Standard OEM	8 hours per licensed product per year

Unused support hours expire at the end of the term. Additional work requires a separate agreed scope. Please provide the affected version, a description of the issue and a reproducible example where possible, without including unnecessary confidential or personal data.

No guaranteed response time, service-level agreement, custom implementation or dedicated engineering project is included. This support description does not limit any statutory rights or remedies relating to the supplied software.

8. Free 30-day evaluation

You can request a free 30-day Premium evaluation through the trial form. It includes the complete Premium library and its advanced compositions for evaluation in your project, without production deployment rights. No payment card is required. It does not automatically convert into a paid subscription or trigger a charge. The separate paid Checkout begins a paid annual subscription, not a trial.

Provide your organisation and contact email, confirm that you act for a business and are authorised to do so, and accept these terms in the displayed language and version before requesting the trial. These contact details are self-declared; providing them does not verify ownership of the email address or identity of the organisation. We confirm the evaluation by providing its licence and confirmation in the browser. The confirmation records the start and end of the 30-day period and the accepted terms language and version.

Save the trial key and confirmation when they are displayed. Trial delivery does not include an automatic email or email-based account recovery. Reopening the same trial using its saved private access link does not restart or extend the evaluation. Submitting the same contact details again does not create a fresh evaluation period. Availability is subject to reasonable technical request limits to prevent automated abuse; contact service@pekagi.io if a legitimate request cannot be completed.

To continue Premium development after the evaluation or make production deployments, obtain the applicable paid plan. The paid-plan provision allowing continued operation of existing licensed deployments does not turn a free evaluation into a perpetual production licence. The evaluation key has an expiry date; the end of the evaluation does not remotely delete downloaded files. Your separate MIT rights remain unchanged.

9. Integration, compatibility and operation

WestCoast Charts is a JavaScript library to be integrated into your application. Unless expressly agreed, the purchase does not include installation, hosting, operation of your website, or a tested connector for every content-management system. Compatibility follows the agreed product description and the documented requirements of the supplied release. Use in WordPress, other CMSs, frameworks, themes, plugins, custom scripts, build tools or hosting environments can involve interactions that affect loading, rendering, performance or stability. This does not mean that all such combinations have been tested or that a documented or expressly agreed compatibility commitment is withdrawn.

You are responsible for your application's integration and operation within your control, including selecting compatible versions, following documented integration instructions, using appropriate access controls, and validating your application data and configuration. Before production changes, carry out reasonable tests in a suitable test or staging environment, keep backups appropriate to the application, and provide a practicable rollback procedure. These measures should be proportionate to the intended use and risks; they do not impose an absolute duty to prevent every fault or automatically remove your rights if a step was omitted.

Tell us about a reproducible problem, including relevant library/browser/host versions and interactions with third-party components, and reasonably cooperate in identifying its cause. Do not send unnecessary personal data or secrets. We remain responsible for our contractual obligations and defects attributable to the supplied software. The presence of WordPress, a plugin, custom code, a modification or another third-party component alone is not a reason to reject a defect claim. To the extent an issue is caused solely by an external component or a customer change for which we are not responsible, making that component compatible is outside the standard purchase unless agreed separately. If our software or conduct also contributed, responsibility is assessed according to the actual causes and applicable law; there is no blanket exclusion for integrated systems.

You remain responsible for decisions based on your data and for any sector-specific requirements of your application. A chart example, including a medical or financial example, is not professional advice or a certification of your finished application. This does not limit an expressly agreed product characteristic or our responsibility for accurately providing the agreed functionality.

10. Liability

We are liable without the limitations in this section for intent and gross negligence, for culpable injury to life, body or health, for fraud or fraudulent concealment of a defect, and under an expressly assumed guarantee to the extent of that guarantee. Mandatory liability, including liability under the German Product Liability Act where applicable, remains unaffected. This applies equally where the relevant conduct is that of our legal representatives or persons we use to perform our obligations.

For property damage and financial loss caused by ordinary negligence, we are liable if we breach a material contractual obligation: an obligation whose fulfilment is necessary for proper performance of this contract and on which you may normally rely. In this contract, these include supplying the licensed software with its agreed essential functionality, providing the purchased access and performing the agreed support obligations. In those cases, compensation is limited to the damage that was foreseeable when the contract was concluded and typical for a contract of this kind. This is not a cap at the licence fee or support-hour budget. Outside these cases, liability for property damage and financial loss caused by ordinary negligence is excluded. The unrestricted cases in the preceding paragraph always take precedence.

The same limits apply to claims for damages arising from the contract or other legal grounds concerning the same supplied services, including claims against our legal representatives and persons used to perform our obligations. They do not restrict claims for performance, correction of defects, a reduction in price, rescission or termination where their statutory requirements are met. Statutory limitation periods, mandatory rights and rules on the burden of proof are not shortened or reversed by these terms.

Any contributory fault and duty to mitigate damage are assessed under applicable law according to their actual effect on the damage. A missing backup, untested integration or third-party component does not automatically exclude liability, and there is no blanket exclusion of data loss or consequential damage that would override the preceding rules. The MIT or other third-party licence disclaimers accompanying code are not used to avoid the obligations we assume under this paid contract.

11. Statutory rights, issues and refunds

Your statutory rights and remedies remain unaffected except for the express, limited rules on damages in section 10, and mandatory rights remain unaffected in every case. The ordinary end-of-term cancellation provisions do not restrict a statutory right to terminate for cause, rescind or seek other remedies.

Please contact service@pekagi.io about delivery problems, defects or a refund request. Any agreed refund should identify the invoice period concerned and explain its effect on the relevant entitlement and future renewal. A refund and cancellation of future renewal are separate operations; the confirmation should make clear whether both have occurred.

12. Contact and licence records

For licence scope, support, delivery, billing assistance or a request to change the named product, contact service@pekagi.io and quote your order reference. Do not send payment-card details or private signing credentials by email.

Retain the order, the applicable version of these terms, the relevant release manifest and the accompanying open-source notices. Those records distinguish the purchased commercial rights from the technical operation of the software.