Privacy Policy

Ojas Care’s long-term purpose is a network of residential care, longevity and Ayurvedic healing campuses in India. No campus exists. It is not built, nothing about it is offered or collected for here, and this policy does not govern it. What this policy is about is the part that runs: a booking layer for spaces. Senior living suites, assisted rooms, Panchakarma units, cottages, and restorative halls are listed here by independent supply partners; you search, hold and pay for one on this site. We are not the property owner, developer, or the on-site employer for any listed space.

Where this policy refers to “your stay,” the physical space and the people running it day to day are a supply partner’s responsibility, not ours.

We collect only what a booking, a listing, or a support request actually needs:

• Contact details — name, email, phone — to confirm a booking or a listing.
• Booking details — dates, space, headcount, and payment status.
• Identity information a supply partner or applicable law requires for check-in, held as a tokenised reference wherever the underlying system supports it — never stored as plain-text government ID numbers by us.
• Usage data — pages viewed, device and browser information, for reliability and fraud prevention, and — where this deployment has analytics switched on — for the page-view measurement described under Cookies and analytics below.

We do not operate a biometric or smart-lock access system, and we do not collect data for a roommate-compatibility or matching engine — neither exists on the platform today.

• To create, confirm, modify, or cancel a booking.
• To route a listing enquiry to the right supply partner, and to work out what they are owed on a booking. We do not split or pay out their share ourselves — that is agreed and settled with them directly, as our Terms say.
• To send booking confirmations, receipts, and service messages.
• To respond to support requests and enforce our Terms of Service.
• To meet tax, accounting, and regulatory record-keeping obligations.

We share the minimum necessary with:

• The supply partner fulfilling your booking — the operator needs your name, contact details, and stay dates to prepare for your arrival.
• Payment processors to capture a payment and process a refund. We do not store full card numbers ourselves.
• Service providers who host our infrastructure or send transactional communications on our behalf, under contract.
• Law enforcement or regulators, only when legally compelled.

We do not sell personal data, and we send no booking, guest, or supply-partner record to any advertising network. What the site’s page-view analytics can send is a separate matter, and the section below says exactly what it is.

Two cookies are ours, and the site needs both: a session cookie that keeps you signed in, and a preference cookie that remembers your theme so pages paint correctly on first load. Your browser also keeps a cart token and a few interface preferences in its own local storage, on your device.

Analytics, stated plainly. This site is built to load Google Analytics 4 and the Meta (Facebook) pixel. They load only on a deployment that has been given a measurement id or a pixel id and has analytics switched on; with neither configured, no Google or Meta script is loaded and nothing is sent to either. Where they are configured they set their own cookies, and the only thing our code tells them is which page you opened — no booking, guest, or payment record is passed to them, because nothing on this site calls them with one. Google and Meta then collect their own technical details, such as your IP address and browser, and may use what they collect to measure and target advertising on other sites.

There is no cookie consent banner here, and we do not detect a Do Not Track or Global Privacy Control signal. Saying otherwise would be a promise the code does not keep. To stop the analytics scripts, block or clear cookies and scripts for this site in your browser settings, or use a tracking-blocker extension or Google’s Analytics opt-out add-on — the site works normally with all of it blocked. Payment providers may set their own cookies on their checkout components, governed by their policies.

We do not collect or hold a security deposit for a stay. If a supply partner asks you for one, they take it from you directly, on their own terms, and it never passes through this site — so we hold no deposit of yours, and nothing you pay here sits in escrow. Payment and refund records for what you do pay on this site are kept for the periods applicable tax and accounting law requires.

We retain booking and financial records for as long as required by applicable law (typically several years for tax and accounting purposes), and account data for as long as your account remains active plus a reasonable period to resolve disputes. You may request erasure of data we are not legally required to retain.

Under the Digital Personal Data Protection Act, 2023, you may request access to, correction of, or erasure of your personal data, and may withdraw consent where consent is the basis for processing. Contact privacy@ojas.care to exercise these rights; we aim to respond within the statutory timeline.

We apply tenant isolation, role-based access controls, and encryption in transit (TLS) across the platform. Out-of-scope data access attempts are refused rather than exposed. No system is perfectly secure, and we will notify affected users of a confirmed breach as required by law.

We may update this policy as the product or the law changes. Material changes will be communicated through the site or by email.

Questions or requests: privacy@ojas.care.