We are working on a resolution to this issue right now. This is an issue with our logout function on the frontend not removing the auth token. There is no risk of scope access outside of your machine.
We will push out a fix shortly.
EDIT: Fix has been deployed. Thanks again!
It now just redirects to the auth page. Clicked on the back button in my browser and voilà
From the screenshot that was provided, they're seeing the client render a page, but it's failing to acquire any data from the API. If they opened the network inspector they'd likely see that the requests are 401'ing after logging out.
I'm not pretending that this is good UX -- it's not -- but it's not evidence of a security issue. That said, we have every intention of nailing down fantastic UX as quickly as possible. (I'm a recent addition to the company but) it pains me personally for anyone to see any mistakes and I hope to impress you soon.
I see some issues with the current version of the product. I think it is 2 cycles behind from being really ready for the the market. First cycle would be feature parity and second cycle could be for robustness because there are alternative that are better. EZSQL is nice but feel very gimmicky.
But there is potential. I know YC's advice is to launch as soon as possible but it is not applicable for all domain and products esp. in enterprise because you have only have few shots to impress people and decision maker are few.
Having said that, there is potential. I am not sure how you can scale the integrations with dbs really fast. You will start seeing problem when you venture out of standard databases and start integrating clickhouse, big query etc. Also, you should consider Grafana as your competitor too as major engineering enterprise do use Grafana as their admin panel.
PS. please take my feedback with grain of salt.
But I think you guys will figure it out.
[1] https://app.outerbase.com/databases
[2] https://app.outerbase.com/settings