Thank you for flagging. This has been fixed. The page affected was a static file hosted outside our application only to be served when the app was inaccessible or offline. No user data was compromised at any point.