Pharmacy Smart
Privacy policy
This policy covers the restricted Pharmacy Smart WhatsApp developer pilot. The pilot is for invited testers and is not approved for public patient use.
Information handled
When an invited tester uses the pilot, it may handle:
- WhatsApp identifiers and transport metadata, message text, delivery status, timestamps, and opaque media references;
- prescription or medicine images and the health-sensitive information visible in them;
- AI-assisted readings, medicine names, strengths, types, quantities, catalogue matches, inventory observations, and alternative candidates;
- tester choices, pharmacist edits and decisions, request revisions, and audit records; and
- technical diagnostics needed to investigate failed or duplicate processing.
Why it is handled
The pilot uses this information to read a submitted request, prepare editable medicine lines, check the configured catalogue and test inventory, obtain pharmacist review, send workflow updates, prevent duplicate processing, and evaluate the pilot's reliability. Pharmacy Smart does not diagnose, prescribe, or replace the pharmacist's judgment.
Service providers and transfers
Meta and WhatsApp carry messages and media. Google Gemini may process submitted prescription evidence for AI-assisted reading. Cloudflare provides the public web and callback path used for the developer test. The current inventory flow is synthetic/local; production eVitalRx effects are not enabled in this pilot. Provider systems may retain their own operational copies under their terms. Pharmacy Smart does not sell pilot data or use it for advertising.
Human review and corrections
AI output is a draft. A pharmacist is expected to review medicine identity, strength, type, quantity, availability, and any alternative before an operational decision. Original evidence, corrections, and decision provenance may be retained for traceability during the pilot.
Retention and deletion
Developer-pilot retention is currently controlled manually and may include local workflow databases, audit records, provider copies, and diagnostic evidence. No fixed automatic deletion period is promised at this stage. Testers should therefore use synthetic or de-identified information. Deletion requests are handled through the process described on the data-deletion page; legal, safety, audit, backup, or provider-held copies may require separate handling.
Security and pilot limitations
The pilot uses bounded callback routes, signed-webhook validation, encrypted address binding, and controlled local access. No system is risk-free. The pilot is not yet a production healthcare service and should not receive emergency, diagnostic, payment, or unrelated personal information.
Your choices and contact route
You may stop using the pilot at any time. For access, correction, privacy, or deletion questions, contact the project administrator through the same channel that invited you to the pilot. A request made in WhatsApp is reviewed manually; sending a phrase does not by itself guarantee immediate deletion from Meta, Google, backups, or legally retained audit records.
Changes
This policy may change as the pilot design changes. The date above identifies the current published version. Material production use requires a reviewed production policy and operating controls.