121

Inspiration Every app I use takes a piece of my privacy. Every WiFi login, every loyalty card, every "create an account to continue." I had dozens of apps — one for each restaurant, one for each store, one for each gym — and every single one collected more about me than it needed to.

It hit me one day: in the real world, I don't have to do this. I walk into a coffee shop, I order, I pay, I leave. They don't know my name. They don't know my email. They don't know my location history. That is normal life. So why does the digital version of the same interaction demand all of me?

We built 121 ("One to One") so the digital version can work the same way. Anonymous by default. You only share what's actually required — never more.

What it does 121 is a privacy bridge between you and every business around you. Open the app, tap "Search Nearby," and 121 finds the places near you — your favorite chains and real local businesses. Tap a place and you get their menu, ordering, and checkout, all inside 121. The business sees an order; they never see your name, your phone, or your location.

You can even order for multiple people: name each item ("Burrito for Eugenio, salad for Sofia") so the kitchen knows whose is whose — without ever knowing who Eugenio or Sofia really are.

The same idea extends past restaurants: shops, gyms, doctor's offices, airports — anywhere you currently "create an account just to use the WiFi." One app. Every place. Total privacy.

How we built it Stack: React + TypeScript + Vite, styled with Tailwind, deployed on Vercel. Live prototype: 121-app.vercel.app Team: A two-person, father-and-son team. I'm the "idea guy" — I designed the experience and built the prototype using AI pair-programming (Claude Code). My son handles the deeper technical architecture and reviews every change I push. He merges what's ready and pushes back on what isn't. Design philosophy: 121 does NOT rebuild what businesses already have. They already have menus, ordering, and checkout. 121 just frames it with a privacy layer — a shield around the business's existing platform. Challenges we ran into Making privacy concrete. Saying "we protect your data" is noise. Showing a real Chipotle order placed without sharing a name is signal. The whole demo had to be built so the privacy story shows itself. Scope discipline. 121 could be a hundred things. We kept narrowing it to "the privacy bridge for any business connection, starting with WiFi" — because diffuse ideas don't get funded. Building as a non-technical founder. I had to design the app, learn enough about how the code works to direct it, and trust the review process with my son to catch what I'd miss. Telling the story without jargon. The deck, the video, the screens — everything has to land for someone who has never thought about a WiFi captive portal in their life. That has been the hardest engineering problem of the project. Accomplishments that we're proud of A working live prototype anyone can open in their browser, not a slideshow. Designed and shipped by a two-person father-and-son team, with no outside funding. Selected by F6S as a notable early-stage project. The "name your order" feature solves a real, everyday problem (ordering food for the family) — while making the privacy story click instantly. Built something that delivers value from day one, without requiring any business to sign up first. What we learned A concept this abstract ("privacy") doesn't sell on its own. A demo where you order a burrito named "Eugenio" and a salad named "Sofia," and the restaurant never learns who they are — that sells. The shortest path from idea to investor was a working prototype we could put in someone's hand, not a deck. The line between "non-technical founder" and "builder" is mostly tooling. With the right AI tools we can ship real screens. With my son's review, we can ship them safely. The technology for 121 already exists — WiFi, captive portals, websites, phones. The innovation isn't a new technology. It's turning the control around. What's next for 121 Summerfest Tech 2026 — booth + stage pitch for prize and investment. First open-access pilots — partnering with a handful of local coffee shops and restaurants to run 121 on real WiFi. From WiFi to the web — extending the 121 privacy layer to website sign-ups and app account creation, where the same problem exists. Native iOS and Android apps — moving from prototype to production-ready mobile builds. A growing community of "121-protected" users who, just by existing, make every business they walk into ask: who is 121, and why do my customers want it?

Built With

• ai
• apis
• built-with-what-languages
• cloud-services
• databases
• did
• frameworks
• or
• other
• platforms
• react-typescript-vite-tailwind-css-react-router-vercel-openstreetmap-overpass-api-nominatim-geolocation-api-node.js-github-claude-(for-claude-code
• technologies
• the
• you