I Was Hospitalized Twice for Food Allergies - So I Built an App to Stop It From Happening Again

Photo Credit: Hunter Chang
When I was seven, I drank a cup of soy milk that had been heated in a pot previously used to cook peanuts.
I don’t remember what it tasted like, or who handed it to me. What I remember is walking into a hospital in Irvine and getting the first open room right away. I remember waking up to Wreck-It Ralph on TV, and staying until nighttime. It all felt so normal, and the thing that put me there was something I couldn’t even see.
Two years later, it happened again, this time at home. Somehow, peanut M&M’s had gotten mixed into a bowl of regular ones. I ate them, went to sleep, and threw up on my bed. My mom saw it on our home security camera and rushed me to a hospital in Santa Monica.
I have life-threatening nut allergies, and those two nights taught me that the most dangerous allergens are often the ones you can’t see.
Both times, the information I needed existed. The pot had been used for peanuts. The peanut M&M’s were right there in the bowl. I just didn’t have that information when it mattered. And it doesn’t get easier as you get older. Labels are tiny, cross-contact warnings are easy to miss, and at a restaurant or a friend’s house, there’s often no label at all.
When you have a severe food allergy, knowing what’s in your food isn’t enough. You also need to know what it touched.
That’s why I built TraceCheck.
The name comes from that first reaction: a trace of peanut left in a pot. With TraceCheck, you photograph a meal or scan a package’s barcode, and it checks the food against the allergens you choose, including “may contain” warnings. It never tells you a food is “safe.” Instead, it flags what might be there and what it can’t know, because I’d rather someone see an extra warning than miss one that matters.
Building it was harder than I expected. Soon after I put the app online, photo scans stopped working, and the live site wouldn’t show me why. I had to dig through the server logs, where I finally found it: some photos labeled as PNG files were actually WebP, and the AI refused to accept the mismatch. The fix was to convert every upload to JPEG before sending it, which also let me shrink big phone photos.
Because allergen profiles are health information, guests can use the scanners without an account, and nothing they scan is saved. If you do make an account, TraceCheck keeps only your email, your allergens, and text records of your scans. It never keeps your photos, and each person can only see their own records. Meal photos are sent to Anthropic’s Claude API for analysis, but TraceCheck doesn’t retain them.
TraceCheck isn’t finished. Next, I want to turn on email verification and let users delete their accounts. And it’s a tool for information, not a replacement for reading labels, asking restaurants, or following your allergy action plan.
For a long time, I thought living with food allergies meant being afraid of food. I’ve learned it also means speaking up, asking questions, and finding ways to take control when you don’t have all the information.
So if there’s one thing I’d tell another teenager with food allergies, it’s this: you’re not being difficult by asking what’s in your food. You’re not overreacting by asking about cross-contact. Your safety is worth the extra question.
I built TraceCheck because I wish I’d had something like it when I was seven. Here’s the app if you would like to try it out: https://food-allergen-scanner.streamlit.app/
_edited.png)




Comments