I have updated the tos to properly cover this issue once and for all