Privacy Policy
Last updated: 11 October 2026
Magetsi Privacy Policy
This Privacy Policy explains how Qwiktech Solutions (Private) Limited, trading as Magetsi ("Magetsi", "we", "us"), collects, uses, shares and protects personal data when you use the Magetsi website at magetsi.co.zw, the Magetsi Android app (and any future iOS app), the Magetsi WhatsApp channel and the Magetsi Assistant (together, the "Service"). Magetsi is the data controller for this data under Zimbabwe's Cyber and Data Protection Act [Chapter 12:07].
We have written this policy to match what our systems actually do. If you have any question about it, contact us using the details in section 15.
1. Key Definitions
- "Personal Data" means information relating to an identified or identifiable individual.
- "Guest" means a person who buys through Magetsi without creating an account.
- "Principals" means the billers and service providers whose products you pay for through Magetsi (for example ZESA, Econet, NetOne, TelOne, DStv, ZINARA, councils, insurers and event organisers).
- "Payment Providers" means the mobile-money, bank and card services that move your payment (EcoCash, OneMoney, InnBucks, O'Mari, SmileCash, Smile & Pay, and card gateways).
- "Service Providers" means third parties who process data on our behalf, such as hosting, messaging, push-notification and AI providers.
2. Scope
This policy covers the website, the Android app published on Google Play (and any iOS app we release), the WhatsApp channel on +263 78 583 2033, and the Magetsi Assistant available in the app and on WhatsApp. Business accounts at business.magetsi.co.zw have their own terms; where a business provides us with its staff's details, that business is the controller and we process the data on its instructions.
3. Data We Collect
3.1 Account data
- Name, surname, email address, phone number and a password (we store only a hash of the password, never the password itself).
- Where Google or Facebook sign-in is offered and you choose it: your email, name and profile picture URL from that provider, the provider's user ID and the sign-in token it issues.
- Security settings, such as whether two-factor sign-in is on.
- Referral or campaign codes you sign up with.
3.2 Transaction and payment data
- What you buy and who it is for: the biller account you pay (meter number, phone number, account or licence number), the recipient's name, phone number, email or address where the product needs one (for example a gift voucher or a bundle for someone else), amounts, currency, product and bundle, and the reference of each transaction.
- How you pay: the mobile-money number you pay from, the payment reference and status returned by the Payment Provider, and for card payments the gateway's reference only. We never see or store your card number or CVV — card details are entered on the card gateway's own page.
- Receipts, tokens (such as ZESA tokens) and confirmations returned by the Principal.
- Saved favourites (nicknamed meters, phone numbers and accounts) and payment reminders you set.
3.3 Wallet and loyalty
- Your Magetsi wallet and loyalty account numbers, balances and ledger entries (earned, spent, refunded).
3.4 Device and technical data
- From the app, on every request: a random install identifier generated by the app on first launch (it is not your Android ID or advertising ID), your platform (Android/iOS), app version, device make and model, and operating system version.
- IP address and browser or app user-agent, recorded in our server logs, error logs and change audit trail, and stored with your sign-in credential when you register or change your password.
- Your push-notification token (issued by Firebase Cloud Messaging) if you allow notifications.
- Crash reports from the app via Firebase Crashlytics: the error, stack trace, device model, OS version and app version, together with your Magetsi user ID (or guest ID) so we can follow up a failure you report.
- On the website: the cookies and browser storage described in section 12.
3.5 Communications
- Magetsi Assistant chats: your messages, the Assistant's replies, the photos and PDF files you attach, your ratings of replies, and the phone or email you give when asking for a human agent.
- WhatsApp: your WhatsApp number, name, and the messages and files you send to our channel.
- Support tickets: your name, phone, email and the details of the problem.
- Contact and lead forms on the website: the name, email, phone and message you submit.
3.6 Guest data
- If you buy without an account, a random guest identifier created by the app or website is stored on your device and sent with your requests so we can show you your basket, payment status and recent purchases. Your purchases, the email and phone you give at checkout, and any Assistant chats are linked to that identifier. If you later sign in on the same device, we link that guest basket and chat history to your account.
3.7 Account deletion survey
- When you delete your account we ask you to pick a reason from a short list and optionally leave a comment. Only the Magetsi team sees it.
4. What We Do Not Collect
- No location. The app does not request location permission. Photos you attach in the Assistant are re-encoded on our server, which strips embedded GPS and camera metadata before storage.
- No contacts, SMS, call logs or files other than the individual photo or PDF you choose to attach.
- No advertising ID. The Android app removes the advertising-ID permission at build time and contains no advertising or third-party analytics SDK.
- No biometric data. Biometric unlock uses your phone's own fingerprint or face sensor; the app receives only a yes/no result and nothing biometric is stored or sent to us.
- No card numbers. See section 3.2.
5. Why We Use Personal Data and the Legal Basis
Under the Cyber and Data Protection Act we process your data on the following bases:
- Performance of a contract — to create and secure your account, take payment, deliver the product to the Principal, issue tokens and receipts, keep your wallet and loyalty balance, send transaction status messages, and answer your support requests and Assistant chats.
- Legal obligation — to keep financial records of payments, respond to lawful requests, and prevent fraud and money laundering.
- Legitimate interests — to keep the Service secure (rate limiting, sign-in logs, error and crash reporting), to diagnose and fix failures with Principals and Payment Providers, to understand how the Service is used, and to tell you about products similar to those you already use.
- Consent — for push notifications (you choose whether to allow them and can turn them off at any time), for optional Google or Facebook sign-in where offered, for marketing messages, and for the analytics and advertising measurement tags on the website (section 12).
If you are in a country whose data-protection law also applies to you (for example the EU or UK GDPR), the bases above correspond to the equivalent bases in that law.
6. Who We Share Data With
We do not sell personal data and we do not share it with advertisers for their own use. We share it only as follows:
- Principals — the biller account (meter, phone, account or licence number), amount and any recipient details the product needs, so the biller can deliver it. Our electricity, DStv, insurance, council and ZIMRA payments are routed through ZB Bank's bill-payment platform; Econet, NetOne and TelOne products go to those operators directly; some billers are routed through the Smile & Pay partner hub; ZINARA licensing goes to ZINARA.
- Payment Providers — the mobile number you pay from and the amount go to EcoCash (via the EcoCash merchant platform) or to ZB Bank's Smile & Pay for OneMoney, O'Mari, SmileCash and InnBucks. Card payments are handled on the hosted page of a card gateway (Stripe or Stanbic Bank, chosen per product and currency); we send the gateway only the amount and our payment reference.
- Google (Firebase) — Firebase Cloud Messaging delivers push notifications. The notification text, which can include the account or meter number, amount and reference, passes through Firebase. Firebase Crashlytics receives crash reports as described in section 3.4.
- Google (Gemini) — the Magetsi Assistant is powered by Google's Gemini models through the Gemini API. See section 13 for exactly what is sent.
- Email, SMS and WhatsApp delivery — transactional emails are sent through Amazon Simple Email Service; SMS one-time codes and alerts through eSolutions (or Infobip as a fallback); WhatsApp messages through Meta's WhatsApp Business Cloud API (or Gupshup).
- Google and Facebook sign-in — where offered and you choose it, the provider verifies your identity and tells us your email, name and picture.
- Cloudflare — the Contact and ZAS lead forms on the website use Cloudflare Turnstile to block bots; your browser token and IP address are sent to Cloudflare for that check.
- Hosting and infrastructure — Amazon Web Services (AWS) hosts our servers and databases in its US East (N. Virginia) region in the United States.
- Legal reasons — to comply with law, court orders, or valid requests by POTRAZ, the Reserve Bank of Zimbabwe, law enforcement or other public authorities, or to protect rights and safety.
- Business transfers — in a merger, acquisition or restructuring, subject to this policy.
7. International Transfers
Our Principals and Payment Providers are in Zimbabwe, but the data we hold is stored outside it: our servers and databases run on Amazon Web Services in the US East (N. Virginia) region of the United States, which also sends our email. Google (Firebase push notifications, Crashlytics and the Gemini API) also processes data outside Zimbabwe, and Stripe, Cloudflare, Meta and Infobip may also process data abroad. Before anything is sent to Gemini we replace phone numbers, meter numbers, account numbers, tokens and email addresses with placeholders (section 13). These providers publish their own data-protection commitments and we rely on their standard terms; we do not claim that every destination country offers protection equivalent to Zimbabwean law.
8. How Long We Keep Data
8.1 Deleting your account
You can delete your account from the app (Profile → Delete account) or at magetsi.co.zw/delete-account without the app. We email a six-digit code to confirm it is you. A wallet that still holds money must be emptied first. When you confirm:
- You are signed out on every device straight away and the account is disabled; your registered push devices are removed immediately.
- For 30 days the account sits in a restorable state. If you change your mind, contact support within those 30 days and a Magetsi administrator can restore it. Nobody can register a new account with that email during the 30 days.
- After 30 days a nightly job erases your personal data: your name, email and phone are overwritten, and your sign-in credentials, password history, security answers, one-time codes, favourites, payment reminders, back-online alerts, push devices, notification preferences, in-app notifications, and Assistant conversations with their photos and files are deleted. Your WhatsApp contact is unlinked from the account.
- Records of past payments — transactions, baskets, payment legs, wallet accounts and the ledger — are kept as financial records. They are no longer linked to your name, email or phone, although the recipient details you typed into an individual purchase (such as a meter or a recipient's number) remain part of that record. The deletion reason you gave is kept as anonymous feedback.
8.2 Other retention we apply automatically
- Assistant conversations: deleted 180 days after the last message; attached photos and PDFs after 30 days.
- WhatsApp photos, voice notes and files: 90 days (the message text is kept).
- Change audit trail (including IP address and user agent): 12 months.
- Application error reports: 30 days. Logs of our calls to Principals and Payment Providers: 365 days.
- Read in-app notifications: 90 days.
- The app's offline cache of your profile, wallet, recent transactions and chats on your device: 7 days, and wiped when you sign out.
8.3 Periods we have not automated
- Transaction and payment records: 7 years after the transaction, to meet our legal record-keeping obligations.
- Support tickets and WhatsApp message text: 24 months after the last message.
- Server request logs (sign-in and one-time-code endpoints): 90 days, after which the log files are deleted.
- Contact-form and lead emails sent to our mailbox: 24 months.
9. Your Rights and How to Use Them
- Access and correction — your name, email and phone can be viewed and edited in Profile in the app or in Settings on the website; for anything else, contact us.
- Deletion — in the app (Profile → Delete account), at magetsi.co.zw/delete-account, or by asking support. Section 8.1 explains what is erased and what is kept.
- Objection and restriction — you may object to processing based on our legitimate interests, including marketing, by contacting us.
- Withdrawing consent — turn push notifications off in your phone's notification settings or in the app's Notifications screen, where you can also choose which types you receive by push, SMS or email; ask to opt out on WhatsApp; disable cookies in your browser (section 12).
- Complaint — if you are unhappy with how we handle your data you may complain to the Postal and Telecommunications Regulatory Authority of Zimbabwe (POTRAZ), the Data Protection Authority under the Cyber and Data Protection Act.
We may need to verify your identity (for example by emailing a code to your registered address) before acting on a request. We respond within 30 days.
10. Security
- All traffic between the app or website and our servers uses HTTPS; the production app refuses to start against a non-HTTPS server and blocks cleartext traffic.
- Passwords are stored as bcrypt hashes. One-time codes are random six-digit codes stored hashed, expire after 5–10 minutes, and are retired after five wrong attempts.
- The app keeps your sign-in tokens, install identifier, guest identifier, saved favourites and push token in the phone's encrypted secure storage (Android Keystore / iOS Keychain), excluded from device backups. Access tokens expire after 24 hours and refresh tokens after 30 days; deleting your account invalidates every token immediately.
- Optional biometric lock on the app, and optional email two-factor sign-in on your account.
- Rate limiting on sign-in, registration, password reset, account deletion and the Assistant, keyed by account and IP address.
- Passwords, tokens, one-time codes and card data are masked or removed before anything is written to our request or error logs. Staff changes to records are audited.
No system is completely secure. Keep your password private and tell us straight away if you think your account has been accessed without your permission.
11. Children
The Service is for adults aged 18 and over and is not directed at children. We do not knowingly collect personal data from anyone under 18. If you believe a child has given us personal data, contact us and we will delete it.
12. Push Notifications, Cookies and Local Storage
12.1 Push notifications (app)
The app asks for notification permission on first launch. If you allow it, we register your device's Firebase token with our servers (with your account or guest identifier) and use it to send payment status updates, sign-in approvals and, where you have not opted out, offers. You can switch notifications off in your phone settings or per type in the app.
12.2 Cookies (website)
- Essential: an encrypted session cookie that keeps you signed in, a CSRF protection cookie, and a "remember me" cookie if you tick that box or sign in with Google or Facebook.
- Analytics and advertising measurement (production site only): Google Tag Manager, the Meta (Facebook) Pixel and the X (Twitter) conversion pixel record page views and some calculator interactions so we can measure our marketing. These providers set their own cookies and receive your IP address and browser details; their use of that data is governed by their own policies. They load only if you choose Accept in the cookie banner shown on your first visit; if you choose Reject, or make no choice, they never load. Your choice is stored in your browser, and you can change it at any time with the Cookie settings button below.
- Third-party content: the Contact page embeds a Google Map and some pages load fonts and icons from Google Fonts and Cloudflare's CDN; those services receive your IP address when the content loads.
12.3 Browser storage (website)
The website keeps working data in your browser's local storage, including your guest identifier, basket reference and items, chosen currency, the details of your last order (email and the phone numbers you entered), your signed-in profile (name, email, phone) while you are logged in, and the meter you last used in the ZESA calculator. This stays on your device; clearing site data in your browser removes it.
12.4 On-device storage (app)
Besides the secure storage in section 10, the app remembers on your device your theme, currency, the last mobile-money number used per payment method, ZINARA vehicle and licence details you entered, and a short offline cache of your recent activity. Favourites saved while signed out stay on the device and are merged into your account when you sign in.
13. The Magetsi Assistant
- Automated responses. The Assistant's replies are generated by Google's Gemini models. It can look up your transactions, balances and favourites, prepare purchases for you to confirm, and raise a support ticket; it does not take payment without your confirmation.
- What the model receives. Your message, your first name, your chosen currency, a summary of the transaction or basket you are asking about, your recent turns in the conversation, and the photos or PDFs you attach. Before anything is sent, phone numbers, meter numbers, account numbers, tokens and email addresses in text are replaced with placeholders and mapped back only on our servers; card numbers are removed permanently. Masking cannot be applied inside an image, so do not photograph cards or documents you would not want a provider to see.
- Human review. If you ask for a person or the Assistant hands over, a Magetsi support agent reads the conversation, including attachments, and may reply in the same chat. The team may also review conversations to improve the Assistant and investigate failures.
- Retention. Conversations are deleted 180 days after the last message, attachments after 30 days, and everything when you delete your account.
- Please do not share passwords, one-time codes, full card numbers or anyone else's personal details in the chat.
14. Changes to This Policy
We may update this policy as the Service changes. The date at the top shows the current version. For material changes we will notify you in the app, on the website or by email before they take effect.
15. Contact Us
Magetsi (Qwiktech Solutions (Private) Limited) — data controller
4th Floor Chiedza House, Cnr First Street & Kwame Nkrumah, Harare, Zimbabwe
Data protection officer: Assegai Analytics, dposervices@assegai.africa
Email: info@magetsi.co.zw
WhatsApp / phone: +263 78 583 2033
