🗓️ Last updated: 12 September 2026
🔎 The short version
Shubhzo is a marketplace, so unlike most MyAppsCart apps it does need an account and it does hold data about you. What it will not do is hand your contact details to a stranger because they clicked a button.
- We collect what a booking needs — your name, mobile number, email and the details of the events you create.
- Neither party's phone number or email is given to the other until a booking is confirmed. Before that the server returns masked values; there is no hidden field for an app to reveal.
- We do not sell your data, and we do not share it with advertisers.
- You can delete your account, and the data attached to it, from inside the app.
📋 What we collect
Everyone
- Account details — your name, mobile number and email address, and the one-time codes used to verify them.
- Your chosen language and display preferences.
- Device information needed to deliver notifications, and basic diagnostic data when something goes wrong.
If you are planning an event
- Event details — occasion, dates, city, guest count and the checklist of services you are booking.
- Bookings and payments — what you booked, the token and balance amounts, payment status, receipts and refunds.
- Guests you add — names, and phone numbers where you provide them, so invitations and RSVPs can be sent.
- Approximate location, only if you use the "use my current location" shortcut to set a city. You can type the city instead.
If you are a vendor
- Business details — business name and type, services, service areas, address, pricing and portfolio photos. Most of this is deliberately public: it is your storefront.
- KYC and payout details — identity and address documents, PAN, and bank account details, which are required before we can pay you.
- Business documents you upload, such as licences and insurance, along with their expiry dates.
Guest lists are your responsibility too. When you add someone else's phone number to a guest list, you are sharing their data with us. Please only add people who would expect an invitation from you.
🎯 Why we hold it
| Data | What it is for |
|---|---|
| Mobile & email | Signing you in, confirming a booking, and reaching you about one. A booking cannot be delivered to an account we cannot contact. |
| Event & booking details | Running the booking itself — the checklist, the token window, quotes, payments and reminders. |
| Payment records | Receipts, refunds, vendor settlements, and the tax records we are required to keep. |
| Vendor KYC | Verifying that a business is real before customers pay it money, and paying the vendor afterwards. |
| Reviews | Shown publicly against the vendor, with your display name. |
| Diagnostics | Finding and fixing faults. Not used to build a profile of you. |
🔒 Contact details, and who gets them
This is the part worth reading twice, because it is the rule the whole marketplace is built on.
- When you send a booking request, the vendor is told what you want, when and where — not who you are. Your number appears to them as
+91 98765•••10. - The same is true in reverse: you do not get the vendor's number for making a request.
- A message thread exists from the moment a request arrives but stays locked until the vendor accepts, so a request cannot be used to harvest a phone number.
- When the vendor accepts, both sides get each other's details at the same moment, because from then on you have a booking together.
- If a request expires unanswered, nobody ever learns anything about the other.
This is enforced on the server. The masked value is what the server sends. There is no unmasked copy sitting in the app waiting to be uncovered.
🤝 Who we share it with
We share the minimum needed to make a booking happen, and nothing for advertising.
- The vendor you book — your name and contact details, once the booking is confirmed, plus the event details they need to do the job.
- The customer who books you, if you are a vendor — the same, in reverse.
- Payment processors — to take payments and issue refunds. They receive what a payment needs, not your event or guest data.
- Government and tax authorities — where the law requires it, including TDS deducted on vendor settlements.
We do not sell personal data, and we do not share it with advertising networks or data brokers.
⏳ How long we keep it
- Your account and events — until you delete your account.
- Payment, invoice and settlement records — for as long as tax and accounting law requires us to keep them, even after an account is deleted. These are financial records, not profile data.
- Reviews — they stay attached to the vendor after an account is deleted, but are detached from your name.
- Diagnostic data — a short retention window, then discarded.
🛠️ Your choices
- See and correct your details — Account → Profile, at any time.
- Turn off notifications — per channel, with quiet hours, in Settings.
- Skip location entirely — type your city instead of using the GPS shortcut.
- Delete your account and its data — see Delete Account.
- Ask us anything — support@myappscart.com.
👶 Children
Shubhzo is for adults arranging events and for businesses serving them. It is not directed at children, and we do not knowingly create accounts for anyone under 18. If you believe a child has created an account, write to us and we will remove it.
✏️ Changes to this policy
If this policy changes in a way that affects you, we will say so in the app rather than quietly editing this page. The date at the top always reflects the current version.
✉️ Contact
Questions about this policy, or about data we hold: support@myappscart.com. We aim to answer within two working days.