Re: Terms
I read through a good amount and I think they make sense. The short version helps, but that always worries me from a legal standpoint. If we summarize something in a legally ambiguous way have we undermined the original intent?
There are some inconsistencies with how you present the data that I think would help to smooth out. On your summary table. You start with the description being more of a goal for that section, than sporadically start switching to the "short version" of what your terms are.
For me I was hoping that it would be the short-version so I essentially get a comprehensive cliff-notes kind of view.
Also some minor issues with bolding some headers
4. Project Termination
4. Survival
As well as inconsistently formatting the short version. (I prefer the all bold version to help clearly show where the short part ends)
Privacy policies are much easier for me to wrap my head around. What you store, How you store it, and what you do with it.
This clause was a good idea that I will "borrow":
If our corporate structure or status changes (e.g., if we restructure, are acquired, or go bankrupt), we will notify all users so that you may choose to anonymize or delete your private data before we pass on any data to a successor or affiliate.
My version is here https://www.pritact.com/privacy-policy.html which I think follows along a lot with yours in spirit, but just has less ground to cover because of the nature of my platform.
I read through a good amount and I think they make sense. The short version helps, but that always worries me from a legal standpoint. If we summarize something in a legally ambiguous way have we undermined the original intent?
There are some inconsistencies with how you present the data that I think would help to smooth out. On your summary table. You start with the description being more of a goal for that section, than sporadically start switching to the "short version" of what your terms are.
For me I was hoping that it would be the short-version so I essentially get a comprehensive cliff-notes kind of view.
Also some minor issues with bolding some headers 4. Project Termination 4. Survival
As well as inconsistently formatting the short version. (I prefer the all bold version to help clearly show where the short part ends)
Privacy policies are much easier for me to wrap my head around. What you store, How you store it, and what you do with it.
This clause was a good idea that I will "borrow":
If our corporate structure or status changes (e.g., if we restructure, are acquired, or go bankrupt), we will notify all users so that you may choose to anonymize or delete your private data before we pass on any data to a successor or affiliate.
My version is here https://www.pritact.com/privacy-policy.html which I think follows along a lot with yours in spirit, but just has less ground to cover because of the nature of my platform.