[iambrakes]

I appreciate your concerns. Let me see if I can ease them. The intention is to make this product as useful as possible at a good price. The license is in place to try and keep a few basic things from happening.

1.) Purchaser buys SoundKit then adds the sounds to a commercial product like a toolkit that they want to sell. Or they add the sounds to a website template that they sell to others. Anything where another user would come along and use those sounds commercially for their own projects.

2.) Purchaser buys SoundKit then gives it to their friends for free.

3.) Purchaser buys SoundKit then places it on a server at an office for everyone to use.

4.) Someone accesses a repo who doesn't have a license for SoundKit, they pull the sounds and use them on another project.

On the other hand, if you buy the license and then you work on a project like a web or mobile app and you want to add the sounds, go for it. If someone else adds to the project or makes changes, that's not a problem. As long as a license owner is involved with the project and added them.

I really don't want to limit the use of the product, I just have to try and keep from everyone giving it to everyone for every use. And regarding the company issue, I should add a multiuser license. It is common in these situations.

At the end of the day, most people are probably not using their licenses correctly for all sorts of design elements, but this gives us some sort of protection in a worst case scenario.

I'll try and update the wording of the license to be as clear as possible for future buyers. If you have already purchased, feat not, the usage will become more flexible, not less.

[BHSPitMonkey]

> On the other hand, if you buy the license and then you work on a project like a web or mobile app and you want to add the sounds, go for it.

Those scenarios involve redistributing the audio files to a public audience, which the license loudly forbids in its current form.

[iambrakes]

The license works the same as any other license you probably have for fonts, images, sounds, etc. For example, if you load a web font in an app, you most likely have a single use license, but thousands of users may use the font when they use the app. They don't however have a right to use that font in other applications.

This is similar. However, I'm going to work on wording that makes the concerned users more comfortable. I understand that this is a tricky situation. And I'm much more interested design then legal matters. I hope I can ease the concerns.