Legal
Mudiwa Privacy Policy
On this page
- The short version
- 1. Who is responsible for your data
- 2. What we collect, and why
- 3. The legal basis we rely on: your written consent
- 4. Automated tools and decisions
- 5. Who we share your data with
- 6. Hosting in the European Union, and other countries (cross-border transfer)
- 7. How long we keep your data
- 8. How we keep your data safe
- 9. Your rights, and how to use them
- 10. Children
- 11. Ads: not active
- 12. Payments: not active
- 13. Changes to this policy
- 14. Contact us
Version: 1.0 · Effective date: 26 October 2026
Dating is personal. Much of what you share on Mudiwa, such as your gender, age, what you're looking for and your face, is what Zimbabwean law calls sensitive data. We treat it that way. This policy explains, in plain words, what we collect, why, who sees it, where it is kept, how long we keep it, and how you stay in control.
It is written to follow Zimbabwe's Cyber and Data Protection Act [Chapter 12:07] ("the Act") and its regulations.
The short version
- We ask before we use your sensitive details. You give consent on a separate screen, one tick at a time, and you can withdraw it in Settings whenever you like.
- Your email address is never shown to other members. Your selfie is never shown on your profile. Your likes are private.
- We don't sell your data, and we will never use your dating details, religion or who you want to meet to target ads.
- Your main data is stored in the European Union (Frankfurt, Germany), which has one of the strongest data protection laws in the world. A few service providers handle limited data elsewhere; section 6 lists them.
- You're in control: download your data, correct it, withdraw consent, or delete your account in a few taps.
- If something goes wrong, we tell the regulator within 24 hours, and we tell you if you're at high risk.
1. Who is responsible for your data
Mudiwa is the service in this policy. It is run by its founder, who decides how and why your data is used and is responsible for protecting it. In the language of the Act, we are the data controller.
You can reach us about anything in this policy, and make any request in section 9:
- Email: kudzilenett@gmail.com
- In the app: Settings → Help → Contact us
We answer privacy requests personally. If you are not happy with how we handled your data, you can also complain to the regulator (see section 9).
2. What we collect, and why
We only collect what we need to run a safe dating app (Act s13(d)). If a field is optional, we say so in the app.
2.1 Details you give us
| What | Examples | Why we need it | Sensitive data? |
|---|---|---|---|
| Sign-in details | Your email address (from the code we send you, or from your Google or Apple account) | To create your account, sign you in, and stop banned people from coming back. Never shown to other members. | No, but we protect it as if it were |
| Basic profile | First name, date of birth (we show your age, not your birthday), gender, city or area | To build your profile, check you're 18+, and show you to the right people | Yes: gender and age (Act s3) |
| Dating details | Who you'd like to see, what you're looking for (for example, something serious or marriage-minded), relationship status | To suggest matches and show your intentions honestly on your profile | Yes: sex life, marital or family status (Act s3) |
| Photos | Up to 6 profile photos | To show your profile and check your selfie against your photos | Can be, when a photo shows sensitive details such as ethnic origin or religious dress |
| Prompts, interests, job and other profile details | Your answers to prompts, interests you pick, job title | To help others get to know you | Some may be, for example if you mention your church or education |
| Messages | Text messages, voice notes (up to 30 seconds), photos in chat (only if both people turn them on) | To deliver your messages, and to protect you from scams, explicit images and abuse | Can be |
| Trusted contact | The name and phone number of the friend or family member you choose | To send them your date plan and alert them if you miss a check-in | Not usually; this is someone else's data, see section 2.4 |
| Reports and appeals | What you tell us when you report someone or appeal a decision | To investigate and keep people safe | Can be |
| Support messages | What you write when you contact us | To help you | Can be |
| Proof of age (only if asked) | A photo of your national ID or passport | Only if you appear under 18 or someone reports you as under 18, or if you need to recover access to your account and other checks fail | Includes your date of birth |
2.2 Your selfie check (biometric data)
Before you can message anyone, you do a short selfie liveness check. Here's exactly what happens:
- You take a short selfie (a few moving frames) in the app.
- Our verification provider checks that you're a real, live person (not a photo of a photo or a mask), compares your face with your profile photos, and estimates your age.
- To do that, it creates a face template: a set of numbers describing your face. This is biometric data under the Act and its regulations, and it is only used with your written consent (Act s12(1)).
- If the automatic check doesn't pass, a trained person on our team looks at your selfie next to your profile photos. We aim to do this within 4 hours, between 07:00 and 23:00 every day.
What we use it for, and nothing else:
- confirming you're real and that your photos are you;
- checking you look 18 or older (if you look younger, we ask for proof of age);
- helping you get back into your account if you lose access to your sign-in method and other checks fail;
- stopping people we have banned for serious harm from coming back under a new account (see section 7).
What we never do with it: show it on your profile or to other members; use it for ads; sell it; or use it to identify you anywhere outside Mudiwa.
Where it goes: our verification provider, Smile ID, processes it for us under a written contract (Act s18(4)–(5)). Smile ID may process face data outside Zimbabwe and the European Union; it is listed in section 5 and section 6.
If you don't want to do the selfie check: you can still create a profile and browse, but you won't be able to message. We require the check before messaging because it is the main way we keep fake profiles, catfishing and scams out of Mudiwa.
2.3 Location
- Your area. When you allow location, we use your phone's location to set your area (for example, "Avondale, Harare") and to work out approximate distances. We store only an approximate location, rounded to about 1 km, and never show your exact location to anyone. You can also pick your area by hand instead. We never read your location in the background.
- Check-ins. If you turn on a date check-in, we use your location only during that check-in. We share it with your trusted contact only if you miss a check-in or choose to share it yourself. It's never shown to your match.
2.4 Information about other people
- Your trusted contact. When you add a trusted contact, you give us their name and number. We only use it to send them your date plan or a missed check-in alert. The first message they get explains who we are and how to stop future messages. Please tell them before you add them.
- Your match, when you share a date. When you use Share my date, your trusted contact receives your match's first name, one profile photo, the place and the time, but never their email address or other contact details.
- Invites. If you invite friends, you share an invite link yourself (for example, in a chat app). We don't access your phone contacts.
2.5 Information collected automatically
| What | Why |
|---|---|
| Device information (model, operating system, app version, a device identifier) | To make the app work on your phone, fix bugs, and stop banned people returning on the same device |
| Log and security data (sign-in times, IP address, failed code attempts) | To keep accounts secure and stop fraud and abuse |
| How you use the app (for example, screens opened, likes sent, data used per session) | To improve Mudiwa, measure whether it's working, and show you your data use. We look at this mostly in aggregate. |
| Push notification token | To send notifications. Lock-screen notifications never include message content. |
We don't use advertising trackers and we don't sell data to data brokers. Our analytics (PostHog) and crash reports (Sentry) are hosted in the European Union and listed in section 5. Our website does not use advertising cookies.
2.6 What we don't collect
- We don't ask for your sexual orientation or show it anywhere.
- We don't ask for your religion, tribe, political views or HIV status. If you choose to mention something like this in a prompt, it becomes visible to people who view your profile, so please think before you share.
- We don't access your contacts, photo gallery (except photos you pick), microphone (except while recording a voice note) or camera (except while taking a photo or selfie).
3. The legal basis we rely on: your written consent
The Act says we may only process sensitive data if you've given consent in writing (s11(1)), and biometric data only with consent in writing (s12(1)). Because almost everything on a dating profile is sensitive, consent is the main basis for what we do.
How we ask. During sign-up, before you enter any sensitive details or take your selfie, we show a consent screen with three separate ticks:
- Your profile and dating details: using your gender, age, dating preferences, photos and other profile details to show you to other members and suggest matches.
- Your selfie check (biometric data): creating a face template from your selfie to confirm you're real, match your photos and check your age.
- Hosting in the European Union: storing and processing your data on secure servers in the European Union (Frankfurt, Germany).
Nothing is pre-ticked. Each tick has a "Why we ask" link explaining it in plain words. Ticks 1 and 3 are needed to use Mudiwa at all. Tick 2 is needed before you can message.
How we record it. For each tick, we keep a record of: your account; which consent; the exact wording version you saw; the date and time; the app version and device; and whether you gave or withdrew it. You can see your consent history in Settings → Consents & my data, and it's included in your data download. This record is your consent in writing.
Other bases we rely on, for limited things:
- Legal obligations. For example, reporting a breach to the regulator, responding to valid court orders, and keeping records the law requires (Act s10(3)(b); s11(5)(d)).
- Protecting someone's life or safety. For example, an urgent threat to a member (Act s10(3)(c); s11(5)(b); s12(3)(e)–(f)).
- Legal claims. Keeping evidence for a dispute or investigation (s11(5)(e); s12(3)(h)).
- Our legitimate interests, for non-sensitive data only. For example, security logs and fraud prevention (s10(3)(e)).
4. Automated tools and decisions
We use automated tools to help keep Mudiwa safe:
- Selfie check (see 2.2);
- Photo screening on your phone that blurs likely-explicit photos in chat and stops likely-explicit profile photos from being added. The check runs on the phone, so the photo is not sent to a third party to be checked;
- Scam and money-request detection in chats (in English to start), which shows you a gentle warning;
- Spam and fake-account signals.
A person makes the decision before any ban for a rule break. Automated tools can show warnings, blur photos or put something in a queue for review. They don't ban you on their own. You have the right not to be subject to a decision based solely on automated processing that significantly affects you (Act s25).
To detect scams, our systems process the text of messages. Your messages are encrypted in transit and when stored, but they are not end-to-end encrypted. This is so our safety tools can work and our team can review messages that are reported. Our team only reads messages when they are reported to us, when our systems flag a serious risk, or when the law requires.
5. Who we share your data with
Other members see your profile: first name, age, photos, prompts, interests, area or approximate distance, what you're looking for, and your verified badge. They never see your email address, selfie, exact location, birthday or who you've liked (only the person you liked sees your like).
Service providers (data processors). We use trusted companies to run Mudiwa. Each one is bound by a contract or terms with us that require it to keep your data secure and use it only to provide its service to us (Act s17, s18(4)–(5)).
| What they do | Where they process | Provider |
|---|---|---|
| Our main database, sign-in and chat delivery, and backups | European Union (Frankfurt, Germany) | Supabase (on AWS eu-central-1) |
| Photo and voice-note storage, and serving photos to the app | Stored in the European Union (EU jurisdiction restriction). Photos are served through Cloudflare's global network, which may keep short-lived cached copies at data centres near you (for example Johannesburg) so they load quickly | Cloudflare R2 |
| Sign-in with your Google account (only if you choose "Continue with Google") | Google's global network. Google tells us your email address and that it is verified; we do not receive your Google password | |
| Sending the sign-in code emails | European Union | Brevo |
| Our website and the tools our team uses to run Mudiwa | Vercel's global network | Vercel |
| Selfie and age check | May be outside Zimbabwe and the European Union | Smile ID |
| Push notifications. Receives your device token and the notification text (lock-screen notifications never include message content) | Global | Expo push service, Google Firebase Cloud Messaging (Android), Apple Push Notification service (iPhone) |
| Messages to your trusted contact (date plans and check-in alerts) | Depends on the messaging service used, which may be outside Zimbabwe and the European Union | Our messaging service providers |
| Analytics | European Union (Frankfurt, Germany) | PostHog (EU Cloud) |
| Crash and error reports | European Union (Frankfurt, Germany) | Sentry (EU region) |
Law enforcement and courts. We only share data with the police or other authorities when there's a valid legal order under Zimbabwean law (for example, a magistrate's order under the Criminal Procedure and Evidence Act [Chapter 9:07]), or in a genuine emergency where someone's life is at risk. We share only what is needed. Our Law Enforcement and Data Requests policy explains this in full.
Reporting illegal content. If we become aware of child sexual abuse material or other clearly illegal content, we will remove it and tell the police (the Zimbabwe Republic Police), as the law expects of hosting providers.
If Mudiwa is sold or restructured, your data may pass to the new owner, who must keep protecting it under this policy and the law. We'll tell you in the app first and you'll be able to delete your account before the change.
We never sell your data and we never share it with advertisers.
6. Hosting in the European Union, and other countries (cross-border transfer)
Mudiwa is made for people in Zimbabwe, but our main servers are in the European Union, in Frankfurt, Germany. That means your data is transferred outside Zimbabwe.
- Why the European Union? The EU's General Data Protection Regulation (GDPR) is one of the strongest data protection laws in the world, with independent regulators. Servers in Frankfurt are reliable and fast enough for Zimbabwean networks.
- What's kept there. Our main database, sign-in and chat (Supabase), our analytics (PostHog) and crash reports (Sentry) are in Frankfurt. Photos and voice notes are stored in the EU (Cloudflare R2, with an EU-only storage restriction). Sign-in emails are sent from the EU (Brevo).
- Photos cached near you. To make photos load quickly, Cloudflare's global network may keep short-lived copies at a data centre close to you (for example Johannesburg). The original stays stored in the EU.
- Adequate protection. The Act allows transfers to a country that ensures an adequate level of protection (s28(1)). We assessed this using the factors in s28(2): the type of data, purpose, how long it's kept, the recipient, the law in Germany and the EU (including the GDPR and its independent regulators), and the providers' security measures. Some of our providers are headquartered in the United States but store our data in the EU and are bound by data-protection terms.
- Your consent as well. We also ask for your unambiguous consent to this hosting (tick 3), which the Act allows (s29(a)).
- Other countries. A few service providers in section 5 may handle limited data in other countries: Google, when you sign in with Google (your email address); the push notification services of Expo, Google and Apple (your device token and notification text); Vercel (our website and team tools); the messaging service that delivers messages to your trusted contact (their number and the message); and Smile ID (your selfie check). We share only what each one needs to do its job.
- Same duty wherever it goes. Every provider is bound by a contract or terms with security and confidentiality duties.
7. How long we keep your data
We keep data only as long as we need it (Act s7(1)(c), s13). The Act doesn't set fixed periods, so these are the periods Mudiwa applies:
| Data | How long we keep it | Why |
|---|---|---|
| Profile (name, age, gender, preferences, photos, prompts) | While your account is open. On deletion: hidden immediately, erased within 30 days | To run your profile |
| Messages, voice notes and photos in chat | While the chat is open. When a chat ends (an unmatch, or either person deletes their account), it disappears from view straight away and its files and text are erased after 90 days, unless held for a report | So you can still raise a report about a recent chat, and so we can deliver the conversation |
| Raw selfie images | Deleted 30 days after the check is decided (approved or rejected), or at once if you withdraw selfie consent | To allow human review and appeals |
| Face template (biometric) | While your account is open. Erased within 30 days of deleting your account or withdrawing selfie consent, except as below for banned accounts | For verification |
| Proof-of-age documents | Deleted within 30 days of the decision. We keep only the result ("age confirmed 18+") | To confirm age |
| Approximate location | While your account is open; replaced each time it updates | For Discover |
| Check-in location | A missed check-in's approximate location is deleted after 30 days. Alert records are deleted after 30 days | For your safety |
| Trusted contact details | Until you remove them or delete your account | For safety features |
| Consent records | For the life of your account plus 3 years | To prove we had your consent |
| Reports, evidence and enforcement records (including the reported messages) | 1 year after the case is closed. Longer if needed for a court case or police investigation | To keep members safe and handle appeals or legal claims |
| Banned for serious harm (for example violence, child safety, intimate images without consent, sex for money, fraud) | A minimal record (protected identifiers, reason code and date) and the related evidence, kept for up to 6 years | To stop the person returning, and for the safety of other members |
| Security and sign-in logs | Up to 90 days | Security and fraud prevention |
| Support messages | 12 months after the last message | To help you and improve support |
| Staff activity records (who looked at what) | 1 year | Accountability |
| Downloads of your data | The download link and file are deleted after 7 days | So your copy is not left lying around |
| Backups | Rolling, overwritten within 35 days | Disaster recovery |
Deleted means deleted. When data is erased, it's removed from our live systems and drops out of backups within 35 days.
8. How we keep your data safe
We take appropriate technical and organisational measures to protect your data (Act s18). These include:
- encryption in transit (TLS) and at rest;
- extra protection and restricted access for face templates, proof-of-age documents and location history;
- email addresses stored separately from profiles, and never shown to members;
- row-level security in our database, so a member can only read what they are allowed to;
- access limited to staff who need it, with individual sign-ins, two-step verification and an audit log of who viewed what;
- confidentiality for everyone who helps us run Mudiwa;
- regular security checks, and a plan to restore service and data after an incident.
If there's a data breach
- We'll notify the regulator (POTRAZ) within 24 hours of becoming aware of any security breach affecting your data (Act s19).
- If the breach is likely to put your rights and freedoms at high risk, we'll tell you without delay, in the app and by email, explaining what happened and what you can do.
- We keep a record of all breaches and cooperate with the regulator's investigation.
9. Your rights, and how to use them
Under the Act (s14, s25) you have the right to:
| Your right | What it means | How to use it on Mudiwa |
|---|---|---|
| Be informed | Know how your data is used | This policy, plus "Why we ask" in the app |
| Access | Get a copy of your data | Settings → Consents & my data → Download my data. We deliver it within 7 days (we aim for 48 hours) as a secure download link that expires after 7 days. Free. |
| Correct | Fix false or misleading data | Edit your profile any time, or ask us to fix anything you can't edit |
| Delete | Have false or misleading data deleted (Act s14(e)), and, on Mudiwa, delete your whole account | Settings → Account → Delete account. Profile hidden immediately; data erased within 30 days except the limited records in section 7 |
| Object | Object to all or part of how we use your data | Email us (section 1) |
| Withdraw consent | Withdraw any consent at any time, without giving a reason, for free (Act s11(2), s12(2)) | Settings → Consents & my data. See below for what happens |
| Human review | Not to be subject to decisions based solely on automated processing that significantly affect you (s25) | Every ban is decided by a person, and you can appeal in the app |
| Complain | Complain to the regulator | POTRAZ (the Postal and Telecommunications Regulatory Authority of Zimbabwe), the Data Protection Authority under the Act. Contact details are on potraz.gov.zw |
What happens when you withdraw consent:
- Profile and dating details (tick 1): we can't run a dating profile without this. Your profile is hidden straight away and we'll help you delete your account.
- Selfie check (tick 2): your face template is erased within 30 days, you lose your "Photo verified" badge, and messaging is locked again. You can keep your profile and browse.
- Hosting in the European Union (tick 3): we can't provide Mudiwa without hosting, so your profile is hidden and we'll help you delete your account.
Withdrawing doesn't affect what we did lawfully before you withdrew.
Other ways to ask. If you can't use the app, email us (section 1) from the email address on your account. We may need to confirm it's really you before we act. We respond to requests within 30 days at most, and usually much faster. We don't charge for requests.
10. Children
Mudiwa is only for adults aged 18 and over. The Act defines a child as anyone under 18 (s3), and children's data needs a parent's or guardian's consent (s26), which doesn't fit a dating app. So:
- we check date of birth at sign-up and estimate age during the selfie check;
- anyone who looks under 18 is paused and asked for proof of age;
- reports of a possible minor are treated as urgent and reviewed within 2 hours (during review hours 07:00–23:00);
- if we find an account belongs to someone under 18, we close it and delete their data, keeping only a minimal record to stop them from re-joining until they turn 18.
If you think a child is using Mudiwa, please report the profile in the app or email us (section 1).
11. Ads: not active
There are no ads in this version of Mudiwa. If we introduce ads, we'll update this policy and tell you in the app before they start.
When ads start, we commit to the following:
- Ads will only be targeted by city and age band.
- We will never use your dating intentions, relationship status, who you want to meet, religion, health or any other sensitive data to target or measure ads.
- We won't share your personal data with advertisers.
- You'll be able to turn off marketing messages at any time.
12. Payments: not active
There are no payments in this version. When paid features start, we'll update this policy to explain what payment data we collect (for example, transaction reference, amount and date). We'll never store full card numbers or mobile-money PINs.
13. Changes to this policy
If we change this policy, we'll update the version number and date. For important changes, especially any new use of sensitive data, we'll tell you in the app before the change and ask for your consent again where the law requires it.
14. Contact us
- Email: kudzilenett@gmail.com
- In the app: Settings → Help → Contact us
- Regulator: POTRAZ (Data Protection Authority), potraz.gov.zw