The day Maa stopped trusting the till

It was a Tuesday. Lunch had thinned out, the cooler was humming, and Maa was sitting at the corner table with her copy and pen. A regular had asked if his wife's number from last month was “in the system.” She wanted to send him an order on her way home.

Maa called me over. She did not want me to look up the number — she wanted me to notlook up the number. “Beta,” she said, “woh log apne app pe daal lete hain. Pata nahi kahan jaata hai sab.” The customer ended up writing his wife's number on the back of the bill, and Maa called him in the evening from her own phone.

That is the day I started thinking properly about Maatrachhaya. Not because of one customer's number — but because of what that small refusal said about every screen in our restaurant.

What Maa already knew

Maa runs the floor of our family restaurant in Moradabad. She has done it through three POS systems, four printers, and at least seven software updates that nobody asked for. She knows every dish by feel, every regular by name, and every shortcut that keeps the day moving.

What she did not know — and never had a reason to learn — is which company stores the number she just punched in. Whether their server is in Delhi or Dublin. Whether their support team can read it. Whether, three years from now, that company will still exist or will have sold its database to someone else. She is not paranoid. She is a small-business owner, and her instinct about other people's software is the same as her instinct about other people's kitchens: I would rather not.

Most POS vendors solve this with a paragraph in their privacy policy. We thought that was the wrong layer to solve it at.

What “easy” really means

I tried every POS we could find before writing a single line of code. Each one was built for someone else: chains with IT teams, owners who live on dashboards, managers comfortable with training videos. None of them was built for the person actually running the floor — someone who had spent her life cooking, not clicking.

Most of them confused “simple” with “fewer features.” Maa does not need fewer features. She needs fewer questions. One screen for billing. One for the kitchen. One for today's numbers. No tabs three levels deep. No English she wouldn't use at the chai stall. If she can run a Saturday lunch without picking up a phone for help, we have got it right.

Why we chose to build it encrypted

The first product decision I made was the strangest one to explain to other founders: I wanted Maatrachhaya's servers to be unable to read our own customers' data. Not by policy — by architecture. The keys would live on the merchant's device. Our database would store ciphertext. Even with full database access, our team would see encrypted bytes.

It is harder to build. Some features become more careful — search, analytics, support. We accepted that, because the alternative is the same conversation Maa already had on a Tuesday afternoon: woh log apne app pe daal lete hain. Pata nahi kahan jaata hai sab.If we could not look her in the eye and say “we don't hold the keys,” the product was not done yet.

That choice is now the spine of the product. You can read exactly how it works, in plain English, on the security page.

Why this work matters

Most restaurants in India are not chains. They are families. Mothers, fathers, sons, daughters — keeping a kitchen running between school runs and account books. They did not sign up to be IT managers, and they should not have to pay extra to feel at home in their own till.

Maatrachhaya is for them. For Maa, in this kitchen. And for every Maa, in every kitchen, who deserves software that gets out of her way — and a vendor who could not betray her trust even if they tried.

She still keeps the copy and pen, by the way. Some habits don't retire. Most days she does not need them. Some days she does. And either way, the till is finally hers.