Software companies keep customer data out.

How your software is developed and supported

Every engineering team builds up a detailed record of the choices it made:

• Commit history across your repositories
• Pull requests with the reviews they received
• Tickets and bugs traced from the first report to the fix
• Your build and test records
• Architecture write-ups and release notes

Client code can stay out

If you build products for clients, they may own that code. Each project like that can be excluded on its own. Whether any client work fits your contracts is for you and your counsel to decide, and we do not give legal advice about it. Starting with your own products tends to be clearer, and internal tools frequently hold valuable history too.

Your code stays in your repos

None of your original files ever leave your systems. Nobody requests credentials, tokens or access to your repositories. License Your Data handles the copy, and a sample needs your approval before anything goes out. You can hold back any product or repository you consider core.

Tickets, logs and customer data

Logs and support threads frequently mention customers by name and include account information. The copy turns all names, whether of people, customers or companies, into placeholders, along with any addresses and account numbers. Whole repos, tools or periods may be excluded as well.

Getting started

The estimate comes first. On the first short call, describe which repositories are your own products, which hold client work, and which tools carry customer conversations. That list usually decides scope on its own. Your engineers can keep releasing throughout, since nobody needs entry to your systems. If your security lead or counsel wants to review the sample, that happens before anything goes out. Stopping is always an option before approval, and nothing has gone out.