Terms of service & privacy policy pages

{"ops":[{"insert":"Hi there, I'm one of archidekt's devs.\n\nSomething seems to have gone wrong with one of our plugins we use to render markdown pages so thanks for pointing that our to us! We'll get that fixed asap. \n\nHere is the "},{"attributes":{"link":"https://storage.googleapis.com/topdekt-user/text/terms_of_service.md"},"insert":"raw link"},{"insert":" to our ToS, and a link to the "},{"attributes":{"link":"https://storage.googleapis.com/topdekt-user/text/privacy_policy.md"},"insert":"privacy policy"},{"insert":". Feel free to go through that if you want, but you're welcome to make whatever videos you want using archidekt so long as you're not making things up we'll be fine (regardless if what you're saying finds archidekt in either a good or bad light). \n\nThat said if you'd prefer, we could just attempt make the view count better. In what ways isn't it up to snuff? Or is the issue with it largely that it can be gamed for more views? If that's the case, that's one of the major reasons we don't really use that as a metric for anything other than a fun \"hey look at this\" kind of metric. \n\nWe've talked about making that view count something more dynamic to show decks on the home page or something, but if that were the case, that view count would need to be made more stringent, as well as implementing some kind of algorithm that figures out which decks to feature. \n\nIn any case looking forward to hearing your thoughts, and thanks for letting us know that our markdown renderer isn't working correctly!\n"}]}