These are Sanova Web Solutions' general licensing and intellectual property terms. If this page conflicts with a signed project agreement, the signed project agreement governs.
1. Client Ownership
Once a website project has been completed and the full project balance has been paid, the client receives ownership of the completed website and the custom deliverables created specifically for that project, subject to any third-party or open-source licensing restrictions.
This may include:
- Custom website layouts
- Custom page designs
- Project-specific source code
- Custom components created specifically for the project
- Client-specific content structures
- Custom graphics created specifically for the project
- Project-specific functionality
- Project files identified as client deliverables
Sanova Web Solutions does not require clients to continue paying a subscription in order to retain ownership of a completed and fully paid website.
2. Transfer of Ownership
Ownership of custom project deliverables transfers only after all outstanding project invoices have been paid in full.
Until final payment has been received, all custom design, development work, source code, concepts, and project deliverables remain the property of Sanova Web Solutions unless otherwise stated in writing.
Sanova is not required to transfer:
- Source code
- Repository ownership
- Production access
- Final design files
- Hosting ownership
- Project credentials
- Other final deliverables
until the project balance has been paid.
3. Source Code
Once the project has been completed and paid in full, Sanova Web Solutions can provide or transfer the source code associated with the completed website.
Depending on the project, this may be done through:
- A Git repository
- GitHub
- A client-controlled development account
- A downloadable project archive
- Another agreed development platform
The client may use the completed project source code to operate, modify, maintain, or expand their website.
4. Sanova Pre-Existing Intellectual Property
Website development often involves systems, components, tools, code, and processes that existed before a particular client project began.
Sanova Web Solutions retains ownership of its pre-existing intellectual property.
This may include:
- Internal development tools
- Reusable components
- Boilerplate code
- Utility functions
- Development libraries
- Internal frameworks
- Design systems
- Generic layouts
- Code patterns
- Internal scripts
- Workflows
- Deployment processes
- Documentation systems
- Business processes
- Internal templates
- Know-how
- Development techniques
These resources may be reused across multiple projects.
The client does not obtain exclusive ownership of Sanova's general-purpose tools or intellectual property simply because those resources were used during development of the client's website.
5. Licence to Use Sanova Components
Where Sanova-owned reusable code or components are included within a completed website, the client receives a licence to use those materials as part of the completed website.
Unless otherwise stated in writing, this licence allows the client to:
- Operate the website
- Host the website
- Modify the website
- Hire another developer to modify the website
- Move the website to another hosting provider
- Continue using the website for their business
The client may not claim exclusive ownership of Sanova's pre-existing reusable systems or prevent Sanova from using similar code, techniques, components, or functionality in other projects.
6. Open-Source Software
Sanova Web Solutions may use open-source software as part of website development.
This may include:
- Frameworks
- Libraries
- Packages
- Development tools
- UI components
- Utilities
- Build tools
- Other open-source software
Examples may include technologies such as React, Next.js, TypeScript packages, and other software commonly used in modern web development.
Open-source software remains subject to its original licence.
Sanova Web Solutions does not claim ownership of third-party open-source software.
Clients receiving a website that incorporates open-source software are also responsible for complying with any applicable open-source licence requirements.
7. Third-Party Software
Websites may rely on third-party products, platforms, or services.
Examples may include:
- Hosting platforms
- Content management systems
- Booking software
- Payment processors
- Ecommerce platforms
- Email providers
- CRM platforms
- Analytics services
- APIs
- Chat services
- Maps
- Scheduling systems
- Form services
- Authentication providers
- Database services
These products are owned and controlled by their respective providers.
The client does not obtain ownership of third-party software simply because it is integrated into their website.
Use of these services is governed by the provider's own terms, conditions, pricing, and licence agreements.
8. Third-Party Accounts
Whenever practical, third-party services required for the operation of a client's website should be created under accounts owned or controlled by the client.
This may include accounts for:
- Vercel
- Domain registrars
- Analytics platforms
- Email platforms
- Payment processors
- Booking platforms
- Ecommerce systems
- CRM software
- Database providers
- API providers
This helps ensure that the client maintains control of their business systems after the website project is completed.
10. Stock Photography
Sanova Web Solutions may use properly licensed stock photography when appropriate.
Stock photography remains the intellectual property of the original photographer or stock provider.
The client receives the right to use stock images according to the applicable licence.
A stock licence does not necessarily give the client exclusive ownership of the image.
The same image may legally be used by other businesses that obtain their own licence.
11. Client-Provided Photography
The client retains ownership of photographs they provide if they already own those photographs.
By providing photography to Sanova Web Solutions, the client confirms that they have the necessary rights or permission to use those images commercially.
Sanova is not responsible for copyright claims arising from materials supplied by the client without appropriate permission.
12. Images Found Online
Images found through Google Search, social media, another business's website, or other online sources are not automatically licensed for commercial use.
Sanova generally will not knowingly use copyrighted imagery without appropriate permission or licensing.
Images supplied as references may be used to guide the visual direction of a project, but they may need to be replaced with appropriately licensed alternatives.
13. Icons and Illustrations
Websites may include icons, illustrations, or other graphical elements supplied by third-party providers.
These assets remain subject to the provider's licence.
Depending on the licence, attribution or other conditions may apply.
Sanova will not claim ownership of third-party graphical assets.
14. Fonts
Websites may use:
- Open-source fonts
- System fonts
- Commercial fonts
- Third-party hosted fonts
Each font remains subject to its own licence.
If a project requires a paid commercial font, the client may be responsible for purchasing the appropriate web licence.
15. Client Logos and Branding
Clients retain ownership of logos, trademarks, brand names, colour systems, graphics, and other brand assets that they provide to Sanova Web Solutions.
By supplying these materials, the client confirms that they have the necessary rights to use them.
Sanova may use client branding solely as necessary to complete the project and as otherwise permitted under the project agreement.
16. Content Ownership
Clients retain ownership of original written content they provide.
This may include:
- Service descriptions
- Business information
- Team biographies
- Policies
- Blog content
- Testimonials
- Product descriptions
- Company history
- Other original written material
If Sanova writes original website content specifically for the client as a paid deliverable, ownership of that custom content transfers to the client after full payment unless otherwise stated in writing.
17. Client Responsibility for Content Rights
Clients are responsible for ensuring that they have permission to use all materials they provide.
This includes:
- Text
- Images
- Videos
- Logos
- Music
- Documents
- Graphics
- Product photography
- Testimonials
- Brand assets
- Data
By providing materials to Sanova, the client represents that their use does not knowingly infringe the rights of another person or organization.
18. Trademarks
Sanova Web Solutions does not transfer ownership of any third-party trademark, brand name, logo, product name, or other protected mark.
Clients are responsible for ensuring that they have the right to use any trademarks or protected brand assets included on their website.
19. Website Design Concepts
Drafts, unused design concepts, rejected concepts, experiments, mockups, and other work not included in the final approved deliverables remain the property of Sanova Web Solutions unless otherwise agreed in writing.
Payment for a completed website does not automatically transfer ownership of every draft or concept created during the design process.
20. Unused Source Code
Source code created during experimentation, testing, prototyping, or internal development that is not included in the final website is not automatically transferred to the client.
Only the final agreed project deliverables are included in the standard ownership transfer.
21. Non-Exclusive Development Techniques
Clients acknowledge that websites often use common development patterns.
Sanova Web Solutions may create similar:
- Navigation systems
- Contact forms
- Layout structures
- Components
- Animations
- User interface patterns
- Development approaches
- Technical solutions
for other clients.
The client receives ownership of their completed project-specific deliverables but does not receive exclusive rights to general web development techniques, functionality, patterns, or ideas.
22. Custom Functionality
Where Sanova develops custom functionality specifically for a client and that functionality is included as a paid deliverable, ownership of the project-specific implementation transfers after full payment.
However, Sanova retains the right to reuse general programming concepts, reusable logic, utilities, approaches, and non-client-specific components developed during the project.
23. Databases and Client Data
The client owns their business and customer data.
This may include:
- Customer records
- Form submissions
- Leads
- Account information
- Product information
- Internal business records
- Uploaded content
- Other client-generated information
Third-party database platforms remain subject to the terms of their respective providers.
24. Website Accounts
Accounts created specifically for the client's ongoing operation of the website should generally be transferred to or maintained under the client's control.
The client is responsible for:
- Keeping login credentials secure
- Maintaining account access
- Paying third-party fees
- Renewing required subscriptions
- Updating billing information
- Maintaining recovery information
Sanova is not responsible for loss of access caused by client account mismanagement after project handoff.
25. Domain Names
The client should own their domain name.
Sanova does not claim ownership of client domain names.
If Sanova assists with domain registration, the domain should whenever practical be registered using client-controlled account information.
Domain names remain subject to the policies and registration requirements of the applicable domain registrar and registry.
26. Hosting Platforms
Hosting software and infrastructure remain the property of the hosting provider.
For example, if a website is deployed through Vercel, the client owns their website but does not own Vercel's platform, infrastructure, or proprietary software.
The client is responsible for complying with the hosting provider's terms and acceptable-use policies.
27. APIs and External Integrations
Websites may connect to third-party APIs or external platforms.
Use of those integrations remains subject to the provider's:
- API terms
- Usage limits
- Pricing
- Rate limits
- Licensing conditions
- Availability
- Privacy requirements
Sanova cannot grant broader rights to an API or external platform than the third-party provider allows.
28. Payment Processing
Where a website uses a third-party payment processor, the payment platform remains owned and operated by the third-party provider.
Examples may include:
- Stripe
- Square
- PayPal
- Shopify Payments
- Other payment services
The client is responsible for establishing and maintaining their own merchant or payment-processing account where required.
29. Software-as-a-Service Platforms
Some functionality may rely on Software-as-a-Service platforms.
Examples may include:
- Booking systems
- Email marketing platforms
- CRM tools
- Ecommerce systems
- Analytics tools
- Customer support systems
- Scheduling platforms
The client receives access to these services under the provider's terms but does not obtain ownership of the software itself.
30. Licence Changes
Third-party providers may change their licence terms, pricing, functionality, or availability.
Sanova Web Solutions does not control these changes.
If a third-party licensing change affects the operation of a client's website, Sanova may assist with updating or replacing the affected service.
Additional development required because of third-party licensing changes may be quoted separately.
31. Licence Expiration
Some paid licences must be renewed periodically.
If a required licence expires, functionality may:
- Stop working
- Become limited
- Lose access to updates
- Lose support
- Display errors
- Require replacement
Unless Sanova has agreed in writing to manage an ongoing licence, the client is responsible for maintaining licence renewals after handoff.
32. Developer Access
Clients may allow another developer or agency to access and modify their completed website after ownership has transferred.
Sanova does not require clients to obtain permission before hiring another qualified developer.
Sanova is not responsible for issues introduced by modifications made by third parties after handoff.
33. Resale of the Website
A client may generally continue using the website as part of their business and may transfer the completed website if the business itself is sold, subject to any third-party licensing restrictions.
Third-party assets, software, licences, subscriptions, and accounts may not always be transferable.
Clients should review the applicable provider's terms before transferring licensed services to another party.
34. Reselling Sanova Components
Client ownership of a completed website does not grant the right to separately extract, package, license, resell, or commercially distribute Sanova's reusable internal components, development tools, boilerplate, or other pre-existing intellectual property as a standalone product.
The licence to those materials is intended to allow normal operation and development of the client's website.
35. Portfolio Rights
Unless otherwise agreed in writing, Sanova Web Solutions may display completed websites as examples of our work.
This may include:
- Screenshots
- Website links
- Client business names
- Client logos
- Project descriptions
- General descriptions of services performed
Sanova may display this information through:
- Our website
- Portfolio pages
- Social media
- Proposals
- Marketing materials
- Case studies
Clients requiring confidentiality should discuss this before the project begins.
36. Attribution
Unless specifically included in the signed project agreement, clients are not required to display a visible "Designed by Sanova Web Solutions" credit on their website.
Sanova may request permission to include a discreet credit or link, but the requirement will be discussed before launch if applicable.
37. Confidential Projects
Certain clients may require their project to remain confidential.
If confidentiality is required, the client should notify Sanova before the project begins.
Where agreed in writing, Sanova may waive portfolio or attribution rights for that specific project.
38. Licence Compliance
Clients are responsible for continuing to comply with the licences associated with any third-party materials used in their website after project handoff.
Sanova will make reasonable efforts to use properly licensed materials during development but cannot control how clients or other developers later modify or use those assets.
40. Project-Specific Licensing Terms
Some website projects may involve unique licensing requirements.
For example:
- Custom software
- White-label development
- Enterprise software
- Exclusive designs
- Licensed datasets
- Commercial APIs
- Proprietary integrations
- Specialized software components
Any project-specific licensing terms should be outlined in the project's proposal or signed agreement.
41. Changes to Licensing Information
Sanova Web Solutions may update this Licensing Information page as our services, technology, or business practices change.
Updates to this public page do not automatically change the licensing terms of an existing signed project agreement.
The effective date shown at the top indicates the current version of this page.
42. Questions About Licensing
If you have questions about ownership, source code, third-party licences, website assets, or intellectual property associated with your project, please contact Sanova Web Solutions before approving your proposal.
We want clients to clearly understand what they own, what they are licensing, and what third-party services may remain subject to separate terms.
Project Agreements
This page provides general information about how Sanova Web Solutions handles website licensing and intellectual property.
Your individual proposal and signed project agreement may contain additional or different licensing terms based on the requirements of your project.
If this Licensing Information page conflicts with your signed project agreement, the signed project agreement will govern.