QuVikme
Smart Living. Everyday.
Privacy Policy
Effective date: 12 Oct 2026
This Privacy Policy (the “Policy”) explains how QuVikme Services, operating under the brand QuVikme (“QuVikme”, “we”, “us”, “our”), collects, uses, stores, shares and protects your personal data when you use the QuVikme Customer App, the QuVikme Vendor App, our website web.quvikme.com and related services (together, the “Platform”).
This Policy is published in accordance with the Information Technology Act, 2000, the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 (“SPDI Rules”), the Digital Personal Data Protection Act, 2023 (“DPDP Act”) and the Digital Personal Data Protection Rules, 2025 (“DPDP Rules”), as each applies from time to time.
By registering, signing in, continuing as a guest, or otherwise using the Platform, you confirm that you have read this Policy and consent to the processing of your personal data as described in it. If you do not agree, please do not use the Platform.
1. Who We Are and Who This Policy Covers
1.1 Data Fiduciary. QuVikme decides why and how your personal data is processed. We are the “Data Fiduciary” under the DPDP Act and the “body corporate” under the SPDI Rules.
Entity: [Registered company name] · CIN: [CIN] · Registered office: [Address]
1.2 Who this Policy covers.
| You are | Description |
|---|---|
| Customer | A person who registers to book home services such as cleaning, beauty, appliance repair, electrical, plumbing, pest control, painting and renovation, and vehicle services |
| Vendor | A service professional who registers on the Vendor App to receive and fulfil bookings |
| Vendor applicant | A person who starts or submits the Join as Vendor application |
| Guest or visitor | A person who browses the Platform without an account, or visits our website |
| Society administrator | [If applicable] A representative of a housing society who manages community access or vendors |
1.3 Independent vendors. Vendors are independent professionals and not our employees. When we share your data with a vendor to complete a booking, that vendor also handles it. We require vendors to use customer data only to fulfil the booking and to keep it confidential.
2. Personal Data We Collect
2.1 Customers.
| Category | Data |
|---|---|
| Account | Full name, email address, 10-digit mobile number, pincode, full address, password (stored in hashed form), profile details |
| Sign-in | If you use Google sign-in, the name, email address and profile identifier that Google shares with us. If you sign in with your mobile number, your number and OTP verification status |
| Addresses | Saved addresses (Home, Work, Other), map pin, default address |
| Bookings | Service, variant and quantity booked, date and time slot, service address, booking ID, status history, start OTP, coupons applied |
| Payments | Razorpay payment reference, amount, payment status, delivery and platform fees, refund requests and reasons, receipts, order and payment history. We do not store full card numbers |
| Referrals and points | Your referral code, codes you enter, friends referred, QVK points earned and redeemed |
| Communications | In-app chat with vendors, chatbot conversations, support tickets and their history, notification preferences |
| Ratings and reviews | Star ratings and comments you submit about a vendor or service |
| Location | As described in Section 4 |
| Vendor applications | Your name and email address, and any further details you submit in the Join as Vendor steps |
| Coming-soon alerts | The area you select and the contact details you give so we can notify you when service starts [confirm] |
2.2 Vendors.
| Category | Data |
|---|---|
| Account and profile | Name, mobile number (used for OTP login), profile photo, business details, address, city, service area |
| KYC and verification | Government-issued identity documents such as [Aadhaar (masked), PAN, driving licence], [police verification and photograph, if required], bank account details, results of identity and bank verification, and the reviewer’s decision and reasons |
| Services and availability | Service categories and whether each is switched on, Online or Offline status, working hours and unavailable periods |
| Subscription and deposit | Plan, start and end dates, the one-time deposit paid through Razorpay, payment references and transaction history |
| Earnings | Wallet balance and ledger, commissions, taxes, penalties, withdrawal requests and payouts, bank details |
| Invoices | Invoice records for completed bookings, including amounts and tax details |
| Job activity | Accept or reject decisions, travel and arrival status, start OTP, job milestones, completion time, proof of work [photos, if required] |
| Communications | In-app chat with customers, support tickets, notifications |
| Ratings | Customer ratings and performance metrics |
| Location | As described in Section 4 |
2.3 Collected automatically. Device model, operating system, unique device and advertising identifiers, app version, language, IP address, access times, screens and features used, crash reports, push-notification tokens, and identifiers set by cookies or software development kits (“SDKs”).
2.4 From third parties. Google (when you use Google sign-in), Razorpay (payment status and masked payment-instrument details), [identity and bank verification providers], and other users (for example, a friend who refers you).
2.5 Sensitive personal data. Under the SPDI Rules, passwords, financial information (bank account, card and UPI details) and [biometric data, if any] are sensitive personal data. We collect these only with your consent and only for the purposes in this Policy. We do not store full Aadhaar numbers unless the law requires it, and we handle any Aadhaar-related data in line with the Aadhaar Act, 2016 and UIDAI directions [confirm].
2.6 Data about other people. If you give us another person’s data, for example an address for a booking or a friend’s referral, you confirm that you are entitled to do so.
2.7 Mandatory and optional data. Some data is needed to create an account, take a booking or verify a vendor. If you do not provide it, we may not be able to offer those parts of the Platform. Guest browsing needs little or no personal data.
3. How and Why We Use Your Data
We use your personal data only for the specified purposes below. Where the basis is consent, you can withdraw it at any time (see Section 12). “Legitimate use” means a use that the DPDP Act permits without separate consent, for example where you voluntarily give us data for a service you requested, or where the law requires it.
| Purpose | Data used | Basis |
|---|---|---|
| Create and manage your account, authenticate you, keep you signed in | Account, sign-in, device data | Consent; legitimate use |
| Show services available at your location and tell you when we reach your area | Pincode, address, selected location, coming-soon alert details | Consent |
| Take, schedule, assign, track and complete bookings, including slot availability and start OTP | Booking, address, location, communications | Consent; legitimate use |
| Match bookings with eligible vendors (Online, KYC-approved, subscribed, within service range) | Vendor status, categories, service area, location, customer address | Consent |
| Verify vendor identity and bank details and decide on approval | Vendor KYC and bank data | Consent; legal obligation |
| Process payments, deposits, subscriptions, refunds, wallet entries, payouts and invoices | Payment, earnings and invoice data | Consent; legal obligation |
| Enable chat and support between customers, vendors and QuVikme | Communications, booking data | Consent |
| Operate ratings, reviews, referrals, QVK points and coupons | Ratings, referral and points data | Consent |
| Send booking updates, OTPs, security alerts and service notices | Contact details, device tokens | Legitimate use |
| Send offers and promotions | Contact details, usage data | Consent (opt-out any time) |
| Prevent fraud, abuse and safety incidents, resolve disputes, enforce our terms | All categories, as needed | Legitimate use; legal obligation |
| Maintain, secure and improve the Platform, fix errors, analyse usage | Device, log and usage data | Consent; legitimate use |
| Comply with tax, accounting, court and regulatory requirements | Transaction, invoice, KYC and account data | Legal obligation |
4. Location Data
4.1 What we collect and why.
| User | Location data | Purpose |
|---|---|---|
| Customer | The location or pincode you select, saved addresses, map pin, and device location if you allow it | Show services available near you, check vendor availability within a 5 km radius, and let you add a service address |
| Customer | Live vendor location during an active booking | Show the vendor’s journey to you after a vendor is assigned |
| Vendor | Device location while the Vendor App is in use and while you are Online or on an active booking | Match you with nearby bookings, support navigation, show your arrival to the customer, and verify that the job happened |
| Society administrator | Vendor location within the society premises (if applicable) | Community access and vendor management |
4.2 Consent and control. We ask for device location permission before collecting it. You can turn it off in your device settings at any time. Some features, such as nearby-vendor matching and live tracking, may then stop working.
4.3 Limits. We do not track customers continuously when no booking is active. Live tracking of a vendor starts only after the vendor is assigned and ends when the service is completed or cancelled. Vendor location is refreshed frequently (about every 30 seconds) while a vendor is Online or on a job, and a vendor can stop collection by going Offline. Location is shared only with the people who need it for the booking.
4.4 Vendor notice. Vendors are told that their location is visible to the booked customer during an active booking and to QuVikme at other times while Online.
5. Payments, Deposits, Subscriptions and Wallet
5.1 Payment processor. Payments are processed by Razorpay and other payment partners we may add. They collect your card, UPI, net-banking or wallet details directly. We receive only a payment reference, status, amount and masked instrument details. We do not store full card numbers.
5.2 Vendor deposit, subscription and payouts. Vendors pay a one-time deposit and a subscription fee through the payment partner. We keep a ledger of deposits, earnings, commissions, taxes, penalties and withdrawals, and we use verified bank details to pay out. The terms on which a deposit is refunded or forfeited are set out in the Vendor Terms [confirm].
5.3 Cancellations and rescheduling. When you cancel or reschedule a booking, we record the booking ID, your action, the new date and time slot (for a reschedule) and the time of the change, update the booking status, and notify you and the assigned vendor, if any. We use this data to manage the booking, prevent misuse and resolve disputes. The rules, fees and timelines for cancelling and rescheduling are set out in our Refund and Cancellation Policy [link].
5.4 Refund requests. When you ask for a refund, we collect the reason you select. We use it with the booking details and status history, the payment record and, where needed, chat messages and vendor arrival and location records, to review your request and to process any refund through our payment partner. We keep these records as described in Section 11. The conditions, amounts and timelines for refunds are set out in our Refund and Cancellation Policy [link].
5.5 Invoices and tax records. We create invoices and keep transaction records as required by tax and accounting law, including GST rules.
6. Chat, Calls and Support
6.1 In-app chat. Customers and vendors can exchange messages tied to a booking. Chat is stored so that both sides can coordinate, and so that we can handle complaints and disputes. We do not read chats routinely. We may review them to investigate fraud, abuse, safety reports or disputes.
6.2 Phone numbers. A vendor assigned to your booking may see your name, address and contact number to carry out the service. [We mask phone numbers where possible — confirm.] You must not use contact details received through the Platform for any purpose unconnected with the booking.
6.3 Chatbot and support. Messages you send to the chatbot, help centre or support tickets, and any calls with our support team [which may be recorded for quality and training — confirm], are used to answer your query and improve support.
7. Ratings, Vendor Performance and Automated Decisions
7.1 Ratings and reviews. Reviews you post may be shown to other users in connection with the vendor and service reviewed, and are used to calculate the vendor’s score.
7.2 Automated processing. We use automated rules to match bookings to vendors and to apply penalties or availability limits that are set out in the Vendor Terms. We may combine ratings, acceptance and cancellation history to assess vendor performance. You may ask for human review of a decision that significantly affects you by contacting us under Section 16.
8. Referrals, QVK Points and Coupons
If you share your referral code, we record when a friend signs up with it, and both of you may earn QVK points as shown in the app. The referrer sees counts of friends referred and points earned, shown on the Refer & Earn screen. Coupons and points are tracked against your account to prevent misuse.
9. Notifications and Marketing
We send booking updates, alerts about vendor assignment, payments and security, and, with your consent, offers. You can switch off promotional notifications in the app settings or follow the opt-out link in any promotional message. We may still send service and legal messages that you cannot opt out of while you hold an account.
10. How We Share Your Data
We do not sell your personal data. We share it only as follows, and only to the extent needed for the stated purpose.
| Recipient | What is shared | Why |
|---|---|---|
| Vendors | Customer name, service address, contact number, booking details, chat messages | To carry out the booking you made |
| Customers | Vendor name, rating, assignment status, live location during an active booking, chat messages | To let you identify, track and communicate with your vendor |
| Society administrators (if applicable) | Vendor name, verification status, entry and exit records, vendor location within the premises | Community access and vendor management |
| Payment partners (Razorpay and others) | Name, contact details, amount, order and refund details | To process payments, deposits, subscriptions, refunds and payouts |
| Verification providers | Identity and bank details of vendors | To verify identity and bank accounts |
| Technology and service providers | Data needed for their service | Cloud hosting, SMS and OTP delivery, push notifications, maps and location, analytics, crash reporting, customer-support tools. They act on our instructions and are bound by confidentiality and security obligations |
| Professional advisers and auditors | Data needed for their work | Legal, accounting, audit and insurance |
| Government and legal authorities | Data they lawfully require | To comply with law, court orders and lawful requests, or to protect rights, safety and property |
11. Data Retention
We keep personal data only for as long as needed for the purposes in this Policy or as the law requires. After that we delete it or anonymise it. The periods below are our standard approach [confirm each period].
| Data | Retention |
|---|---|
| Account and profile data | While your account is active, and for 30 days after you ask us to delete it, unless the law requires us to keep some of it |
| Booking records and booking chat | 24 months after the booking is completed, or longer while a complaint or dispute is open |
| Payment, invoice, wallet and tax records | As required by tax, GST and company law, generally 8 years |
| Vendor KYC documents and verification records | While the vendor is active, and for [period] afterwards for safety, fraud-prevention and legal purposes |
| Location data | Live tracking data is kept only for the active booking and for [period] afterwards for safety and audit purposes |
| Support tickets and chatbot records | [period] after the ticket is closed |
| Logs and security records | As required by law, and in any case for at least one year where the law requires it |
| Referral, points and coupon records | While your account is active, plus [period] for audit |
| Inactive accounts | May be deleted or anonymised after [24] months of inactivity, after notice to you |
12. Your Rights and Choices
12.1 Your rights. Under the DPDP Act, the SPDI Rules and other applicable law, you may:
- Access a summary of the personal data we hold about you and the processing we do, and the names of those we have shared it with.
- Correct, complete or update inaccurate or incomplete data.
- Erase your data, unless we must keep it by law or for a legitimate use that continues.
- Withdraw consent at any time. Withdrawal does not affect processing done before it, and it may mean we can no longer provide some services.
- Seek grievance redressal from us, and the Data Protection Board of India if you remain unsatisfied.
- Nominate another person to exercise these rights if you die or become unable to do so.
12.2 How to use them. Use the profile and account settings in the app, or write to our Grievance Officer in Section 16. We may ask you to verify your identity first. We aim to respond within [30] days, and in any case within the period the law sets.
12.3 Deleting your account. Customers can delete their account in the app. Vendors can request deletion by contacting support. Before deletion we may need to settle pending bookings, payments, wallet balance or disputes. We keep records we are legally required to keep, and delete or anonymise the rest.
12.4 Marketing and permissions. You can opt out of promotional messages, and switch off location, notification, camera, photo and contacts permissions in your device settings.
12.5 Complaints to the Board. You may complain to the Data Protection Board of India once it is operational for complaints and you have first raised the matter with us and not had a satisfactory response.
13. Data Security and Breaches
We use reasonable security practices consistent with the SPDI Rules and the DPDP Act. These include encryption in transit and, where appropriate, at rest; hashed passwords; single-use OTPs that expire; role-based access controls; restricted access to vendor KYC documents; secure server infrastructure; and regular security reviews. We require our service providers to apply equivalent safeguards.
No system is completely secure, and we cannot guarantee absolute security. Please keep your password and OTPs confidential and do not share them. Share your booking start OTP only with the vendor assigned to your booking.
If a personal data breach occurs, we will notify the Data Protection Board of India and the affected people, in the manner and time the law requires.
14. Children
The Platform is for people aged 18 and above. We do not knowingly collect personal data from children, and we do not track or target advertising at them. If we learn that we hold a child’s data without verifiable consent of a parent or lawful guardian, we will delete it promptly. If you believe a child has given us data, please contact us.
15. Third-Party Links and Services
The Platform may link to or integrate services of third parties, such as payment gateways, maps or Google sign-in. Their privacy practices are their own, and we are not responsible for them. Please read their policies.
16. Grievance Officer and Contact
For questions, requests or complaints about this Policy or your data, please contact:
Grievance Officer / Data Protection Officer: [Name]
QuVikme: [Registered company name and address]
Email: [privacy@quvikme.com]
Phone: [Number], [days and hours]
We will acknowledge your complaint within 48 hours and aim to resolve it within [30] days, and in any case within the period the law sets.
17. Changes to This Policy
We may update this Policy from time to time to reflect changes in our services or the law. We will change the “Last Updated” date and, for material changes, tell you through the app, by email or by notice before the change takes effect, and ask for fresh consent where the law requires it. If you keep using the Platform after the effective date, the updated Policy applies to you.
18. Governing Law and Jurisdiction
This Policy is governed by the laws of India. Subject to any rights you have under law, the courts at [Pune, Maharashtra] have exclusive jurisdiction over disputes arising from it.
