Status and dates
Version 1.1 is effective from 29 August 2026 and was last updated on 29 August 2026. It is founder-authorized. External legal review and a formal DPDP readiness assessment are deferred.
Who is responsible
Healhab is operated by V Saravana Priya, a sole proprietor trading as Healhab, at 1/457-1, S.P. Cottage, Sathya Sai Nagar, Krishnagiri, Tamil Nadu 635002, India. Healhab's founding team owns public enquiries and privacy requests.
Public visitor data
The public site may process technical request data, consent preferences, approved measurement events after consent, information you intentionally submit in an enquiry, and information you choose to enter after activating public support chat. Technical data may include request time, route, referrer, broad device or browser information, IP-derived network or approximate-location information, error category, environment, and release.
Enquiry data
The India-focused enquiry service may collect your name, work email, mobile number with country code, clinic name, enquiry type, optional non-clinical details, consent or acknowledgement state, and a one-time request identifier. Healhab uses this information to validate, deduplicate, store, route, answer, secure, and administer the enquiry. The enquiry type, name, clinic, email, and phone number may be sent through Meta WhatsApp to configured Healhab recipients so the founding team can follow up. Public forms must not contain clinical information.
How we use information
Healhab uses public-site information to operate and secure the site, answer enquiries and non-clinical support questions, understand consented public-site usage, diagnose coded failures, prevent abuse, maintain records, and meet applicable obligations. Healhab does not use public enquiry or chat content as clinical records.
Optional public support chat
Healhab offers Tawk.to chat for product and company questions on the anonymous marketing site. The Tawk.to script remains unloaded until you choose Continue to chat after seeing the public-support warning. Tawk.to may process the messages and contact details you intentionally enter, together with technical session, browser, device, page, referrer, IP-derived network, and approximate-location data. Healhab does not set chat attributes from enquiry forms, authenticated accounts, clinic records, or family accounts. Do not share patient names, health information, recordings, reports, credentials, files, or emergency concerns. Tawk.to and its subprocessors may process information outside India, including in the United States, according to their infrastructure and terms.
Analytics and browser monitoring
Google Tag Manager and the tags configured through it, Microsoft Clarity, and New Relic Browser may load only after the applicable optional-measurement consent. Healhab's governed event adapter excludes form values, health information, credentials, and free-text enquiry content. Rejecting optional measurement does not block public content or enquiry submission.
Public-site service providers
Healhab currently relies on Cloudflare Pages to deliver the public site; Railway for application and PostgreSQL hosting; Meta WhatsApp to notify configured Healhab recipients about enquiries; Tawk.to for visitor-activated, non-clinical public support chat; and, after optional measurement consent and configuration, Google Tag Manager and its configured tags, Microsoft Clarity, and New Relic for public-site measurement and monitoring. Each provider processes data for its stated function and under its own infrastructure and terms.
Authenticated-product providers
The separate authenticated Healhab product may also use Cloudflare R2 for configured file storage, Google Gemini for configured AI or transcription processing, Meta WhatsApp for configured operational messages, and Railway for application and database hosting. Clinical and authenticated-product processing is governed additionally by clinic agreements and product notices; this does not mean every public visitor's data is sent to each product provider.
Processing outside India
Although Healhab initially operates in India, some providers may process, transmit, or store information outside India according to their infrastructure and contractual arrangements. Healhab does not promise India-only data residency. Ask Healhab about the current provider configuration before sharing information.
Retention and deletion
Healhab has not adopted a fixed automatic expiry for most public enquiries, support-chat records, operational records, provider analytics, backups, or clinical records. Information may remain stored while it is needed to operate, secure, administer, support, or document the service, resolve disputes, respond to requests, or meet applicable obligations. Stored measurement and live-chat choices remain until you withdraw them, clear browser storage, or the applicable consent version changes. Provider-held chat and technical data follow Tawk.to configuration and any later deletion action. Temporary audio and configured feedback-source files follow separate product cleanup rules where those rules are active. A deletion request may be limited where information must be retained for security, backups, legal needs, or a clinic-controlled clinical record.
Your choices and requests
You may ask what personal data Healhab processes about you and with whom it has been shared, request correction or updating, request erasure where continued retention is not necessary, withdraw consent, or submit a privacy grievance. Email from your registered address or provide your registered mobile number. Healhab may request proportionate verification before acting. The founding team tracks requests and aims to respond within 30 days. Requests concerning a clinic-controlled clinical record may need to be handled with that clinic.
Clinical customer data
Clinical and authenticated-product data is separate from a public marketing enquiry. It is also handled under applicable clinic agreements, product notices, role-based access, and the clinic's own responsibilities. Do not use a public enquiry route to submit clinical information.
Changes and contact
Healhab will update the effective and last-updated dates when this policy materially changes. For privacy, legal, security, abuse, or accessibility questions, contact the founding team. This policy does not claim that Healhab has completed a formal DPDP compliance assessment.