Ask HN: How do I protect myself when providing freemium SaaS product?
I've been developing a service that applies version control ideas to a fairly conservative field and would appreciate tips on ensuring I protect myself, legally, from possible issues that may be created when I open it to the public.
As a Canadian university student who's been on HN for awhile, I have a vague idea of what I should do- terms and conditions, separation of financials, and copyright notices- but have no comprehensive, or coherent, solution regarding how to avoid legal trouble which is expensive, time consuming, and generally unpleasant.
Thanks for any tips or guides you may have.
5 comments
[ 3.0 ms ] story [ 25.2 ms ] threadA more HN-style recommendation is to not provide a freemium B2C product, but to provide a paid B2B product. That is, do not invite general users to abuse your system for free, but rather encourage serious businesses to pay for your service. This will attract more lucrative, less problematic customers. If you have questions on how to do this given your product, post a Show/Ask HN about it. :)
[1]: https://github.com/Automattic/legalmattic