Pushpa uses trusted AI platforms to analyse documents and power conversations. When you send a health document, relevant content is transmitted to these processors in an encrypted request. We do not attach your phone number, account login, or other account identifiers to these requests — only the document content and the medical context needed to read it. A document is sent as it appears, so where a patient name is printed on the report it forms part of what is read; this is how Pushpa can tell whose report it is.
In the mobile app, we ask for your explicit consent before your first AI conversation or document upload. Your companion messages, uploaded health documents — and, during live sessions, your voice and anything you show on camera — are processed by the AI platforms below to generate responses. This can include health details you choose to share. It is used only to answer you — never for advertising, and never to train or fine-tune any AI model. You can decline and continue using the rest of the app.
Our third-party processors
ServicePurposeCountry
Google AI (Gemini)
Document vision analysis and extraction, AI conversations, and live voice/video companion sessions (real-time processing)
USA
Google AI (Imagen 3)
Medical illustration generation for reports
USA
Amazon Web Services (S3)
Encrypted file storage for health documents
India / Singapore
Meta (WhatsApp Cloud API)
Messaging platform for all WhatsApp interactions
USA
Twilio
SMS OTP delivery, voice call infrastructure
USA
Expo
Push notifications for iOS and Android
USA
Each processor is bound by a Data Processing Agreement (DPA) and their own published privacy policies. Data submitted through these APIs is never used to train or fine-tune any AI model.
The mobile app also loads static decorative images and 3D visuals from content delivery networks (Pexels, icons8, unpkg/Spline). These requests contain no personal or health data.
Analytics & diagnostics
To keep the app stable and understand how it is used, we use PostHog for product analytics and session replay, and Google Firebase for crash reporting, performance monitoring, and push notification delivery. In session replays, text inputs and images are masked so recordings do not capture readable medical data, names, or document contents. These services receive usage events, a device push token, and diagnostic data — not your health documents — and process it in the United States. You can turn analytics off at any time in the mobile app under Profile → Privacy → Share usage analytics.
ServicePurposeCountry
PostHog
Product analytics and masked session replay
USA
Google Firebase
Crash reporting, performance monitoring, push delivery
USA