Boundary before capability
Powerful recovery tools require a clear authorization boundary.
Kalu Kode products and research are intended for software that the operator owns or is explicitly authorized to inspect, capture, assess, recover, migrate, refactor, or test.
We may refuse work
Technical accessibility is not permission.
- copy or commercialize another party’s software without authorization;
- bypass access controls, licensing controls, DRM, or anti-cheat systems;
- extract credentials, secrets, private user data, or restricted content;
- evade security controls or terms imposed by an authorized system owner;
- impersonate another product or retain protected branding and assets without permission;
- conceal the source or purpose of an unauthorized recovery.
A recovery engagement may require written confirmation of ownership or authorization. Kalu Kode may refuse work when the authorization, purpose, data handling, or legal boundary is unclear.
The ability to technically observe or recover a client-side artifact is not a statement that the artifact may legally be reused. Customers remain responsible for obtaining appropriate legal advice and rights.
Take the next step
Bring the authorization with the problem.
If ownership, access, or data boundaries are unclear, the first conversation should resolve those questions before any artifact is shared.