Basically I'm interested in reading the privacy policy because I didn't like that the software asked for my name/email to start the trial, and the license only had reverse engineering restrictions and a warranty waiver.
Basically I'm interested in reading the privacy policy because I didn't like that the software asked for my name/email to start the trial, and the license only had reverse engineering restrictions and a warranty waiver.
Aside from that, Expandrive looks amazing and like it will solve a great many problems.
This is so we can use the API. It makes it sound scarier than it is.
We never capture/store any credentials. Everything stays on your client machine.
Are you going to use it for validation purposes?
Are you going to send introductory emails to the user to help them discover the features of your application?
Sorry to be the devil's advocate, but you need to explain clearly in the privacy policy why are you asking for personal information, and how are you planning to use it.