This is something that I keep wondering for each product that I built. Usually I'd go for something that is generated by some online services but then I don't really understand the contents and not really sure
A. About it's legality in global context
B. Best practices
C. Whether I'm missing something
The same goes for Privacy policy document
What are some good resources or questions to that can help in creating these documents with decent understanding.
P.S. I am a developer
Is it necessary? No.
Does it help these tech companies from getting sued? Yup.
I keep mine short, simple, and easy to read. I try to keep it around 10 points.
But this is basically what I've got it down to:
1. By using this product, you agree to these terms // stating your company name and the copyrights to your name (that no one can use it but you).
2. Service: what the service is and what it does.
3. Privacy policy: letting user know what info you collect, including cookies & usage.
4. Disclosure of any of that data: do you keep it for yourself or share it with third-parties?
5. GDPR-compliance and protection of the data you collect (including sharing it with government agencies if you are running a platform that might have some questionable materials, etc.)
6. Analytics: while you are talking about data, are you using any third-parties to collect data?
7. Pricing/Payment/Refunds: if you have a third-party service running the charges, they are collecting data -- so you should divulge the service you are using and also show they have a privacy policy. Or in regards to pricing --that it may be subject to change but notice will be given.
8. Changes to terms/privacy policy: letting user know that these terms may change -- if they do, you will email them or you are allowed to change them on your own without letting them know.
9. Statement about what they own when they are using their product -- for example: if your product creates something for the user, do they own that or do you still own everything or are they able to claim ownership?
10. Final statement about ensuring proper use of the product, your state's laws (you will use this product accordingly within reason of the State of California laws), etc.
There can be subcategories within these or you can create your own. But I'd rather keep the legal jargon to a minimum. Basically, the Terms of Service and Privacy Policy just shows who you are, that you are acting to the best of your ability and with good intentions with your own product and service, as well as user data, and that should anyone try to sue you -- you have some "legalities" set up to protect yourself and your own customers.
I hope this helps. It is great to use a generator, but sometimes... it's easier just to write up a quick template for all of your products and follow it.