NDA Before Discovery
We can sign an NDA before reviewing the idea, GDD, pitch deck, prototype, roadmap or existing build.
Security and IP
Security, NDA and IP Ownership
Commercial game development needs clear legal, security and delivery terms before production starts, especially when source code, assets, repositories and confidential game ideas are involved.
NDAAvailable before detailed project discussion
Source codeOwnership and access terms defined in the SOW
AccessRepository and build permissions agreed upfront
LicensesThird-party and open-source dependencies reviewed before use
What We Define Before Production
Security and ownership terms are aligned before development work expands, not after the first build is delivered.
Source Code and IP Terms
Source code ownership, project assets, IP transfer terms and delivery format are documented in the statement of work.
Repository and Access Model
We agree whether work happens in your repository or a shared controlled environment, including access control and secure communication rules.
Licenses and Dependencies
Third-party assets, open-source dependencies and usage licenses are reviewed before integration.
Contractor Disclosure
If a role requires subcontractor participation, disclosure and approval terms are documented before work starts.
Data Retention and Build Delivery
Build delivery, file access, data retention and post-launch support terms are agreed before release.
Procurement Questions We Expect
These questions are answered clearly in a commercial game development engagement.
Who owns code?
Ownership is defined contractually before production starts.
Where is the repository?
We can work in a client repository or controlled shared environment with agreed permissions.
How is access controlled?
Repository, build, file and communication access is role-based and revocable.
Are third-party assets used?
Licenses, attribution and usage terms must be reviewed before integration.
Are subcontractors involved?
Subcontractor disclosure and approval rules are stated in the commercial terms.
What happens after launch?
Build handoff, data retention, support, bug fixing and LiveOps terms are defined separately.
Handover artifact
Source ownership is only useful when the transfer is operational
This handover inventory is the concrete counterpart to contract language. It should be agreed before production and updated before final acceptance.
- RepositoriesSource branches, history, code owners and access-transfer status.
- Build accessSigning keys, CI/CD, store roles and deployment documentation.
- Assets and licensesEditable source, third-party terms, fonts, plugins and attribution.
- Operational dataBackend ownership, analytics access, backups and credential rotation.
NDA and IP FAQ
Can you sign an NDA before we share details?
Yes. NDA-first discovery is available before detailed project review.
Can you work in our repository?
Yes. Repository access, branch rules, permissions and workflow can be aligned during setup.
Who owns source code and assets?
Ownership and transfer terms are defined in the statement of work before production starts.
Do you use third-party or open-source assets?
Only when approved for the project, with license and usage terms reviewed before integration.
How is project access handled?
Access to repositories, builds and shared files is controlled by role and removed when no longer needed.
Need NDA-First Discovery?
Start with a short description of the project and the documents you need protected.