End User License Agreement

This End User License Agreement governs the use of digital deliverables, systems, code, automations, templates, and related materials created by ORD Studio. It applies to all clients who receive work from the studio, regardless of the nature of the engagement. By accepting a deliverable, you agree to the terms described here.

Ownership

ORD Studio retains full ownership of its internal methods, frameworks, proprietary processes, reusable code libraries, component systems, design templates, automation logic, and any tools or systems developed independently of a specific client project. These assets represent the studio's intellectual property and are not transferred to the client as part of a standard engagement unless explicitly agreed upon in writing.

Ownership of custom deliverables created specifically for your project, such as bespoke pages, brand-aligned components, or client-specific automation flows, may transfer to the client upon full payment, depending on the terms agreed in the engagement. If ownership transfer is not explicitly stated in a written agreement, the studio retains rights to those assets.

License Granted

Upon full payment and project completion, the client receives a non-exclusive, non-transferable license to use the final deliverables created specifically for their project. This license permits the client to operate, display, and maintain the delivered work for their own business purposes. The license does not transfer ownership of the underlying methods, tools, or frameworks used to build the deliverables.

Permitted Use

The client may use the final deliverables to run and grow their own business. This includes publishing their website, operating automations and workflows, using dashboards and internal tools, and maintaining their digital systems. The client may also make their own updates or modifications to their deliverables after handoff, provided those changes do not violate any third-party license terms embedded in the work.

Restricted Use

The client may not resell, redistribute, sublicense, white-label, or repurpose ORD Studio's proprietary assets, templates, systems, or internal code structures for use in unrelated businesses or projects without explicit written permission from ORD Studio. Reverse engineering, copying, or commercializing deliverables in ways not covered by the original engagement is prohibited.

This restriction applies to reusable design components, automation templates, workflow structures, and any materials clearly originating from ORD Studio's internal library rather than built exclusively for your project.

Third-Party Components

Projects delivered by ORD Studio may include third-party software, open-source libraries, plugins, fonts, icon sets, or platform integrations. These components remain subject to their own individual licenses and terms of use. ORD Studio will disclose significant third-party dependencies where relevant, but it is the client's responsibility to remain compliant with any third-party license obligations that apply to their continued use of the delivered work.

Source Files and Access

Access to source files, raw design files, editable development files, or internal build assets is provided only when explicitly included in the agreed project scope. If source file delivery is not listed in the engagement agreement, only the final production-ready output will be delivered. Requests for source files after project completion may be accommodated at an additional cost.

Intellectual Property

All intellectual property developed by ORD Studio that is not explicitly transferred in writing remains the property of ORD Studio. This includes but is not limited to: reusable code modules, internal templates, automation logic patterns, design system components, and strategic frameworks used across multiple client projects. These are tools of the trade and are not bundled into any client deliverable by default.

Written Exceptions

Any deviation from the terms in this agreement, including full ownership transfer, expanded licensing rights, or permission to redistribute deliverables, must be agreed upon in a separate written document signed or explicitly confirmed by both parties. Verbal agreements, informal messages, or implied understanding do not constitute written exceptions for the purposes of this agreement.