Terms of Service
These are the working terms for every project I take on at VelrixTech — mainly app builds, plus the occasional website or software work that supports them. It's not a 40-page legal document. It's the rules we both work by, written the way I'd explain them to you on a call.
TL;DR
- Every quote is indicative until we confirm scope in writing.
- Payments are milestone-based — small advance, then stage-wise. You only pay for work you've approved.
- On full payment you get the complete source-code handover, and everything stays in your name.
- 30 days of free support after launch.
- Either of us can pause or exit at a milestone — you keep everything delivered and paid for.
How do quotes and project scope work?
Every quote I give is indicative until we've confirmed the scope in writing. Before any money changes hands, we agree the exact features, deliverables and timeline — usually over WhatsApp or email — and that written summary becomes the plan we both work from.
App projects go wrong when scope stays vague. A ballpark from a first call can shift once we get into the details — screens, logins, backend, admin panel — so I'd rather over-clarify up front than surprise you later. What moves a quote up or down is in the app cost guide; typical durations are in the timeline guide.
How do payments work?
Payments are milestone-based. You pay a small advance to start, then the rest in stages as each phase of work is completed and approved by you. You never pay for work you haven't seen and signed off on.
In practice: you approve the design in Figma before development starts, you review working builds as they come, and each payment stage only comes due after you've approved the one before it. No large upfront amount, no paying blind — the milestone system protects you as much as me.
What about revisions and new requirements?
Revisions are included, as long as they fall within the scope we agreed in writing. If you want something significantly new — a feature we never discussed, or a change of direction — I'll quote it separately as an addition, and always before doing the work.
The line between the two is common sense. Adjusting a screen's layout or rewording text — revision, included. Adding a payment module to an app scoped without one — new work, quoted separately. Either way, you'll never see a charge you didn't agree to first.
Who owns the app when it's done?
Everything ends up in your hands. On full and final payment, I hand over the complete source code, and everything runs in your name from day one — your Play Store and App Store accounts, your domain, your hosting. No lock-in, nothing held back.
Your app gets published under your own developer accounts, not mine. Don't have them yet? I'll help you set them up in your name (Google Play is $25 one-time, Apple's Developer Program $99/year — paid directly to the platforms). Why this matters is explained in the guide to hiring an app developer.
What support do I get after launch?
Every project includes 30 days of free post-launch support. If a bug turns up or something breaks in that window, I fix it at no extra charge. After 30 days, ongoing maintenance or new features are quoted separately whenever you need them.
What that covers: fixing things that were in the agreed scope but aren't working right — free. New features you thought of after launch — new work, scoped like any other job. Most clients just message me on WhatsApp and we sort it out.
Beech me project rokna pade to kya hoga?
Koi problem nahi. Aap bhi aur main bhi — dono kisi bhi milestone boundary par project pause ya exit kar sakte hain. Jo kaam deliver ho chuka hai aur jiska payment ho chuka hai — code, design, sab — woh aapka hai, aap le ja sakte ho.
Budget change hota hai, priorities shift hoti hain — startup life me yeh normal hai, main isko personally nahi leta. Milestone system isi liye hai: har stage ek clean exit point hai. Koi cancellation penalty nahi, koi "kill fee" nahi — bas jo stage chal raha hai usko settle karke alag hote hain.
What happens if there's a disagreement?
We talk — like adults, first. Almost every project dispute I've seen traces back to a miscommunication somewhere, and a straight conversation fixes it faster than any legal clause. If I've made a mistake, I'll own it and fix it at my cost.
The written scope we agreed at the start protects both of us — it's the reference point when memories differ. I won't pad this page with jurisdiction and arbitration boilerplate copied from someone else's website. If something genuinely can't be resolved by talking, we deal with it honestly, in writing, step by step.
A note on these terms
This page is in plain language on purpose. Your written project scope plus this page is our working agreement. If anything is unclear, ask me before we start — I'd rather answer ten questions now than have one misunderstanding later. For how I handle your data, see the privacy policy; for everything else, the FAQ covers it.
Want anything here clarified before you start?
Ask me directly — about payments, handover, scope, anything. Before you spend a rupee.
Free consultation · Reply within 24 hours · No sales pitch
Last updated: 10 July 2026 · Found something outdated? Tell me and I'll fix it.