Ownership & Handoff
Your App Is Yours.
Built for you means owned by you. For completed custom deliverables, SBG’s contract is designed to transfer the rights SBG actually owns and can legally transfer once the applicable payment requirements are satisfied—not make your application depend on us forever.
No Required Attribution
Your App Is Not Our Billboard.
SBG does not put a “Built by SBG” footer, badge, watermark, backlink, co-branding mark, or other mandatory SBG affiliation into your customer-facing application. We do not reserve advertising space in something you paid us to build. Your product should present itself under your brand—not ours.
SBG’s name can still appear where it legitimately belongs in private project records, handoff evidence, support records, or signed documents. That is documentation, not customer-facing branding. Any notice independently required by a third-party or open-source license is separate from SBG attribution.
The practical promise
Source Custody Without Hostage Games
The exact accepted Services Agreement and Statement of Work control a real engagement. This page explains the current public model without pretending SBG can transfer rights it does not own.
What Transfers or Stays Yours
- Materials and intellectual-property rights you already owned or validly supplied
- SBG-owned transferable rights in completed custom source code, custom documentation, and other custom deliverables identified in the applicable Statement of Work, after the applicable amounts are fully paid
- Transferable rights in completed custom deliverables from a fully paid completed stage even if a later stage never proceeds
What Does Not Magically Become Custom IP
- SBG background technology, reusable tools, methodologies, generic components, templates, know-how, and pre-existing materials
- Open-source software and third-party technology, which remain subject to their own licenses and rights
- Incomplete internal working material, experiments, drafts, or unfinished items that were never identified as completed deliverables
Accounts & source
The Goal Is a Clean Handoff, Not Permanent Dependency
Where practical, production resources intended to belong to you should ultimately be held in or transferred to client-controlled accounts. SBG cannot transfer ownership of a hosting platform, third-party account, open-source project, or other technology it does not own.
When source custody is part of the engagement, SBG uses authenticated transfer and release evidence. We also encourage an independent client-controlled source repository or archive. A recorded SBG handoff proves the SBG handoff event and its evidence; it does not fabricate proof that you finished a download or independently confirmed receipt.
Client-provided materials remain client property. A payment dispute over a later or separate amount does not, by itself, claw back rights already transferred in fully paid completed custom deliverables.
Public summary only. The accepted Services Agreement, Statement of Work, applicable Change Orders, third-party licenses, and applicable law control the exact rights for a real engagement.