OopsLock

Bank staff need LLMs, but leaks are unacceptable. OopsLock blocks risky prompts locally and only allows overrides via an NFC tap, adding a physical human-in-the-loop gate without slowing work.

Comment

Inspiration We leaked so much private information into chatGPT... it's kinda concerning at this point

What it does OopsLock is a Chrome extension that sits between employees and LLM chatbots. It scans prompts locally for sensitive patterns and blocks high-risk submissions instantly. If the user truly needs to proceed (or if we detected a false positive), they must physically approve with an NFC tap, so risky actions can’t happen “by accident”

How we built it though blood sweat and tears...

Challenges we ran into oh so many.

Accomplishments that we’re proud of Our demo works in 67% of the time. The code is clean, readable, and well-documented. We did not sleep.

What we learned So much about how NFCs work, how painful CORS can be if it wants to, and how troublesome ngrok can be.

What’s next for OopsLock

Big money.

Built With

Share this project:

Updates