I get that fear and it's fair. SlickGPT is OS, self-hostable and just runs locally, so you can check the code and run your own instance if you don't trust that

I get that fear and it's fair. SlickGPT is OS, self-hostable and just runs locally, so you can check the code and run your own instance if you don't trust that ours running on Vercel is on-par with the one in the repo. You can also put a soft and hard cap on your API quota on the OpenAI page and monitor it to verify that only you are using it. The key is passed (see https://github.com/ShipBit/slickgpt/blob/main/src/lib/ChatInput.svelte https://github.com/ShipBit/slickgpt/blob/main/src/lib/ChatIn...) to a Vercel edge function (see https://github.com/ShipBit/slickgpt/blob/main/src/routes/api/ask/%2Bserver.ts https://github.com/ShipBit/slickgpt/blob/main/src/routes/api...) that does the actual call to the OpenAI API. This function is stateless and doesn't store anything. I also put it in your localStorage using a store (see https://github.com/ShipBit/slickgpt/blob/main/src/misc/stores.ts https://github.com/ShipBit/slickgpt/blob/main/src/misc/store...) so that you don't have to enter it over and over again. As for the "what is this trying to solve" - read our documentation in the GitHub repo over at https://github.com/ShipBit/slickgpt https://github.com/ShipBit/slickgpt.