Legal
Terms, privacy & the agreement
Plain language first. Where a term matters, it is bolded rather than buried.
1. Using this website
This site exists to explain what Shree Dev builds and to collect project enquiries. Sending an enquiry does not create a contract, a booking, or an obligation on either side.
Demo storefronts are illustrative. Names, products and prices inside a demo are placeholders and are not an offer for sale.
What we publish, and what we do not
- We do not publish prices we have not verified against current market sources.
- We do not publish client work, logos or photographs without written permission.
- We do not use testimonials that we cannot attribute to a real, consenting client.
Third-party names
Brand names such as Google, WhatsApp, Amazon, Flipkart, Razorpay or courier companies belong to their owners and are used descriptively only. Shree Dev is not affiliated with, endorsed by, or an agent of any of them.
2. Privacy note
What we collect, and why
- Enquiry form: business name, your name, phone, email, locality, how you sell today, and what you want the site to do. Used to reply to you and to scope a project. Nothing else.
- Partial answers: the form saves as you type. If you leave without submitting, those partial answers may remain on your device and, once the form is connected to a server, may reach us so we can help you finish.
- Prospect research: we use official public business listings (such as the Google Places API) to identify businesses that could benefit from a store. We collect business-level details — shop name, category, locality, public business phone — not profiles of individuals.
What we never do
- We do not scrape websites or map listings to harvest contact details.
- We do not sell, rent or trade your details.
- We do not add you to a list you cannot leave.
Being removed
Every outreach email carries a removal link. Asking on the phone or by reply works too. We honour removal within 24 hours and keep a suppression record so you are never re-added.
Where the data lives
Enquiries are stored in a database provisioned for the project, with access limited to the people building it. For a delivered project, the database is provisioned in your account and ownership transfers to you at handover.
Cookies and tracking
This site sets no advertising cookies and runs no third-party analytics scripts. The enquiry form uses your browser’s local storage so a draft is not lost. Clearing site data removes it.
Your requests
Ask for a copy of what we hold about your business, or ask us to delete it, and we will do so within 30 days — except where a signed project agreement or tax law requires us to keep an invoice.
3. Payment, refunds and maintenance position
These are the positions we hold. Your signed agreement states your actual numbers and supersedes anything general written here.
Payment structure
- A booking amount to start the build, and the balance before handover.
- Work stops if an agreed milestone payment is unpaid for more than 14 days, after one written reminder.
- All amounts, taxes and due dates are on the invoice, in INR.
Refunds
- Before work starts: the booking amount is refundable in full.
- Once build has started: refundable pro-rata for undelivered scope, less work already done and any third-party costs already paid (domain, hosting, courier accounts, payment gateway setup).
- After handover: the build fee is not refundable. Maintenance is cancellable at the end of any paid period.
Maintenance
- Maintenance is a separate, explicitly stated monthly or annual rate. It is never bundled invisibly into the build price.
- It covers monitoring, verified backups, security and dependency updates, small content changes within an agreed monthly limit, and a written monthly report.
- It does not cover new features, redesigns, content entry beyond the agreed limit, or fixing damage caused by third-party edits made outside our instructions.
- It is cancellable with 30 days’ notice. If it lapses, the site keeps running on your own accounts; you keep every credential.
Handover condition
Full access — admin credentials, database ownership, hosting and the domain — transfers after the final payment clears. Before that you review a staging URL. The domain is registered in your name, or transferred to you on payment, so it can never be used as leverage against you.
4. The project agreement (template)
This is the shape of the document you will sign. The signed version is generated per project from your form answers, carries your selected scope and your price, and is timestamped and hashed on our server when you submit your signature.
4.1 Parties
Shree Dev (“the Developer”) and the named client (“the Client”), with the Client’s business name and address as provided on the intake form.
4.2 Scope
The scope is the exact list of features selected on the intake form, reproduced in Schedule A of the signed agreement. Anything not listed in Schedule A is out of scope and, if wanted later, is quoted separately before it is built.
4.3 Price and payment
Total project fee, booking amount, balance due date, and applicable taxes as stated on the invoice. This amount is final for the stated scope. Maintenance charges are stated separately and are not part of the project fee.
4.4 Delivery
The delivery date is stated in the agreement and starts when the Client’s content (product data, images, logo) is complete. Delays caused by missing client content move the date, not the price.
4.5 Intellectual property and data ownership
On receipt of the final payment, the Client owns the delivered site, its content, its database and the domain. The Developer retains the right to reuse generic components, libraries and non-client-specific code. Third-party software keeps its own licence.
4.6 Maintenance
Maintenance is governed by the separate rate and terms stated in the agreement, beginning on the handover date, cancellable with 30 days’ notice.
4.7 Liability
The Developer is not responsible for the Client’s product quality, stock accuracy, courier performance, payment-gateway decisions, or content the Client supplies. Total liability is limited to the fees paid for the project.
4.8 Termination
Either party may terminate in writing. On termination the Client pays for completed work and third-party costs already incurred, and receives the corresponding files.
4.9 Signature
Signing electronically is binding. On submit, the agreement is frozen as a PDF, hashed, timestamped from the server (not the browser), and emailed to both parties with the timestamp, IP and document hash recorded.
Read this before signing anything we send.
If a sentence in your agreement contradicts this page, the agreement wins — it is the document written for your project. Ask us to change it before you sign; we would rather edit a clause than argue about it later.