3 ms·
Using any ticket/bug/issue tracker is better than not using one. That said, much of the information you put in one of these is really sensitive, perhaps even c
by dsr_ 6y ago
Using any ticket/bug/issue tracker is better than not using one.
That said, much of the information you put in one of these is really sensitive, perhaps even confidential and quite often embarrassing if leaked.
So. Privacy policy? Extremely generic, and doesn't guarantee you anything.
Terms of Service?
"We take no responsibility and assume no liability for Content you or any third party posts on or through Service. However, by posting Content using Service you grant us the right and license to use, modify, publicly perform, publicly display, reproduce, and distribute such Content on and through Service. You agree that this license includes the right for us to make your Content available to other users of Service, who may also use your Content subject to these Terms."
I don't know about you, but I don't really want the discussion of security-critical bugs in my product to be publicly reproduced and made available to other customers.
Maybe fix this, Linear?
- fwip 6y agoI'm pretty sure that's bog-standard EULA for "We need to show the tickets you made to other users on your team."
- dsr_ 6y agoBut that's not what it says, so it's not appropriate. "We keep the data that you store with us confidential. Our staff will not look at it unless you specifically ask us to investigate a specific issue. Other than legal requirements (e.g. a valid subpoena) we won't share it with anyone unless you've identified them to us as part of your team or otherwise authorized to see your data." You should always say what you mean in contracts.
- jorde 6y agoThanks, we'll be updating our ToS soon and addressing this feedback. We take user privacy and security extremely seriously (many of us worked at Coinbase) and would never expose anything without your consent. I think this clause was for potentially opting into public sharing but it's not something we do.