Skip to content
Build in Public

Actually live. And then the lawyers showed up.

The door opened. Real traffic, real money, real legal obligations I'd been pretending didn't exist.

SD
Shubham Datarkar
· 3 min read
Updated

The door opened today. Not the rehearsal, not the load test, not the "hand on the handle" dramatic pause. The actual, real, strangers-can-find-you-on-the-internet open. PROJECT_STATUS flipped to prod-live. And the first thing that happened wasn't a booking. It was a lawyer in my head saying "where's your privacy policy?"

Turns out, the moment you go live with a product that handles personal data and payments in India, you're not just a builder anymore. You're a data processor under DPDP, and if you serve anyone in the EU (you will, eventually), you're under GDPR too. These aren't optional. These aren't "add later." These are "a regulator can fine you if a user asks where their data goes and you shrug."

So today, alongside the euphoria of being actually live, I wrote the pages nobody reads until they need them: Privacy Policy, Terms of Service, Refund Policy. Each one honest, each one written in plain language instead of lawyer-fog, each one telling the truth about what we collect, why, and what happens if you want it gone. The DPDP Act is clear about consent and purpose limitation. I'd rather get it right now than retrofit honesty later.

The rename that changed everything

And then the other big move: the great "Vendor" to "Host" rename. Every screen, every API route, every database reference, every piece of copy. It sounds cosmetic. It's not.

"Vendor" is transactional. A vendor sells you something and disappears. "Host" is relational. A host welcomes you into their space. Yukta isn't a vendor -- she's hosting a session. Mukesh isn't vending coworking time -- he's hosting people in his space. The language shapes how the product feels, and "vendor" made it feel like a marketplace. "Host" makes it feel like what it is: a platform where independent professionals welcome their people.

One word. Every file. Worth every find-and-replace.

The rest of launch day

Dynamic sitemap generation so Google can actually find us. Newsletter signup so people who aren't ready today can come back tomorrow. An industry-category taxonomy so hosts can be discovered by what they do, not just who they are. And a feedback widget in the host dashboard -- because the single most important thing on launch day isn't celebrating. It's listening.

The door is open. People are walking in. And the first thing I learned is that launching doesn't end anything. It starts everything.

by Shubham DatarkarBuild in Public

Reactions

How was this article?

Newsletter

Never miss the next one

Get the latest playbooks, build logs, and the occasional unpublished idea straight to your inbox. One signal a week — no noise.