Skip to main content
Back to home

Legal Documents

IP Policy

How source code ownership, IP transfer, third-party licensing, and white-label credit rules work across SessDev engagements.

Version
v1.0.0
Last updated
2026-05-11
Status
Binding document

01Ownership of deliverables

On final payment, all custom source code, configuration, and original documentation produced for your engagement transfers to you. SessDev retains no ownership over your custom deliverables.

02Buyout clause

Even before final payment, you may exercise the Buyout Protocol to acquire all work-in-progress source code by paying the remaining engagement fees in full. See the Buyout Protocol for details.

03Third-party components

Deliverables may incorporate third-party libraries and assets governed by their own licenses (MIT, Apache 2.0, BSD, commercial SaaS). License compliance is your responsibility post-handoff.

04Open-source contributions

SessDev retains the right to contribute generic, non-confidential utilities back to the open-source ecosystem provided they contain no client-identifying logic, brand, or business rules.

05Credits and references

As a shadow agency, we do not publicly claim credit for client work. We do not list clients on our website, and we honor white-label terms by default.