Privacy policy for the WhatsApp pilot

Aarogya Sarthi LLP operates this WhatsApp pilot. This notice covers the pilot and the backend account it creates when someone messages the pilot number. It does not cover other app features, existing patient reports, or any future report-processing service.

The pilot sends a welcome message, a reminder, or an attachment acknowledgement. It does not offer medical advice or a report interpretation.

When you message the pilot number, WhatsApp’s Cloud API sends our webhook a message event. That event can include your WhatsApp sender identifier and phone number, a message identifier, message type, text, and information about an attached photo or document. We read the incoming event in memory to check Meta’s signature and decide which fixed reply to send.

Delivery and status events may also reach the webhook. They are acknowledged separately and do not create a reply or a conversation record.

• An internal account ID, account and sender-link timestamps, an active-account flag, your WhatsApp sender identifier, and the phone number represented by that identifier. A new account also receives a default profile called “Self”; creating this WhatsApp-linked backend account does not require an email address or password.
• A per-account count of received messages and the time that conversation record was last updated.
• For each accepted inbound message: Meta’s message ID, the receiving business Phone Number ID, the linked account ID, the fixed reply selected by the pilot, its sending state, and related timestamps. These records help prevent repeat replies when Meta retries a webhook.

The temporary webhook proxy logs the request time, method, and HTTP response status. The WhatsApp handler writes generic operational error messages, such as a failed reply, without adding the message body or sender identifier.

We do not persist the text you send, a media file ID, or the contents of a PDF or photo in these WhatsApp tables. The current pilot does not download attachments, inspect existing patient reports, or call an AI model.

We use the sender link to recognise a returning person, the conversation count to choose the appropriate acknowledgement, and message IDs and sending state to handle duplicate deliveries and retries. We attempt to send the selected fixed reply to your WhatsApp number through Meta’s Cloud API.

The current pilot does not use WhatsApp messages to analyse reports, build a medical history, or make health predictions.

Messages and our replies pass through WhatsApp and Meta’s Cloud API. WhatsApp’s own handling of information is described in its privacy policy.

For this local pilot, a temporary Cloudflare HTTPS tunnel forwards only the webhook route to our local backend. This connection is temporary.

Our retention limit for pilot accounts, WhatsApp identity links, conversation state, and inbound-event records is 30 days after collection. Known on-disk operational log files have a seven-day limit. Operators use a manual cleanup tool with a 29-day database cutoff; deletion is not automatic or scheduled. Retention of terminal/session output remains under review.

You may request earlier deletion at support@aarogyasarthi.com. To verify control of the linked WhatsApp account, we send a short-lived code to that account and ask you to provide it to support. A phone number supplied by email alone is not enough. After verification, an operator manually deletes the pilot account and its linked conversation and event records and clears inventoried local pilot backups and logs.

A WhatsApp-only account has no password, so the existing app account-deletion endpoint is not a self-service deletion route for this pilot.

For questions about this pilot or requests concerning your pilot account information, email Aarogya Sarthi LLP at support@aarogyasarthi.com.