1. Who we are and what this policy covers
Zikorra Services Limited ("Zikorra", "we", "us" or "our") operates the Zikorra website, the Zikorra customer app, the Zikorra Artisan app and the systems used to administer and support those services. We connect people who need services with artisans and help them manage requests, quotes, appointments, communications and service records.
This policy explains how we handle personal data about website visitors, waitlist subscribers, customers, artisans, people contacting support and authorised administrators. Zikorra is the data controller for the processing described here.
You can contact us at:
- Email: support@zikorra.com, with “Privacy” in the subject line.
- Address: No. 10 Hon. Rufus Oyedepo Street, Sangotedo, Lagos, Nigeria.
This policy gives information about data processing. Reading it or accepting our Terms of Service is not, by itself, consent to optional marketing, analytics or sensitive-data processing.
2. Personal data we collect
The information we handle depends on the features you use and whether you are a customer, artisan, visitor or administrator.
| Category | Examples and source |
|---|---|
| Account and contact details | Name, phone number, country, optional email, profile photo, and any date of birth or gender you choose to add through available profile features. These normally come from you. |
| Account security | Password hash, verification and recovery records, session identifiers, token records, sign-in times, IP address and browser/device information associated with authentication. |
| Customer preferences | Saved artisans, saved service addresses, address labels, area, local government area, state, landmarks and location coordinates you provide or confirm. |
| Artisan profile and work information | Biography, experience, services, work photos and captions, working hours, availability, service radius, work address, service area and onboarding or training results. |
| Identity and verification information | For artisans: NIN and identity details, identity-document images, proof of address, certifications where submitted, profile photos, a short selfie video and review decisions. Customers may optionally submit an identity-document type, number and image. |
| Booking and service records | Requested service, description, urgency, address and coordinates, requested or agreed time, quote amounts, agreed price, start-code records, status changes, completion evidence, cancellation or rescheduling reasons, ratings and reviews. |
| Wallet and payment records | Customer and artisan wallet identifiers and balances; amounts held for jobs; ledger entries and references; top-up account name, bank and number; deposit amount, sender name and provider reference/status, and provider-supplied transaction details where received; artisan payout bank code/name, account number and resolved account name; withdrawal amount, destination snapshot, status, failure reason and timestamps. |
| Communications and submitted media | Job chat, images and voice notes, service-request photos, videos or audio, support messages, complaints, dispute evidence and other information you send to us or another participant. |
| Location and trip information | A location you select, enter or obtain through your device, an artisan's work location, and location updates shared while an artisan travels to a job. |
| Notifications and activity | Push-delivery identifiers, device platform and app, notification content and read status, chat presence and message read receipts. |
| Website and waitlist information | Email address or phone number you enter in the waitlist, website usage and browser/device information collected through analytics, and information you send when contacting us. |
| Administration and safety records | Staff account information, verification decisions, support actions, internal notes, moderation decisions, operational reports, authorised exports and audit records identifying actions, times, affected records, IP addresses and user agents. |
Other people may provide information about you through a booking, review, complaint or support request. Administrators may create an artisan invitation containing contact and onboarding details. We also receive technical delivery information from the providers that help operate the service.
Please avoid including unrelated identity documents, bank credentials, health information or other sensitive information in job descriptions, public reviews, photos or chat. If you provide another person's information, make sure you have authority to do so and tell them how it will be used.
3. Why we use personal data
We use personal data to:
- Create and manage accounts, verify phone ownership, authenticate sessions and help with account recovery.
- Display artisan profiles and relevant services, use your selected location to find suitable providers and remember preferences you choose to save.
- Deliver service requests, quotes, appointments, rescheduling, job updates, completion records and reviews.
- Let participants communicate and receive service notifications.
- Where wallet payments are enabled, record incoming transfers, reserve funds for accepted job quotes and extra work, release or return held funds, resolve payout accounts, process artisan withdrawals and reconcile pending or failed transactions.
- Review artisan identity and professional information, administer onboarding and review optional customer identity submissions.
- Share trip progress and estimate arrival time when an artisan uses location sharing.
- Respond to support requests, investigate disputes and misuse, moderate content and keep administrative records.
- Operate, troubleshoot, secure and improve the services and understand website usage.
- Send the launch or availability updates you requested through the waitlist, subject to applicable consent requirements.
- Comply with applicable duties, respond to valid legal requests and establish, exercise or defend legal claims.
We rely on the following legal bases as applicable: performing our agreement with you or taking requested steps before it; consent for processing that requires your choice; compliance with a specific legal obligation; and legitimate interests in service security, support, dispute handling and service improvement, where those interests are not overridden by your rights. Device permission alone does not establish every legal basis. Sensitive-data processing, including identity material where applicable, requires its own lawful condition. We do not treat all verification as legally mandated KYC.
4. Location, camera, photos and microphone
Customer location. You can enter or confirm a service address manually. If you allow device location access, we can use it to help fill in your address and search for services. A service address and its coordinates become part of the booking record when you submit a request.
Artisan location. We use work-location and service-area information for discovery and coverage. While you are on the way to a job, trip sharing can collect location updates, including while you use another app where your device permissions and operating system allow. The booking customer receives trip progress and arrival estimates. Sharing is designed to stop when work starts, the job is cancelled or the trip is no longer eligible.
The trip feature keeps the latest reported point in a short-lived cache, currently expiring after 15 minutes without another update, rather than maintaining a route-history table. That expiry does not erase the booking address, profile location, provider-held data or other records described in this policy.
Camera, photos and audio. We request access when you use features such as identity capture, work photos, booking attachments or voice notes. A selfie video is used for identity review and is not a public profile video. Denying a permission can prevent the related capture, upload or tracking feature. You can change permissions in your device settings.
5. Information visible to other people
Zikorra acts as an intermediary connecting customers and independent artisans. Customers and artisans are responsible for their own conduct, representations, omissions, services and subsequent use of information shared with them through the Services. The limitations in Section 11 apply, without excluding Zikorra’s own obligations under applicable law.
Artisan profiles. Customers can see information such as your name, profile image, service area, biography, services, work photos, working hours, experience, verification status, ratings and reviews. Your identity documents and NIN are not intended to appear on your public profile.
Bookings. A requested or assigned artisan can receive the job details needed to assess or perform the work, including the service description, submitted attachments, address and coordinates. Participants see relevant names, profile information, job records and communications. Phone numbers become visible at relevant accepted-booking stages. Do not assume a pending request hides the job's address from the artisan receiving it.
Reviews. Reviews and reviewer display information may appear with artisan profiles. Ratings also form part of participant and job records. Avoid posting someone else's private address, document number or contact details in a review.
Support and administration. Staff can access account, booking, verification and support records through the administration system. Role permissions govern particular actions, exports and access to job conversations. Authorised staff may read job conversations for support, operations or safety purposes. Job chat is not end-to-end encrypted against Zikorra. Internal notes and operational exports may contain personal data.
Media links. Ordinary job attachments and chat images or audio currently use externally hosted media links that can be opened by someone who obtains the link. Access to the job or chat screen does not make the underlying media link private. Do not use these upload features for confidential documents; identity submission uses a separate private-upload process.
6. Providers and other recipients
We use external services to operate relevant features. Depending on your use and the deployed configuration, recipients include:
| Recipient or service category | Information involved and purpose |
|---|---|
| Infrastructure, database and cache providers | Account, booking, communication and technical data needed to host and operate the services. |
| Cloudinary | Uploaded profile and work images, booking/chat media and identity material for storage and delivery. New identity uploads use private delivery controls; ordinary profile and work media can be publicly accessible. |
| Termii | Phone number and message content for verification codes and operational SMS. |
| Expo and the Apple/Google push-delivery services | Push identifiers, delivery data and notification content used to deliver app notifications. Depending on settings, content can appear on your lock screen. |
| Google Routes, when enabled | Trip origin and job destination coordinates used to calculate traffic-aware arrival estimates. |
| Google Analytics | Website event, browser/device and identifier data used to understand website traffic and usage. |
| Bank-side payment providers, when a live service is enabled | Account/contact details needed to issue a top-up account; bank code and account number for payout-account lookup; recipient name and destination, amount, narration and transfer reference for withdrawals; status/reconciliation information. Live provider arrangements must be identified before use. The current development sandbox does not send real bank transfers. |
| Website waitlist service | Your submitted email address or phone number and associated request metadata. The website currently submits these to a service hosted at ms-oauth2.onrender.com. |
We may also disclose relevant information to professional advisers, authorities or courts where legally justified, to investigate threats or wrongdoing, or in a business transfer subject to applicable protections. We disclose booking information to the other participant as described above; that participant is responsible for their own subsequent use of information outside Zikorra.
Some providers may handle personal data outside Nigeria. Any such transfer must have a lawful basis and appropriate protection under applicable Nigerian data-protection rules. Contact us for information about relevant recipients, locations and transfer arrangements. This policy does not claim that all data stays in Nigeria.
Zikorra shall not be liable for interruptions, security failures or other incidents attributable to third-party service providers outside its reasonable control, as set out in Section 11. This does not exclude or limit any duty, liability or responsibility which Zikorra cannot lawfully exclude under applicable data-protection laws, including its obligations as a data controller.
7. Website cookies, analytics and local storage
The public website includes Google Analytics, which can use cookies and similar identifiers to measure visits, viewed pages, interactions and browser/device characteristics. The reviewed website does not currently provide an in-site analytics preference control. Browser cookie controls and blocking tools may limit collection, but do not replace any consent we are legally required to obtain.
The administration website uses authentication cookies to maintain authorised staff sessions. The apps use device storage for session credentials and certain preferences, including selected saved-location identifiers. Local drafts and temporary media may also exist on your device. Changing device or browser settings can affect sign-in and other features.
Joining the waitlist requests launch and availability updates. You may ask us to remove your contact from the waitlist or stop optional promotional contact by emailing us. Withdrawing optional marketing permission does not stop essential account-security or booking communications.
8. Wallet and payment information
When enabled, customer and artisan wallets are separate records. Customer funds can be held for an accepted job quote or extra-work price. Confirmation releases the held amount to the artisan wallet, less any disclosed applicable fee; cancellation returns held money to the customer wallet. A dispute keeps the money held pending resolution. We record these movements and their job references, and use bank, deposit and payout records to reconcile results and investigate errors or suspected misuse.
Artisans can submit a payout bank code and 10-digit account number. The returned account name is shown for checking. A withdrawal records the destination as it was when requested, together with its amount, reference, progress, result and any failure reason. Financial notifications can include amounts and bank-account details, which may appear on the device lock screen depending on settings. Authorised administration functions provide payment reports and operational oversight.
Real bank-backed payments are not yet available in the current implementation: the bank-side provider integration is pending, and the development sandbox only simulates accounts, deposits and payouts. When payments are disabled, accepting a quote books the job without a wallet charge. We must identify any live provider and its relevant data use before enabling that service. A test account labelled “Sandbox Bank” must never be used for a real transfer.
Do not send card security codes, banking passwords or banking PINs in chat or support messages. The wallet integration does not require you to save a payment card or create a client-only transaction passcode.
9. Retention and account deletion
Retention depends on the record, the purpose for which it is needed, unresolved bookings or complaints, security needs and applicable legal requirements. There is currently no fixed published retention period for identity uploads, job/chat/support history, financial records, operational exports or backups. Account closure must not be understood as an automatic purge of these records.
You can request account deletion in the app using your current password. The self-service flow requires open jobs to be finished, cancelled or otherwise resolved first. Contact support if you cannot access the flow or need help with an outstanding job. This product restriction does not remove your right to make a separate data-erasure request.
On successful account deletion, we disable access, revoke sessions, deactivate push registration and remove or replace core account identifiers. Customer saved addresses, saved artisans and specified profile and identity-reference fields are cleared. Job, chat, support, verification, financial and administrative records can remain. Retained financial records can include bank-account information, deposit/payout details, historical destination snapshots and ledger references. Their content may still identify you, including through addresses, attachments or messages; replacing an account name does not anonymise every historical record.
Uploaded files held by storage providers are not automatically erased by the account-deletion flow. Deleting the app also does not delete server-held records. You may request erasure of specific information through the contact above. We assess the request and explain any lawful reason for retaining information, subject to applicable rights and duties. The absence of a fixed schedule is not permission to retain data indefinitely.
10. Security
The services include password hashing, session-revocation controls, access checks, private delivery controls for new identity uploads and administrative audit records. Access to particular administrative functions depends on staff permissions. These measures reduce risk but do not guarantee that every upload, device, provider or historical record is secure. Contact us promptly if you suspect unauthorised access or disclosure. We will handle incidents and any required notifications under applicable law.
11. Limitation of Responsibility and Third-Party Conduct
Zikorra shall not be responsible for any loss, damage, unauthorised disclosure or misuse of personal data arising from the independent acts or omissions of customers, artisans or other third parties, including circumstances where such persons access, copy, disclose or otherwise misuse information legitimately made available to them through the Services.
Zikorra shall also not be liable for interruptions, security failures or other incidents attributable to third-party service providers outside its reasonable control.
Nothing in this Policy, however, excludes or limits any duty, liability or responsibility which Zikorra cannot lawfully exclude under applicable data-protection laws, including its obligations as a data controller.
12. Your rights and choices
Subject to applicable law, you may request access, correction, erasure, restriction, portability, information about recipients and retention, or object to relevant processing. You may withdraw consent where processing relies on it and seek review of a qualifying automated decision. Withdrawal does not undo prior lawful processing. Contact the address above; we may proportionately verify identity and explain any lawful limitation. You may also complain directly to the Nigeria Data Protection Commission.
You can edit available profile fields, manage saved addresses, change notification and device permissions, and request account closure. Declining optional information may limit the related feature rather than prevent all use of Zikorra.
Search and availability checks use factors such as location, service, working hours and job state. Verification and dispute features include staff review. These features should not be understood as a guarantee of provider suitability or an automated background-check service.
13. Children
Zikorra is intended for adults aged 18 and above. Do not create an account or submit identity material for a child. If you believe a child has supplied personal data, contact us so we can assess and address it. This statement does not imply that we have verified every user's age.
14. Changes and contact
We will identify the effective date of an updated policy and provide additional notice where required. A change to this policy does not itself supply consent for a new purpose that requires consent.
For questions, privacy requests or concerns, email support@zikorra.com or write to No. 10 Hon. Rufus Oyedepo Street, Sangotedo, Lagos, Nigeria.