Last updated: 14 September 2026
This policy explains what personal data the BARKA GO mobile applications collect, why we collect it, who we share it with, and the choices you have. It covers two apps:
com.barkago.client) — the customer app for booking
rides, deliveries, food orders and pharmacy requests.com.barkago.driver) — the app used by drivers
and by pharmacy staff to receive and fulfil those orders.Both apps are operated by BARKA GO ("we", "us"). Contact details are at the end of this policy.
| Data | Why |
|---|---|
| Phone number | This is how you sign in. We send a one-time code by SMS and use the number to identify your account and to contact you about an order. |
| Approximate and precise location | To show nearby drivers, set pickup and drop-off points, follow a trip in progress, and calculate distance and price. |
| Notification token | A device identifier issued by Firebase Cloud Messaging so we can alert you about order status, trip offers and messages. |
| Order and trip history | Pickup and destination addresses, timestamps, prices, order contents and ratings — needed to run the service, resolve disputes, and meet accounting obligations. |
| Basic device and diagnostic data | App version, operating system version and error reports, used to diagnose crashes and failures. |
If you apply to drive or to work for a partner pharmacy, we collect the following so we can verify your eligibility before letting you accept orders:
| Data | Why |
|---|---|
| Full name | Identification, and shown to customers during a trip or delivery. |
| Driver's licence number and expiry date | To confirm you are licensed to drive and that the licence is valid. |
| Photographs of your driver's licence (front and back) | To verify the licence is genuine and matches the details you gave. |
| Vehicle type, registration plate and registration number | To identify the vehicle and show it to customers awaiting a pickup. |
| Photographs of the vehicle registration document (front and back) | To verify the vehicle is registered to you or that you are entitled to drive it. |
| Profile photograph | Shown to customers so they can recognise who is arriving. |
| Location while you are on duty | To match you with nearby orders and let customers follow a trip in progress. |
| Earnings, wallet balance and withdrawal requests | To pay you and keep an accurate financial record. |
The apps ask for camera and photo permission only when you are actively submitting a document or a profile picture. We do not browse or upload anything else from your device, and the permission can be refused or revoked at any time in your device settings — the rest of the app continues to work.
We share only what each provider needs to perform its function:
| Provider | What it receives | Purpose |
|---|---|---|
| Twilio | Your phone number | Sending the one-time sign-in code by SMS |
| Google (Firebase Cloud Messaging) | Notification token, device identifier | Delivering push notifications |
| Google (Maps and Places) | Location and address searches | Displaying maps and suggesting addresses |
| LigdiCash | Payment amount and transaction reference | Processing payments and driver withdrawals |
| Meta (WhatsApp Business) | Your phone number and message content | Order notifications sent over WhatsApp, where that channel is used |
We also disclose data where the law requires it, or where it is necessary to investigate fraud, abuse, or a safety incident.
Data is held on servers operated by Amazon Web Services in the Africa (Cape Town) region, and is transmitted over encrypted HTTPS connections. Identity documents are stored so that only authorised BARKA GO staff carrying out verification can access them.
You can request deletion of your BARKA GO account and its data at any time by emailing [email protected], quoting the phone number the account is registered to. We verify the request comes from the account holder, and we action it within 30 days.
Some records are retained after deletion where the law requires it — for example, financial records of completed trips and payments. Everything else, including identity documents and profile photographs, is erased.
The apps are not directed at children and are not intended for anyone under 18. We do not knowingly collect data from children. If you believe a child has given us personal data, contact us and we will delete it.
All traffic between the apps and our servers uses encrypted HTTPS connections. Sign-in uses a one-time code sent to your phone rather than a stored password, and session tokens are held in the operating system's protected storage on your device. Access to identity documents is limited to staff who need it for verification.
No system is perfectly secure. If a breach affects your personal data, we will notify affected users and the relevant authorities as required by law.
If we change this policy we will update the date at the top of this page, and, where the change is significant, tell you in the app before it takes effect.
Questions about this policy, or about your data: