1. Introduction
This Privacy Policy explains how Pi Health (π) collects, uses, stores and protects information when you use our healthcare applications ("the Apps"). Pi has personal local workflows and connected Clinic/Hospital modes. For pricing and the free tier, see our Terms of Service.
We have written this to describe what the software actually does today, not what it may do later. Where something is planned but not built, we say so.
2. What Information We Collect
- Your account: your email address, which is how you sign in, along with your name, contact details and clinic locations. Signing in uses a one-time code sent to your email, so we do not store a password for the free apps.
- Patient data: the records you enter, including demographics, medical history, vitals, consultation notes, prescriptions and lab or imaging results. This is held on our servers as described in section 4.
- Operational data: logs needed to keep the service running and secure, such as errors and sign-in events. We do not use third-party analytics.
3. How We Use Your Information
- To provide the clinical features you are using.
- To keep the service secure, available and backed up.
- When your clinic has enabled an AI-assisted feature, to send the minimum relevant prompt and clinical context to the configured AI provider and return a draft for a healthcare professional to review.
- To answer your support requests.
- To tell you about material changes to the service.
We do not profile you, and we do not use patient data to decide what to show you.
4. Where Your Data Is Held
This differs by product, and the differences are real, so they are set out separately.
Personal local mode
- The personal local workflow stores records in a device-local database. It does not automatically upload them to Pi Health or make them available on other devices.
- Clinic/Hospital browser access connects to a configured dedicated server. Personal mode and connected server mode have different storage and access boundaries.
- Device-local data stays on the device unless you deliberately transfer it. User-controlled backup, restore and optional sync are still in development.
Chorda and Maxima (clinics and hospitals)
- Each customer gets their own application instance, database, database role and credentials. A time-bounded trial may share a PostgreSQL server with other Pi Health products, but never a database or schema. A trial that converts to paid production is moved to dedicated database infrastructure as part of that conversion.
- Where that instance runs is agreed with you, and can be outside India.
Self-hosted
- You run the software on your own infrastructure and hold your own database. We do not receive your patient data at all.
- If you configure an external AI provider, information sent through that feature leaves your infrastructure and is handled under your agreement with that provider. Pi Health does not receive those requests.
5. How We Protect It
- Connections between your browser and our servers are encrypted in transit.
- Personal automatic backup and restore are not ready. Server backup, retention and recovery arrangements must be confirmed for each licensed deployment; do not assume a device-local record has a remote recovery copy.
- Connected deployments use their team access controls. Native local identity is separate; production device unlock and recovery features are still being developed.
- We do not claim any certification or third-party audit. We describe the measures we take rather than naming a standard we have not been assessed against.
6. Who Else Is Involved
- We do not sell patient data or share it with sponsors. Sponsorship is a proposed funding programme and is not operational today.
- Advertising or sponsor branding is not an operational personal-app funding programme today. Any future programme must be disclosed before launch and must not share patient records.
- Our hosted services use contracted infrastructure. This applies to data deliberately stored in connected deployments, not automatically to device-local personal records. Hosting and backup arrangements are documented for each deployment.
- An explicitly enabled connected AI feature may send selected clinical context to its configured provider. Confirm the provider, consent, retention and contractual terms for your pilot. Future managed AI services and pricing are not announced here.
- Transactional email: Resend receives the email address and sign-in or service message needed to deliver it. We do not put patient records in those messages.
- We may disclose information where the law requires it.
7. Your Rights and Choices
- You can access and correct your data in the Apps, and ask us to delete it.
- Getting your data out: there is no self-service export yet. One is being built. Until it exists, ask us and we will provide your records to you.
- Deleting your account removes your records from the live service. Scheduled database backups and provider-managed recovery copies may keep historical bytes for their documented retention period afterwards. They are not restored except for disaster recovery, and expire through the applicable backup-retention process.
- If you are a patient rather than a doctor, your records were entered by your clinician, and requests about them should go to that clinic. We will help them respond.
8. Changes to This Policy
We will update this page when the service changes, and change the date at the top when we do. Material changes will also be communicated in the Apps.
9. Contact Us
For questions, support, data requests or complaints, please get in touch. If you are not satisfied with our response, the DPDP Act gives you the right to complain to the Data Protection Board of India.