How we handle NDAs and IP ownership for international clients

Legal questions come up in nearly every serious client conversation eventually, and they matter more, not less, when the engagement crosses borders. Our position on both NDAs and intellectual property ownership is deliberately simple, because complexity here mostly benefits whichever party wrote the contract, not the relationship between the two sides.

If a prospective client wants an NDA signed before sharing details of their project, we sign it, using their template when reasonable or our own mutual version when they don't have one. This isn't a point we push back on; protecting a client's confidential information before a contract even exists costs us nothing and matters a great deal to them at that early stage.

Code, designs, and any other deliverable becomes fully the client's property once the engagement is paid in full, with no ongoing license-back to us and no restriction on how they use or modify it afterward. We don't retain rights to reuse a client's custom work for another project, and we say so explicitly in every contract rather than leaving it ambiguous or buried in fine print.

International IP assignment has real jurisdictional nuances that a generic template sometimes misses. We use contract language reviewed for validity in both India and the client's home jurisdiction, since an IP assignment clause that's unenforceable in the client's country isn't actually protecting them, whatever the document happens to say on paper.

We avoid one-sided contract clauses that would be unusual for a client to accept, indefinite non-competes, ownership claims over a client's underlying business idea, and similar terms that exist mainly to protect an agency rather than reflect the actual working relationship. If a clause wouldn't make sense from the client's side of the table, we don't include it.

For a client based in a jurisdiction with unusual requirements around work-for-hire IP assignment, we had contract language specifically reviewed by counsel familiar with that jurisdiction, rather than relying on a generic template, since a clause that's standard and enforceable in most countries isn't automatically valid everywhere.

When a client has their own standard vendor agreement, we review it against our own baseline expectations, sign what's reasonable, and flag specific clauses for negotiation rather than either accepting everything unquestioned or insisting on our own template regardless of what they already have in place.

For engagements touching health data, financial data, or other especially sensitive categories, we go beyond a standard NDA to formal data processing agreements matching the client's regulatory obligations, GDPR for European clients, HIPAA-adjacent handling for US health data, rather than treating every project's confidentiality needs identically.

Publishing our actual position on NDAs and IP ownership, rather than leaving it as something only discovered deep into a sales process, is a small trust-building move. A prospective client shouldn't have to guess at our legal defaults before deciding whether it's even worth a conversation.

We review any requested addition on its own merits rather than resisting changes reflexively. Some requested clauses are entirely reasonable and we accept them without friction; others would meaningfully shift risk in a way we'd need to price differently or decline, and we're direct about which is which rather than either rubber-stamping everything or resisting on principle.

For engagements where a client's own developers contribute directly alongside ours, we clarify IP ownership explicitly in the contract before that collaborative work begins, since joint development can otherwise create real ambiguity about ownership that's much harder to untangle after the fact than to define clearly upfront.

For specialized work requiring a subcontractor, a particular animation specialist, a specific platform expert, we extend the same confidentiality obligations from the primary NDA down to that subcontractor before sharing any client information with them, rather than treating our own internal team boundary as the edge of confidentiality protection the client was promised.

Clients rarely ask about this explicitly, but we disclose our subcontracting practices upfront and confirm the confidentiality chain extends properly, since an NDA that technically covers only our direct employees while sensitive information flows to an unbound third party isn't actually delivering the protection the client believed they were getting when they signed it.

We also make a point of explaining our legal defaults during the very first substantive conversation, well before a formal proposal is even drafted, rather than treating it as fine print to be discovered later in a contract review. Clients have told us this upfront transparency itself builds trust faster than the specific legal terms do, since it signals we're not trying to quietly embed anything unusual or one-sided that would only surface once someone actually read the full document carefully near the end of a sales process.

Nearly every custom build incorporates open-source libraries and frameworks under their own separate licenses, which clients sometimes don't realize means the final deliverable isn't 100 percent exclusively owned code in the strictest sense. We explain this distinction clearly during contracting, walking through which parts are custom work transferring fully to the client and which are open-source components used under their own standard, generally permissive licensing terms.

A project that pauses partway through, for funding reasons or a shift in priorities, and resumes months later sometimes needs updated contract terms, particularly if pricing or scope has changed since the original agreement. We formally amend the IP and payment terms in writing when a project resumes after a genuine pause, rather than relying on the original contract's terms carrying forward automatically without anyone revisiting whether they're still accurate.

This matters most for IP ownership specifically, since we want zero ambiguity about which deliverables were covered under the original payment terms versus the resumed engagement's terms, especially if the client's own business circumstances changed materially during the pause.