Privacy policy

This is a draft describing what the system actually does with data today, written for the engineering handoff — it is not an approved legal privacy policy. Legal review is a launch checklist item (spec §21) before this can be treated as binding.

What we collect

Account details (name, email, phone), delivery addresses, order and request history, and payment records (via our payment provider — we don't store card numbers ourselves).

If you pay by EcoCash, we keep the EcoCash transaction ID and any screenshot of the payment you upload, so our team can confirm the money arrived. Screenshots are stored privately and only staff checking payments can open them.

If you continue with Google, Google shares your name, email address and a Google account ID with us — nothing else (we don't read your contacts, emails or files, and we don't keep your profile photo). You can still set a ZimExpress password at any time with “Forgot password”.

Analytics and cookies

We use Google Analytics to understand how the shop is used: how many people visit, whether they come back, which pages and products they look at, and roughly which country and type of device they use. Google Analytics sets cookies in your browser to recognise a returning visitor, and your IP address is shortened before it is stored.

When you're signed in, we send Google Analytics a random account number so it can count you once across your phone and computer. We never send your name, email address, phone number, address or payment details. We use these reports only to improve the shop, and we don't use them for advertising.

You can block or delete these cookies in your browser settings, or use Google's opt-out add-on (tools.google.com/dlpage/gaoptout). The shop works the same without them.

What we don't share

Your data is never shared with the private sourcing network. Country agents and suppliers never see your name, contact details, or payment information — they only ever see what a specific sourcing case requires them to know.

Where data lives

Data is stored in our managed Postgres database. Private sourcing/agent data is kept in physically separate tables from customer data, with server-enforced access control — see SECURITY.md in the codebase for the technical detail.