UPDATE: My cofounder has just found the bug and deployed a fix. Refresh and it shouldn't happen again.