When you invest in a website, it is important to understand who owns what. At Inspry, we believe in being transparent and clear about ownership, licensing, and usage rights so there are no surprises during or after a project.
This page explains how ownership works across deliverables, custom code, background materials, third‑party commercial software, and open‑source software when you work with Inspry.
Plain‑English Summary
- You own the custom deliverables we create for you once invoices are paid in full.
- Inspry retains ownership of its pre‑existing tools, frameworks, and internal systems.
- Third‑party software is governed by its own license terms, not Inspry’s.
- Open‑source software remains open‑source and is licensed under its original license.
- Clear boundaries protect you, Inspry, and future maintainability of your site.
The full legal details are defined in Inspry’s Master Services Agreement (MSA) and Statement of Work (SOW). This page is provided for clarity and education only.
1. Project Deliverables (What You Own)
Deliverables are the specific items Inspry agrees to create for you and documents in your approved Statement of Work (SOW). Examples include:
- Custom WordPress themes or child themes
- Custom Shopify themes or theme customizations
- Custom plugins built specifically for your site
- Custom PHP, JavaScript, CSS, or HTML written for your project
- Page templates, layouts, and structural components
- Final design assets explicitly included in the SOW
Ownership
Once all invoices related to the project are paid in full:
- You own the deliverables created specifically for your project
- Deliverables are considered “works made for hire” where applicable
- You may use, modify, and maintain these deliverables for your website or business
Ownership applies only to what is explicitly listed in the SOW.
2. Background Materials (What Inspry Retains)
Background Materials are tools, systems, code, and processes Inspry developed before your project or uses across multiple clients.
Examples include:
- Internal frameworks or starter themes
- Reusable code libraries and utilities
- Deployment scripts, automation tools, and DevOps processes
- Proprietary workflows, methodologies, and configurations
- Internal monitoring, maintenance, or management systems
Why This Matters
Background Materials allow Inspry to:
- Deliver projects efficiently
- Maintain high quality and security standards
- Support and maintain sites long‑term
Your Rights
If Background Materials are included within your deliverables:
- You receive a license to use them as part of your website
- You may not resell, redistribute, or reuse them outside your site
- Ownership remains with Inspry
This protects both parties and avoids legal and licensing conflicts.
3. Third‑Party Commercial Software
Most modern websites rely on third‑party commercial tools. These may include:
- Premium WordPress plugins or Shopify apps
- Commercial themes or add‑ons
- SaaS tools and APIs (email, analytics, search, payments, shipping, etc.)
Licensing Rules
- Third‑party commercial software is governed by the vendor’s license, not Inspry’s
- Some licenses may be provided by Inspry while you are on an active support plan
- Other licenses may be purchased and owned directly by you
Important Notes
- You do not own third‑party commercial code unless the vendor explicitly grants ownership
- Access to updates and support depends on maintaining valid licenses
- If Inspry‑provided licenses are discontinued or removed, you may be required to purchase your own
Inspry cannot modify, relicense, or transfer ownership of third‑party commercial software.
4. Open‑Source Software
WordPress, Shopify themes, and many related tools are built on or incorporate open‑source software.
Examples include:
- WordPress Core
- Open‑source plugins and libraries
- Open‑source JavaScript frameworks and utilities
How Open‑Source Licensing Works
- Open‑source software remains governed by its original license (GPL, MIT, Apache, etc.)
- Neither Inspry nor the Client owns open‑source code
- You are free to use, modify, and distribute open‑source software within the terms of its license
Any custom code Inspry writes on top of open‑source software may still be owned by you as a deliverable, while the underlying open‑source code remains open‑source.
5. Media, Assets, and Licensing
All websites must use properly licensed media assets.
This includes:
- Photos
- Videos
- Illustrations
- Fonts and icons
Inspry Policy
- Free or attribution‑restricted stock assets are not permitted unless explicitly approved
- Assets must be licensed for commercial use
- Inspry may provide licensed stock assets or require Client‑provided assets
This policy protects Clients from copyright claims, takedowns, and legal liability.
6. What Happens If You Move or Duplicate the Site
If your site is duplicated, cloned, or migrated:
- Inspry‑provided licenses, keys, and tools may be revoked
- Background Materials remain Inspry property
- Third‑party licenses may require re‑purchase
Formal offboarding ensures:
- Proper license cleanup
- Secure handoff
- No unexpected disruptions
7. Why These Boundaries Exist
Clear ownership rules:
- Protect your business
- Reduce legal and licensing risk
- Ensure long‑term maintainability
- Allow Inspry to continue supporting and improving your site
This structure is standard across professional development agencies and enterprise software providers.
Questions?
If you have questions about ownership, licensing, or what is included in your project:
- Review your Statement of Work (SOW)
- Review Inspry’s Master Services Agreement (MSA)
- Contact our team before making changes or migrations
We’re always happy to clarify expectations upfront.
Transparency builds better long‑term partnerships.
Thousands of successful projects for 15 years
Contact us to book a free,
no-obligation consultation.