Who is responsible?
CarryGo is operated by CARRYGO ONLINE MARKETPLACE LTD, a fully registered company with Registration No. 9911730.
CarryGo operates online and currently has no customer-facing physical office. Customers can reach support through the website’s Help & Contact page and support chat.
For support and privacy enquiries, use Help & Contact and the website support chat. Explain your request without sending passwords, OTPs, recovery codes or identity documents in chat.
Information used by the service
Account information can include your name, username, email, phone number, role, profile photo and verification status. Google sign-in, when configured and chosen, uses identity information returned by Google.
Identity verification uses an uploaded NIN slip and one identity photo, either uploaded or captured with the camera. Authorised administrators record the NIN and compare the photograph and account details manually. NIN slips are encrypted in private storage and accessible only to their owner and authorised administrators. The identity photo is private while awaiting review. With your consent, after approval the same photo becomes your CarryGo profile photo and may be displayed to other signed-in users. Historical private verification selfies remain private. Manual review does not prove liveness or confirmation by an official NIN database; no live NIN API is connected for this flow. Photo-quality hints are advisory. CarryGo records review decisions and consent. Customer verification is limited to NIN, identity photo and bank account checks. When enabled and separately authorised by you, CarryGo sends your NIN to Kora (Korapay) for identity lookup and compares the returned first and last names with your registered account. Returned names are encrypted; the provider reference and outcome are retained for review. Uploaded photos and slips are not sent by this lookup. Email, phone and transaction PIN security remain separate. Historical records are retained privately. Contact support for retention and deletion details before consenting.
Delivery and purchase records can include item descriptions, pickup and delivery addresses, recipient contact details, prices, status changes, delivery evidence and dispute evidence. A shop may supply recipient information even when the recipient has no CarryGo account.
The application also keeps wallet and transaction records, conversations and attachments where supported, reviews, support feedback, session records and security activity. Security activity includes event time, IP address and an estimated browser/device label.
Why information is used
Information supports account access, eligibility checks, arranging and tracking deliveries, purchases, wallet and escrow records, withdrawals, dispute handling and customer support. Session and security records support authentication, abuse prevention and investigation.
Processing needed to provide a requested account, purchase or delivery service supports performance of that service contract. Security and fraud-prevention processing serves legitimate interests, subject to applicable rights and safeguards. Where a legal obligation applies, records may be processed to meet that obligation. Where consent is requested, it must be specific and can be withdrawn; withdrawal does not invalidate earlier lawful processing.
Cookies, sessions and external services
The website uses browser cookies and server-side sessions for sign-in, request protection and visitor-chat continuity. Remembered sign-in can keep a browser recognized when selected. Clearing cookies can end access to a visitor conversation.
Public pages currently request font resources from Google Fonts, which sends a network request from the visitor’s browser to that service. Google sign-in is a separate optional integration when configured.
Browser settings let you manage cookies, but blocking essential cookies may prevent sign-in or visitor chat from working. Additional optional tracking requires appropriate information and any consent required by law.
Storage and retention
Records are stored by the application and any configured storage or backup services. Clearing a browser session does not delete server-side conversation or transaction records.
Retention depends on the purpose of the record and applicable legal requirements. Transaction and dispute records may need to remain available for reconciliation, complaints and lawful record-keeping; verification, support and security records should be kept only while needed for their purpose. Deletion requests may be limited by these requirements. Ask Help & Contact about retention or deletion for a particular record, including backup copies.
Your requests and choices
Depending on the applicable law and circumstances, data rights can include access, correction, erasure, restriction, portability, withdrawal of consent and objection to processing or certain automated decisions. Rights may be subject to legal conditions and exceptions.
Use Help & Contact to submit a privacy request. Describe the request without sending passwords, OTPs, recovery codes or identity documents in chat. Identity may need to be verified before account information can be disclosed or changed.
For information about rights and complaints in Nigeria, consult the Nigeria Data Protection Commission. A support conversation is not a complaint submitted to the Commission.
Protecting your information
The application includes access controls, password hashing, optional two-factor authentication, encrypted authenticator secrets and encrypted NIN storage. These controls do not guarantee that every deployment or communication is risk-free.
Keep account credentials and private links secure. Use the account-security page to review sessions and security activity. Report suspected misuse through Help & Contact without sharing secret codes.
Privacy information in Nigeria
For official guidance, visit the Nigeria Data Protection Commission. The Commission’s own data-rights request page describes rights categories; it is not a CarryGo request form.