PharmaGO Privacy Policy
Effective date: April 28, 2026 Last updated: April 28, 2026
This Privacy Policy describes how BayTech ("we", "us", "PharmaGO") collects, uses, shares, and protects information in connection with the PharmaGO mobile application (the "App") and the related services available at https://pharmagoapp.co (together, the "Services").
By creating an account or using the Services you agree to the practices described in this policy. If you do not agree, do not use the Services.
1. Who we are
PharmaGO is operated by:
- BayTech (the data controller)
- Contact: support@pharmagoapp.co
- Postal address: provided on request to support@pharmagoapp.co
For questions about this policy or to exercise your rights, contact us at support@pharmagoapp.co.
2. Information we collect
We only collect data we need to operate the App. Categories:
2.1 Account & identity
- Phone number (E.164 format) — primary identifier and OTP login.
- Email address — optional for customers, required for pharmacies and delivery personnel for receipts and operational communication.
- Full name — for receipts, courier handoff, and pharmacy verification.
- Role — one of
customer,pharmacy,delivery, oradmin. - Password — only used by the pharmacy + delivery + admin roles; stored hashed by Supabase Auth (we never see the plaintext).
2.2 Address & location
- Saved delivery address(es) — manually entered street address; we parse it into structured city / region / postal code / country.
- Approximate and precise device location — used only by the delivery role during an active delivery to route orders and update ETA. Location collection stops as soon as the delivery is completed.
- The customer role may use coarse location to surface nearest-pharmacy hints; this is opt-in and never broadcast to other users.
2.3 Health-related content (prescriptions)
- Prescription images — uploaded by customers at order time, optionally OCR-scanned on-device using ML Kit. Images are linked to the order record and only visible to (a) the ordering customer, (b) the receiving pharmacy, (c) the assigned delivery driver, and (d) PharmaGO admin staff for fraud / dispute resolution.
2.4 App activity & device
- Audit logs — login events, role switches, order state transitions, push-notification opt-in changes. Logs are retained for security investigations.
- Push notification token (Firebase Cloud Messaging device token) — to deliver order/delivery updates.
- Device metadata — OS version, app version, locale, time zone — used for crash diagnostics via Google Play Vitals.
2.5 We do not collect
- Contacts, SMS, call logs, photos outside of those you explicitly upload, browsing history, financial account numbers, or biometric data.
- We do not use third-party advertising SDKs, third-party analytics SDKs, or third-party trackers.
3. How we use information
We use information to:
- Authenticate you (OTP / password login).
- Create and fulfill orders — sending the prescription and delivery address to the pharmacy and delivery driver assigned to that order.
- Route deliveries and provide live tracking to the customer.
- Send order, delivery, and account notifications.
- Detect fraud, abuse, and security incidents (audit logs, anomaly detection).
- Comply with applicable law (e.g., responding to lawful requests from authorities).
- Improve the App by reviewing aggregated, non-identifying performance metrics surfaced by Google Play Vitals.
We do not sell or rent personal data, and we do not use your data for behavioral advertising.
4. Legal bases (where GDPR / similar laws apply)
| Purpose | Legal basis |
|---|---|
| Account creation, order fulfillment, delivery routing | Performance of a contract |
| Audit logs, fraud prevention, security | Legitimate interests |
| Push notifications | Consent (you can revoke at any time in OS settings) |
| Background / precise location during delivery | Consent (delivery role only, prompted in-app) |
| Tax/regulatory record-keeping | Legal obligation |
5. Sharing of information
We share data only with the parties needed to operate the Services:
| Recipient | Data shared | Purpose |
|---|---|---|
| Supabase (database, auth, storage, realtime) | All operational data (account, orders, prescriptions, audit logs) | Backend hosting / storage |
| Firebase Cloud Messaging (Google) | Push notification token + payload | Delivering push messages |
| Google Maps / location services | Coarse and precise coordinates during a delivery | Map rendering and ETA |
| The pharmacy and delivery driver assigned to your order | Your delivery address, name, phone, and prescription image | Order fulfillment |
| Law enforcement / regulators | Only what is legally compelled | Compliance |
We do not share data with advertisers, data brokers, or analytics aggregators.
6. International transfers
Supabase and Firebase may process data in regions outside your country of residence. We rely on the standard contractual clauses (or equivalent) provided by those processors for international transfers.
7. Retention
| Data | Retention |
|---|---|
| Account profile | Until account deletion |
| Order history (incl. prescriptions) | 24 months from delivery, then archived in encrypted storage and purged after the legal minimum required for tax/regulatory reasons |
| Audit logs | 12 months rolling |
| Push tokens | Until revoked or device unregisters |
| Live location | Discarded after the delivery completes (only ETA + final delivered position is retained on the order record) |
8. Your rights
Depending on your jurisdiction, you may have the right to:
- Access the personal data we hold about you.
- Correct inaccurate data (most fields are editable in-app under "Profile").
- Delete your account and associated data ("Delete account" in-app, or email support@pharmagoapp.co).
- Export your data in a machine-readable format.
- Withdraw consent (e.g., revoke push notifications or location permission via your device's OS settings).
- Object to processing or request restriction.
- Lodge a complaint with your local data-protection authority.
We respond to verified requests within 30 days.
9. Children
PharmaGO is intended for adults (18+). We do not knowingly collect data from children. If you believe a child has registered, contact support@pharmagoapp.co and we will delete the account.
10. Security
- All traffic uses TLS to Supabase REST/Realtime and Firebase services.
- Passwords are hashed by Supabase Auth (we do not see plaintext).
- Row Level Security (RLS) policies in Postgres enforce per-user data isolation, including for audit logs.
- Prescription images are stored in access-controlled storage; the URLs are not enumerable.
No system is perfectly secure; if you suspect unauthorized access, contact us immediately.
11. Permissions we request on Android
| Permission | Why |
|---|---|
CAMERA | Photographing prescriptions for upload and OCR. |
ACCESS_FINE_LOCATION / ACCESS_COARSE_LOCATION | Live delivery routing (delivery role) and nearest-pharmacy hints (customer role, optional). |
POST_NOTIFICATIONS | Order status updates (Android 13+). |
FOREGROUND_SERVICE + FOREGROUND_SERVICE_LOCATION | Continuous delivery tracking when the app is backgrounded by the driver. |
FOREGROUND_SERVICE_REMOTE_MESSAGING | Reliable handling of high-priority order messages while the app is killed. |
RECEIVE_BOOT_COMPLETED, WAKE_LOCK, VIBRATE | Re-arm scheduled notifications after device restart and ensure timely delivery. |
INTERNET | Connectivity to backend Services. |
You can grant or revoke any permission in your device's OS settings; the App degrades gracefully (e.g., scanning is disabled without CAMERA).
12. Changes to this policy
We may update this policy. The "Last updated" date at the top will change, and material changes will be communicated in-app or via email. Continued use of the Services after the change constitutes acceptance.
13. Contact
- Support / privacy requests: support@pharmagoapp.co
- Website: https://pharmagoapp.co
- Privacy policy URL: https://pharmagoapp.co/privacy
This document is the canonical source. The version hosted at https://pharmagoapp.co/privacy must mirror this file 1:1.