Privacy Policy

1. Who this policy covers

ASIYE GROUP (PTY) LTD, trading as Asiye, is responsible for the personal information it processes to operate its passenger, driver, Asiye Go, Work/Club, delivery, safety and support services. This policy describes the Cash/Card payment model and the limited records kept to resolve historical Wallet balances.

2. Information we process

• Account and contact details: names, phone numbers, email addresses, authentication identifiers, account preferences and support correspondence.
• Profile and verification information: current profile photographs, the final image from a live face scan, driver identity documents, licences, address and vehicle documents, and the status of authorised reviews.
• Trip and delivery information: pickup and destination addresses, saved Home/Work locations, GPS positions, booking times, fares, passenger membership, pickup verification status, trip history and recipient instructions.
• Payment and bank information: provider references, amounts, payment/refund statuses, driver bank-verification and subaccount details, and historical payment or Wallet reconciliation records.
• Device, permissions and safety information: app/device versions, notification tokens, diagnostics, fraud-prevention and security records, and the contact details you deliberately select for a safety-sharing feature.

3. Live face scan and profile photographs

The app uses your front camera to capture a current profile or verification photograph. During the live scan it may ask you to centre your face, turn your head or smile. On-device face detection processes camera frames to guide this capture; the final photograph is uploaded to Asiye's cloud service and can be saved as your profile or verification image.

The native capture feature saves a still photograph. It does not record the movement sequence as a video or create a template for automated face matching. If Asiye introduces a materially different use of facial information, the policy and applicable notices will be updated before that use.

The image helps passengers and their matched driver recognise each other at pickup and helps authorised staff review profiles and safety concerns. A matched passenger or driver may see the profile image within the trip experience. Identity documents and other private verification files are not published on the public website.

Live capture can be required to finish account verification. Camera permission is requested through your device. You can change device permissions, request correction of a profile image, or request deletion of the account and associated information where retention is no longer required, using the contacts and deletion route in this policy.

4. Why we use personal information

We process information to create and secure accounts, verify driver and vehicle eligibility, match and manage rides and deliveries, display trip identity, operate navigation and safety sharing, calculate or agree fares, facilitate payments and refunds, answer support requests, investigate incidents, prevent abuse, and meet applicable legal obligations. We use the appropriate legal basis for each purpose; where consent is required, we seek it. Marketing communications must offer an appropriate opt-out.

5. Location, camera and selected contacts

Location supports driver availability, pickup, navigation and live-trip safety functions while the relevant feature is in use, including background use where supported, disclosed and permitted by the device. Camera access supports live profile capture and driver document or vehicle photographs. Notifications support booking and safety updates. The contact picker provides the contact details you choose; it is not permission to publish your address book.

Trip sharing is optional. A tracking link can expose limited trip and location information to anyone who receives or forwards that link. Current token-based links normally expire 72 hours after issue. Do not post them publicly. Contact support promptly to request that a shared link be revoked or access reviewed.

6. Cash, Paystack Card payments and legacy Wallet records

Cash fares are collected by the driver after the ride or delivery. When Card is available, payment is processed through Paystack after the driver is assigned and the fare is agreed. Drivers are onboarded as Paystack subaccounts. Each Paystack card transaction specifies that driver's subaccount, with 80% allocated to the driver and 20% to Asiye before provider processing fees; Asiye bears the Paystack transaction fee under this model.

Asiye retains the payment references, amounts, verification statuses, subaccount/bank-verification records and refund records needed to administer the service. Card details are entered into Paystack's payment interface. Do not send full card numbers, card PINs or passwords to support.

Asiye Wallet is discontinued for new funding, new bookings and ongoing cash-out services. Do not make new EFT deposits to fund a Wallet. Historical balances and transaction evidence are retained only for reconciliation, eligible refunds, disputes and required records. Removing the feature does not erase a customer's existing claim to eligible funds. Contact support for a review under the legacy-funds refund process.

7. Service providers and disclosures

We share only information reasonably needed for the relevant purpose with the matched driver/passenger or delivery participants, authorised staff, and providers of cloud hosting, authentication, mapping, communications, notifications and payments. These include Google/Firebase for relevant app and cloud functions, mapping providers used by the app, and Paystack for Card processing and driver subaccounts. These providers may process information outside South Africa; applicable safeguards must be used for cross-border processing.

We may disclose information to authorities where lawfully required or as reasonably necessary to respond to a safety incident, fraud or a legal claim. We do not publish identity documents, complete driver bank details or private pickup secrets on public policy pages.

8. Retention, security and deletion

Account and verification information is kept while reasonably needed to provide, verify and protect the service. Trip, financial, incident and support records may be retained longer where required for accounting, tax, regulatory, fraud-prevention, safety, legal claims, chargebacks or unresolved disputes. Different records therefore have different retention needs; this policy does not promise that every copy, backup or legally required financial record disappears immediately when an account is closed.

We restrict access by role and purpose, use authentication and access controls for private records, and review information for deletion or de-identification when the purpose and any required retention period have ended. Contact the Information Officer enquiries address to ask what information is held and why it is being retained.

You can request account and associated data deletion without reinstalling the app at asiye.cloud/delete/. We may verify your identity before acting. Information no longer needed will be deleted or de-identified, while any justified retained records remain restricted to their retained purpose.

9. Your rights and privacy contact

Subject to applicable law, including POPIA, you can request access, correction or deletion where permitted, object to applicable processing, withdraw consent where that is the processing basis, or raise a concern about your information. Withdrawal can affect features that depend on that information and does not undo processing that was lawful before withdrawal.

Send requests to the Information Officer of ASIYE GROUP (PTY) LTD, care of admin@asiye.cloud, telephone 031 566 1165, or the registered office above. You may also contact South Africa's Information Regulator.

10. Children and account eligibility

Asiye is not designed as a child-directed service. Driver account holders must meet the age, licensing and other requirements that apply to their services. A parent or legally authorised person should contact us if a child's information has been supplied without the required authority or safeguards. We will review the circumstances and act as required; an app download does not itself establish lawful consent to process a child's information.

11. Changes to this policy

We may update this policy when the service, providers or processing practices change. The revised date will appear above, and material changes will be communicated through an appropriate channel.