Source license

This document is a review draft and is not in force. Prepared on 15 September 2026.

This license is offered by Marek Jóźwiak, trading as Godsend, ul. Okopowa 14/92, 01-063 Warszawa, Poland, NIP 5273223291, REGON 545009660 (“Godsend”, “we”, or “us”). The licensee is the person or organization identified in the order. Each developer seat is assigned to one named individual.

This license applies to proprietary Godsend shader components, their framework integrations, and accompanying files expressly supplied as part of a paid Godsend offer (the “Components”). It covers the React, Svelte, and Vue versions included in that offer. Third-party dependencies and assets remain governed by their own licenses, as explained in section 10.

The Terms and digital content agreement govern accounts, access, orders, and support. The Refund and cancellation notice governs refunds and withdrawal. Together with the accepted order, these documents form the agreement for your Godsend license. Mandatory law takes priority. An expressly agreed written variation takes priority over these standard terms for the matter it addresses.

Once the purchase is paid and the seat is assigned, we grant its named developer a non-exclusive, worldwide license to:

• download covered Components through authorized delivery methods during the access period;
• make working and backup copies in private development environments and repositories;
• study, modify, translate, adapt, combine, and extend the Components;
• incorporate the Components in unlimited personal, commercial, internal, and client projects;
• deploy, reproduce, display, and distribute the Components as an integrated part of finished websites, applications, and other end products; and
• charge for those end products, including through subscriptions or usage fees.

There are no per-project fees, royalties, revenue shares, or public attribution requirements. Copyright and third-party license notices included in source files must remain where their applicable licenses require them.

A finished end product is a website, application, or other work with its own purpose and value beyond supplying reusable Components. A SaaS application that uses a shader in its interface is an end product. A service that lets users obtain our Components as reusable source is not.

One seat covers one named developer, across that developer’s devices and covered projects. Buying through an organization does not give every employee, affiliate, or contractor a seat.

Each developer who independently obtains Components, incorporates them into new projects, or works on them as reusable development assets needs a seat. Non-developers who view a preview, review a design, manage a project, or use the finished product do not need a seat for that activity.

A team purchase covers only the number of named seats stated in its written order. Every developer uses their own account and registry credentials. An individual account, token, registry response, or downloaded catalog must not be shared as a substitute for additional seats.

Private build systems, hosting providers, backup services, and deployment tools may process the source on your behalf to build, secure, store, and operate permitted projects. Access must be restricted to the work they perform, and must not give their staff or customers an independent right to reuse the Components. A non-human build process is not an additional developer seat. Any registry access it performs must use a supported, confidential credential for an authorized seat.

A seat cannot be sold, lent, or freely transferred. Contact us for corrections to the purchaser’s details or a proposed reassignment within an organization. A reassignment requires our written agreement; it must not leave two developers using one seat.

You may deliver a finished client project, including its private source repository, without requiring the client to buy a seat merely to receive, operate, host, back up, or maintain that project.

The client and people maintaining the delivered project may make changes needed to keep that particular project working, including fixes to its embedded Components. This limited permission does not let them extract a Component for a different project, maintain a reusable Godsend library, download from the registry, or distribute the Component separately. Those activities require the relevant developer’s own seat.

The same distinction applies to contractors. Work confined to operating or maintaining a delivered project is permitted under the project permission above. Independently selecting, obtaining, or reusing Components for development work requires a seat.

Give the recipient a copy of, or stable reference to, this license and identify the embedded material that remains licensed by Godsend. Do not include unrelated Components or your registry credentials in the handover. You may transfer your rights in your own project work, but cannot grant rights in the Components beyond this license.

Except for the end-product and client-delivery permissions above, you must not:

• publish, sell, give away, rent, sublicense, or otherwise distribute the Components as standalone or reusable assets, including modified or translated versions;
• put Component source in a public repository, package, gist, paste, file-sharing collection, or downloadable example;
• distribute Components inside templates, themes, starter kits, boilerplates, UI kits, component packs, educational source bundles, or marketplace products intended for others to build new projects;
• operate a mirror, proxy, wrapper, registry, export tool, or generator that supplies the Components to people without the required rights;
• build a competing source library or source-delivery product by copying or adapting the Components; or
• share accounts or credentials, evade access controls, or obtain private files outside the access granted to your seat.

Changing variable names, porting to another framework, converting to another language, or combining source with other files does not remove these restrictions.

These restrictions protect our licensed implementation. They do not give us ownership of a visual style, idea, mathematical technique, independently developed implementation, or material whose separate license permits the relevant activity. Nothing here excludes a statutory right to observe, study, test, make a necessary backup, or achieve interoperability where that right cannot lawfully be restricted.

Web applications necessarily deliver executable code to end users. Serving the code needed to run a permitted end product in a browser is allowed, even where a technically skilled person could inspect it. You are not required to make extraction technically impossible.

Do not deliberately offer reusable Component source, development source maps containing that source, a source download, or an extraction API to the public. Keep development repositories and original source maps private where reasonably practicable. Ordinary browser execution is distinct from distributing a source library.

Public Godsend previews and documentation allow evaluation of the product. Their availability does not by itself license paid Components for use in your own projects. Any express permission or separate license attached to a public example remains effective.

The named developer may use private coding assistants, agents, and hosted development tools to work on permitted projects. Choose settings and provider terms that restrict the submitted Components to providing that service and do not authorize their use to train a shared model or make reusable source available to other customers.

You must not contribute the Components to a public or shared training dataset, model-training or fine-tuning corpus, searchable source collection, prompt pack, or retrieval service accessible to unlicensed users. You must not expose registry credentials or source through a public agent endpoint.

Generated or transformed code that reproduces protected parts of a Component remains subject to this license. Your independently created project code and other output do not become Godsend property merely because an assistant helped produce them. Review automated changes before deployment.

The access period controls new downloads and updates. It does not impose an expiry date on lawfully obtained copies.

After an annual plan expires, or you close an account without a refund, the named developer may continue using versions lawfully retrieved during paid access in both existing and new permitted projects. Keep your own lawful copies: continued use does not include a right to retrieve them again after registry access ends.

Lifetime and Founding Lifetime access cover the operating life of the Godsend core catalog, as explained in the Terms. They do not guarantee indefinite hosting or access to separately sold products. Lawfully retrieved copies remain usable if the platform closes.

The grant for those copies continues for the duration of the applicable copyright, subject to the termination provisions below and any mandatory law. Ordinary expiry, a security suspension, or a change in our prices does not by itself terminate it.

A full refund of an entire purchase or a final chargeback that reverses its payment ends the license granted through that purchase, subject to any rights preserved by mandatory law or the written resolution. A refund of only one renewal or part of an order affects only the period or rights identified in that resolution; it does not automatically revoke independently paid earlier rights.

When a license ends, stop using the affected Components and remove their copies from systems and projects under your control. Replace them in deployed projects where continued use is no longer licensed. Copies retained solely because law requires them, or in immutable backups that cannot reasonably be selectively erased, must be isolated from use and removed through the applicable retention cycle. Do not destroy unrelated records that must lawfully be preserved.

A pending payment dispute or credible security investigation may justify pausing new downloads. It does not establish a breach by itself. We will review available evidence and provide an explanation and a way to respond, unless doing so would compromise security or be unlawful.

For a remediable material license breach, we will normally give written notice describing the issue and at least 14 calendar days to remedy it before terminating the affected license. We may act immediately to stop active source redistribution, credential compromise, fraud, or conduct that makes a remedy impracticable. Measures must be proportionate to the affected conduct. You may ask for a human review.

We do not remotely delete client projects or disable deployed Components. You remain responsible for addressing copies you supplied without continuing rights. Refunds, partial refunds, and consumer remedies are also governed by the Refund notice.

You retain ownership of your original project work. Godsend and its licensors retain their rights in the Components. Modifying a Component does not transfer ownership of the underlying material to you, and does not transfer your original additions to us.

Third-party dependencies and assets remain subject to their own licenses. This agreement neither restricts their separate permissions nor grants rights their owners have not granted. In particular, a paid seat does not automatically license third-party fonts, photographs, logos, trademarks, videos, or other demonstration content shown in previews. Check the relevant notices and replace assets where necessary.

The warranty, liability, complaint, governing-law, and dispute provisions in the Terms apply to this license. Consumer rights and other non-waivable rights remain unaffected. A later license version does not retroactively narrow rights already granted for downloaded versions without a lawful basis or your express agreement.

For licensing questions, team orders, and suspected misuse, contact [CONTACT_EMAIL — to be confirmed before publication] or write to the address in section 1. Do not send passwords or registry tokens.