Data we handle
- Identity, contact, account, address and profile information.
- Orders, Ride and Delivery activity, support messages, device identifiers and service diagnostics.
- Customer payment references, amounts, status, wallet and purchase history. KariGO uses hosted checkout and does not ask Customers to enter raw card or bank credentials into KariGO.
- Captain location during availability and accepted active work, including background location while an assignment is active.
- Captain and Partner onboarding evidence, and Partner payout bank-account information.
Why we use it
We use information to provide accounts, orders, Rides, Deliveries, payments, support, onboarding, fraud and security controls, legal compliance, service communications and reliability. Required and optional fields are identified by the feature that requests them.
Location
Customer location supports address, pickup and service-area features. Captain precise location supports availability, navigation and live tracking during accepted work. Background collection is limited to active work and is designed to stop when the job ends. Precise Ride location is not used for advertising. Saved city or state may be used to select eligible sponsored cards within KariGO.
Payments
Flutterwave hosts supported Customer checkout. KariGO keeps the minimum payment and reconciliation evidence needed for wallet, order, refund, dispute and finance workflows. Legacy provider payloads have been minimized; raw card, bank-account, authorization and provider-customer structures are not retained in those payloads.
Private documents
New Captain and Partner onboarding documents use access-controlled Google Cloud Storage. Partner reads are authenticated and backend-mediated, and no permanent public document URL is created. Live deletion can remain recoverable within Google Cloud's seven-day soft-delete window. Provider systems may retain protected copies for longer under their processing terms, so deletion is not described as immediately irreversible.
Historical Partner evidence
Seven historical Partner approval records remain as audit history, but their former file objects are unavailable. They are marked for reacquisition. Any replacement is submitted again through the authenticated private-document workflow and linked to the historical record.
Providers and recipients
KariGO sends information needed for the relevant flow to providers such as Render, Google Cloud Storage, Flutterwave, Google Maps, Expo/Firebase, Agora and communications providers. A provider may also process information for security, fraud prevention, diagnostics, legal compliance or other purposes described in its terms. Some transfers, including active Google Maps requests, can qualify as sharing under Google Play even when they support a KariGO feature. GCS private document storage is handled under KariGO's accepted Google Cloud data-processing terms.
Ride place searches send the search text, a temporary search-session identifier and relevant location context through KariGO to Google Places. KariGO does not maintain a dedicated raw search-history list. Google may retain search terms and related request data to provide and improve its services under the Google Maps Platform terms and Google Privacy Policy. A selected destination and its permitted transaction record are separate from the raw search query.
Website analytics and cookies
If you accept website analytics, KariGO may use Google Analytics 4 on public website pages. Google provides the analytics technology. The limited analytics data can include analytics cookies or browser identifiers, a sanitized page path without its query or fragment, safe referrer information, browser and device characteristics, coarse geographic information, timestamps and approved business-interaction events.
We use this information for aggregate usage measurement, navigation understanding, application-funnel measurement and CTA effectiveness. Analytics remains off unless you accept. You can reject it or later withdraw consent through Cookie settings in the site footer.
KariGO analytics must not intentionally transmit names, email addresses, phone numbers, addresses, message or form contents, payment details, transaction references, account IDs, record IDs, tokens, OTPs, filenames or uploaded documents.
Analytics retention is configured in Google Analytics rather than by a browser cookie alone. When analytics is activated in the future, KariGO will apply the configured event and user-data retention periods and review aggregate reporting only for as long as needed for the purposes above. Google may process analytics data under its applicable processing terms.
Customer app advertising
KariGO first shows eligible direct KariGO campaigns. When that inventory is unavailable, the Customer Android app may ask Google AdMob to fill the otherwise-unused placement with a clearly labelled native ad. AdMob may process the device IP address, ad or app-set identifiers, app and ad interactions, and diagnostic information for advertising, analytics and fraud prevention. KariGO does not receive Google's user-level advertiser profile.
The app uses Google's consent and privacy-choice tools where required and requests non-personalized ads from this placement. If consent does not permit an ad request, or no ad is available, KariGO shows no fallback ad. You can reopen advertising privacy choices from the app's Privacy and security screen when Google requires that option.
Google advertising requests and UMP consent initialization are disabled in the current Customer iOS release. Its included Google Mobile Ads SDK has default SDK-related crash reporting that is not explicitly disabled. We disclose those crash diagnostics for SDK reliability analysis and app functionality, not linked to the KariGO account and not used by KariGO for tracking. This does not mean iOS advertising requests are enabled.
Retention and deletion
Account deletion deactivates the selected access, revokes active sessions and deletes eligible unattached private objects after provider confirmation. Orders, financial reconciliation, approved onboarding evidence, disputes, security and audit records may remain only while needed for a defined legal, finance, safety, security or compliance reason. KariGO reviews retained categories and removes or minimises information when the applicable reason no longer requires it.
See the secure deletion process.
Your choices
You can manage permissions, update eligible profile fields, request account deletion and contact support about access or correction. Disabling a permission may prevent the feature that needs it.
Contact
Use the KariGO contact and support form. Do not send passwords, OTPs, card details or provider credentials through a public message.
