zambia
  • zambia
  • ghana

Shopping cart

empty-cart-img

Your Cart is empty

Go to Shop

Subtotal:

0.00
Draft — under legal reviewThis document is a draft prepared for review by a Zambian lawyer before publication. Highlighted text in square brackets marks points that are still to be confirmed. Until the review is complete, the version of the Terms and Conditions dated 16 March 2025 and the Privacy Policy last modified November 2024 remain the published versions.

Data Policy

Chiseko Agritech and Logistics Limited, trading as Sekonomics — Draft 1.1 for legal review (replaces the Privacy Policy last modified November 2024) — 13 November 2026

Related: Terms and Conditions · Usage Policy

What personal data Sekonomics actually collects, why, who it is shared with, where it is stored, how long it is kept and what your rights are under the Data Protection Act No. 3 of 2021.

This Data Policy explains how Chiseko Agritech and Logistics Limited (“Chiseko”, “we”, “us”) collects and uses personal data when you use the Sekonomics platform at www.chiseko.com (the “Platform”). It is written to describe what the Platform actually does today. Where a practice is planned but not yet live, it says so.

Chiseko is the data controller for the personal data described here within the meaning of the Data Protection Act No. 3 of 2021 (the “Act”). [CONFIRM: Chiseko's registration as a data controller with the Office of the Data Protection Commissioner, and the registration number to cite here. Registration is required by the Act; see Drafting Note 1.]

This Policy replaces the Privacy Policy last modified in November 2024. That document described practices the Platform does not have (advertising partners, custom-audience advertising, CCTV, alcohol age verification, telephone call recording, prize draws, job applications, Facebook registration and third-party cookies); none of them applies and they have been removed.

1. Who we are and how to contact us about your data
  • 1.1Chiseko Agritech and Logistics Limited, [CONFIRM: registered office address — the previous Privacy Policy gave Plot 3132566, John Ken Road, 10 Miles, Chibombo, Zambia].
  • 1.2Email: info@chiseko.com [CONFIRM: whether the dataprotection@chiseko.com mailbox cited in the previous Privacy Policy exists on the company's Amazon WorkMail account and is monitored; if so, list it here instead]. Telephone or WhatsApp: +260 960 821 404 or +260 775 944 114. Website: www.chiseko.com.
  • 1.3[LAWYER TO CONFIRM: whether the Act requires Chiseko to designate a data protection officer, and if so the officer's name and contact details to be inserted here.]
2. The personal data we collect
  • 2.1When you register and manage an Account:
    1. your mobile phone number, stored both as entered and in international (E.164) format, and whether it has been verified by a one-time passcode;
    2. your name (stored as your username) and, if you give it, your email address, together with whether the address has been verified by a confirmation link and who added it (you, an administrator, or a legacy record);
    3. the account type you chose (farmer, buyer, market intelligence, transporter or partner), and, for staff, an administrator role;
    4. profile details according to your account type: contact name, organisation name, address lines, city and province; for buyers, business type and delivery address; for transporters, vehicle type, capacity in kilograms, coverage area, and the base you give us (an address and/or a pin on a map, stored as latitude and longitude with a note of which it was), which is used only to rank delivery tasks by distance from you; for partners, sector and what you offer; for market intelligence subscribers, the commodities you follow;
    5. where you are on the map, if you choose to give it. The registration form offers you one location and what it is for depends on your account type: for a farmer or seller, the farm or collection point a transporter will be sent to and from which delivery is priced; for a buyer, the default delivery address, which fills in your checkout and which you can change for any single order; for a transporter, the base your vehicle normally starts from, used only to rank delivery jobs by distance from you; for a partner, where you are based. We do not ask a Market Intelligence subscriber for a location at all, because nothing is collected from or delivered to a subscription. GIVING IT IS OPTIONAL AND NO REGISTRATION IS REFUSED WITHOUT IT. We store the latitude and longitude, the address, town or district in the words you typed, and a record of how the point was arrived at: whether you placed a pin yourself, allowed your device to give its own position, or typed a place name that our routing provider turned into coordinates; which provider that was; for a device position, the accuracy in metres that your browser reported; for a place name, how large the place our provider matched is, in kilometres, and whether that is inside the accuracy threshold published on the Platform; and the date it was captured or last changed. We keep that record so that a delivery priced from an estimate is always shown as an estimate and never as a measurement. If you skip the step we hold no coordinates for you, only whatever town or district you typed in the address fields, and we ask again later on your profile page, on the form for listing produce, and at checkout. [CONFIRM: a location given at registration can be changed by the Account holder at any time under Profile > Map location; removing it altogether is handled as a deletion request under section 9.]
    6. for farmers: first and last name, the type of identity document (NRC or passport) and its number, farm address lines, city or district and province, the crops you grow and the quantities you expect;
    7. the dates your Account was created and last used, how many times you have signed in, and, if your Account is deactivated, when, by which administrator and why.
    8. A position from your device is used only if you ask for it. The "Use my current location" button is the only thing on the Platform that reads your device position; it does nothing until you press it, your browser then asks your permission in its own words, and if you decline, nothing is sent to us and you can place a pin by hand instead. We take a single position at that moment. We do not track you, we do not read your position in the background, we do not read it again on later visits, and we keep no history of positions: the one coordinate pair you agreed to give is stored on your Account and is replaced, not added to, if you set it again. [LAWYER TO CONFIRM: whether a one-off device position taken on an express button press, held as a single business location on the Account, is "precise location data" requiring separate consent and a separate consent record under the Act, or whether the browser permission prompt and this Policy suffice.]
  • 2.2When you sign in. The Platform has no passwords. To sign you in we generate a one-time passcode and send it to your phone by SMS or to your verified email address. We store: a cryptographic hash of the passcode (never the passcode itself), its expiry time, the number of attempts, when it was last sent and which channel was used; a log of every passcode request with your phone number, the time, your IP address, the outcome and the SMS provider's reference; and a delivery log for every SMS and email passcode showing the recipient, the sender ID used, the carrier, the delivery status reported by the provider, any error and the cost. Delivery-receipt callbacks from the SMS provider are stored as received, including the sending server's IP address.
  • 2.3When you list produce or post a requirement:
    1. for a Listing: title, produce, category, description, quantity and unit, price and currency, Grade, province, district and area, the dates available, and any photographs you upload (which are stored on our server);
    2. for a Requirement: title, produce, category, description, quantity and unit, Grade, target price and currency, delivery province, district and area, delivery notes, the date needed by and how often;
    3. for an expression of interest against a Requirement: quantity, unit, price, an optional link to your Listing and your message;
    4. the review status of each item and the history of every status change, with the administrator who made it and the reason.
    5. for a Listing, where the produce is: a pin you place on the map on the listing form (stored as latitude and longitude and marked as a pin), or, for a Listing submitted without a pin, an estimate of the district centre obtained from our routing provider from the district and province you typed, marked as an estimate. For an estimate we also keep how large the place our routing provider matched is, in kilometres, and whether that is inside the accuracy threshold published on the Platform, so that a delivery priced from the estimate can be shown as an estimate and not as a measurement. The location is used to price delivery from your farm and to direct the transporter who collects; it is shown to a transporter only once they have taken the delivery task. Requirements still have unused latitude and longitude fields [CONFIRM: no form populates them at the date of this draft].
  • 2.4When you place an order or pay:
    1. the name, company, delivery address, city, province or state, country, postal code, phone number, email address and order note you enter at checkout;
    2. the products, quantities, prices, delivery cost, currency, exchange rate applied and total of the Order, and its fulfilment and payment status;
    3. the map location of your delivery address (latitude and longitude) and how it was established — a pin you placed on the map at checkout, or a match our routing provider made from the address you typed, recorded as an address match or a district-level estimate, and for an estimate how large the matched place is in kilometres — together with the delivery quote you were shown: each point of dispatch, the road distance, the rate per kilometre, the minimum charge and whether it applied, the cost of each leg and the provider that measured it. Where no road route reached your address, the quote and the Order also record the town or village the produce is carried to instead and the statement you were shown about it;
    4. for the transport of your Order: a delivery task for each point of dispatch, with the transporter who took it and the times it was claimed, collected and delivered. The delivered time is the record from which the Grade Claim window and the farmer payment period in the Terms and Conditions run, and any later correction to it is recorded with who made it and why;
    5. references from our payment provider, Lipila: our own order reference, the payment reference and transaction identifier Lipila gives the payment, which of the two methods you used, the result code and explanation, and a record of each interaction with Lipila with any secret values removed. If you pay by mobile money you enter the mobile money number on the Chiseko checkout page and we pass it to Lipila so that the payment request reaches your handset; we do not keep it as a separate record of its own, beyond the phone number already on your Account and your Order, and if the number you give cannot be used we keep a note of the attempt with all but the last three digits hidden. We never receive or store your card number, security code or mobile money PIN: the card is entered on Lipila's own page, and the PIN only on your own handset;
    6. for bulk buyers, historical trades that Chiseko has recorded from paper invoices with your agreement, marked as historical, including your purchase order number and the line items;
    7. if you are a farmer, the amounts paid to you for produce, recorded outside the Platform in Chiseko's accounting records [CONFIRM: there is no in-Platform payout record at the date of this draft].
  • 2.5When you use Market Intelligence:
    1. your subscription status (free trial, active, cancelled or ended), the start and end dates of your free trial and of each quarter you have paid for, and the history of status changes;
    2. once billing is live: a record of each quarter you buy and of each payment that was started and not completed — the amount, the currency, the dates the quarter covers, our own reference, and the reference and result our payment provider gave it. No payment method is stored. Lipila does not issue payment-instrument tokens and does not offer stored cards, mandates or recurring charges, so Chiseko holds nothing it could charge you with: every payment is one you approve yourself on your own handset or on Lipila's card page (Terms and Conditions clause 25.4). [CONFIRM: billing is not active at the date of this draft; no quarter has been bought and no subscription payment exists.]
    3. for buyers, analytics derived from your own Orders (quantities and prices of each commodity over time, and seasonal suggestions based on them).
    4. if you cancel a quarter you have paid for: a record of the refund we owe you. It holds the amount and currency, the quarter it relates to, how the figure was worked out (what you actually paid, the cost of one month of it, the months forfeited and the months refunded), the date your access to Market Intelligence ended, who cancelled and when, and — once we have paid you — the reference of that payment, the administrator who recorded it and any note they added. It is a record of money we owe and then pay by hand: we hold no payment instrument of yours, nothing is credited automatically, and the record is the only evidence that the refund was due and was paid (Terms and Conditions clause 25.5). [RETENTION PERIOD: kept with the Orders, invoices and payments records in clause 7.2(c) — e.g. 6 years after the end of the financial year in which the refund arose — because it is an accounting record of money paid out.] [CONFIRM: no refund record exists at the date of this draft; nobody has bought a quarter, so nobody has cancelled one.]
  • 2.6Other data you give us:
    1. reviews and ratings you post on produce;
    2. articles, market notes or stories you author on the Platform, if you have been given authoring rights, with any images you upload;
    3. messages you send through the contact form (name, email address and message), which are emailed to Chiseko, and details you submit through the public farmer registration form, which are emailed to Chiseko;
    4. correspondence with us by email, phone or WhatsApp.
  • 2.7Technical data and cookies:
    1. your IP address, recorded when you request a sign-in code and when an administrator changes your Account, and in the ordinary access logs of our web server [CONFIRM: web-server log retention];
    2. a session cookie (“userInfo”) holding your sign-in token and basic profile so that you stay signed in, and a “region” cookie holding the currency or region you selected;
    3. your shopping cart and wishlist, kept in your browser's local storage on your device, not on our server, until you check out or clear them;
    4. We do not use analytics, advertising or tracking cookies, pixels or third-party scripts. [CONFIRM: verified by searching the Platform's code for common analytics and advertising tags; none is present.]
  • 2.8Administrator records. Every change an administrator makes to a user Account (for example changing an email address, changing a role, or deactivating the Account) is written to an audit log recording the administrator, the person affected, what changed (the values before and after), the reason and the administrator's IP address. Administrators' own actions are therefore also personal data that we keep.
3. Data we deliberately do not collect
  • 3.1We do not collect passwords, card numbers, security codes, mobile money PINs, bank account numbers, date of birth, gender, marital status, health data or biometric data. We do not track your location: we do not collect continuous, background or historical location, we do not log where you are when you browse or sign in, and we have no access to your device position unless you press "Use my current location" and your browser then obtains your permission, which takes a single position and is described in clause 2.1. [CONFIRM: this clause previously said we collect no precise location from the device at all; that changed on 13 November 2026 when a map pin was added to registration, and a device position is now one of three ways you may give us one business location.]
  • 3.2We do not receive personal data about you from data brokers, social media platforms or public sources, and we do not build marketing profiles of you.
  • 3.3Market Intelligence source messages. Price observations in Market Intelligence are transcribed from messages posted in trader WhatsApp groups of which Chiseko staff are members. Staff export a chat manually and paste it into an administration tool. The tool separates the sender's phone number from the message and discards it; the number is never stored and never appears in Market Intelligence. What is stored is the message text, the date, the parsed price and commodity, and a truncated, salted cryptographic hash of the sender's number whose only purpose is to recognise the same message pasted twice; it cannot be reversed to the number and is never shown to users. [LAWYER TO CONFIRM: whether a truncated salted hash of a phone number is pseudonymised personal data under the Act, and whether Chiseko's processing of trader-group messages — as a group member, for a commercial product, without the posters' consent — is lawful under the Act's legitimate-interest or other grounds. CONFIRM: the message text itself is kept verbatim and could contain a phone number or name that the trader typed into the message; administrators should be instructed to remove such details before confirming a price, and the tool should be changed to strip phone-number patterns from message text. See Drafting Note 3.]
4. Why we use your personal data and the legal basis
  • 4.1We use your personal data for the following purposes. [LAWYER TO CONFIRM: the wording of the lawful bases under the Act (in particular consent, performance of a contract, compliance with a legal obligation and legitimate interests) and the section references to cite.]
    1. To create and secure your Account and sign you in by one-time passcode, to detect and limit abuse of the sign-in system, and to prove that a code was sent and delivered — necessary to provide the service you asked for, and in our legitimate interest in keeping Accounts secure.
    2. To verify who you are: for farmers, to check the identity document, farm address and crops you give us, which is how buyers can rely on a Listing — necessary for the contract with you and in our and buyers' legitimate interest in a trustworthy marketplace.
    3. To review, publish and manage Listings and Requirements, and to match supply with demand — necessary for the contract with you.
    4. To take and fulfil Orders, arrange transport, process payments through Lipila, handle Grade Claims and refunds, pay farmers and keep accounting records — necessary for the contract, and to comply with tax and accounting law.
    5. To price and route delivery: to turn a delivery address, a farm location or a transporter's base into map coordinates, including the one location you may give when you register — which we hold so that we can price a delivery to or from you without asking you to place the same pin again on every listing and every order, and so that a transporter can be directed to the right gate, to measure the road distance from the point of dispatch to the delivery address and charge the per-kilometre delivery rate, to rank delivery tasks for transporters by distance, and to give transporters directions — necessary for the contract with you and, for the transporter's base, for the contract with the transporter. [LAWYER TO CONFIRM: the lawful basis for sending the address to a routing provider outside Zambia; see section 6.]
    6. To run Market Intelligence: to manage your trial and subscription, and, for buyers, to calculate analytics from your own Orders — necessary for the contract with you.
    7. To contact you about your Account, Orders, Listings, Requirements, claims, payments and changes to our terms — necessary for the contract and for our legal obligations.
    8. To keep audit records of administrator actions and status changes, so that disputes can be resolved from the record — in our legitimate interest and, for money matters, to comply with law.
    9. To respond to your enquiries, complaints and requests to exercise your rights — necessary for our legal obligations and legitimate interests.
    10. To show aggregate statistics on the Platform (numbers of farmers, buyers, districts and volumes; supply and demand by commodity) that do not identify anyone — in our legitimate interest.
    11. To comply with the law, respond to lawful requests from authorities, and establish, exercise or defend legal claims.
  • 4.2Marketing. At the date of this draft the Platform does not send marketing messages; the only emails and SMS it sends are sign-in codes, email-address confirmation links, account notices from administrators and copies of contact-form submissions. If we begin sending marketing by email, SMS or WhatsApp we will do so only as the Act permits, will tell you, and will give you a simple way to opt out in every message. [CONFIRM: to be updated if marketing begins.]
  • 4.3Automated decisions. The Platform does not make decisions about you by automated means that have legal or similarly significant effects. Every Listing, Requirement and Account decision is made by a person. The demand-matching tool ranks candidate Listings for an administrator to consider; the buyer analytics feature makes suggestions for you to consider; neither makes a decision.
5. Who we share your personal data with
  • 5.1Other users of the Platform, only to the extent needed for a trade:
    1. if you are a farmer who expresses interest in a buyer's Requirement, that buyer can see your name, phone number and email address so that you can speak;
    2. if you are a buyer, the farmer or transporter fulfilling your Order receives the delivery address, contact name and phone number needed to deliver it [CONFIRM: today this is passed on by Chiseko staff, not shown automatically in the farmer's Account];
    3. the public pages of the Platform show approved Listings only in summary (crop, grade, province, district, volume and harvest window) and never show a Seller's name, contact details, price or exact location. Requirements are shown only to signed-in sellers and administrators, without the buyer's contact details.
  • 5.2Service providers who process data on our instructions:
    1. Amazon Web Services, Inc. (AWS) — hosts the Platform's web server, database and uploaded images, in the AWS us-east-1 region (Northern Virginia, United States). Daily database backups are kept on the same server [CONFIRM: backup retention period and whether copies are sent to Amazon S3; at the date of this draft the S3 upload in the backup script is disabled].
    2. Amazon Simple Email Service (SES), part of AWS, region us-east-1 (United States) — sends our emails, including sign-in codes from otpnoreply@chiseko.com; SES receives your email address and the message.
    3. Amazon WorkMail, part of AWS — hosts the @chiseko.com mailboxes in which your emails to us are stored [CONFIRM: WorkMail region].
    4. D7 Networks (Direct7 Networks), based in the United Arab Emirates — sends sign-in codes by SMS; D7 receives your mobile phone number and the message, and returns delivery receipts. The sender ID shown on your phone is “Sekonomics”, registered with D7 Networks and the Zambian mobile networks.
    5. Lipila, operated by Hobbiton Technologies Limited of Lusaka, Zambia — processes payments made at checkout. Lipila stores no payment method for you. What it receives depends on how you pay. For a mobile money payment it receives the mobile money number you entered, your email address, the amount, the currency, a description of the Order and our order reference; your mobile money PIN is entered only on your own handset and reaches neither Lipila's website nor Chiseko. For a card payment it receives your first and last name, email address, phone number, delivery address, city, country and postal code, the amount, the currency, a description of the Order and our order reference, and you then enter your card details directly on Lipila's own page, under Lipila's own privacy policy, so the card number and security code reach neither Chiseko nor this Policy's systems. Buying a prepaid quarter of Market Intelligence works the same way and sends Lipila the same fields, with a description of the quarter and our own subscription reference in place of the Order's. [LAWYER TO CONFIRM: that Hobbiton Technologies Limited is registered as a data processor, or otherwise lawfully able to process personal data, under the Data Protection Act No. 3 of 2021, and that a written processing agreement with it is in place.]
    6. Our routing and geocoding provider, which turns addresses into map coordinates and measures road distances. The Platform is built to use HeiGIT gGmbH (openrouteservice.org), Heidelberg, Germany, which uses OpenStreetMap data, and can alternatively use Google LLC (Google Maps Platform), United States. [FOUNDER TO CONFIRM: which provider is live. At the date of this draft neither key has been entered on the server, so no live address is being sent to either; the Platform reports delivery as “not yet quotable” instead.] The provider receives the delivery address you type or the coordinates of the pin you place, the coordinates of the produce location, and a transporter's base address; it does not receive your name, phone number, email address or the contents of the Order. Where no road route to your delivery point can be found, the provider is also asked which towns or villages lie nearest to it, so that the delivery can be priced to the nearest one reachable by road; that request sends only the coordinates. The coordinates, distances and nearby place names it returns are kept in our database (section 7) so that the same address is not sent again.
    7. During development and testing only, the public OpenStreetMap Foundation demonstration servers (Nominatim for addresses, OSRM for routes) were used with a small number of test addresses and the district names of the existing Listings. Those servers forbid production use and the Platform refuses to use them in production unless an administrator overrides it explicitly. [CONFIRM: the override is not set on the live server.]
    8. Open-Meteo (weather) and the publishers whose public RSS feeds we read (news) receive no personal data about you; our server requests their public data on a schedule.
  • 5.3Transporters. A transporter who takes a delivery task on the Platform, or whom Chiseko engages for a delivery, receives for that delivery only: the pickup and delivery addresses and their map locations, the contact name and phone number at each end (the seller's for a collection from a farm, the buyer's for the delivery), what is being carried and the quoted delivery charge. Until a transporter takes the task, they see the task without the contact details. Transporters must use these details for that delivery and nothing else (Usage Policy). A location you gave at registration is treated exactly like one given for a single order: a farmer’s farm or collection point and a buyer’s delivery point are released to the transporter carrying that delivery, once they have taken it, and to Chiseko administrators. They are not shown on the Platform to other buyers or sellers, who see only the district. A transporter’s own base is shown to nobody but the transporter themselves and Chiseko administrators: it is used only to order the list of available jobs on that transporter’s own screen, it is never shown to a buyer or a seller, and it is never part of any price charged to anyone.
  • 5.4Professional advisers, auditors and insurers, under confidentiality, where needed to run our business or deal with a claim.
  • 5.5Authorities. The Office of the Data Protection Commissioner, the Zambia Revenue Authority, the Competition and Consumer Protection Commission, the police, courts and other authorities where the law requires or permits, or to establish, exercise or defend legal claims.
  • 5.6A buyer of our business. If Chiseko or substantially all of its assets are sold or merged, personal data may be transferred to the new owner, who must continue to use it in accordance with this Policy.
  • 5.7We do not sell personal data. We do not share it with advertising networks or data brokers.
6. Where your data is stored and international transfers
  • 6.1The Platform's server, database, uploaded images and backups are hosted by Amazon Web Services in the United States (region us-east-1). Emails are sent through Amazon SES in the United States. Sign-in SMS messages are sent through D7 Networks in the United Arab Emirates. Payments are processed by Lipila (Hobbiton Technologies Limited) in Zambia, so the payment leg does not leave the country; the record of it is nevertheless held on the server in the United States with everything else. Delivery addresses, produce locations and transporter bases are sent to our routing provider to be turned into coordinates and road distances: openrouteservice.org (HeiGIT gGmbH) in Germany, or Google Maps Platform in the United States if that provider is selected. Each of these involves transferring your personal data outside Zambia.
  • 6.2Zambia's Data Protection Act No. 3 of 2021 restricts the transfer of personal data outside Zambia, and requires that sensitive personal data be processed and stored on servers or in data centres located in Zambia. [LAWYER TO CONFIRM: (a) whether any category of data we hold — in particular NRC and passport numbers, and payment and payout details — is “sensitive personal data” under section 2 of the Act, which would make hosting it outside Zambia unlawful regardless of safeguards; (b) which of the Act's conditions for transferring other personal data outside Zambia (data-subject consent, a Commissioner-approved adequacy or contractual safeguard, or another ground) Chiseko relies on for AWS, SES, D7 and the routing provider (openrouteservice.org, Germany, or Google, United States) — the payment provider is no longer among them, since Lipila is in Zambia — the routing transfer is of an address and coordinates without a name attached, and the lawyer should say whether that changes the analysis; and (c) whether Chiseko must migrate hosting to a Zambian data centre or an AWS region acceptable to the Commissioner. See Drafting Note 1. This Policy does not claim that the current arrangement complies; it describes it.]
  • 6.3Where we transfer data outside Zambia we rely on the service provider's contractual commitments to protect it (AWS's, D7's and the routing provider's data-processing terms) and on the technical measures in section 8. By registering, you acknowledge that your data will be processed in the countries named above. [LAWYER TO CONFIRM: whether acknowledgement at registration is sufficient consent under the Act, and whether a separate, explicit consent step is needed.]
7. How long we keep your data
  • 7.1At the date of this draft the Platform does not delete data automatically. Deactivating an Account switches off sign-in but keeps the record; withdrawing a Listing or Requirement keeps it with a “withdrawn” status. Deletion happens when you ask for it (section 9) or when we run a periodic clean-up, subject to the periods below. [CONFIRM: retention is a policy decision, not yet implemented in code; the periods below are proposals for the founder and lawyer to confirm.]
  • 7.2Proposed retention periods:
    1. Account and profile data: for as long as your Account is active, and for [RETENTION PERIOD: e.g. 12 months] after it is closed or deactivated, unless a longer period below applies.
    2. The location on your Account — the coordinates, the address text and the record of how the point was arrived at: kept with your Account and profile data in (a) above, for as long as your Account is active and for [RETENTION PERIOD: e.g. 12 months] after it is closed or deactivated, because it is a profile detail and not a transaction record. A location that has been copied onto a Listing, an Order or a delivery task is part of that record and is kept for that record’s own period, so changing or removing the location on your Account does not change the figure a past delivery was priced at. [FOUNDER TO CONFIRM: whether a registration location should be deleted sooner than the rest of the profile, given it is a home or farm location rather than a delivery address for one order.]
    3. Farmer identity document type and number: for as long as your Account is active; deleted [RETENTION PERIOD] after closure. [LAWYER TO CONFIRM: any know-your-customer or tax obligation to keep it longer.]
    4. Orders, invoices, payments, payouts, Grade Claim records and the audit trails behind them: [RETENTION PERIOD: e.g. 6 years] after the end of the financial year in which the transaction took place, to meet tax and accounting law. [LAWYER TO CONFIRM: the retention period required by the Income Tax Act and Value Added Tax Act.]
    5. Sign-in code hashes: deleted on use or expiry. Sign-in request and message delivery logs, including IP addresses: [RETENTION PERIOD: e.g. 12 months].
    6. Administrator audit logs: [RETENTION PERIOD: e.g. 6 years], because they are the record relied on in disputes.
    7. Listings, Requirements and expressions of interest: for as long as your Account is active and for [RETENTION PERIOD] afterwards; withdrawn and rejected items are kept for the same period with their status.
    8. Market Intelligence source messages: the parsed price and message text are kept indefinitely as part of the price history; the salted sender hash is kept with them. [FOUNDER TO CONFIRM.]
    9. Contact-form emails and correspondence: [RETENTION PERIOD: e.g. 24 months].
    10. Routing cache: the coordinates obtained for an address, the extent of the place that was matched, the road distance, route and directions between two points, and the towns and villages found nearest a point are kept in our database, with the name of the provider that produced them, for [RETENTION PERIOD: e.g. 12 months] so that a repeated quote does not send the address to the provider again. The cache holds the address text and coordinates, not your name or Order. [CONFIRM: no automatic purge exists yet; see Drafting Note 3.]
    11. Delivery tasks and their status history, including the delivered time and any audited correction to it: kept with the Order records for the same period, because the delivered time is the record from which Grade Claims and farmer payment are reckoned.
    12. Database backups: [CONFIRM: rotation period in the backup script]; a deleted record may persist in a backup until that backup is rotated.
    13. Subscription refund records (clause 2.5(d)), including the workings behind the figure and the date access ended: kept with the payment records in (c) above — [RETENTION PERIOD: e.g. 6 years] after the end of the financial year in which the refund arose — because the record is the evidence that money was owed to a subscriber and paid to them. [LAWYER TO CONFIRM: that the accounting retention period in (c) is the right one for a refund paid to a consumer.]
  • 7.3Aggregate statistics that do not identify anyone may be kept indefinitely.
8. How we keep your data secure
  • 8.1Connections to the Platform are encrypted with TLS (HTTPS). Sign-in codes and email-confirmation tokens are stored only as cryptographic hashes; there are no passwords to steal. Sign-in code requests are rate-limited per phone number and codes expire quickly.
  • 8.2Card details are never entered on, sent to or stored by our systems: they are entered on Lipila's own card page. A mobile money PIN is never entered anywhere on the Platform or on any web page at all — only on your own handset, in answer to the request Lipila sends it. The mobile money number you give at checkout does pass through our systems on its way to Lipila, because that is how the request reaches your phone. Records of payment provider interactions are stored with secret values removed.
  • 8.3Access to the database and server is limited to Chiseko's technical staff and contractors who need it, under confidentiality. Administrative functions on the Platform are limited to accounts with an administrator role, and every administrative change to a user Account, Listing, Requirement, subscription or content item is logged with the person responsible.
  • 8.4The database is backed up daily. Backups are stored on the same server [CONFIRM: encryption of backups and off-server copies].
  • 8.5Trader phone numbers in Market Intelligence source data are discarded before storage (section 3).
  • 8.6No system is perfectly secure. If we discover a personal data breach that is likely to harm you we will notify the Data Protection Commissioner and, where required, you, within the periods the Act requires. [LAWYER TO CONFIRM: breach-notification duties and time limits under the Act.]
  • 8.7You must keep your phone number and email address under your control and never share a one-time passcode; see the Usage Policy.
9. Your rights
  • 9.1Under the Data Protection Act No. 3 of 2021 you have rights over your personal data, which you can exercise by contacting us at the details in section 1. [LAWYER TO CONFIRM: the exact list of rights, the exceptions and the response time limits under the Act.] They include the right to:
    1. be told what personal data we hold about you and receive a copy of it (access);
    2. have inaccurate or incomplete data corrected (rectification) — you can update most Account details yourself in your profile;
    3. have your data erased where we no longer have a lawful reason to keep it (erasure), subject to the retention obligations in section 7;
    4. object to processing based on our legitimate interests, and to any direct marketing;
    5. receive the data you gave us in a structured, machine-readable form and have it sent to another controller where technically feasible (portability);
    6. withdraw a consent you have given, without affecting processing already carried out;
    7. not be subject to a decision based solely on automated processing that has legal or similarly significant effects on you;
    8. lodge a complaint with the Office of the Data Protection Commissioner, Zambia [CONFIRM: current contact details of the Commissioner's office].
  • 9.2To protect your data we will check that a request comes from you, normally by sending a one-time passcode to the phone number on your Account. We aim to respond within thirty (30) days, and will tell you if we need longer for a complex request. There is no fee unless a request is manifestly unfounded or excessive.
  • 9.3Closing your Account. You can ask us to close your Account at any time. We will deactivate it immediately and delete or anonymise the data we are not required to keep at the end of the retention periods in section 7. Orders, invoices and payment records are kept for the period the law requires even after your Account is closed.
10. Children
  • 10.1The Platform is for people aged 18 and over. We do not knowingly collect personal data from anyone under 18. If you believe a child has registered or given us personal data, contact us and we will delete it.
11. Links to other sites
  • 11.1Market Intelligence contains links to news publishers' websites, and the Platform's footer links to our Facebook and LinkedIn pages. Those sites have their own privacy policies and we are not responsible for them. The card payment page is provided by Lipila (Hobbiton Technologies Limited) under Lipila's own privacy policy.
12. Changes to this Policy
  • 12.1We will update this Policy when the Platform's practices change — for example when subscription billing goes live, when a payout or claim feature is built, or if hosting moves. The current version, with its date, is always published on the Platform. Material changes will be notified to you by email, SMS or a notice in your Account before they take effect, and where the Act requires your consent we will ask for it.