Software companies keep customer data out.

How your software is developed and supported

The decisions of an engineering team are written down at length:

• Your repos and the commits behind them
• Pull requests and their review comments
• Tickets and bugs traced from the first report to the fix
• Test and build history
• Architecture notes and release notes

Customer data inside tickets and logs

It is common for support conversations and logs to carry details about customers and their accounts. In the copy, placeholders replace each person, customer and company, as well as addresses and account numbers. Whole repos, tools or periods may be excluded as well.

Keeping client code out

When you write software for clients, the code may be theirs. It can be left out one project at a time. It is up to you and counsel to decide if client projects suit the terms you signed, and we do not advise on the legal side. What you own is usually an easier place to start, and internal tools often carry history that is equally useful.

Your code stays in your repos

Your originals never leave your systems. Nobody requests credentials, tokens or access to your repositories. The copy is prepared by License Your Data, and you sign off on a sample before anything is shared. You can withhold any repository or product that you consider central.

A good place to begin

Ask for the estimate first. Use the first short call to explain which repos are yours, which belong to client projects, and where you talk with customers. Scope is often decided by that list by itself. Shipping carries on as normal, because your systems never need to be accessed. Any review of the sample by counsel or security happens before anything leaves. Until you approve, you are free to stop, with nothing shared.