Privacy for users and pandits

This Privacy Policy explains how Puja Partner ("we", "us") collects, uses, shares, and protects personal information when you use our website and services to discover, book, or provide pooja and ritual services in India.

Last updated: July 17, 2026

Everyone

Account, location, device, and notification data.

Read section

Users

Addresses, bookings, wallet, payments, and reviews.

Read section

Pandits

Profile, KYC, payouts, services, and Pandit Network.

Read section

Sharing & rights

Processors, retention, security, and requests.

Read section

Who this policy covers

This policy applies to users who book pandits, pandits (experts) who offer pooja services, and visitors who browse public pages. By creating an account or using Puja Partner, you acknowledge this Privacy Policy together with our Terms and Conditions and Refund Policy.

All Accounts

Information we collect from everyone

Account and identity

Name, email address, phone number, password (stored in hashed form), role (user, pandit/expert, or admin), profile photo, email verification status, and account active status.
Referral code, referred-by relationship, referral reward status, and account timestamps (created and updated).
Address, city, state, pincode, latitude, and longitude when you register, update your profile, or save a location.
Login, session, and security-related data needed to authenticate you and protect your account.

Device, notifications, and usage

Firebase Cloud Messaging (FCM) push tokens when you allow push notifications on a supported app or device.
Browser and device information reasonably needed to run the website, debug issues, and keep sessions secure.
In-app notifications, email delivery records, and realtime event activity related to bookings, wallet, and account updates.
Auth tokens and limited preferences may be stored in your browser (for example localStorage or sessionStorage) so you stay signed in and the product works correctly.

User Privacy

Privacy terms for users booking a pandit

What we collect from users

Saved service addresses including house/flat details, landmark, area, city, state, pincode, receiver name, receiver phone, coordinates, and default-address preference.
Booking details: selected pandit, ritual/pooja type, date and time, service option (with or without pooja samagri), service location, notes, payment status, and booking lifecycle status.
Start and end approval actions, rejection reasons, OTP verification for arrival/completion flows where used, and related timestamps.
Wallet balance and ledger entries such as booking payments, refunds, referral rewards, and related descriptions.
Razorpay payment order references and verification records (not full card numbers).
Reviews, ratings, and feedback you submit after a completed pooja.

How user data is used

To create your account, verify your email, manage your profile, and show nearby or recommended pandits.
To place and manage bookings, enforce the 24-hour advance booking rule, process payments, and handle refunds to your wallet.
To share necessary service details with the assigned pandit so they can reach the correct venue and perform the pooja.
To send booking, payment, refund, reminder, and support communications by email, in-app notification, push, or realtime updates.
To operate referral rewards, prevent fraud or misuse, and improve matching, reliability, and support.

What users can see about others

Public pandit profile information such as display name or nickname, photo, city/state, bio, expertise, languages, service areas, travel radius, ratings, and listed pooja services with prices.
You do not see another user’s private addresses, wallet balance, payment credentials, or personal account settings.
Pandit KYC documents, bank account numbers, UPI IDs, and payout details are never shown on public profiles.

Pandit Privacy

Privacy terms for pandits and experts

What we collect from pandits

Public profile data: name, nickname, profile photo, bio, experience, expertise, languages, city, state, service areas (up to platform limits), travel radius, rating, and total bookings.
Onboarding and Pathshala/training profile details, weekly availability slots, and active status.
Pooja/service listings: names, descriptions, duration, pricing (with and without samagri), inclusions, exclusions, samagri lists, media, muhurat settings, languages, devotee limits, and notes.
Verification status, rejection reasons, onboarding progress, and compliance submission metadata (for example new joining or bank re-verification).
KYC and payout data: Aadhaar front/back images, PAN image, payout method, account holder name, account number, bank name, branch, IFSC, and UPI ID.
Expert wallet ledgers: earnings, commissions, penalties, Pandit Network plan purchases, withdrawals, and admin payout decisions.
Pandit Network data: help requests, availability posts, festival availability, contact number on requests, dakshina range, location, and response status.

How pandit data is used

To verify identity and approve or reject expert access before public booking features are fully enabled.
To display your public profile and services to users searching for pandits and poojas.
To match bookings to your availability, service areas, and ritual offerings, and to run start/end confirmation workflows.
To calculate earnings after platform commission, process wallet credits, apply policy penalties where applicable, and handle withdrawal requests.
To operate Pandit Network subscriptions, help requests, emergency replacement flows, and related notifications.
To investigate fraud, policy violations, disputes, and payout or KYC compliance issues.

Public vs restricted pandit data

Public or discoverable: profile summary, services, pricing, ratings, city/state, service areas, and availability signals needed for booking.
Restricted to you and authorized admins/ops: Aadhaar, PAN, bank/UPI details, full wallet ledgers, withdrawal requests, and compliance files.
When you create a Pandit Network help request or availability post, eligible verified pandits may see the ritual, date/time, location, dakshina, and contact details you provide for that request.

Platform Practices

Sharing, storage, and your controls

How we share information

With the other party to a booking: users and pandits receive the minimum details needed to complete the scheduled pooja.
With admins and authorized operators: for verification, support, refunds, payouts, disputes, safety, and platform operations.
With Razorpay: to create and verify payment orders. We store payment references and ledger amounts, not full card credentials.
With Brevo: to send transactional emails such as verification, password reset, booking updates, and refund notices.
With Cloudflare R2 (object storage): to store profile photos, KYC images, ritual media, and operational backups.
With Firebase: to deliver push notifications when you have provided an FCM token.
With Google Places (where used): to help you search or confirm addresses and coordinates.
When required by law, to protect rights and safety, investigate fraud, or respond to lawful requests.

Location privacy

Location is used to save addresses, show nearby pandits, match service areas, create bookings, and power Pandit Network nearby matching.
You may search for an address or use device location detection where the product supports it.
Accurate coordinates are required for many booking and network workflows so the pandit can reach the correct venue.

Cookies and local storage

Puja Partner primarily uses browser storage (such as localStorage for auth tokens and remembered email, and sessionStorage for short-lived UI/session cache) rather than relying on advertising cookies.
These technologies are used for authentication, session continuity, maintenance-mode awareness, and basic product function—not for selling your personal data.
You can clear browser storage or sign out to remove local auth data, though that will require you to log in again.

Retention, security, and your rights

We retain account, booking, wallet, payment, refund, verification, payout, and dispute records as needed to provide the service, meet legal and accounting needs, prevent fraud, and resolve disputes.
Payment ledgers, completed bookings, commissions, penalties, and payout history may be kept even after profile changes because they are operational and audit records.
We use authentication, access controls, payment signature verification, ledger checks, and admin restrictions to protect data. No online system is perfectly secure.
You may request access, correction, or deletion of eligible personal data by contacting support. Some requests may be limited by legal, payment, dispute, fraud-prevention, or accounting requirements.
Puja Partner is intended for people who can lawfully create an account and book or provide services. Do not submit another person’s identity documents, bank details, or contact data without permission.

Privacy requests and contact

To request access, correction, deletion of eligible data, or privacy support, contact hello@pujapartner.com or call +91 93277 23447. We may need to verify your identity before acting on a request. Operations are based in Surat, Gujarat, India.

Terms and Conditions Refund Policy