Who owns what — the Website's own content, and the basic IP setup for project Deliverables, reused parts, and client materials.
This Notice covers two things. First, the IP in this Website itself. Second, the basic setup we use to split IP in client projects, which a given Project Agreement may change.
The design, layout, own text, graphics, and branding of myonestopsolution.com belong to myonestopsolution, part of the Mentark group of companies, or are used under license. Copyright and trademark law protect them. You may view and share pages of this Website for your own personal or info use. But you may not copy, republish, or use its design, own written content, or branding for gain. That needs our written OK first.
Who owns IP in a given project is, in the end, set by that project's Project Agreement. It may adopt, tweak, or swap out the basic setup below. Absent another written deal, we sort project IP into these groups:
Custom code, designs, and content made just for a client's project pass to the client, by handover or license. That happens once we get full pay for that Deliverable, as set in the Project Agreement. Until full pay comes in, we keep ownership of the Deliverables.
Our own tools, boilerplate, frameworks, reusable UI parts, scripts, and common know-how count as "Pre-Existing IP." These are built before or apart from a given project, and they stay our property. Where Pre-Existing IP sits inside a Deliverable, the client gets a license to use it as part of that Deliverable. We keep the right to reuse the same Pre-Existing IP in other jobs.
Open-source libraries, outside plugins, fonts, stock assets, and licensed SaaS tools used in a project stay under their own license terms. We pick these parts in good faith, and we do not hand over more rights in them than their own licenses allow.
Logos, brand assets, product content, data, and other items the client gives us stay the client's property. In turn, the client gives us a license to use them only to deliver the project.
Early drafts, unused design ideas, working files, and in-house templates not picked as final Deliverables stay our property. The one exception: the Project Agreement hands them to the client by name.
Clients may have a set IP need — say, full source-code ownership, sole use, or another license setup. If so, they should raise it before the Project Agreement is signed. That way, the deal can set ownership terms just for that job.
Questions about this policy or an active project?
