Built by an indie dev who hated privacy policies.

I was learning SwiftUI and React Native for my internship. As part of the learning process, I built a simple unit conversion app — length, weight, temperature conversions. Nothing fancy.

But to publish it, I needed a privacy policy. With a hosted URL.

I'd built apps before and always used Notion for hosting. But seriously, why use Notion for this? It's clunky, unorganized, and not built for legal documents.

Plus, I was planning to go indie. I wanted to build and ship multiple apps. I couldn't afford to set up a website and pay for hosting every single time just for a privacy policy URL.

So I looked at existing tools.

And they all sucked.

Pain point after pain point kept piling up.

Initially, GetClauseApp was just a personal project. I wasn't planning to make it public.

But then I thought: if I'm facing this problem, every other indie dev probably is too. There's a clear market gap.

So I decided to build it in the open and make it free for the community.

Hi, I'm Akshat Srivastava (@iamkahanikaar on Twitter).

I'm a final-year B.Tech CSE student from India and an iOS developer by trade. I'm currently doing my second internship, and I've been building apps for the past few years.

Projects I've built:

• GetClauseApp (obviously)
• Fix My Ride (highway assistance app)
• AEGIS (home surveillance system with edge AI)
• Sounair (gesture-based music player — hover your hand to control music)
• 20+ other apps, hackathon projects, and experiments

The app I'm most proud of? Hard to say. Every project taught me something. But if I had to pick one, it'd be the first real-world app I built during my first internship — the first app published to the App Store that an actual end user was going to use. That felt different.

Beyond code:

I write Hindi/Urdu poetry under the pen name @iamkahanikaar.

Poetry is my way of processing the world. I observe a lot — I like to watch, listen, and notice things most people miss. Then I write it down.

It's how I spend time alone and talk to myself.

Why I don't like social media:

Honestly? I hate it. I'm only on Twitter now because building GetClauseApp forced me to be. Before this, I was a pure consumer — scroll, learn, move on.

But I wanted GetClauseApp to reach developers. And for that, I had to show up.

So here I am.

GetClauseApp is free for indie developers. It always will be.

Why?

Because I'm a huge fan of products like VLC and WinRAR. They're useful. They're reliable. And they've never charged you for basic use.

GetClauseApp follows the same philosophy.

I built this as my way of giving back to the developer community. GitHub is free. Stack Overflow is free. GetClauseApp should be free too.

What stays free:

• Unlimited privacy policy generation
• Updates to your policies anytime
• Basic compliance (GDPR, DPDP)

Will there be paid tiers?

Yes. Eventually.

But not for basic hosting. That'll always be free.

Paid tiers will be for advanced features like:

• App Store submission guides
• CCPA and additional regional compliance templates
• Priority support for small teams and startups
• Advanced analytics on policy views

The goal isn't to gatekeep. It's to make GetClauseApp self-sustaining so I can keep building it.

The hardest part wasn't the code. It was figuring out the Case System.

Existing tools ask you 50 questions. Who's going to answer all of that for a simple app?

I wanted a better way:

• Effective
• Easy to use
• Covers all the important stuff
• Asks the minimum number of questions

That's where the Case System came from.

You tell GetClauseApp:

• Do you collect data? (Yes/No)
• What data do you collect? (Email, location, etc.)
• Why do you collect it? (Analytics, functionality, etc.)
• Do you use third-party services? (AdMob, Firebase, etc.)

That's it. 6–8 questions max.

Based on your answers, GetClauseApp auto-generates the relevant clauses. If you don't collect location data, you don't see location-related questions.

It took me 3–4 days just to figure out the logic. But it was worth it.

Right now, GetClauseApp generates privacy policies. But the vision is bigger.

Coming soon:

• App Store submission guide: Step-by-step answers for App Store's confusing data collection questions
• Google Play submission guide: Same thing, but for Google Play
• Age rating questionnaire: Automate that too
• Terms & Conditions generator
• Cancellation & Refund Policy generator
• Additional regional compliance: CCPA and other regulations

The goal is simple: end-to-end compliance for indie developers.

You shouldn't have to spend 3 hours Googling legal stuff. You should spend 3 minutes on GetClauseApp and get back to building.

One year from now (May 2027):

Success for me looks like this:

• Small teams and startups are using GetClauseApp
• Schools, hospitals, and local businesses that just need to 'be compliant' are using it
• GetClauseApp is funding itself, so I can scale to a bigger team

I want GetClauseApp to be community-driven, not just an indie dev's side project.

Not specifically for privacy policies. But I've been rejected for related issues:

• I said I don't collect names, but I accidentally ticked the name collection box. Rejected.
• I built an app for my internship company with a login system but didn't include a delete account option. Rejected.
• I used Google AdMob but didn't request Apple's App Tracking Transparency permission. Rejected.

Each rejection taught me something. And each one reinforced why GetClauseApp needs to exist.

I'm an iOS dev by trade, so my setup revolves around that.

GetClauseApp is that product.

Ship it faster. Don't overthink it.

I'm still struggling to get users right now. But you know what?

GetClauseApp has already changed so much since I launched it a week ago:

• Email masking feature added
• Templates updated
• Questions improved. We now ask why you collect data, not just what data.

If you have an idea, build the MVP and ship it. Don't wait for perfection.

You'll learn more in one week of real users than in one month of building in private.

If you're reading this, here's what I'd love from you:

1. 1Try the product. See if it solves your problem.
2. 2Give me honest feedback. If you liked it, tell me what worked. If you didn't, tell me what needs to improve.
3. 3Spread the word. If GetClauseApp helped you, share it with another indie dev.

GetClauseApp isn't just my project. It's a community-driven product.

The more feedback I get, the better it becomes.

If you're worried about privacy policies, you're already one step ahead of most developers.

Most devs just blindly follow templates and hope for the best.

You care enough to be here. That's a good sign.

Give GetClauseApp a shot. It's free. It takes 3 minutes. And if it saves you even one hour of frustration, I've done my job.

— Akshat