Software companies keep customer data out.

How your software is developed and supported

Engineering teams leave a long, detailed record of their decisions:

• Your repos and the commits behind them
• Review comments on each pull request
• Tickets and bugs traced from the first report to the fix
• Test and build history
• Architecture write-ups and release notes

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 withhold any repository or product that you consider central.

When tickets and logs hold customer data

Logs and support threads frequently mention customers by name and include account information. In the copy, placeholders replace each person, customer and company, as well as addresses and account numbers. Any tool, repo or time period can also be left out entirely.

Code owned by clients may stay out

Code written for clients may be owned by those clients. You can exclude it on a project by project basis. Whether any client work fits your contracts is for you and your counsel to decide, and we do not give legal advice about it. The simplest start is often your own products, and your internal tools can hold history that is every bit as useful.

Getting started

The estimate comes first. In the first short call, say which repositories hold your products, which contain work for clients and where conversations with customers live. That list alone usually settles the scope. Your engineers can keep shipping the whole time, because no one needs access to your systems. Should your head of security or counsel want to review the sample, they do so before anything is shared. You can stop at any point before you approve, and nothing has been shared.